Difference between revisions of "MessageHeader FHIR Resource Proposal"
| Line 63: | Line 63: | ||
Message | Message | ||
| − | Detailed message resource mappings can be found at: http://www.hl7.org/implement/standards/fhir/message-mappings.htm | + | Detailed message resource mappings (for v3 & v2) can be found at: http://www.hl7.org/implement/standards/fhir/message-mappings.htm |
==Resource appropriateness== | ==Resource appropriateness== | ||
Revision as of 18:52, 27 May 2013
This page documents a Pending FHIR Resource Proposal
Contents
- 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
Message
Owning committee name
Infrastructure and Messaging
Contributing or Reviewing Work Groups
FMG, OO, MnM,
FHIR Resource Development Project Insight ID
pending
Scope of coverage
A transmission requesting action on a bundle of one or more resources or a response to such a request.
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.
RIM scope
Message
Detailed message resource mappings (for v3 & v2) can be found at: http://www.hl7.org/implement/standards/fhir/message-mappings.htm
Resource appropriateness
Expected implementations
Content sources
V3 and V2 published specifications.
Example Scenarios
Resource Relationships
Timelines
pending
