2022 - 09 Bidirectional Services e-Referrals (BSeR)

Participants:

                P1: Clinical Service Provider – referral initiator

                P2: Extra-clinical Service Provider – referral recipient

Scenario 1: BSeR FHIR IG Validation

P1 generates referral request and validates using the HL7 validator

Roles generates referral feedback and validates using the HL7 validator

It’s required for P1 to pass the validation to proceed to the next scenario in this Connectathon. It’s optional for P2 if P2 is not ready to produce the feedback report. It is however required for P2 to consume and process the validated referral request.

Scenario 2:   The referral initiator initiates the referral task by sending the referral service request to the referral recipient. The initiator is related to an organization and a service delivery location.

P1:         Referral Request creation & send

P2:         Register practitioner/organization (with an endpoint) to P1 referral testing system. P1 should work with P2 and have them registered before the connectathon

Step 1: Creation of the referral request package

• P1 creates referral request package payload using messaging paradigm; conforming to http://hl7.org/fhir/us/bser/StructureDefinition-BSeR-ReferralMessageBundle.html
• Send to (referral) messaging endpoint; $process-message

Success Criteria:   Confirm successful response message (or ACK) and screenshot of recipient system that shows the received message or content.

Bonus point:        Referral request message Bundle include Patient consent; referral recipient handles this consent to initiate a Referred Patient Intake workflow culminating in a Service Delivery Plan creation

Scenario 3: The referral recipient consumes the received referral request package and parse the package and extract clinical information in the package. The clinical information is available in the referral request document bundle - http://hl7.org/fhir/us/bser/StructureDefinition-BSeR-ReferralRequestDocumentBundle.html

P2: Receive and consume the referral request packet

Step 1: P2 provides the messaging endpoint (<system URL>/$process-message).

Step 2: P2 receives the referral request package

• Sends the ACK to referral recipient in the (synchronous) messaging.
• Consumes the data and confirms that it has enough information to develop service plan.

Success Criteria:   Sent ACK to the initiator (where the referral request is coming from) and screenshot of initiator system that shows the messaging was successful. P2 shows the patient data for the service plan.

Scenario 4: The referral recipient (assuming the service plan was established, and the patient is following the service plan) creates referral feedback bundle(s) and send the feedback to the referral initiator. In real world, the feedback will be sent periodically over time. For the connectathon, it will be one time (or more if P2 is willing to test).

P2: Creation of Service Delivery Feedback Report (iteratively if possible) culminating in Referral Activity status http://hl7.org/fhir/us/bser/StructureDefinition-BSeR-ReferralActivityStatus.html). P2 sends the feedback report to the referral initiator and receive ACK message.

Step 1: P2 creates referral feedback package and sends it to referral initiator using a message bundle

• Referral initiator endpoint should be available from the initial referral request.
• The feedback message should be sent to <referral initiator URL>/$process-message

Step 2: P2 may repeat the feedback messaging. Proper status indication and resource bundling should be performed if this is repeating

Step 3:  P1 should send ACK back to P2 synchronously and updates the referral status.

Success Criteria:   ACK is received by P2 from P1. P1 shows the feedback report in the P1 system.