Difference between revisions of "MessageHeader FHIR Resource Proposal"
| Line 98: | Line 98: | ||
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this resource. They should demonstrate the full scope of the resource and allow exercising of the resources capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) --> | <!-- Provide a listing of the types of scenarios to be represented in the examples produced for this resource. They should demonstrate the full scope of the resource and allow exercising of the resources capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) --> | ||
| + | Using the message resource it is reasonable to expect development of scenarios similar to | ||
| + | v2 messaging exchanges. | ||
| + | |||
| + | 1) Patient Administration - Admission, Discharge and Transfer scenarios | ||
| + | |||
| + | 2) Order entry - for labs, pharmacy, imaging, etc. | ||
| + | |||
| + | 3) Observation reporting - lab results, microbiology, imaging results, etc. | ||
==Resource Relationships== | ==Resource Relationships== | ||
Revision as of 20:09, 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
The messaging paradigm embodied in v2 is widely understood and used within contemporary healthcare. Given that wide base of knowledge and experience it is reasonable to assume that members of the v2 community will experiment and likely adopt use of FHIR resources using this paradigm.
The message resource will allow development of FHIR based messaging likely within healthcare entities and across organizational boundaries over time.
Expected implementations
Content sources
V3 and V2 published specifications.
Example Scenarios
Using the message resource it is reasonable to expect development of scenarios similar to v2 messaging exchanges.
1) Patient Administration - Admission, Discharge and Transfer scenarios
2) Order entry - for labs, pharmacy, imaging, etc.
3) Observation reporting - lab results, microbiology, imaging results, etc.
Resource Relationships
The most likely place to look for resources to be included in FHIR messages would look at v2 messages and look for analogous resources. (This might also lead to understanding gaps in FHIR that need to filled.)
Timelines
pending
