STATEMENT OF WORK ARIZONA HIE INTEGRATION FOR NON-DAP ELIGIBLE DATA SUPPLIERS.PDF
Extracted text (via pymupdf)
19307 characters
DocuSign Envelope ID: FD4F0437-3314-4041-82BB-C0168628718D Page 1 of 7 Last Updated May 10, 2023 Statement of Work Arizona HIE Integration for Non-DAP Eligible Data Suppliers This Statement of Work (“SOW”) is a binding contract between the parties and is hereby made a part of, and incorporated by reference into, the Participant Agreement (“Agreement”) by and between HEALTH CURRENT, on behalf of itself and its joint venture affiliate Contexture, (“Contexture”) and the entity listed below (“Participant”) and subject to all the terms and conditions contained therein. The SOW is effective upon execution by both parties (“SOW Effective Date”). Following this SOW, all references to the term “Agreement” in the Agreement will include the terms and conditions of the Agreement and this SOW, for the term of this SOW, as herein defined. Party: PARTICIPANT Legal Business Name: Maricopa County DBA: Department of Correctional Health Services Physical Street Address: 234 N. Central Avenue Suite 5000 Physical City, State, Zip Phoenix AZ 85004 Primary Contact: Name: Noe Sanchez Phone: 602-506-5535 Email: n.sanchez@maricopa.gov Email for Invoices: CHSAP@maricopa.gov Whereas, Contexture has commenced transitioning all HIE participants to an integrated HIE technology platform that will serve participants across both Arizona and Colorado starting in 2025 (the “HIE Technology Integration”); Whereas, the HIE Technology Integration will offer Participant improved HIE system performance and scalability, additional patient and clinical search functionality, more expansive EHR interoperability, improved patient matching and data management functionality, multi-state data reporting and analytics services, and HITRUST certified data security and protection systems; Whereas, Participant is a Data Supplier to the Arizona HIE and desires to continue supplying Data to Contexture’s integrated technology platform; Whereas, Participant’s cooperation with and assistance in the HIE Technology Integration is essential to the timely transfer of, and access to, Data, to the establishment of services on and configuration of new system interfaces to the integrated HIE platform; Whereas, this SOW will outline the steps required to transition Participant’s Arizona HIE connection to the new integrated HIE platform; Now, therefore, in consideration of the foregoing, the Parties agree as follows: 1) DEFINITIONS. The capitalized terms used in this SOW will have the definitions provided in this SOW or, if not provided in this SOW, in the Agreement. a) “API” means an Application Programming Interface and refers to the method for facilitating the secure exchange of structured electronic health information to the HIE. API exchange is limited to existing connections in place between the HIE and specific EHR vendor hubs. The list of available hub connections will be made available to Participant, upon request. Docusign Envelope ID: 67996CAF-5266-4258-9702-C1FD7122B101 DocuSign Envelope ID: FD4F0437-3314-4041-82BB-C0168628718D Page 2 of 7 Last Updated May 10, 2023 b) “CCD” means Continuity of Care Document and refers to an electronically generated, patient-specific clinical summary document. CCDs may be encounter-based or may include a more comprehensive view of all patient data, including medication, vitals, procedures, labs, encounters, etc. For the purposes of this SOW, any XML document type that follows the C-CDA standard is acceptable in the CCD category of the Data Supplier services. c) “Data Supplier” means an entity that makes Data available for access through the HIE and has entered into a Participation Agreement with Contexture. d) “Interface Specification” means the technical connection requirements provided by Contexture for exchange of Data. e) “Implementation” means the build out and initial testing of the Data Services described in this SOW. f) “Live Date” means the date after Implementation of the Data Services described in this SOW on which Data Supplier’s Data can be exchanged with other participants through the Contexture Integrated HIE. g) “Remote Integrator” is a listening agent installed within the Participant’s environment to retrieve CCDs. 2) Description of HIE Data Supplier Services. Participant is a Data Supplier and agrees to send Data to the integrated HIE Platform in the following manners (Select All that apply): Table A: Summary of Data Supplier Services HIE Data Service (Check all that apply) Data Service Description CCD Data Supplier Participant is a Data Supplier that will send CCD Data to the Contexture integrated HIE platform pursuant to one of Contexture’s approved data delivery methods. Select Preferred Data Delivery Method(s) (if known): Direct Secure Message API/ Web-Services (Integrating the Healthcare Enterprise (IHE) Profile) SFTP (Secure File Transfer Protocol) Remote Integrator HL7 Message Data Supplier (via Interface) Participant is a Data Supplier that will send HL7 messages via HL7 Interfaces. The Parties will build one or more of the following HL7 Interface types from Participant’s electronic health record (“EHR”) system to the Contexture integrated HIE platform. (CHECK THOSE THAT APPLY): Lab Result Interface Admission, Discharge, Transfer (ADT) Interface Pathology Report Interface Radiology Report Interface Transcribed Report Interface Immunization Interface Syndromic Surveillance Interface Docusign Envelope ID: 67996CAF-5266-4258-9702-C1FD7122B101 DocuSign Envelope ID: FD4F0437-3314-4041-82BB-C0168628718D Page 3 of 7 Last Updated May 10, 2023 Inbound HL7 messages must follow HL7 standards as well as Contexture’s Interface Specifications, which will be provided during Implementation. 3) Implementation and Ongoing HIE Data Services. Contexture will use commercially reasonable efforts to implement and provide ongoing Data Services (as applicable based on Participant’s selected Data Supplier Services) to Participant as set forth in Table B. Table B: Summary of Implementation Services and Contexture’s Obligations Service Requested Description Implementation Project Management Contexture will assign an implementation project manager to oversee Implementation planning, scheduling and execution. The project manager will be the primary point of contact for Participant during Implementation of Data Services to the new Contexture HIE platform. Contexture’s project manager and Participant will jointly be responsible for managing the project schedule and managing any technical connectivity issues. Account Management and Client Support Contexture will assign an account manager to provide required training on the HIE Policies and Permitted Use requirements and to address ongoing Participant needs. Participant’s Account Manager will be its primary point of contact following the Implementation and Live Date. Contexture’s Client Support team will provide routine maintenance, support desk and system monitoring services for the Services in accordance with the terms of the Agreement. For CCD Delivery Implementation (if applicable) Contexture will provide the following services as part of the analysis, design, and testing of the CCD Delivery Implementation: Support set up of a secure connection with Contexture’s data center; Determine data delivery method; Build connection or CCD interfaces in accordance with Contexture’s specifications for selected data delivery method; Connect interfaces to the new HIE platform; and Provide identity management services to facilitate the matching of Individuals and Data across disparate systems. For HL7 Message Interface Implementation (if applicable) Contexture will provide the following services as part of the analysis, design, and testing of each Data Supplier HL7 Interface: Participate in project kick-off and engage in Implementation with necessary focus and resources to meet planned project timeline of 19 sequential weeks maximum; Participate in project meetings, testing session and defect mitigation sessions and take necessary action toward resolution of any issues; Provide sample messages to begin initial pre-validation process (this is typically two-weeks / ~10,000 messages); Support set up of a secure virtual private network connection between Data Supplier’s EHR and the new HIE platform; Docusign Envelope ID: 67996CAF-5266-4258-9702-C1FD7122B101 DocuSign Envelope ID: FD4F0437-3314-4041-82BB-C0168628718D Page 4 of 7 Last Updated May 10, 2023 Conduct analysis of data feeds and develop interface specifications; Build interfaces in conjunction with EHR system vendors and in accordance with Contexture’s Interface Specifications; and Connect interfaces to the HIE System. Escalation Contact Contexture shall make available a point of contact for escalation of issues or concerns during the Implementation. Maintenance, Service Desk, and Support Services Contexture will provide routine maintenance, Service Desk, and System Availability and Network Monitoring services for the Data Supplier in accordance with the terms of the Agreement. 4) PARTICIPANT OBLIGATIONS. To ensure a timely and successful HIE Technology Integration, Participant agrees to meet the following requirements during the SOW Term and in accordance with any timelines specified herein. a) Contracts: Participant acknowledges that during the HIE Technology Integration period, Contexture will provide Participant with updated terms and conditions related to the exchange of information through the Contexture HIE, which Participant will have the opportunity to review. b) Compliance i) Notice of HIE Participation and Management of Patient Rights Process. Pursuant to Section 5 of the Agreement, Participant acknowledges that in acting as a Data Supplier to the Contexture HIE, Participant is responsible for complying with the Arizona Health Information Organization Law (codified at A.R.S. §§ 36-3801 through -3809). By executing this SOW, Participant acknowledges that it has read and understood Contexture’s Policies, including its HIE Notice and Opt-Out Policy. If Participant is a Healthcare Provider, Participant is required to: i) update and appropriately distribute its Notice of Privacy Practices to inform Patients of its participation in the HIE; (ii) provide Patients with notice of their right to Opt-Out of having their information compiled and shared in HIE, and (iii) appoint an individual, or individuals, within the organization to manage the Patient Opt-Out process and timely notification of Contexture. ii) PARTICIPANT ACKNOWLEDGMENT. By providing an Individual’s Data to the HIE, Participant represents and warrants that it has a HIPAA-compliant treatment, payment or healthcare operations relationship with the Individual and that Participant is authorized to send Data through the HIE for that Individual. c) Technical: Participant agrees to perform the technical obligations described in Table C in support of the Services described in this SOW. Table C: Participant Technical Obligations Requirement Description Timeline Planning and Resource Coordination Participant shall coordinate internal resources required for the HIE Technology Integration work to proceed and participate in a project Kick-Off meeting to establish an Implementation Schedule. Participant acknowledges that Implementation of the Data Services will require multiple meetings and that Contexture can only proceed with participation from the Participant and Participant’s vendor(s) (if applicable). Kick-Off Meeting to be scheduled within 60 days of SOW Effective Date Vendor Engagement Participant acknowledges that its EHR vendor may be required to engage as part of the Implementation ofData Ongoing Docusign Envelope ID: 67996CAF-5266-4258-9702-C1FD7122B101 DocuSign Envelope ID: FD4F0437-3314-4041-82BB-C0168628718D Page 5 of 7 Last Updated May 10, 2023 and Vendor Fees Supplier and HIE Data Services. Participant shall coordinate all vendor resources required for the HIE Technology Integration work, including delivery to Contexture of test messages. Contexture is not responsible for any vendor feesassociated with Interface development or Data exchange. Points of Contact (POC) Participant is required to provide names, titles and contact information for the following points of contact: 1) POC for Implementation related services; 2) POC for escalation of Implementation issues; 3) POC for service outages, disruptions or changes in HIE Data Services; and 4) POC for HIPAA Compliance or Privacy Officer. Participant agrees to notify Contexture within fourteen (14) days of any changes to these roles. Participant to provide POCs within 30 days of SOW Effective Date For CCD Delivery Implementation (if applicable) Participant will work with Contexture to determine the Data delivery method and to establish a connection or CCD-A interface in accordance with Contexture’s specifications for selected Data delivery method. Participant will work with Contexture to conduct any required acceptance testing, defect remediation, and validation testing in the test and production environments. Within 10 Weeks of Project Kick- off Meeting For HL7 Message Interface Implementation (if applicable) Participant will work with Contexture to establish a project timeline, design and test each HL7 Interface, participate in project meetings; Participant agrees to comply with Contexture’s Interface Specifications, which shall be supplied during Implementation; Participant will test necessary sample messages to begin initial pre-validation process (this is typically two-weeks / ~10,000 messages); Participant will cooperate with Contexture to conduct any required acceptance testing of its HL7 Interface and engage in any defect remediation and validation testing in the production environment. Within 19 weeks of Project Kick- Off Meeting HL7 Standards Contexture utilizes the current version of HL7, as available at http://www.hl7.org/index.cfm, in the development of HL7 Interfaces between Participant and the HIE. Participant shall be responsible for applying the appropriate Logical Observation Identifiers Names and Codes (LOINC®) terminology to any lab results prior to providing such results to Contexture. Ongoing Docusign Envelope ID: 67996CAF-5266-4258-9702-C1FD7122B101 DocuSign Envelope ID: FD4F0437-3314-4041-82BB-C0168628718D Page 6 of 7 Last Updated May 10, 2023 OID Purchase and Requirements As a Data Supplier, Participant agrees to purchase an Object Identifier (OID) through HL7.org if one has not been purchased previously and to follow HL7 standards regarding OID branching. Use of Participant’s EHR assigned OID is not permissible for HIE Data Exchange. As soon as possible following execution of the SOW and before Implementation can commence, Participant shall provide Contexture with its unique HL7 registered OID and any applicable OID Branching. Within 30 days of SOW Effective Date New Facilities Participant shall supply Contexture with the Tax Identification Number for each facility that will be sending Data as a Data Supplier hereunder. If Participant acquires or otherwise affiliates with a new clinical practice whose Data will be sent to the HIE, Participant will promptly notify Contexture of the facility name and OID before such facility’s Data is sent through a Participant interface. Ongoing 5) HIE TECHNOLOGY INTEGRATION RACI MATRIX. Contexture and Participant will jointly and severally perform and complete the HIE Technology Integration Services described herein in accordance with the role matrix and timelines set forth below, when the listed service is applicable to the Participant. Table C: Implementation Requirements RACI Matrix (As Applicable to Participant’s Data Services) Task Responsibility Per Role Contexture Participant EHR Vendor OID Purchase Accountable Kickoff Meeting Accountable Responsible Responsible Completion of Prerequisites Accountable Responsible Responsible Compliance with HIE Specifications Accountable Responsible Responsible Compliance with HIE Policies & Procedures Accountable Responsible Responsible Interface Build Accountable Responsible Responsible Informed User Acceptance Testing Accountable Responsible Consult Defect Remediation Accountable Responsible Responsible Responsible Go/No Go Accountable Responsible Responsible Consult Deploy to production Accountable Responsible Informed Informed Enable interface feed into production Accountable Informed Responsible Validation in production Accountable Responsible Responsible Consult Production defect remediation Accountable Responsible Responsible Responsible Production Support Overview meeting Accountable Responsible Responsible Informed Docusign Envelope ID: 67996CAF-5266-4258-9702-C1FD7122B101 DocuSign Envelope ID: FD4F0437-3314-4041-82BB-C0168628718D Page 7 of 7 Last Updated May 10, 2023 6) DISCLAIMER AND RESERVATION OF RIGHTS. CONTEXTURE WILL NOT BE RESPONSIBLE FOR ANY FAILURE TO COMPLETE OR TIMELY PERFORM THE SERVICES THAT IS SUBSTANTIALLY CAUSED BY THE PARTICIPANT’S FAILURE TO MEET THE OBLIGATIONS SET FORTH HEREIN, INCLUDING FAILURE TO ALLOT APPROPRIATE TIME AND RESOURCES FOR IMPLEMENTATION AND TESTING. DURING THE TERM OF THIS SOW, CONTEXTURE MAY IN ITS DISCRETION ADD ADDITIONAL REQUIREMENTS AND OBLIGATIONS TO THE SERVICES THROUGH CHANGE ORDERS ATTACHED HERETO, WHICH PARTICIPANT AGREES TO PERFORM, PROVIDED CONTEXTURE USES COMMERCIALLY REASONABLE EFFORTS TO NOTIFY PARTICIPANT OF SUCH CHANGE ORDER(S) AT LEAST 30 DAYS IN ADVANCE. 7) TERM. This SOW shall have a term of two (2) years or until such time as the HIE Technology Integration has been successfully completed and Participant is sending Data to and receiving Services from the new integrated HIE Platform, whichever is earlier (“SOW Term”). The Services described in this SOW may be terminated by either party as described in the Agreement or upon 90 days’ prior written notice to the other party. 8) This SOW may be executed in one or more counterparts, duplicate originals, or facsimile versions, each of which will be deemed an original, but all of which together will constitute one and the same instrument. 9) The Integrated Services shall continue to be governed by the terms and conditions of the Participation Agreement between Health Current and Participant. By signatures of their duly authorized representatives, the Parties hereby agree to be bound by the terms of this SOW. FOR HEALTH CURRENT, A CONTEXTURE MARICOPA COUNTY ORGANIZATION: BOARD OF SUPERVISORS Authorized Signature Authorized Signature Printed Name and Title Chairman, Board of Supervisors Date Date ATTEST: ________________________________ Clerk of the Board Date: ______________________ Approved as to form: ________________________________ Deputy County Attorney Date: ______________________ Docusign Envelope ID: 67996CAF-5266-4258-9702-C1FD7122B101 8/19/2024