# EPIC HL7 v2 + FHIR configuration

**URL:** https://openhealthhub.org/t/epic-hl7-v2-fhir-configuration/2908
**Category:** FHIR
**Created:** [8 January 2026 16:57 UTC](https://openhealthhub.org/t/epic-hl7-v2-fhir-configuration/2908 "2026-01-08T16:57:55Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![mayfield.g.kev](https://openhealthhub.org/user_avatar/openhealthhub.org/mayfield.g.kev/32/648_2.png) [@mayfield.g.kev](https://openhealthhub.org/u/mayfield.g.kev)
#### Post date: [8 January 2026 16:57 UTC](https://openhealthhub.org/t/epic-hl7-v2-fhir-configuration/2908/1 "2026-01-08T16:57:55Z")

</div>

Has anyone had any experience of doing this in the UK?

I’m working for new style regional diagnostics organisation (name will be NHS NW Genomics from April) - we will need to extend the data models in both HL7 v2 and FHIR for enterprise rather than point to point use.

I believe we are the first to attempt this in the UK (xlabs/npex may have done so for laboratory), so not expecting many/any answers 🙂  
I’m starting with EPIC as it has quite good documentation (and a local NHS Trust is using EPIC as it’s EPR). Will be wanting to move onto meditech afterwards.

The proposed change is being worked on but can be found here [Correlation Identifier - NHS North West Genomics v0.1.0](https://nw-gmsa.github.io/StructureDefinition-CorrelationIdentifier.html)  
This relates to FHIR Identifiers and V2 EI and CX datatypes - I’m calling it a data contract as it crosses standards (and also spread into IHE XDS).