This page provides a list of the FHIR artifacts defined as part of this implementation guide.

Behavior: Capability Statements

The following artifacts define the specific capabilities that different types of systems are expected to have in order to comply with this implementation guide. Systems complying with the implementation guide are expected to declare conformance to one or more of the following capability statements.

Server conformance for Diagnostic Message Handling	Server conformance for Diagnostic Message Handling
Server conformance for prescription Message Handling	Server conformance for prescription Message Handling
Server conformance for Encounter Message Handling	Server conformance for Encounter Message Handling

Behavior: Message Definitions

These define the types of messages that can be sent and/or received by systems complying with this implementation guide

Notitification Admission	Admission Notification - care provision started. FHIR equivalent of HL7v2 ADT^A01
Notitification Discharge	Discharge Notification - patient handed over. FHIR equivalent of HL7v2 ADT^A03
Diagnostic Messaging	Unsolicited transmission of an observation message. FHIR equivalent of HL7v2 ORU^R01
Patient Create	Patient Create. FHIR equivalent of HL7v2 ADT^A28
prescription-order	prescription-order
prescription-order-update	prescription-order-update

Terminology: Code Systems

These define new code systems used by systems conforming with this implementation guide

Messaging Events

NHS Greater Manchester Messaging Events

Example: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like

notification-admit	Notifiation Admission FHIR Message - Admit a patient
Notification Discharge FHIR Message	Notification Discharge FHIR Message - Discharge a patient
Patient Create FHIR Message	Patient Create FHIR Message - Add person information
NEWS2 Diagnostic Report FHIR Message Example	NEWS2 Diagnostic Report FHIR Message Example