This page is part of the Da Vinci Clinical Documentation Exchange (v0.1.0: STU 1 Ballot 1) based on FHIR R4. The current version which supercedes this version is 1.1.0. For a full list of available versions, see the Directory of published versions 
Push (Unsolicited Communication)
Information Exchange Interaction Description
The Push (Unsolicited Communication) information exchange interaction is a alternative way to handle a Push interaction for a FHIR APIs. It uses the Communication Resource to send a message that communicates information to a recipient system. A system should send a Communication task to the recipient system to notify the system of the available communication. This approach allows the recipient system to determine if the task will be performed or not, and when it will be performed. Alternatively, a system may send a Communication resource directly to the recipient system if a task-based workflow is not supported.
This information exchange mechanism includes useful differences from the Push (POST and PUT) method also used to create and update information on an external system. This is a curated (or processed) information exchange. It encompasses a task to accept/process the response. The task may be completed by a system or a human or a combined effort.
This information exchange method can be used when there is a need for the Information Recipient to decide if the Communication will be accepted or not, and if there is a need for the Information Sender to monitor the progress of the processing of the Communication by the Recipient system.
Actor Descriptions
Information Sender
An Information Sender is a system that delivers a message to an Information Recipient.
Information Recipient
An Information Recipient is a system that receives a message from an Information Sender.
Actor Interaction Diagram
Unsolicited Communication without Task
|
Unsolicited Communication with Task
|
Processing Steps
Preconditions
The Information Sender has established rules about information sharing requirements after various types of service events occur.
The Information Sender has access to look-up digital addresses for Information Recipients or has previously been given the address information for the Information Recipient.
A secure information transport mechanism exists between the Information Sender and all Information Recipients.
Trigger
Something (a process step, event or request) in the Information Sender’s workflow happens, causing the need for information to be shared with an external entity.
Main Flow
The Information Sender sends a communication message with the agreed health record information to the Information Recipient(s) who are known to need the information.
Alternatively, If the Information Recipient supports a task-based workflow, the Information Sender sends an Unsolicited Communication Task to the Information Recipient. The Information Recipient determines if it will execute the task or not and when it will execute the task. It then does a Pull (Get) to retrieve the indicated Communication and gather/processes the supplied information.
Post Conditions
Each Information Recipient receives the communication message and processes it according to their business logic and optional support of associated tasks.
Detailed Specification
For a more detailed specification of the Push (Unsolicited Communication) Interaction, consult the HRex implementation guide.
