MessageHeader FHIR Resource Proposal
- 1 Message
- 1.1 Owning committee name
- 1.2 Contributing or Reviewing Work Groups
- 1.3 FHIR Resource Development Project Insight ID
- 1.4 Scope of coverage
- 1.5 RIM scope
- 1.6 Resource appropriateness
- 1.7 Expected implementations
- 1.8 Content sources
- 1.9 Example Scenarios
- 1.10 Resource Relationships
- 1.11 Timelines
- 1.12 gForge Users
Owning committee name
Infrastructure and Messaging
Contributing or Reviewing Work Groups
FMG, OO, MnM,
FHIR Resource Development Project Insight ID
Scope of coverage
A transmission requesting action on a bundle of one or more resources or a response to such a request.
This page describes how FHIR Resources can be used in a traditional messaging context, much like HL7 v2. Applications claiming conformance to this framework claim to be conformant to "FHIR messaging".
In FHIR messaging, a "request message" is sent from a source application to a destination application when an event happens. Events mostly correspond to things that happen in the real world. The request message consists of a bundle of resources, with the first resource in the bundle being this Message resource. The Message resource has a code - the message event - that identifies the nature of the request message and carries additional request metadata. The other resources in the bundle depend on the type of the request.
The events supported in FHIR, along with the resources that are included in them, are defined below.
The destination application processes the request and returns one or more response messages which are also a bundle of resources, with the first resource in the bundle being a Message resource with a response section that reports the outcome of processing the message and any additional response resources required.
Detailed message resource mappings can be found at: http://www.hl7.org/implement/standards/fhir/message-mappings.htm
V3 and V2 published specifications.