Virtually Healthcare HL7 FHIR Implementation Guide, published by Virtually Healthcare. This guide is not an authorized publication; it is the continuous build for version 0.1.0-current built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/Virtually-Healthcare/Virtually-Healthcare-FHIR-Implementation-Guide/ and changes regularly. See the Directory of published versions

Clinical Data Repository

Overview

Clinical Data Repository Interfaces Overview

Clinical Data Sharing API

The CDR Data Sharing API follows the following standards:

• UK SNOMED CT and LOINC for our clinical terminology.
• NHS Data Dictionary for identifiers and values, such as NHS Number, GMC, GMP, ODS, etc.
• HL7 UK Core
• HL7 International Patient Access Server
• IHE Query for Existing Data for Mobile (QEDm) Server
• HL7 UK - UK Core Access

Incoming Events

The following standards can be supported:

• HL7 v2 Admission, Discharge and Transfers (ADT), IHE Patient Identifier Cross-referencing (PIX) and/or IHE Patient Administration Management (PAM) following NHS England HL7 v2 (2.4) ADT Messaging Specification
• HL7 v2 Unsolicited Observations (ORU), following Digital Health and Care Wales HL7 v2 (2.5.1) ORU, UK SNOMED CT coding of OBX is preferred.
• IHE and HL7, HL7 FHIR based event notifications

Outgoing Events

The following is supported:

• Consultation write backs to EMIS and TPP via IM1

The following standards can be supported:

• HL7 v2 Admission, Discharge and Transfers (ADT), IHE Patient Identifier Cross-referencing (PIX) and/or IHE Patient Administration Management (PAM) following NHS England HL7 v2 (2.4) ADT Messaging Specification
• HL7 v2 Unsolicited Observations (ORU), following Digital Health and Care Wales HL7 v2 (2.5.1) ORU, UK SNOMED CT coding of OBX is preferred.
• IHE DSUB/DSUBm or HL7 v2 MDM
• IHE and HL7, HL7 FHIR based event notifications