Bidirectional Services eReferral (BSeR), published by HL7 Public Health Working Group. This guide is not an authorized publication; it is the continuous build for version 2.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/bser/ and changes regularly. See the Directory of published versions
There are two supported high-level use cases that can be used individually or in combination and that drive transport options. This flexibility is needed to support point-to-point transport as well as transport through Health Information Exchanges and Health Information Networks.
One option for transmitting the content in this implementation guide is a push option with 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 messageHeader 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:
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.
The second option for transmitting the content in this implementation guide is notify and pull. In this case, a point-to-point RESTful exchange is supported.
The following profiles have been defined for the RESTful Submit Option:
The focus of the BSeR Referral Task is the BSeR Referral ServiceRequest.