Difference between revisions of "MessageHeader FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
Line 109: Line 109:
 
Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording)
 
Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording)
 
  -->
 
  -->
 +
 +
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==
 
==Timelines==

Revision as of 19:51, 27 May 2013



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

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

gForge Users