UKCore Hackathon Supporting Guide

This guidance is under active development by NHS England and content may be added or updated on a regular basis.

Share Clinical Document plus Notifications

Pattern

Builds on both Traditional Document Exchange and Share Clinical Documents and adds event notification feeds to interested parties.

Document and Document Metadata are shared via open api’s. The document metadata is used to query for patient patient documents

mhd

Pros

  • Builds on widespread existing support for patient admissions and discharges in acute trusts.
  • Can be extended to feed a Master Patient Index (MPI)
  • Extends patient admission and discharge notifications from acute only to primary, mental health and social care.
  • Can be used to send practitioner or patient notifications using Alerts

Cons

  • Makes use HL7 v2 standard, however it is believed this can be converted to FHIR
  • HL7 v2 ADT standardisation is not widespread. If HL7 v2 is chosen, it is recommended HSCIC ITK - HL7v2 Interoperability Message Specification is used as this has similar data model to UKCore-Patient and UKCore-Encounter.

FHIR Technical Framework Options

This is a topic for discussion. It is likely suggestions here include FHIR Message and FHIR RESTful. HL7 mappings of HL7 v2 to FHIR favour the use of FHIR Messaging or Transactions.

However the use of identifiers (NHS Number, ODS Codes, GMP/GMC codes, etc) in the UK would also allow a mapping to single FHIR Resource. E.g. a HL7 v2 ADT_A03/A03/A04 would map to a FHIR Encounter, HL7 v2 ADT_A28/A31 would map to a FHIR Patient.

This leads to the following interactions:

back to top