Hekma connects to Epic, Cerner, Athena Health, and most major EHR systems using standard FHIR R4 APIs that your EHR already supports. Typical setup: 1–2 business days.
Epic FHIR R4
Read-only · Standard API
Matching scope
Diagnosis, labs, meds, procedures
Data writes
Read-only access only
PHI transmission
De-identified insights only
Setup time: 1–2 business days
IT Objection Handler
“We use Epic. Can we connect?”
Yes. Hekma is compatible with Epic FHIR R4 API layer. We use standard read-only FHIR endpoints — the same ones your health information exchanges already use. No Epic App Orchard build required for initial connectivity.
“We are on Cerner/Oracle Health.”
Yes. Cerner FHIR API supports the same read-only patient record access. Standard configuration on your Cerner admin portal.
“We use Athena Health.”
Yes. Athena open API supports FHIR-based connectivity for approved partners.
“We have a proprietary or regional EHR system.”
Contact us. We have connected to 15+ EHR systems beyond the major three. If your system has an HL7 FHIR layer or HL7 v2 interface, we can connect.
What “Connection” Means in Practice
Hekma reads specific structured data fields relevant to trial matching — diagnosis codes, lab values, medication lists, procedure history. We do not read clinical notes in their entirety, we do not write to your EHR, and we do not modify any patient record. Read-only, passive, continuous. Data never leaves your institution without a commercial transaction initiated by a pharma buyer — and even then, what leaves is a de-identified match indicator, not the patient record.
Implementation Timeline
IT team configures FHIR endpoint
Standard read-only FHIR API configuration on your EHR admin portal
Hekma platform onboarding
Hospital admin setup, trial category preferences, per-insight fee configuration
First patient matches delivered
AI begins passive matching against active pharma trials. First match reports generated.
First revenue flowing
Pharma purchases insights. Revenue flows to your institution.
No capital expenditure. No infrastructure purchase. No new headcount required.
Compliance Documentation Provided at Connection
Standard FHIR R4 connection. Read-only. No custom build. Full compliance documentation provided.