BEKHealth website screenshot

BEKHealth

BEKhealth is a clinical research technology company whose BEKplatform applies a BERT-based deep-learning model to structured and unstructured electronic health record data — physician notes, pathology reports, clinical endpoints — to power trial feasibility, patient matching and research-grade real-world data for sponsors, CROs and research site networks. The company markets 25+ proprietary EHR adapters reaching roughly 80% of the EHR market (Epic, Cerner, athenahealth, NextGen, eClinicalWorks, Veradigm, Greenway, ModMed, DrChrono, Elation, AdvancedMD, Flatiron, OpenEMR and others), a longitudinal patient graph mapped to an ontology of more than 24 million clinical terms, and the BEKnetwork of 200+ research sites covering 30M+ patient records. Delivery is enterprise SaaS — sold direct and through AWS Marketplace, and embedded in partner platforms such as CRIO eSource/CTMS. BEKhealth operates a documentation portal at docs.bekhealth.com and an Auth0 OpenID Connect issuer at auth.bekhealth.com, but publishes no public developer portal, API reference or machine-readable specification; the documented route to the platform is a demo request and a contracted onboarding with BAAs and DUAs.

BEKHealth is profiled on the APIs.io network. Tagged areas include Company, Healthcare, Clinical Trials, Clinical Research, and Electronic Health Records.

BEKHealth’s developer surface includes engineering blog, support, pricing, FAQ, authentication, and 17 more developer resources.

26.9/100 emerging ▬ flat Agent 9/100 agent aware Full breakdown ↓
scored 2026-08-17 · rubric v0.11.0
0 APIs
CompanyHealthcareClinical TrialsClinical ResearchElectronic Health RecordsReal World DataArtificial IntelligencePatient RecruitmentLife SciencesHealth Data

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0
Composite quality — 26.9/100 · emerging
Contract Quality 0.0 / 21
Developer Ergonomics 3.0 / 17
Commercial Clarity 8.9 / 17
Operational Transparency 0.0 / 11
Governance 1.3 / 10
Discoverability 4.9 / 9
Regulatory Posture 8.8 / 15
Agent readiness — 9/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 10
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Regulatory Posture applies to this provider. Its tags matched the Health regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/bekhealth: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Bekhealth Authentication

2 schemes

SECURITY

Bekhealth Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Bekhealth Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Get Started 1

Portal, sign-up, and the first successful call

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Access & Security 4

Authentication, authorization, and security posture

Operate 3

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 4

The organization behind the API

Other 4

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: bekhealth
name: BEKHealth
description: BEKhealth is a clinical research technology company whose BEKplatform applies a BERT-based deep-learning model
  to structured and unstructured electronic health record data — physician notes, pathology reports, clinical endpoints —
  to power trial feasibility, patient matching and research-grade real-world data for sponsors, CROs and research site networks.
  The company markets 25+ proprietary EHR adapters reaching roughly 80% of the EHR market (Epic, Cerner, athenahealth, NextGen,
  eClinicalWorks, Veradigm, Greenway, ModMed, DrChrono, Elation, AdvancedMD, Flatiron, OpenEMR and others), a longitudinal
  patient graph mapped to an ontology of more than 24 million clinical terms, and the BEKnetwork of 200+ research sites covering
  30M+ patient records. Delivery is enterprise SaaS — sold direct and through AWS Marketplace, and embedded in partner platforms
  such as CRIO eSource/CTMS. BEKhealth operates a documentation portal at docs.bekhealth.com and an Auth0 OpenID Connect issuer
  at auth.bekhealth.com, but publishes no public developer portal, API reference or machine-readable specification; the documented
  route to the platform is a demo request and a contracted onboarding with BAAs and DUAs.
image: https://www.bekhealth.com/wp-content/uploads/2025/02/BEKhealth_Logo-1.webp
url: https://raw.githubusercontent.com/api-evangelist/bekhealth/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.20'
created: '2026-08-06'
modified: '2026-08-06'
tags:
- Company
- Healthcare
- Clinical Trials
- Clinical Research
- Electronic Health Records
- Real World Data
- Artificial Intelligence
- Patient Recruitment
- Life Sciences
- Health Data
apis: []
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: DomainSecurity
  url: security/bekhealth-domain-security.yml
- type: Website
  url: https://www.bekhealth.com/
- type: Blog
  url: https://www.bekhealth.com/clinical-research-blog/
- type: Support
  url: https://www.bekhealth.com/contact/
- type: Contact
  url: https://www.bekhealth.com/contact/
- type: Pricing
  url: https://www.bekhealth.com/pricing-roi/
- type: TermsOfService
  url: https://www.bekhealth.com/terms-and-conditions/
- type: PrivacyPolicy
  url: https://www.bekhealth.com/privacy-policy/
- type: Login
  url: https://auth.bekhealth.com/
- type: Integrations
  url: https://www.bekhealth.com/partners/
- type: KnowledgeBase
  url: https://www.bekhealth.com/ehr-library/
- type: Press
  url: https://www.bekhealth.com/news/
- type: FAQ
  url: https://www.bekhealth.com/frequently-asked-questions/
- type: Marketplace
  url: https://aws.amazon.com/marketplace/pp/prodview-kmhelvjo5koma
- type: LinkedIn
  url: https://www.linkedin.com/company/14836396/
- type: SecondaryMarket
  url: https://forgeglobal.com/bekhealth_stock/
- type: LLMsTxt
  url: llms/bekhealth-llms.txt
- type: WellKnown
  url: well-known/bekhealth-well-known.yml
- type: Authentication
  url: authentication/bekhealth-authentication.yml
- type: OpenIDConnect
  url: authentication/bekhealth-authentication.yml
- type: OAuthScopes
  url: scopes/bekhealth-scopes.yml
- type: Conformance
  url: conformance/bekhealth-conformance.yml
- type: Compliance
  url: conformance/bekhealth-conformance.yml
x-enrichment:
  date: '2026-08-06'
  status: minimal
  artifacts_added: 8
  pass: local-v1
x-coverage:
  state: gated
  reason: customer-only-docs
  detail: BEKhealth runs a real documentation portal at docs.bekhealth.com, but every path on it — the root, /openapi.json,
    /llms.txt, even /.well-known/agent-card.json — returns a 302 into the company's Auth0 tenant at auth.bekhealth.com, so
    the contract is readable only by an existing customer with a signed BAA/DUA; nothing on the public marketing site names
    an API at all.
  evidence:
  - url: https://docs.bekhealth.com/
    status: 302
  - url: https://docs.bekhealth.com/openapi.json
    status: 302
  - url: https://api.bekhealth.com/openapi.json
    status: 404
  - url: https://www.bekhealth.com/.well-known/agent-card.json
    status: 404
  - url: https://www.bekhealth.com/llms.txt
    status: 200
  - url: https://auth.bekhealth.com/.well-known/openid-configuration
    status: 200
  checked: '2026-08-06'