NHS North West Genomics
2.0.9 - ci-build United Kingdom flag

NHS North West Genomics - Local Development build (v2.0.9) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

Architecture - Enterprise Integration Patterns (EIP)

graph TD;


DocumentMessaging["<b>Document Messaging</b><br/><b>Laboratory Testing Workflow (LTW)</b><br/><br/>e.g. V2 Messaging (ORU_R01, MDM_T02, ORM_O01, OML_O21, etc) and FHIR Messaging/Transactions"]
DocumentSharing["<b>Document Sharing/<br/>EURIDICE Document Exchange</b><br/><br/>e.g. IHE XDS (SOAP API), IHE MHD and NHSE NRL (FHIR RESTful API) "]

DocumentEventNotifications[<b>Document Event Notifications</b><br/><br/>e.g. NHSE MNS and IHE DSUBm]
ClinicalDocumentArchitecture[<b>Clinical Document Architecture</b><br/><br/>e.g. CDA, FHIR Document<br/>EU Laboratory Report<br/>International Patient Summary] 
DocumentWorkflow[<b>Document Workflow</b><br/><br/>e.g. IHE XDW]

DataSharig["<b>Data/Resource Sharing<br/>EURIDICE Resource Exchange</b><br/><br/> HL7 IPA/IHE QEDm, NHS England Care Connect API (FHIR RESTful API)"]
ResourceEventNotifications[<b>Resource Event Notifications</b><br/><br/>e.g. FHIR Subscription]
ConversationalMessaging[<b>Conversational Workflow</b><br/><br/>e.g. FHIR Workflow, NHSE Electroinc Prescription Service and Genomic Order Management System]


DocumentMessaging --> DocumentSharing
DocumentSharing --> DocumentEventNotifications
DocumentSharing --> ClinicalDocumentArchitecture
DocumentEventNotifications --> DocumentWorkflow
ClinicalDocumentArchitecture --> DocumentWorkflow

DocumentMessaging --> DataSharig
DataSharig --> ResourceEventNotifications
ResourceEventNotifications --> ConversationalMessaging

DocumentSharing --> |expands to| DataSharig
DocumentEventNotifications --> |expands to| ResourceEventNotifications

classDef green fill:#D5E8D4;

class DocumentMessaging,DocumentSharing,DataSharig green

This diagram provides a high-level view of enterprise interoperability across the NHS. Most NHS Trusts have implemented some form of Document Messaging, typically through HL7 v2 messaging and, increasingly, FHIR-based transactions.

Many Shared Care Record providers (including the former LHCREs) have also established Document Sharing capabilities. Examples include One London, Lancashire & South Cumbria, and Cheshire & Merseyside, enabling clinical documents to be exchanged and consumed across organisational boundaries.

Several regions have progressed further by implementing Data/Resource Sharing in addition to document sharing. Examples include the Yorkshire & Humber Care Record, SiDER, and the Great North Care Record. These initiatives support the exchange of structured clinical data through APIs and shared resource models, moving beyond traditional document-centric interoperability.

Collectively, these Shared Care Record platforms are likely to form a significant foundation for the emerging Single Patient Record (SPR) landscape.

As a newly established diagnostic organisation (April 2026), we have already implemented all three interoperability layers—Document Messaging, Document Sharing, and Data/Resource Sharing—building upon capabilities developed prior to our formal establishment.

Our strategic ambition is to progress towards Conversational Messaging, which aligns with the direction being taken by national diagnostic services such as the Genomic Order Management Service (GOMS). Conversational Messaging supports structured request-response interactions between systems that mirror real-world business processes (for example, "Can you fulfil this request?" followed by an acceptance, rejection, or request for further information), enabling more dynamic and workflow-oriented interoperability.

Realising this model depends on widespread adoption of Data/Resource Sharing through capabilities such as the Single Patient Record (SPR) and FHIR APIs, together with national eventing services such as the NHS Multicast Notification Service (MNS). Without these foundations, organisations typically revert to point-to-point HL7 v2 messaging or FHIR transaction and bundle patterns, which are less effective for coordinating complex, multi-organisational workflows.

Importantly, both Document Messaging and Conversational Messaging are likely to play a role in addressing the "write-back" challenge frequently discussed in relation to SPR. Document Messaging provides a proven mechanism for distributing updates to consuming systems, whilst Conversational Messaging offers a more sophisticated approach for coordinating actions, acknowledgements, and workflow state changes across organisational boundaries.

Genomic Enterprise Integration

Genomic Enterprise Integration


Document Messaging

This basic patten is the exchange of records via Document Messaging and is supported by a wide area of Messaging Patterns In NHS Trusts this is often supported by a Trust Integration Engine.

graph LR;

    s[Data Source]
 

    d[Data Consumer]

s --> |v2 Message<br/>FHIR Message<br/>FHIR Transaction| d 


Example - Laboratory Testing Workflow

Is based on Document Messaging and two flows are combined to create a workflow e.g. IHE Laboratory Testing Workflow (LTW)

graph LR;

 subgraph s[Order Placer];
    EPR
 end

subgraph d[Order Filler];
    LIMS
end

EPR --> |LAB-1 Laboratory Order OML_O21/ORM_O01| LIMS
LIMS -->  |LAB-3 Laboratory Report ORU_R01| EPR


Document Sharing

Document Messaging main limitation is it is between two parties, often in health care many other practitioners are involved. Messaging can be used to solve this but it begins to have scaling and data concurrency issues.

graph LR;

    s[Document Consumer]
    d[Document Registry & Repository]

s --> |Query API<br/>XDS API<br/>FHIR RESTful| d 


Example - Document Exchange

See also Health Information Exchange - Document Exchange

graph LR;

    s[Document Consumer]
    
    subgraph d[Document Registry & Repository];
        Registry
        Repository
    end

s --> |Find Document References ITI-67 FHIR RESTful<br/>Registry Stored Query ITI-18| Registry
s --> |Retrieve Document ITI-68<br/>Retrieve Document Set ITI-41| Repository

Example - NHS England National Record Locator

See NHS England National Record Locator

Example - Cross Enterprise Document Sharing Laboratory

Electronic Document Management (EDM) is a common practice for storing and sharing documents across healthcare systems and common formats for the documents are often PDF. In diagnostics this is not desirable and so instead a document format called Clinical Document Architecture (CDA), in HL7 FHIR this is known as FHIR Document

This is described in [IHE https://wiki.ihe.net/index.php/Sharing_Laboratory_Reports](https://wiki.ihe.net/index.php/Sharing_Laboratory_Reports HL7 Europe Laboratory Report, NHS England Pathology is a based on this but it using Document Messaging, the EU is likely to use Document Sharing.

Document Event Notifications

Prerequisite is Document Sharing

graph LR;


Publisher[Document Notification Publisher]
Broker[Document Notification Broker]
Subscriber[Document Notification Subscriber]
Recipient[Document Notification Recipient]

Publisher --> |Event Publish| Broker
Subscriber --> |Event Subscription| Broker
Broker --> |Event Notify| Recipient

Example - Multicast Notifcation Service

See NHS England Multicast Notification Service API

Example - Document Subscription for Mobile (DSUBm)

See IHE Document Subscription for Mobile (DSUBm)

Data Sharing

Can be considered an extension of Document Sharing where the data contained in the documents is queryable. This data is known as Resources and is related to Segments used in HL7 v2 Messaging.

This is the most common use of HL7 FHIR.

graph LR


provider[Resource Access Provider<br/><br/>Genomic Data Platform]
consumer[Resource/Data Consumer]

consumer --> |Request Resources| provider
provider --> |Respond| consumer

Example - Resource Exchange

See also Health Information Exchange - Resource Exchange

Resource Event Notifications

Prerequisite is Data Sharing

graph LR;


Publisher[Resource Notification Publisher]
Broker[Resource Notification Broker]
Subscriber[Resource Notification Subscriber]
Recipient[Resource Notification Recipient]

Publisher --> |Event Publish| Broker
Subscriber --> |Event Subscription| Broker
Broker --> |Event Notify| Recipient

Event Messaging

Placeholder for MNS discussion

sequenceDiagram



participant OrderPlacer

participant OrderFiller

note over OrderPlacer,OrderFiller: LAB-1 Laboratory Order

OrderPlacer -->> OrderPlacer: Share Laboratory Order via Resource Access Provider

OrderPlacer -->> OrderFiller: Event Notification

OrderFiller -->> OrderPlacer: Retrieve Resources or Document

note over OrderPlacer,OrderFiller: LAB-3 Laboratory Report

OrderFiller -->> OrderFiller: Perform Test and share Laboratory Report via Resource Access Provider
OrderFiller -->> OrderPlacer: Event Notification
OrderPlacer -->> OrderFiller: Retrieve Resources or Document
``

## Conversational Messaging (Resource/Data)

See [Conversation Patterns](https://www.enterpriseintegrationpatterns.com/patterns/messaging/Conversation.html)
For a FHIR implementation see [FHIR Worfklow](https://hl7.org/fhir/R4/workflow.html)

This is a replacement for [Document Messaging](#document-messaging) (i.e. HL7 v2, FHIR Messaging and FHIR Transaction)

Prerequisite is [Data Sharing](#data-sharing) and [Resource Event Notifications](#resource-event-notifications-), [polling](https://www.enterpriseintegrationpatterns.com/patterns/messaging/PollingConsumer.html) can be used as an interim measure if event notification infrastructure is not available.

```mermaid
sequenceDiagram 

 

participant OrderPlacer

participant OrderFiller

note over OrderPlacer,OrderFiller: LAB-1 Laboratory Order

OrderPlacer -->> OrderPlacer: Share Laboratory Order via Resource Access Provider

OrderPlacer -->> OrderFiller: Task Event Notification (Task status = requested) 

OrderFiller -->> OrderPlacer: Retrieve Laboratory Order

alt accepted
OrderFiller -->> OrderPlacer: Task Event Notification (Task status = accepted) 
note over OrderPlacer,OrderFiller: LAB-3 Laboratory Report
OrderFiller -->> OrderFiller: Perform Test and share Laboratory Report via Resource Access Provider
OrderFiller -->> OrderPlacer: Task Event Notification (Task status = completed) 
OrderPlacer -->> OrderFiller: Retrieve Laboratory Order
else rejected
OrderFiller -->> OrderPlacer: Task Event Notification (Task status = rejected) 
else other
alt Exception Order Filler initiated
OrderFiller -->> OrderPlacer: Task Event Notification (Task status = rejected/cancelled) 
else Exception Order Placer initiated
OrderPlacer -->> OrderFiller: Task Event Notification (Task status = rejected/cancelled) 
end
end

Example - NHS England Genomic Order Management System

See NHS England Genomic Order Management System

Example - HL7 AU eRequesting

See AU eRequesting Implementation Guide

Example - NHS England Electronic Prescription Service

See NHS England Electronic Prescription Service - Dispensing

Conversational Messaging (Document)

Example - IHE Cross-Enterprise Document Workflow Content Profile (XDW)

See Cross-Enterprise Document Workflow Content Profile (XDW)