Introduction

The Generic FHIR Receiver is a component which will receive messages to the GP Practice which are:

• Delivered using Messaging Exchange for Social Care and Health (MESH).

• Structured using FHIR STU3 messages.

• Which meet the ITK3 specification.

The Generic FHIR Receiver will obtain messages from the MESH Client or API depending on the Workflow ID within the MESH message header.

Various types of messages are received into GP Practices via MESH; some other component (referred to in the documentation as a Message Distributor) will usually handle all the incoming messages for the Practice MESH "mailbox", and distribute them to the appropriate handler for processing according to a workflow identifier and/or other metadata in the MESH header. The Generic FHIR Receiver will, therefore, receive its messages from this Message Distributor.

In summary, the responsibilities of the Generic FHIR Receiver are:

• Receive incoming ITK3 FHIR messages.

• Verify the message is a well-formed XML.

• Verify the message is a valid FHIR message conforming to the ITK3 specification.

• Match the message subject to a known Patient.

• Send Infrastructure and Business Acknowledgement messages (which are also FHIR messages which conform to the ITK3 specification) where these have been requested. 

• Raise workflow tasks as appropriate using the data in the payload.

Requirements

Generic FHIR Receiver background and requirements:

Open

Compliance, Assurance and Testing

See the Generic FHIR Receiver section on Onboarding Overview of the Digital Care Services Interoperability Standards and Requirements.

Dependencies

Roadmap

Items on the Roadmap which impact or relate to this Standard