Tefca Transactions Clause Samples
Tefca Transactions. 6.5.1 QHIN Message Delivery
a. See requirements in Section 5.5.1a and 5.5.1b
b. If an Initiating Node sends a Message Delivery for T-PH-ECR that requires a Reportability Response from the Responding Node, the Initiating Node MUST support the required Reportability Response standards, as specified in Table 3 below.
c. Initiating Nodes MUST use the appropriate, corresponding content standards, as specified below for Integrating the Healthcare Enterprise (IHE) standards-based transactions. Electronic Case Reporting (T-PH-ECR) Prior to January 1, 2026 Health Care Providers: HL7 CDA® R2 Implementation Guide: Public Health Case Report Release 2: the Electronic Initial Case Report (eICR) Release 1, STU Release 1.1 - US Realm Public Health Authorities and Delegates: HL7 CDA® R2 Implementation Guide: Reportability Response, Release 1, STU Release 1.0 - US Realm As of January 1, 2026 Health Care Providers: HL7 CDA® R2 Implementation Guide: Public Health Case Report - the Electronic Initial Case Report (eICR) Release 2, STU Release 3.1 - US Realm Public Health Authorities and Delegates: HL7 CDA® R2 Implementation Guide: Reportability Response, Release 1, STU Release 1.1 - US Realm
6.5.2 QHIN Query
a. Not applicable.
6.5.3 Facilitated FHIR
Tefca Transactions. 7.5.1 QHIN Message Delivery
a. See requirements in Section 5.5.1a and 5.5.1b.
b. Initiating Nodes MUST use the appropriate, corresponding content standards, as specified in Table 5 below for Integrating the Healthcare Enterprise (IHE) standards- based transactions.
5.1 Implementation Guide: Electronic Laboratory
7.5.2 QHIN Query
a. Not applicable.
7.5.3 Facilitated FHIR
Tefca Transactions. 5.5.1 QHIN Message Delivery This SOP supports TEFCA Exchange in the form of a QHIN Message Delivery from any Initiating Node (e.g., a Node maintained by a Health Care Provider or clinical laboratory) to a PHA or its Delegate, in accordance with Applicable Law and the Common Agreement.
a. An Initiating Node MUST only send Message Deliveries to a PHA, its Delegate, or other Responding Node, that is listed in the RCE Directory Service as capable of receiving Message Deliveries. All Initiating Nodes MUST include the RCE Directory Service entry Organization Resource ID at the most granular level (e.g., lowest level Subparticipant or child) in addition to its HomeCommunityID within the ▇▇▇▇ information. <▇▇▇▇:Attribute FriendlyName="RCEDirectoryID" Name="urn:oasis:names:tc:xspa:1.0:subject:organization-id"> <▇▇▇▇:AttributeValue>2.16.840.1.113883.3.1833.5</▇▇▇▇:AttributeValue> </▇▇▇▇:Attribute>
Tefca Transactions