FHIR Push Clause Samples
The FHIR Push clause defines the process by which one party transmits healthcare data to another using the FHIR (Fast Healthcare Interoperability Resources) standard. This typically involves sending patient records, clinical summaries, or other health information in a structured, machine-readable format directly to a recipient system, often triggered by specific events or updates. By standardizing the method and format for data transfer, this clause ensures interoperability between systems and facilitates timely, accurate information sharing, thereby reducing errors and improving care coordination.
FHIR Push a. See requirements in 5.5.3.1a and 5.5.3.
FHIR Push a. See requirements in 4.4.3.1 of this SOP.
FHIR Push a. See requirements in 4.4.3.1 of this SOP as applied to the XP Code T-HCO-QM.
FHIR Push a. See requirements 4.4.3.1 as applied to the XP Code T-HCO-CC.
FHIR Push a. Any Initiating Node may initiate a FHIR Push to any other Responding Node, in accordance with Applicable Law.
FHIR Push a. Initiating Nodes MUST only send FHIR Pushes to a PHA or its Delegate who have a FHIR Endpoint listed in their RCE Directory Entry.
b. Initiating Nodes MUST include their Resource ID of the Organization entry in the RCE Directory Service within the OAuth information.