This wiki has undergone a migration to Confluence found Here
Difference between revisions of "MessageHeader FHIR Resource Proposal"
Jump to navigation
Jump to search
| Line 59: | Line 59: | ||
<!-- Identify the formal RIM mapping for the root concept of the resource. The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. --> | <!-- Identify the formal RIM mapping for the root concept of the resource. The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. --> | ||
Message | Message | ||
| + | |||
| + | Detailed message resource mappings can be found at: http://www.hl7.org/implement/standards/fhir/message-mappings.htm | ||
==Resource appropriateness== | ==Resource appropriateness== | ||
Revision as of 18:46, 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
RIM scope
Message
Detailed message resource mappings 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
