BSeR: Bidirectional Services_eReferral - Local Development build (v2.0.0-connectathon). See the Directory of published versions

Transport Options

There are two supported transport options that can be used individually or in combination. This flexibility is needed to support point-to-point transport as well as transport through Health Information Exchanges and Health Information Networks.

FHIR Messaging Option

One option for transmitting the content in this implementation guide is the use of FHIR Messaging. FHIR Messaging involves the use of a top-level FHIR Message bundle and then a small FHIR Messaging header. FHIR Messaging enables the movement of content through an information exchange intermediary and allows, but does not require, a store and forward exchange paradigm. The FHIR Message header includes the identity of the ultimate intended recipient and other information helpful for message exchange. All resources should be populated in the FHIR Message bundle because subsequent retrieval of resources back through an intermediary may not be enabled.

The following profiles have been defined for the FHIR Messaging Option:

Profiles

• BSeR Referral Message Bundle
• BSeR Referral MessageHeader
• BSeR Referral Task

The first resource in the BSeR Referral Message Bundle is the BSeR Referral MessageHeader and the focus of the BSeR Referral MessageHeader is the BSeR Referral Task. The focus of the BSeR Referral Task is the BSeR Referral ServiceRequest.

Basic REST Option

The second option for transmitting the content in this implementation guide is described here as Basic REST. In this case, a point-to-point RESTful exchange is supported. If the immediate inclusion of all resource content must be ensured, then a top level bundle and insistence on their inclusion will be the responsibility of the transmitting server.

The following profiles have been defined for the RESTful Submit Option:

Profiles

• BSeR Referral Task

The focus of the BSeR Referral Task is the BSeR Referral ServiceRequest.