Difference between revisions of "MessageHeader FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
Line 54: Line 54:
 
As a rule, resources should encompass all of these aspects.
 
As a rule, resources should encompass all of these aspects.
 
  -->
 
  -->
 +
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.
  
 
==RIM scope==
 
==RIM scope==

Revision as of 18:49, 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.

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.

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

gForge Users