Expectations of Participants. 12.01. Minimum Requirement for Participants that request Message Content for Treatment. HIETexas exists to promote the seamless exchange of health information across a variety of technical platforms and Health Information Networks. A core principle of eHealth Exchange is that Participants make commitments to the minimum level of data sharing that they will support so that all other Participants can know, and rely on, each Participant’s commitment. All Participants that choose to participate in a specific Use Case must comply with all of the Performance and Service Specifications for a Use Case and must take measures to require that its Participant Users comply with all of the Performance and Service Specifications for a Use Case and must take measures to require that its Participant Users comply with all of the Performance and Service Specifications for a Use Case. a. Participants that request, or allow their respective Participant Users to request, Message Content for Treatment shall have a corresponding reciprocal duty to respond to Messages that request Message Content for Treatment. A Participant shall fulfill its duty to respond by either (i) responding to the Message with the requested Message Content or, (ii) responding with a standardized response that indicates the Message Content is not available or cannot be exchanged. Nothing in this Section 12.01(a) shall require a disclosure that is contrary to a restriction placed on the Message Content by a patient pursuant to Applicable Law. b. Each Participant that requests, or allows its respective Participant Users to request, Message Content for Treatment shall Transact Message Content with all other Participants for Treatment, in accordance with Sections 6, 12.01(a) and 14 of this Agreement. If a Participant desires to stop Transacting Message Content with another Participant based on the other Participant’s acts or omissions in connection with this Agreement, the Participant may temporarily stop Transacting Message Content with such Participant either through modification of its Participant Access Policies or through some other mechanism, to the extent necessary to address the Participant’s concerns. If any such cessation occurs, the Participant shall provide a Notification to the THSA of such cessation and the reasons supporting the cessation, and the THSA shall provide notice to the other Participants regarding such cessation. The Participants shall submit the Dispute leading to the cessation to the Dispute Resolution Process in Section 21. If the cessation is a result of an Adverse Security Event that was reported to, and deemed resolved by, the THSA pursuant to Section 14.03, the Participants involved in the Adverse Security Event and the cessation shall engage in the Dispute Resolution Process in Section 21 in an effort to attempt to reestablish trust and resolve any security concerns arising from the Adverse Security Event.
Appears in 1 contract
Expectations of Participants. 12.01. Minimum Requirement for Participants that request Message Content for Treatment. HIETexas exists to promote the seamless exchange of health information across a variety of technical platforms and Health Information Networks. A core principle of eHealth Exchange is that Participants make commitments to the minimum level of data sharing that they will support so that all other Participants can know, and rely on, each Participant’s commitment. All Participants that choose to participate in a specific Use Case must comply with all of the Performance and Service Specifications for a Use Case and must take measures to require that its Participant Users comply with all of the Performance and Service Specifications for a Use Case and must take measures to require that its Participant Users comply with all of the Performance and Service Specifications for a Use CaseT reatment.
a. All Participants that request, or allow their respective Participant Users to request, Message Content for Treatment shall have a corresponding reciprocal duty to respond to Messages that request Message Content for Treatment. A Participant shall fulfill its duty to respond by either (i) responding to the Message with the requested Message Content or, (ii) responding with a standardized response that indicates the Message Content is not available or cannot be exchanged. All responses to Messages shall comply with Performance and Service Specifications, this Agreement, any agreements between Participants and their Participant Users, and Applicable Law. Participants may, but are not required to, Transact Message Content for a Permitted Purpose other than Treatment. Nothing in this Section 12.01(a) shall require a disclosure that is contrary to a restriction placed on the Message Content by a patient pursuant to Applicable Law.
b. Each Participant that requests, or allows its respective Participant Users to request, Message Content for Treatment shall Transact Message Content with all other Participants for Treatment, in accordance with Sections 6, 12.01(a) and 14 of this Agreement. If a Participant desires to stop Transacting Message Content with another Participant based on the other Participant’s 's acts or omissions in connection with this Agreement, the Participant may temporarily stop Transacting Message Content with such Participant either through modification of its Participant Access Policies or through some other mechanism, to the extent necessary to address the Participant’s 's concerns. If any such cessation occurs, the Participant shall provide a Notification to the THSA Coordinating Committee of such cessation and the reasons supporting the cessation, and the THSA shall provide notice to the other Participants regarding such cessation. The Participants shall submit the Dispute leading to the cessation to the Dispute Resolution Process in Section 21. If the cessation is a result of an Adverse Security Event a Breach that was reported to, and deemed resolved by, the THSA Coordinating Committee pursuant to Section 14.03, the Participants involved in the Adverse Security Event Breach and the cessation shall engage in the Dispute Resolution Process in Section 21 in an effort to attempt to reestablish trust and resolve any security concerns arising from the Adverse Security EventBreach.
Appears in 1 contract
Expectations of Participants. 12.01. Minimum Requirement for Participants that request Message Content for Treatment. HIETexas exists to promote the seamless exchange of health information across a variety of technical platforms and Health Information Networks. A core principle of eHealth Exchange is that Participants make commitments to the minimum level of data sharing that they will support so that all other Participants can know, and rely on, each Participant’s commitment. All Participants that choose to participate in a specific Use Case must comply with all of the Performance and Service Specifications for a Use Case and must take measures to require that its Participant Users comply with all of the Performance and Service Specifications for a Use Case and must take measures to require that its Participant Users comply with all of the Performance and Service Specifications for a Use Case.
a. All Participants that request, or allow their respective Participant Users to request, Message Content for Treatment shall have a corresponding reciprocal duty to respond to Messages that request Message Content for Treatment. A Participant shall fulfill its duty to respond by either (i) responding to the Message with the requested Message Content or, (ii) responding with a standardized response that indicates the Message Content is not available or cannot be exchanged. All responses to Messages shall comply with Performance and Service Specifications, this Agreement, any agreements between Participants and their Participant Users, and Applicable Law. Participants may, but are not required to, Transact Message Content for a Permitted Purpose other than Treatment. Nothing in this Section 12.01(a) shall require a disclosure that is contrary to a restriction placed on the Message Content by a patient pursuant to Applicable Law.
b. Each Participant that requests, or allows its respective Participant Users to request, Message Content for Treatment shall Transact Message Content with all other Participants for Treatment, in accordance with Sections 6, 12.01(a) and 14 of this Agreement. If a Participant desires to stop Transacting Message Content with another Participant based on the other Participant’s acts or omissions in connection Connection with this Agreement, the Participant may temporarily stop Transacting Message Content with such Participant either through modification of its Participant Access Policies or through some other mechanism, to the extent necessary to address the Participant’s concerns. If any such cessation occurs, the Participant shall provide a Notification to the THSA Coordinating Committee of such cessation and the reasons supporting the cessation, and the THSA shall provide notice to the other Participants regarding such cessation. The Participants shall submit the Dispute leading to the cessation to the Dispute Resolution Process in Section 21. If the cessation is a result of an Adverse Security Event a Breach that was reported to, and deemed resolved by, the THSA Coordinating Committee pursuant to Section 14.03, the Participants involved in the Adverse Security Event Breach and the cessation shall engage in the Dispute Resolution Process in Section 21 in an effort to attempt to reestablish trust and resolve any security concerns arising from the Adverse Security EventBreach.
Appears in 1 contract
Expectations of Participants. 12.01. 13.01. Minimum Requirement for All Participants that request Message Content for Treatment. HIETexas exists to promote the seamless exchange of health information across a variety of technical platforms and Health Information Networks. A core principle of eHealth Exchange is that Participants make commitments to the minimum level of data sharing that they will support so that all other Participants can know, and rely on, each Participant’s commitment. All Participants that choose to participate in a specific Use Case must comply with all of the Performance and Service Specifications for a Use Case and must take measures to require that its Participant Users comply with all of the Performance and Service Specifications for a Use Case and must take measures to require that its Participant Users comply with all of the Performance and Service Specifications for a Use Case.
a. All Participants that request, or allow their respective Participant Users to requestsubmit Messages that seekrequest, Message Content for Treatment shall have a corresponding reciprocal duty to respond to Messages that request seekrequest Message Content for Treatment. A Participant shall fulfill its duty to respond by either (i) responding to the Message with the requested Message Content or, (ii) responding with a standardized response that indicates the Message Content is not available or cannot be exchanged. All responses to Messages shall comply with NHIN Performance and Service Specifications, this Agreement, any agreements between Participants and their Participant Users, and Applicable Law. Participants may, but are not required to, respond to Messages that seekTransact Message Content for a Permitted PurposesPurpose other than Treatment. Nothing in this Section 12.01(a13.0112.01(a) shall require a disclosure that is contrary to a restriction placed on the Message Content by a patient pursuant to Applicable Law.
b. Each Participant that requests, or allows its respective Participant Users to requestsubmit Messages that seekrequest, Message Content for Treatment shall Transact exchangeTransact Message Content with all other Participants for Treatment, in accordance with Sections 67, 13.016, 12.01(a) and 14 1514 of this Agreement. If a Participant desires to stop Transacting exchangingTransacting Message Content with another Participant based on the other Participant’s acts or omissions in connection with the NHIN or this Agreement, the Participant may temporarily stop Transacting exchangingTransacting Message Content with such Participant either through modification of its Participant Access Policies or through some other mechanism, to the extent necessary to address the Participant’s concerns, and shall notify the NHIN. If any such cessation occurs, the Participant shall provide a Notification to the THSA Coordinating Committee of such cessation and the reasons supporting the cessation, and the THSA shall provide notice to the other Participants regarding such cessation. The Participants shall submit the Dispute leading to the cessation to the Dispute Resolution Process in Section 2123.21. If the cessation is a result of an Adverse Security Event a Breach that was reported to, and deemed resolved by, the THSA NHIN Coordinating Committee pursuant to Section 14.0316.03,14.03, the Participants involved in the Adverse Security Event Breach and the cessation shall engage in the Dispute Resolution Process in Section 21 2321 in an effort to attempt to reestablish trust and resolve any security concerns arising from the Adverse Security EventBreach.
Appears in 1 contract