Connect to your EHR

Send Ovok data to a hospital's EHR or clinical information system over FHIR or HL7 v2.

Connect your project to a hospital's EHR or clinical information system (CIS), so readings and results reach the system clinicians already use.

The path depends on what the hospital system speaks.

The hospital systemPathStart here
A FHIR-native EHRUse the FHIR R4 API directly.FHIR-native EHRs
An HL7 v2 system, which is most hospital CISMake an Ovok HL7 connection.Connect over HL7 v2

FHIR-native EHRs

A FHIR-native EHR needs no connection object. It calls the same FHIR R4 API as your own apps.

TaskHowPage
Sign inCreate an admin application and exchange its id and secret for a token with client_credentials at POST /oauth2/token.Authenticate
Pull what changedSearch with _lastUpdated=gt<timestamp>.Queries and pagination
Pull everythingStart a bulk $export: NDJSON files, with _since for increments.Export system data
Receive changesCreate a Subscription with a rest-hook channel. Each delivery is signed in X-Signature.Subscription
Write into OvokPut the hospital's MRN in Patient.identifier and use a conditional create, so a patient is never created twice.Patient

HL7 v2 hospital systems

Most hospital CIS take HL7 v2 over MLLP, often behind an interface engine. An Ovok HL7 connection sends each new Observation as an HL7 v2 ORU^R01 message in the IHE PCD-01 profile.

  • Codes: IEEE 11073 MDC, LOINC or SNOMED CT. Units: UCUM.
  • A small HL7 agent runs inside the hospital network and opens an outbound connection to Ovok. The hospital opens no inbound port.
  • A connection is one form in the Console or one API call. No code per hospital.

Pages in this guide

  1. Connect over HL7 v2: make the connection, install the agent, test and go live.
  2. HL7 message reference: what is sent, what is skipped, acknowledgements, retries and resends.
  3. Troubleshooting HL7 connections: the usual failures and what to do.

See also

Last updated on

On this page