QHIN Technical Framework definition

QHIN Technical Framework. The framework relies almost completely on Integrating the Healthcare Enterprise (IHE) standards and transactions which do not represent most health information exchange implementations today. Most public health transactions (immunizations for example) are not currently implemented with IHE technologies. This framework may make it difficult to ensure public health transactions can be easily sent between two QHINs and would suggest that standards-based implementations in use today such as HL7 standards be supported. Another concern is if only IHE standards are used between QHINs that implies that they must unencrypt the message to translate it into another standard for transmission. We recommend that QHINs be required to follow national standards set by ONC and included in the ISA. The QHIN Technical Framework (QTF) should also separate transport and payload standards for “push” exchange. The specific standards used for QHIN to QHIN “push” transport could be executed in several different ways, but TEFCA should insist that for any of them a variety of payloads are allowed (HL7 v2, CDA, and FHIR bundles) and that the “header” information of each of these payloads is kept intact and unaltered through the TEFCA described multi-hop process. HL7 FHIR API standards as specified in the QTF do not adequately support “push” messaging through a decision support intermediary because it does not specify a messaging header. “FHIR Messaging” needs to be specified in addition to the basic FHIR API to support the “push” use through decision support intermediaries.
View Source
QHIN Technical Framework or “QTF” means the document incorporated by reference into this Agreement, that may include: (i) technical requirements, functional requirements, and privacy and security related requirements for the exchange of TI between QHINs; and (ii) technical, privacy, and security flow-down requirements for the QHIN to the QHIN Participants and/or Subparticipants (if any) in addition to the privacy and security Flow-Downs of the Common Agreement.
View Source

Examples of QHIN Technical Framework in a sentence

  • Designation (including its correlative meanings “Designate,” “Designated,” and “Designating”): the RCE’s written confirmation to ONC and Signatory that Signatory has satisfied all the requirements of the Common Agreement, the QHIN Technical Framework, all applicable SOPs, and is now a QHIN.

  • Except as otherwise expressly provided herein, the QHIN shall be required to comply with any updates to the QHIN Technical Framework no later than eighteen (18) months after such updates have been approved by ONC.

  • Each QHIN’s security policy shall include written policies and procedures consistent with the technical requirements specified in the QHIN Technical Framework to ensure a secure channel for communications between QHINs and between QHINs and Participants.

  • Each QHIN shall meet the requirements of the then applicable QHIN Technical Framework which is incorporated herein by reference into these MRTCs and made a part hereof.

  • Each QHIN’s security policy shall require that all Participant cryptographic certificates meet or exceed the applicable criteria in the QHIN Technical Framework.

  • The Common Agreement requires that when the QHIN Caucus is voting on a new SOP or an amendment to the Common Agreement, the QHIN Technical Framework, or an SOP, or when the Participant/Subparticipant Caucus is voting on a new SOP or an amendment to an SOP, the action must be approved by at least two-thirds (2/3) of the votes cast by the members of the respective Governance Body.

  • Each QHIN shall abide by the auditable events requirements described in the QHIN Technical Framework.

  • A QHIN Designation shall not be issued by the RCE unless and until the Provisional QHIN certifies, and the RCE has confirmed and documented, that the Provisional QHIN in question has satisfied the applicable requirements of the Common Agreement and the QHIN Technical Framework, including satisfaction of any testing requirements set forth therein.

  • Connectivity Services: the technical services provided by a QHIN, Participant, or Subparticipant to its Participants and Subparticipants that facilitate TEFCA Exchange and are consistent with the requirements of the then-applicable QHIN Technical Framework.

  • The RCE is responsible for developing the Common Agreement in coordination with ONC, including the Additional Required Terms and Conditions (ARTCs) and the Qualified Health Information Network (QHIN) Technical Framework (QTF) in addition to the Minimum Required Terms and Conditions (MRTCs) that ONC published in the TEFCA Draft 2 Guidance.