Attachment A - Contexture HIE Participation Agreement

Revised 1/1/26
Statement of Work
Health Care Provider Gold Bundle
This Statement of Work (“SOW”) is an A‚achment that is incorporated by reference into the 
Contexture HIE Parঞcipaঞon Agreement (the “Agreement”). This SOW is subject to the terms and 
condiঞons contained in the Agreement between the parঞes and is made a part thereof. In the 
event of any conflict or inconsistency between the terms of this SOW and the terms of this 
Agreement, the terms of this SOW shall govern and prevail. The Exhibit(s) to this SOW, if any, 
shall be deemed to be a part hereof. In the event of any inconsistencies between the terms of the 
body of this SOW and the terms of the Exhibit(s) hereto, the terms of the body of this SOW shall 
prevail.
Participant Information
Legal Name of Participant Entity:
Trade Name/Doing Business As:
Physical Address:
Street Address:
City, State, Zip:
Tax ID Number (TIN):
Primary Contact:
Name:
Title:
Phone:
Email:
Billing Contact:
Is a third party named as the billing 
contact?
☐Yes ☐No
If yes, complete the fields to the right 
with the third party’s information
Organization:
Name: 
Title: 
Phone:
Email: 
Billing Street Address:
Billing City, State, Zip:
Contacts listed in this section may be changed at any time and without the need for an 
amendment to this SOW by a) emailing the Contexture Help Desk at Helpdesk@contexture.org,
b) emailing the Contexture team member assigned to the Participant, or c) emailing 
getconnected@contexture.org.
!)-,/
$,/
'#!+
'$(%!,!!+#(( /!+0#(.
X


$.$
*
(( /!+
$+!
!)+,&!',
$(%!
!!+






! $%
$%%$'#
((+ $',(+

	
)-%%-$00$#(( /!+0#(.
$,/
("
(( /!+


$.$
*
(( /!+
$+!
!)+,&!',
(( /!+



-%
-$00$
(( /!+









	


		
	

2
Eligibility and Permi‚ed Purpose: 
Will Participant be directing Contexture 
to provide the Solutions covered by this 
SOW to one or more Affiliates?
☐No
☐Yes, complete Exhibit C with all Affiliates 
Participant Service Area:
; Arizona
☐Colorado
☐Arizona and Colorado
☐Naঞonal
Participant agrees to notify Contexture within 14 business days of any changes to Participant’s 
Service Area and Contacts as listed in Participant Information.
1.0
Definiঞons. All capitalized words and phrases not defined in this Statement of Work have 
the meanings given elsewhere in the Agreement, including in the Cover Sheet and the HIE 
General Terms and Condiঞons.
a.
"Beds" means the maximum number of beds for which a hospital and/or facility 
holds a license, or is otherwise authorized, to operate.
b.
“CCD” means Conঞnuity of Care Document and refers to an electronically 
generated, paঞent-specific clinical summary document.  
c.
“Direct Secure Messaging Network” means the communicaঞons network offered 
by Contexture to enable secure exchange of paঞent informaঞon and other 
messages among Parঞcipant and others, including health care providers, payers, 
and paঞents, in accordance with the Direct Standard.
d.
“Direct Secure Messaging Network Directory” means the repository of 
informaঞon regarding Authorized Users of the Direct Secure Messaging Network 
collected, maintained, and made available by Contexture, in accordance with 
applicable Policies and Procedures.
e.
“Direct Standard” means the set of protocols and technical specificaঞons, as 
defined by 45 C.F.R § 170.202(a) and endorsed by the Office of the Naঞonal 
Coordinator for Health IT (ONC), to enable the secure exchange of health 
informaঞon over the Internet. Contexture supports all XDS Direct Standard 
protocols and an external web-based plaorm for managing Direct Secure mail 
inboxes.
f.
“Effecঞve Date” means the later of January 1, 2026, or the date of last signature 
on this SOW (for SOWs executed a[er January 1, 2026).
g.
“HISP” means Health Informaঞon Service Provider and refers to the accredited 
network service operator that allows for clinical data exchange on a naঞonal level 
through Direct Secure Messaging. HISP works by allowing hospitals, health plans, 
doctors, health informaঞon exchanges, and consumers a way to access the Direct 
Secure Message Network. 







	


		
	

3
h.
“HL7 Interface” means an automated connecঞon and process for formaমng 
informaঞon in accordance with the HL7 messaging standard to enable the secure 
exchange of Data between linked applicaঞons.
i.
“Idenঞty Only Inbound Data” is data that is leveraged solely for the purposes of 
creaঞng an output idenঞty that will not become part of the clinical record/content 
and therefore cannot be used in any HIE products or services without specific 
approval.   
j.
“Implementaঞon” means the installaঞon and iniঞal tesঞng of the services 
described in this SOW.
k.
“Implementaঞon Fees” means one-ঞme Fees that are applicable to the iniঞal SOW 
term only and not to any renewal SOW term.
l.
“Limited Use Inbound Data” is data, such as physical health and/or behavioral 
health data, which may include Part 2 Data, that is leveraged solely for limited 
purposes such as electronic clinical quality measures (eCQMs), other quality 
reporঞng, or otherwise specified use cases. This data may not be used for the 
purposes of HIE products and services except for idenঞty enrichment services. 
m.
“Live Date” means the date a[er Implementaঞon of the services described in this 
SOW on which Contexture begins receiving the requested data.
n.
“Message” means a Direct Secure Message used to send informaঞon via the 
Contexture provided HISP, in accordance with the Direct Trust specificaঞons.
o.
“Non-Part 2 Inbound Data” refers to inbound data that contains physical health 
and/or behavioral health data and that does not include Part 2 Data. This data 
may be shared, in accordance with system-level consent, across HIE products and 
services.   
p.
“Noঞficaঞon” is an electronic noঞficaঞon indicaঞng that a paঞent has undergone 
a triggering event. A Noঞficaঞon may or may not be a complete message, which is 
a type of standard HL7 message generated by healthcare systems based upon 
events.
q.
“Part 2 Mixed Inbound Data” refers to inbound data to Contexture from a general 
medical facility that operates a Part 2 Program and provides non-Part 2 services —
such as physical or behavioral health services (a “mixed use facility”).  Part 2 Mixed 
Inbound Data may come from an organizaঞon with Part 2 designaঞon that cannot 
separate the Part 2 data from other data types OR an organizaঞon with Part 2 
designaঞon that is capable of separaঞng its data into separate interfaces.  Any 
mixing of non-Part 2 data with Part 2 data must be treated as Part 2 Data due to 
the inability to separate the two types of data.  
r.
“Part 2 Only Inbound Data” refers to inbound data to Contexture from a medical 
facility that operates a Part 2 program and is not a mixed-use facility – these 
faciliঞes are someঞmes referred to as single use faciliঞes. 
s.
“Soluঞon” has the same meaning as in the HIE General Terms and Condiঞons and 
may also be referred to as “Service.” 






	


		
	

4
2.0
Contexture Soluঞon: Contexture will use commercially reasonable efforts t provide the 
following Soluঞon:
Portal
PaঞentCare 360™Portal (Portal) is a web-based plaorm where parঞcipants are able to access 
and query individual paঞents’ comprehensive health records. This funcঞonality allows 
parঞcipants to review demographic data, past health issues, test results, and medicaঞon history 
providing a longitudinal view of a Member’s health records. Contexture populates the Portal with 
data from a wide variety of healthcare enঞঞes from across the U.S. with the majority of the data 
coming from enঞঞes in Arizona and Colorado.
Soluঞon Selected: ☐Yes ☐No
Portal Single Sign-On
Parঞcipants can access PaঞentCare 360 Portal seamlessly within their system with Single Sign 
On. PaঞentCare 360 Portal Single Sign On uঞlizes industry standard technology to manage 
authenঞcaঞon acঞviঞes across systems while providing role-based access control. This soluঞon 
provides an improved user experience by reducing the number of ঞmes required to authenঞcate 
into various systems..
Soluঞon Selected: ☐Yes ☐No
HL7 Data Sender
Inbound HL7 is a soluঞon that brings data into the HIE via Health Level 7 (HL7) format. Each 
HL7 data type has its own interface. Contexture will implement and maintain one of more of the 
following HL7 Interface types from the Parঞcipant’s electronic health record (“EHR”) system to 
the HIE.
Soluঞon Selected: ☐Yes ☐No
Parঞcipants may choose to send one data type or mulঞple data types, select those that apply.
☐Laboratory Results
☐Radiology Reports
☐PACs Link
☐Transcripঞon
☐Pathology Results
☐ADTs
☐RDE (Pharmacy Treatment Encoded Order)
☐OMP (Pharmacy Treatment Order)
☐Syndromic Surveillance
☐Electronic Lab Reporঞng
☐VXU


X






	


		
	

5
Inbound HL7 messages must follow HL7 standards as well as the specificaঞons provided by 
Contexture’s data ingesঞon vendor.
Select the data type that will be sent to Contexture: 
☐Limited Use Inbound Data
☐Part 2 Only Inbound Data
☐Part 2 Mixed Inbound Data
☐Non-Part 2 Inbound Data
CCD Data Sender
CCD Data Sender is a Soluঞon that brings data into the HIE via CCD-A format. Contexture will 
implement and maintain a connecঞon from Parঞcipant to the HIE System to ingest CCD/care 
summary documents from the Parঞcipant, who is acঞng as a Data Sender. 
CCD Bidirecঞonal is a Soluঞon that enables parঞcipants to send data to the HIE in CCD-A 
format while also allowing them to query and retrieve CCDs directly into their Electronic Health 
Record (EHR) systems. Contexture will implement and maintain a secure connecঞon between the 
Parঞcipant and the HIE system, ensuring smooth transmission and retrieval of CCD/care 
summary documents.  
Select the data type that will be sent to Contexture: 
☐Limited Use Inbound Data
☐Part 2 Only Inbound Data
☐Part 2 Mixed Inbound Data
☐Non-Part 2 Inbound Data
Bidirecঞonal Configuraঞon: ☐Yes ☐No
Soluঞon Selected: ☐Yes ☐No
Direct Secure Message
Contexture offers HISP services and Direct Secure Messaging Network addresses to Parঞcipants   
if they use an electronic health record (EHR). For Parঞcipants with an EHR that is not capable of 
providing HISP services or if an EHR does not exist, Contexture offers a web-based soluঞon for 
sending and receiving Messages.
Soluঞon Selected: ☐Yes ☐No
Noঞficaঞons- Pick 1
Soluঞon Selected
☐Yes ☐No
☐Admission, 
Discharge, 
Transfer (ADT) 
Noঞficaঞon
ADT Noঞficaঞon will be sent regarding admission, discharge, and transfer 
events for Members on the Parঞcipant’s Member File upon receipt of data 
from HIE parঞcipants.
☐Laboratory 
Noঞficaঞon
Laboratory Noঞficaঞon will be sent regarding all lab results for Members on 
the Parঞcipant’s Member File.










	


		
	

6
☐Pathology 
Noঞficaঞon
Pathology Noঞficaঞon will be sent regarding new pathology reports for 
Members on the Parঞcipant’s Member File.
☐Transcripঞon 
Noঞficaঞon
Transcripঞon Noঞficaঞon will be sent regarding new paঞent notes for 
Members on the Parঞcipant’s Member File.
☐Radiology 
Noঞficaঞon
Radiology Noঞficaঞon will be sent regarding new radiology reports for 
Members on the Parঞcipant’s Member File.
☐HTP 
Noঞficaঞon 
(Colorado 
Parঞcipants Only) 
Regional Accountable Enঞঞes (RAEs) uঞlizing Hospital Transformaঞon 
Program (HTP) Noঞficaঞons will receive ঞmely HTP measure data from 
Colorado hospitals’ Inbound HTP data feeds for Members on the RAE’s 
Member File. RAEs can be noঞfied via flat file delivered daily or weekly. This 
soluঞon is only available in Colorado.
☐Mental Health 
Hospitalizaঞon 
Noঞficaঞon
Mental Health Hospitalizaঞon Noঞficaঞon will be sent when a Member on 
the Parঞcipant’s Member File is admi‚ed, discharged, or transferred from 
parঞcipaঞng faciliঞes. These faciliঞes are not included in Contexture's ADT 
Noঞficaঞon soluঞon.
☐Cholesterol 
Noঞficaঞon
Cholesterol Noঞficaঞon will be sent regarding the Parঞcipant’s Members' 
lipid panel results, including Total Cholesterol, High-Density Lipoprotein 
Cholesterol (HDL-C), Low-Density Lipoprotein Cholesterol (LDL-C), and 
Triglycerides
☐Hepaঞঞs 
Noঞficaঞon
Hepaঞঞs Noঞficaঞon will be sent regarding the Parঞcipant’s Members’ 
hepaঞঞs panel (A, B, C, and anঞ-body results).
☐Diabetes 
Noঞficaঞon
Diabetes Noঞficaঞon will be sent for the Parঞcipant’s Members’ diabetes 
panel, including Hemoglobin A1C, esঞmated average Hemoglobin A1c, 
fasঞng blood sugar, and glucose tests.
☐COVID-19 
Noঞficaঞon
COVID-19 Noঞficaঞon will be sent when a Member on the Parঞcipant’s 
Member File has a new COVID lab result (posiঞve or negaঞve).
3.0
Delivery Frequency and Methods:  Parঞcipant specific decisions made during 
Implementaঞon
a.
sFTP- Noঞficaঞons can be sent as HL7 files real ঞme as data comes in or can be 
sent as a daily report.
b.
HL7 Interface- Noঞficaঞons will be sent via Virtual Private Network (VPN) real 
ঞme to Parঞcipant.
c.
Direct Secure Message- Noঞficaঞons can be sent real ঞme as data comes in or as 
a daily report to the Parঞcipant.
4.0
Contexture Obligaঞons:
a.
General Obligaঞons
i.
Project and Implementaঞon Management. Contexture will assign an 
Implementaঞon project manager to oversee Implementaঞon planning, 
scheduling and execuঞon. The Implementaঞon project manager will be the 
first point of contact for Parঞcipant during Implementaঞon. Contexture’s 
Implementaঞon project manager and Parঞcipant will jointly be responsible 
for managing the project schedule, risks, and issues.






	


		
	

7
ii.
Ongoing Maintenance, Help Desk, & Monitoring Support. Contexture will 
provide rouঞne maintenance, help desk and system monitoring services 
for this product in accordance with the terms of the Agreement and 
Contexture’s then-current Service and Support Level Addendum.
b.
Soluঞon Specific Obligaঞons. 
i.
PaঞentCare 360 Portal:
(1) Authorized User Training. Contexture will provide online training 
modules, available on the Contexture website, to all Authorized Users 
listed on the request form.
ii.
PaঞentCare 360 Portal Single Sign On (SSO)
(1) Contexture will provide Documentaঞon required for SSO connecঞvity, 
to include user instrucঞons when accessing SSO for the first ঞme.
(2) Contexture will enable the SSO funcঞonality, uঞlizing industry best 
pracঞces in technology with Security Asserঞon Markup Language 
(SAML) to manage authenঞcaঞon across systems while providing role-
based user access control and other privacy needs.
iii.
Inbound HL7: Contexture will provide the following services as part of the 
analysis, design, and tesঞng of Parঞcipant’s inbound and outbound HIE 
interfaces:  
(1) Parঞcipate in project kick-off and engage in Implementaঞon with 
necessary focus and resources to meet a project Implementaঞon 
ঞmeline of nineteen (19) sequenঞal weeks.
(2) Support set up of a secure connecঞon between Data Sender’s EHR 
and the HIE System.
(3) Conduct analysis of data feeds and develop interface specificaঞons.
(4) Build interfaces in conjuncঞon with EHR and system vendors.
iv.
CCD Data Sender
(1) Support set up of a secure connecঞon with Contexture.
(2) Review, with parঞcipant, data delivery method (e.g., Direct Secure 
Message, XDS.b, SFTP, Remote Integrator or API) and build interfaces 
in conjuncঞon with Contexture specificaঞons.
(3) Conduct necessary tesঞng and data quality validaঞon.
(4) Connect interfaces to the HIE System.
(5) Provide idenঞty management services to facilitate the matching of 
paঞents and data across disparate systems.
v.
Direct Secure Message.
(1) Contexture will provide Participant with access to the Direct Secure 
Messaging Network for the sole purpose of enabling Authorized Users 
to transmit and receive PHI for the purposes permitted under the 
Agreement, Contexture Policies, Applicable Law and the Business 






	


		
	

8
Associate Agreement. All access to and use of the Direct Secure 
Messaging Network will be restricted to Authorized Users of 
Participant as permitted under this Agreement and Applicable Law and 
Contexture Policies. 
(2) Contexture will assign each of Participant’s Authorized Users an 
account or other means of accessing the Direct Secure Messaging 
Network.
vi.
Quick Results. If the participant organization and/or their healthcare 
providers do not have codes assigned to them by the health systems 
sending data into the HIE, Contexture will help the participant to engage 
with the health system to get a provider code created.
(1) Authorized User Training. Contexture will provide online training 
modules, available on the Contexture website, to all Authorized Users. 
All Authorized Users identified on the Authorized User request form 
will receive the link and registration information.
vii.
Noঞficaঞons
(1) Contexture will provide its standard Member File requirements that 
define content and format specificaঞons, which are required for 
Noঞficaঞons delivery. 
(2) Depending on Parঞcipant Member File delivery method decided, 
Contexture and Parঞcipant will establish needed connecঞvity for 
Member File delivery. If applicable, Contexture will provide all sFTP 
requirements and establish an sFTP locaঞon for the transfer of the 
Parঞcipant’s Member File. The Member file must be updated at least 
every 30 days by Parঞcipant to conঞnue receiving Noঞficaঞons. If 
applicable, Contexture will work with Parঞcipant to establish Direct 
Secure Message account for delivery of Member File.
(3) Contexture will idenঞty manage each Parঞcipant’s Member File and 
then generate the applicable Noঞficaঞon for the Parঞcipant’s Member 
File.
(4) Contexture will validate that connecঞvity, user access, and locaঞon 
meet Contexture’s data security standards and requirements.
(5) Contexture will update the Noঞficaঞon feed/report when updated 
Member Files are received from Parঞcipant (at least every 30 days or 
the Noঞficaঞons delivery will stop).
5.0
Parঞcipant Obligaঞons: Parঞcipant agrees to do the following in support of the Soluঞons 
described in this SOW:
a.
General Obligations.
i.
Participant acknowledges that the successful and timely Implementation of 
the Services covered by this SOW will require Participant’s active 
participation.






	


		
	

9
ii.
Coordinate both internal and vendor resources (if applicable) required for 
the Implementation and testing work to proceed. Participant 
acknowledges that such Implementation will require multiple meetings, 
and that Contexture can only proceed with participation from the 
Participant and its vendors.
iii.
Comply with all requirements included in the Implementaঞon 
Documentaঞon provided by Contexture. 
iv.
Project Delays. Contexture and Parঞcipant acknowledge that delays 
beyond their control may occur during the project, including but not 
limited to, obtaining approvals and resource availability. Parঞcipant is 
accountable for engaging vendor and working to miঞgate any delays 
caused by vendor organizaঞon.
b.
Soluঞon Specific Obligaঞons:
i.
PaঞentCare 360 Portal
(1) Authorized User Accounts for Portal Access. Access to the HIE and 
Solutions covered by this SOW will be provided only to Authorized 
Users. Participant will provide all information requested by 
Contexture, including a unique email address, in connection with the 
establishment of each Account, which may be used only by the 
Authorized User of the applicable Account. Participant is responsible 
for requiring all Authorized Users to meet the requirements of this 
SOW and applicable Policies and Laws for access to the HIE and 
Services covered by this SOW. Participant will ensure the security and 
confidentiality of each Account and the associated login credentials 
and will notify Contexture immediately if any Account login credentials 
are lost, stolen, or otherwise compromised.  
(2) Contexture provides access to the Solutions covered by this SOW via 
secured methodology. Consistent with industry standards and best 
practices, Contexture is incorporating multi-factor authentication for 
access to the Solutions by all Authorized Users that access the Portal 
through the web following Implementation and on a schedule that is 
mutually agreeable to Contexture and Participant (in no case to exceed 
three (3) months). All Authorized Users of Participant that access the 
Portal through the web portal will be trained on and required to install 
and utilize a software application that will be used to validate 
Authorized Users’ identities.  
(3) Each Authorized User will complete all training required by 
Contexture, and Participant will certify that each Authorized User has 
completed all such training.
(4) Changes in Authorized User Status. Participant is responsible for 
initiating, updating, removing or suspending access of its Authorized 
Users to the HIE in compliance with applicable Laws and Policies and 
the Agreement. Participant shall take immediate action regarding any 
changes in the status of any Authorized User (or their ability to access 






	


		
	

10
the HIE or Solutions covered by this SOW) as set forth in the 
applicable Policies, including but not limited to employee departures or 
terminations.
(5) Permitted Use Policy. Participant is responsible for requiring all 
Authorized Users to meet the requirements of this SOW and 
Contexture’s applicable Permitted Use Policies and Applicable Laws 
for access to the HIE.
(6) Participant Responsibility for Actions of Authorized Users. Participant 
is fully responsible for all liabilities and damages incurred through 
access and use of the Solutions covered by this SOW by Participant’s 
Authorized Users. Any activity completed by an Authorized User of 
Participant will be deemed to have been completed by Participant.
(7) Third-Party Service Providers. As part of this Soluঞon, Authorized 
Users may access and use services and products provided by third-
party service providers. Parঞcipant's access and use of third-party 
services and products will comply with Secঞon 2.6 (Third-Party Service 
Providers) of the HIE General Terms and Condiঞons. These services 
and products are subject to change and Contexture has no duty to 
noঞfy Parঞcipant of changes.
ii.
PaঞentCare 360 Portal Single Sign On (SSO)
(1) Parঞcipant will comply with all Contexture Documentaঞon for this 
specific Soluঞon.
(2) Access to the HIE and Services covered by this SOW will be provided 
only to Authorized Users. Parঞcipant will provide all informaঞon 
requested by Contexture, including a unique email address, in 
connecঞon with the establishment of each Account, which may be 
used only by the Authorized User of the applicable Account. 
Parঞcipant is responsible for requiring all Authorized Users to meet the 
requirements of this SOW and applicable Contexture Policies and Laws 
for access to the HIE and Services covered by this SOW. Parঞcipant 
will ensure the security and confidenঞality of each Account and the 
associated login credenঞals and will noঞfy Contexture immediately if 
any Account login credenঞals are lost, stolen, or otherwise 
compromised.  
(3) Parঞcipant will comply with all obligaঞons of the PaঞentCare 360 
Portal Soluঞon.
iii.
Data Sender HL7:
(1) Parঞcipant shall provide a point of contact (POC) for outage 
informaঞon as well as a HIPAA Compliance or Privacy Officer. 
Parঞcipant agrees to noঞfy Contexture within fourteen (14) days of 
any changes to these roles. 






	


		
	

11
(2) HL7 Requirements:
(a) Contexture uঞlizes the current version of HL7, as available at 
h‚p://www.hl7.org/index.cfm, in the development of HL7 
Interfaces between Parঞcipant and the HIE System. 
(b) Parঞcipant will cooperate with Contexture to conduct any required 
acceptance tesঞng of its HL7 Interfaces.
(c) Parঞcipant shall map and apply the appropriate vocabulary, 
ontology and/or terminology codes (e.g. LOINC® vocabulary codes 
to lab test results or SNOMED® CT concepts for pathology 
reports) to the content of Parঞcipant data prior to providing data to 
the HIE. 
(3) OID Requirements:
(a) Parঞcipant shall obtain and register an OID (a globally unique ISO 
idenঞfier) via HL7.org so that Contexture may accurately idenঞfy 
and route data to other HIE Parঞcipants. 
(b) Parঞcipant shall provide Contexture with its unique HL7 registered 
OID as soon as possible following execuঞon of this Agreement and 
before Implementaঞon commences. 
(c) The OID must be unique and different from the electronic health 
record issued OID
(d) Parঞcipant must follow HL7 standards regarding OID branching or 
adopt the Contexture OID Branching Standard.
(e) Parঞcipant shall provide advance noঞce to Contexture of OID and 
facility modificaঞons before sending data inbound to the HIE.
(f) Parঞcipant shall send Facility OID and Facility Name in HL7 
interface in accordance with Contexture interface specificaঞon.
(4) Provide necessary producঞon messages to begin iniঞal pre-validaঞon 
process (this is typically two-weeks / ~10,000 messages).
(a) Parঞcipant will engage in the review of pre-validaঞon outcomes 
and make changes to the HL7 structure to comply with the HIE 
Gold Standard, as defined in Contexture Documentaঞon, and HL7 
Standards, as applicable. 
(5) By providing a Member’s data to the HIE, Parঞcipant represents and 
warrants that it has a HIPAA-compliant treatment, payment or 
healthcare operaঞons relaঞonship with the Member and that 
Parঞcipant is authorized to send data to the HIE for that Member.
(6) Prohibited Data Submissions. Parঞcipants will comply with the 
requirements of Secঞon 4.4 (Prohibited Data Submissions) of the HIE 
General Terms and Condiঞons.  






	


		
	

12
(7) Facility Changes. If Parঞcipant establishes, acquires or otherwise 
affiliates with a new clinical pracঞce whose data will be sent to the 
HIE, Parঞcipant will promptly noঞfy Contexture of the facility name 
and OID before such facility’s data is sent through a Parঞcipant 
interface. The addiঞon of new faciliঞes may be subject to addiঞonal 
Implementaঞon Fees. Addiঞonally, if any faciliঞes are removed, 
Parঞcipant will noঞfy Contexture within 30 days.    
iv.
CCD Data Sender
(1) Parঞcipant agrees to coordinate both internal and external vendor 
resources (if applicable) required for the Implementaঞon and tesঞng 
work to proceed. Parঞcipant acknowledges that such Implementaঞon 
will require mulঞple meeঞngs, and that Contexture can only proceed 
with the parঞcipaঞon from the Parঞcipant and its vendors. 
(2) OID Requirements.
(a) Parঞcipant shall obtain and register an OID (a globally unique ISO 
idenঞfier) via HL7.org so that Contexture may accurately idenঞfy 
and route data to other HIE Parঞcipants. 
(b) Parঞcipant shall provide Contexture with its unique HL7 registered 
OID as soon as possible following execuঞon of this Agreement and 
before Implementaঞon commences.
(c) The OID must be unique and different from the electronic health 
record issued OID.
(d) Parঞcipant must follow applicable standards regarding OID 
branching or adopt the Contexture OID Branching Standard.
(e) Parঞcipant shall provide advance noঞce to Contexture of OID and 
facility modificaঞons before sending data inbound to the HIE.
(f) By providing a Member’s data to the HIE, Parঞcipant represents 
and warrants that it has a HIPAA-compliant treatment, payment or 
healthcare operaঞons relaঞonship with the Member and that 
Parঞcipant is authorized to send data to the HIE for that Member.
(3) Prohibited Data Submissions. Parঞcipants will comply with the 
requirements of Secঞon 4.4 (Prohibited Data Submissions) of the HIE 
General Terms and Condiঞons.
(4) Facility Changes. If Parঞcipant establishes, acquires or otherwise 
affiliates with a new clinical pracঞce whose data will be sent to the 
HIE, Parঞcipant will promptly noঞfy Contexture of the facility name 
and OID before such facility’s data is sent through a Parঞcipant 
interface. The addiঞon of new faciliঞes may be subject to addiঞonal 
Implementaঞon Fees. Addiঞonally, if any faciliঞes are removed, 
Parঞcipant will noঞfy Contexture within 30 days.    






	


		
	

13
v.
Direct Secure Message. 
(1) Installaঞon. Parঞcipant will be solely responsible, at Parঞcipant’s own 
expense, for acquiring, installing, and maintaining all hardware, 
so[ware, and other equipment as may be necessary for Parঞcipant and 
each Authorized User to connect to, access, or use the Direct Secure 
Messaging Network except for any web portal tools provided by 
Contexture specifically for accessing the Direct Secure Messaging 
Network. 
(2) Parঞcipant Responsibility for Authorized Users. 
(a) Parঞcipant is solely responsible for all use of the Direct Secure 
Messaging Network by each Authorized User and for compliance 
by each Authorized User with the applicable terms of this 
Agreement, Applicable Law and Contexture Policies, and any 
addiঞonal terms of use applicable to the Direct Secure Messaging 
Network. Upon request by Contexture, Parঞcipant will verify that 
each Authorized User has agreed to be bound by any such 
addiঞonal terms of use.
(b) Parঞcipant will immediately noঞfy Contexture upon becoming 
aware of any breach of this Agreement or any such addiঞonal terms 
of use and will assist Contexture in the enforcement and miঞgaঞon 
of any such breach by Parঞcipant or any Authorized User. 
(c) Parঞcipant is responsible for iniঞaঞng, updaঞng, removing or 
suspending access of its Authorized Users to the HIE in compliance 
with Applicable Law, Contexture Policies and the Agreement. 
(d) Parঞcipant shall noঞfy the Contexture Help Desk immediately of 
any changes in the status of any Authorized User (or their ability to 
access the HIE or Services) as set forth in the applicable 
Contexture Policies. 
(e) Parঞcipant shall take reasonable acঞons, in accordance with 
Applicable Law, Contexture Policies, and industry standards, to 
confirm that all Messages transmi‚ed by Parঞcipant via the Direct 
Secure Messaging Network originate from Authorized Users.
(3) Messaging Content. Parঞcipant shall not, in conjuncঞon with the 
Direct Secure Messaging Network, use any means, program, or device, 
or permit any other person to use any means, program, or device, 
including, but not limited to, adverঞsing, instant messaging, or so-
called “pop-ups,” to solicit business or to influence or a‚empt to 
influence for commercial purposes (through economic incenঞves or 
otherwise) any diagnosঞc or treatment-related decision of a health 
care provider. The bona fide professional recommendaঞon of an 
Authorized User to another health care provider regarding the 
treatment or diagnosis of a shared paঞent is not intended to be 
prohibited by this provision; however, Contexture shall have sole 
discreঞon to determine the bona fide non-commercial and clinical 






	


		
	

14
nature of all Clinical Messages and uses of the Direct Secure 
Messaging Network.
(4) Direct Secure Messaging Network Directory. 
(a) Parঞcipant shall idenঞfy an individual who will complete any 
applicable Contexture provided training and assume responsibility 
for the accuracy and integrity of informaঞon provided by 
Parঞcipant to Contexture for inclusion in Contexture’s Direct 
Secure Messaging Network Directory. 
(b) Parঞcipant agrees that, at minimum, all of its Authorized Users who 
are duly licensed health care providers will be listed in the Direct 
Secure Messaging Network Directory. 
(c) Parঞcipant acknowledges that Contexture may use all directory 
and related informaঞon that it maintains in conjuncঞon with the 
Direct Secure Messaging Network, whether provided by 
Parঞcipant or obtained otherwise, for HISP maintenance and 
operaঞons related to the Direct Secure Messaging Network, 
interoperability with other HISPs, disclosure to appropriate third-
parঞes, and creaঞon and maintenance of other provider directories, 
as Contexture, in its sole discreঞon, deems appropriate.
(5) Prohibited Uses of the Direct Secure Messaging Network Directory.
(a) Parঞcipant and its Authorized Users are prohibited from 
commercially redistribuঞng the Direct Secure Messaging Network 
Directory. 
(b) Parঞcipant may not provide to any third party HISP or permit a 
third party HISP to acquire or create a copy of the Direct Secure 
Messaging Network Directory. 
(c) Parঞcipant may not provide or use the Direct Secure Messaging 
Network Directory for direct markeঞng or database markeঞng. 
(d) Parঞcipant may not sell, disclose or make available the Direct 
Secure Messaging Network Directory to any third party unless 
expressly authorized in wriঞng by Contexture.
(6) Parঞcipant Audits by Contexture. Upon reasonable request, 
Parঞcipant shall allow Contexture to access, inspect, and audit 
Parঞcipant’s systems and records relaঞng to the use of the Direct 
Secure Messaging Network, including any data or informaঞon 
transmi‚ed or received by Parঞcipant, for purposes of operaঞng and 
maintaining the Direct Secure Messaging Network and determining 
Parঞcipant’s compliance with this Agreement, Applicable Law and 
Contexture Policies.






	


		
	

15
vi.
Noঞficaঞons
(1) Follow all requirements associated with delivery of Member File and 
receipt of Noঞficaঞons, to include leveraging the Contexture 
systems/soluঞons (such as sFTP).
(2) Cooperate with Contexture to conduct any required acceptance 
testing of the Notifications Data.
(3) Member Files.
(a) Participant will send updated Member Files that meet Contexture’s 
specifications at least every 30 days. If Participant fails to send an 
updated Member File at least every 30 days, then Contexture has 
the right to discontinue the delivery of Notifications data until an 
updated file is delivered and processed.
(b) By including a Member on Participant’s Member File, Participant 
represents and warrants that it has a current HIPAA-compliant 
treatment, payment or healthcare operations relationship with the 
Member and that Participant is authorized to receive data through 
the HIE for that Member.
(4) Participant acknowledges that it is responsible for the proper use of all 
data received through the HIE and Services in accordance with the 
Agreement, Applicable Law and Contexture Policies. 
(5) Participant is responsible for ensuring that only users who require 
access to the Notifications are granted credentialed access. 
(6) Participant acknowledges that Contexture does not have any 
obligation or ability to monitor or review the content of the data for 
accuracy or completeness before making the data available through 
the HIE.
6.0
Fees and Payment: The following Fees are payable to Contexture by electronic means 
(such as e-check, ACH transfer, or credit card), unless Contexture determines that is not 
feasible. Fees are nonrefundable.
a.
Implementaঞon Fees. 
Reference Implementaঞon Fee Table in Exhibit A, Version 1.
Implementation Fees: $ 
☐Implementation Fees paid by State funding
☐Implementation Fee Not Applicable due to ONE Platform Migration
☐Participant to pay Implementation Fee
i.
If paid by the Participant, Contexture will invoice Participant 50% of the 
Implementation Fees within 30 days of the SOW Effective Date. 
Contexture will invoice the remaining 50% at the earlier of (i) two weeks 
after Implementation of a Service covered by this SOW, or (ii) six months 
after SOW Effective Date. 

X






	


		
	

16
ii.
Use of State Program Funding to cover Implementation Fees is subject to 
availability and Participant’s eligibility. If the programs are discontinued, or
the funds are no longer available, or the Participant is ineligible at the time 
that Participant seeks to implement the Services covered by this SOW, 
then Participant shall be responsible for the Implementation Fees.
b.
Subscripঞon Fees. 
Reference Subscripঞon Fee Table in Exhibit B, Version 1.1.
i.
Subscription Fees will be billed starting the first month after 
Implementation of any Service covered by this SOW. Participant is 
responsible for paying the full amount of the Subscription Fees once 
billing begins. 
ii.
The number of Authorized Users, Member File size or number of Beds, as 
applicable, will be reviewed at Live Date then quarterly or annually (based 
upon Parঞcipant’s billing cadence, as indicated in Exhibit B) with the 
Participant and the fee tier will be adjusted based upon that review 
effective for the first billing, subsequent quarter or year, as applicable. 
iii.
Participant is responsible for informing Contexture immediately when 
there is a change in Authorized Users, Member File size or number of 
Beds, as applicable.
iv.
Contexture typically updates fee schedules on an annual calendar year 
basis effective January 1st of each year. Contexture will provide updated 
fee tables to be incorporated by reference as exhibits at least 60 days 
prior to the effective date, in accordance with Section 6.6 (Fee Increases) 
of the HIE General Terms and Conditions. 
c.
Invoicing and Payment.
i.
Invoicing and payment of Fees under this SOW is governed by Section 6.0 
(Fees and Payment) of the HIE General Terms and Conditions.  
ii.
Participant shall provide an email address to Contexture for electronic 
invoicing and shall update Contexture within 14 business days of any 
change in that email address.
iii.
If Parঞcipant has elected to have a third-party receive and pay invoices for 
the Services covered by this SOW, Parঞcipant acknowledges that 
Parঞcipant has the ulঞmate responsibility to pay all invoices issued under 
this SOW. Parঞcipant is responsible for ensuring all billing contact 
informaঞon is kept up to date.
d.
Pricing Validity. 
i.
The pricing set forth in this SOW is valid for 90 days from Parঞcipant’s 
receipt of this SOW. If the SOW is not executed by Parঞcipant within 90 
days of receipt, then Contexture reserves the right to adjust the pricing.






	


		
	

17
7.0
Term, Terminaঞon and Suspension.
a.
Term: The iniঞal term of this Agreement shall run from the Effecঞve Date unঞl 
December 31st of the year contract signed.
b.
SOW Renewal: This SOW will automaঞcally renew for addiঞonal one (1) year 
terms, beginning January 1st a[er the expiraঞon of the iniঞal term, unঞl a Party 
terminates the Agreement as provided in the HIE General Terms and Condiঞons. 
c.
SOW Terminaঞon: SOW may be terminated by either Party without terminaঞng 
the enঞre Agreement for any of the reasons set forth in Secঞon 7.1 (Agreement 
Terminaঞon) of the HIE General Terms and Condiঞons. Upon the terminaঞon or 
expiraঞon of this SOW, Contexture will cease providing access to all Services for 
Parঞcipant and its Authorized Users, and Parঞcipant and its Authorized Users will 
stop accessing and using all Services. 
d.
Suspension: Contexture may limit, suspend, or terminate the access of a 
Parঞcipant or Authorized User to some or all of the Soluঞons for and of the 
reasons set forth in Secঞon 7.3 of the HIE General Term and Condiঞons.
8.0
SIGNATURES:
Each of the individuals signing below on behalf of either Party hereby represents and 
warrants that they are signing with full and complete authority to bind the party, and 
each identified Affiliate listed in Exhibit C on whose behalf they are signing to each term 
of this SOW. Participant affirms and agrees that (i) each Affiliate is a Participant under the 
entire Agreement and (ii) the signer below agrees on behalf of each Affiliate to all
applicable terms of the Agreement, including, but not limited to, the HIE General Terms 
and Conditions, any applicable Special Terms and Conditions, and the Business Associate 
Agreement/Addendum.  
Contexture, a Colorado nonprofit 
corporation
Signature:
Printed Name:
Title:
Signature Date:
Signature:
Printed Name:
Title:
Signature Date:
$,/
("
(( /!+






	


		
	

18
Exhibit A, Version 1:
Implementaঞon Fees
'ŽůĚ,ĞĂůƚŚĐĂƌĞWƌŽǀŝĚĞƌƵŶĚůĞ/ŵƉůĞŵĞŶƚĂƚŝŽŶ&ĞĞƐ
^ŽůƵƚŝŽŶ
/ŵƉůĞŵĞŶƚĞĚ͍
^ŽůƵƚŝŽŶEĂŵĞ
^ĞůĨͲWĂLJͬ,^
/ŵƉůĞŵĞŶƚĂƚŝŽŶ
&ĞĞ
WƌŝĐŝŶŐhŶŝƚ
ηŽĨ
/ŵƉ͘
☐
,>ϳĂƚĂ^ĞŶĚĞƌ
Ψϭϰ͕ϭϬϬ
WĞƌ>ŽĐĂƚŝŽŶ;ŚŝůĚ
KƌŐͿ
☐
ĂƚĂ^ĞŶĚĞƌ
Ψϭϯ͕ϭϬϬ
WĞƌ>ŽĐĂƚŝŽŶ;ŚŝůĚ
KƌŐͿ
☐
WϯϲϬ;tĞďͲĂƐĞĚͿ
Ψϰ͕ϬϱϬ
WĂƌĞŶƚKƌŐ;ϭdžͿ
☐
WϯϲϬ;^ŝŶŐůĞ^ŝŐŶͲKŶͿ
Ψϭϭ͕ϵϱϬ
,Z/ŶƐƚĂŶĐĞ
☐
ŝƌĞĐƚ^ĞĐƵƌĞDĞƐƐĂŐĞ;tĞďWŽƌƚĂů
ĐĐĞƐƐͿ
Ψϯ͕ϱϬϬ
WĂƌĞŶƚKƌŐ;ϭdžͿ
☐
ŝƌĞĐƚ^ĞĐƵƌĞDĞƐƐĂŐĞ;,Z
/ŶƚĞŐƌĂƚŝŽŶͿ
Ψϭϯ͕ϯϱϬ
,Z/ŶƐƚĂŶĐĞ
☐
EŽƚŝĨŝĐĂƚŝŽŶ;hŶŝƋƵĞDĞŵďĞƌ&ŝůĞͿ
Ψϱ͕ϵϬϬ
WĞƌEŽƚŝĨŝĐĂƚŝŽŶ














	


		
	

19
Exhibit B, Version 1.1:
Subscripঞon Fees
Arizona Fee Schedule – 35% Subsidy 
Quoted 
Tier
Member File Size
Annual
Quarterly 
Fee
Monthly 
Fee
Billing 
Cadence
Fee
Less 
Bundle 
Discount
Less State 
Subsidy
Net Price
☐
1
1,500
ΨϮ͕ϴϮϬ
Ψϭ͕ϬϲϬ
Ψϲϭϲ
Ψϭ͕ϭϰϰ
ΨϮϴϲ
Ψϵϱ
Annual
☐
1,501
2,500
Ψϲ͕ϰϬϬ
ΨϮ͕ϯϮϬ
Ψϭ͕ϰϮϴ
ΨϮ͕ϲϱϮ
Ψϲϲϯ
ΨϮϮϭ
Annual
☐
2,501
5,000
Ψϵ͕ϲϮϬ
Ψϯ͕ϰϴϬ
ΨϮ͕ϭϰϵ
Ψϯ͕ϵϵϭ
Ψϵϵϴ
Ψϯϯϯ
Annual
☐
5,001
7,500
Ψϭϱ͕ϬϲϬ
Ψϱ͕ϮϬϬ
Ψϯ͕ϰϱϭ
Ψϲ͕ϰϬϵ
Ψϭ͕ϲϬϮ
Ψϱϯϰ
Annual
☐
7,501
10,000
ΨϮϬ͕ϰϰϬ
Ψϲ͕ϴϲϬ
Ψϰ͕ϳϱϯ
Ψϴ͕ϴϮϳ
ΨϮ͕ϮϬϳ
Ψϳϯϲ
Quarterly
☐
10,001
15,000
ΨϮϳ͕ϭϮϬ
Ψϵ͕ϯϴϬ
Ψϲ͕ϮϬϵ
Ψϭϭ͕ϱϯϭ
ΨϮ͕ϴϴϯ
Ψϵϲϭ
Quarterly
☐
15,001
25,000
Ψϰϰ͕ϴϮϬ
Ψϭϱ͕ϲϬϬ
ΨϭϬ͕ϮϮϳ
Ψϭϴ͕ϵϵϯ
Ψϰ͕ϳϰϴ
Ψϭ͕ϱϴϯ
Quarterly
☐
25,001
50,000
Ψϳϵ͕ϲϬϬ
ΨϮϳ͕ϰϬϬ
Ψϭϴ͕ϮϳϬ
Ψϯϯ͕ϵϯϬ
Ψϴ͕ϰϴϯ
ΨϮ͕ϴϮϴ
Quarterly
☐
50,001
75,000
ΨϭϮϲ͕ϴϮϬ
ΨϰϮ͕ϭϰϬ
ΨϮϵ͕ϲϯϴ
Ψϱϱ͕ϬϰϮ
Ψϭϯ͕ϳϲϭ
Ψϰ͕ϱϴϳ
Quarterly
☐
75,001
100,000
ΨϭϲϮ͕ϴϮϬ
Ψϱϯ͕ϱϮϬ
Ψϯϴ͕Ϯϱϱ
Ψϳϭ͕Ϭϰϱ
Ψϭϳ͕ϳϲϭ
Ψϱ͕ϵϮϬ
Quarterly
☐
100,001
150,000
ΨϮϬϴ͕ϮϮϬ
Ψϲϳ͕ϬϰϬ
Ψϰϵ͕ϰϭϯ
Ψϵϭ͕ϳϲϳ
ΨϮϮ͕ϵϰϮ
Ψϳ͕ϲϰϳ
Quarterly
☐
150,001
200,000
ΨϮϱϵ͕ϵϴϬ
Ψϴϭ͕ϵϬϬ
ΨϲϮ͕ϯϮϴ
Ψϭϭϱ͕ϳϱϮ
ΨϮϴ͕ϵϯϴ
Ψϵ͕ϲϰϲ
Quarterly
☐
200,001
300,000
ΨϮϵϲ͕ϰϰϬ
ΨϵϮ͕ϳϰϬ
Ψϳϭ͕Ϯϵϱ
ΨϭϯϮ͕ϰϬϱ
Ψϯϯ͕ϭϬϭ
Ψϭϭ͕Ϭϯϰ
Quarterly
☐
300,001
400,000
Ψϯϭϰ͕ϰϴϬ
Ψϵϴ͕ϲϰϬ
Ψϳϱ͕ϱϰϰ
ΨϭϰϬ͕Ϯϵϲ
Ψϯϱ͕Ϭϳϰ
Ψϭϭ͕ϲϵϭ
Quarterly
☐
400,001
500,000
Ψϯϯϴ͕ϮϴϬ
ΨϭϬϱ͕ϴϬϬ
Ψϴϭ͕ϯϲϴ
Ψϭϱϭ͕ϭϭϮ
Ψϯϳ͕ϳϳϴ
ΨϭϮ͕ϱϵϯ
Quarterly
☐
500,001
600,000
Ψϰϭϱ͕ϵϲϬ
ΨϭϯϬ͕ϰϰϬ
Ψϵϵ͕ϵϯϮ
Ψϭϴϱ͕ϱϴϴ
Ψϰϲ͕ϯϵϳ
Ψϭϱ͕ϰϲϲ
Quarterly
☐
600,001
750,000
Ψϰϴϭ͕ϵϲϬ
Ψϭϱϱ͕ϰϰϬ
Ψϭϭϰ͕ϮϴϮ
ΨϮϭϮ͕Ϯϯϴ
Ψϱϯ͕ϬϲϬ
Ψϭϳ͕ϲϴϳ
Quarterly
☐
750,001
1,000,000
Ψϱϲϰ͕ϬϴϬ
Ψϭϴϯ͕ϮϲϬ
Ψϭϯϯ͕Ϯϴϳ
ΨϮϰϳ͕ϱϯϯ
Ψϲϭ͕ϴϴϯ
ΨϮϬ͕ϲϮϴ
Quarterly
☐
1,000,001
1,400,000
ΨϲϬϯ͕ϲϴϬ
Ψϭϵϵ͕ϮϴϬ
Ψϭϰϭ͕ϱϰϬ
ΨϮϲϮ͕ϴϲϬ
Ψϲϱ͕ϳϭϱ
ΨϮϭ͕ϵϬϱ
Quarterly
☐
1,400,001
1,800,000
Ψϳϲϵ͕ϭϬϬ
ΨϮϰϱ͕ϲϰϬ
Ψϭϴϯ͕Ϯϭϭ
ΨϯϰϬ͕Ϯϰϵ
Ψϴϱ͕ϬϲϮ
ΨϮϴ͕ϯϱϰ
Quarterly
☐
1,800,001
2,200,000
Ψϵϯϲ͕ϴϲϬ
ΨϮϵϭ͕ϯϲϬ
ΨϮϮϱ͕ϵϮϱ
Ψϰϭϵ͕ϱϳϱ
ΨϭϬϰ͕ϴϵϰ
Ψϯϰ͕ϵϲϱ
Quarterly
☐
2,200,001
2,600,000
Ψϭ͕ϬϵϮ͕ϱϰϬ
Ψϯϯϱ͕ϬϬϬ
ΨϮϲϱ͕ϭϯϵ
ΨϰϵϮ͕ϰϬϭ
ΨϭϮϯ͕ϭϬϬ
Ψϰϭ͕Ϭϯϯ
Quarterly
☐
2,600,001
3,000,000
Ψϭ͕Ϯϯϲ͕ϱϰϬ
Ψϯϳϭ͕ϬϬϬ
ΨϯϬϮ͕ϵϯϵ
ΨϱϲϮ͕ϲϬϭ
ΨϭϰϬ͕ϲϱϬ
Ψϰϲ͕ϴϴϯ
Quarterly
☐
3,000,001
3,500,000
Ψϭ͕ϯϵϴ͕ϱϰϬ
Ψϰϭϭ͕ϱϬϬ
Ψϯϰϱ͕ϰϲϰ
Ψϲϰϭ͕ϱϳϲ
ΨϭϲϬ͕ϯϵϰ
Ψϱϯ͕ϰϲϱ
Quarterly
☐
3,500,001
4,000,000
Ψϭ͕ϱϳϴ͕ϱϰϬ
Ψϰϱϲ͕ϱϬϬ
ΨϯϵϮ͕ϳϭϰ
ΨϳϮϵ͕ϯϮϲ
ΨϭϴϮ͕ϯϯϮ
ΨϲϬ͕ϳϳϳ
Quarterly
☐
4,000,001
4,500,000
Ψϭ͕ϳϱϴ͕ϱϰϬ
ΨϱϬϭ͕ϱϬϬ
Ψϰϯϵ͕ϵϲϰ
Ψϴϭϳ͕Ϭϳϲ
ΨϮϬϰ͕Ϯϲϵ
Ψϲϴ͕ϬϵϬ
Quarterly
☐
4,500,001
5,000,000
Ψϭ͕ϵϯϴ͕ϱϰϬ
Ψϱϰϲ͕ϱϬϬ
Ψϰϴϳ͕Ϯϭϰ
ΨϵϬϰ͕ϴϮϲ
ΨϮϮϲ͕ϮϬϳ
Ψϳϱ͕ϰϬϮ
Quarterly
☐
5,000,001
5,500,000
ΨϮ͕ϭϭϴ͕ϱϰϬ
Ψϱϵϭ͕ϱϬϬ
Ψϱϯϰ͕ϰϲϰ
ΨϵϵϮ͕ϱϳϲ
ΨϮϰϴ͕ϭϰϰ
ΨϴϮ͕ϳϭϱ
Quarterly
☐
5,500,001
6,000,000
ΨϮ͕Ϯϵϴ͕ϱϰϬ
Ψϲϯϲ͕ϱϬϬ
Ψϱϴϭ͕ϳϭϰ
Ψϭ͕ϬϴϬ͕ϯϮϲ
ΨϮϳϬ͕ϬϴϮ
ΨϵϬ͕ϬϮϳ
Quarterly
☐
6,000,001
6,500,000
ΨϮ͕ϰϳϴ͕ϱϰϬ
Ψϲϴϭ͕ϱϬϬ
ΨϲϮϴ͕ϵϲϰ
Ψϭ͕ϭϲϴ͕Ϭϳϲ
ΨϮϵϮ͕Ϭϭϵ
Ψϵϳ͕ϯϰϬ
Quarterly
☐
6,500,001
7,000,000
ΨϮ͕ϲϱϴ͕ϱϰϬ
ΨϳϮϲ͕ϱϬϬ
Ψϲϳϲ͕Ϯϭϰ
Ψϭ͕Ϯϱϱ͕ϴϮϲ
Ψϯϭϯ͕ϵϱϳ
ΨϭϬϰ͕ϲϱϮ
Quarterly
☐
7,000,001
7,500,000
ΨϮ͕ϴϯϴ͕ϱϰϬ
Ψϳϳϭ͕ϱϬϬ
ΨϳϮϯ͕ϰϲϰ
Ψϭ͕ϯϰϯ͕ϱϳϲ
Ψϯϯϱ͕ϴϵϰ
Ψϭϭϭ͕ϵϲϱ
Quarterly
X






	


		
	


Contexture HIE Parঞcipaঞon Agreement 
HIE PA Cover Sheet 
Revised 2/12/2026 
Page 1 of 3 
CONTEXTURE HIE PARTICIPATION AGREEMENT 
Cover Sheet 

Descripঞon of this Agreement 
Contexture is a nonprofit organizaঞon that provides electronic health informaঞon exchange 
(“HIE”) and HIE-related services. Parঞcipant desires to parঞcipate in Contexture’s HIE under 
the terms and condiঞons of this HIE Parঞcipaঞon Agreement (“Agreement”). 
 
Parঞcipant Informaঞon 
Legal Name of Parঞcipant 
Enঞty: 
 
Trade Name/Doing 
Business As: 
 
Corporate Address: 
 
Tax ID Number (TIN): 
 
Enঞty Type(s):  
܆Healthcare Provider 
܆Health Plan 
܆Public Health Authority 
܆Medical Examiner or Coroner 
܆Organ Procurement Organizaঞon 
☐Value-Based Organizaঞon 
 
 
Contact for Noঞce under 
Secঞon 13.2 (Noࢼce) of 
the HIE General Terms 
and Condiঞons:  
 
 
Privacy Officer Contact: 
 
Security Officer Contact: 
 
All Contacts and the associated contact informaঞon provided in this Cover Sheet may be 
changed at any ঞme and without the need for a formal contract amendment by a) emailing the 
Contexture Help Desk; b) emailing the Contexture engagement team member assigned to the 
Parঞcipant; or c) emailing getconnected@contexture.org. 
Contract Term & Renewals 
Effecঞve Date: 
Agreements fully executed before January 1, 2026, have an 
Effecঞve Date of January 1, 2026. 
Agreements fully executed a[er January 1, 2026, have an 
Effecঞve Date of the date of the last signature.  

((-"
 ,
((-"% , %%-(. %+
!)-
%
%%-(
%%-(
!(
&()#$)
((-"
 ,


((-"% , %%-(. %+
&*""*!..! %%-(. %+



!+!
'
%%-(



	
*"
*!..!






	


		
	


Contexture HIE Parঞcipaঞon Agreement 
HIE PA Cover Sheet 
Revised 2/12/2026 
Page 2 of 3 
Iniঞal Term: 
The Iniঞal Term of this Agreement shall run from the Effecঞve 
Date unঞl December 31 of that year. 
Renewals: 
This Agreement will automaঞcally renew for addiঞonal one (1) 
year terms, beginning January 1 a[er the expiraঞon of the Iniঞal 
Term, unঞl the terminaঞon of this Agreement as provided for in 
the HIE General Terms and Condiঞons or elsewhere in the 
Agreement. 
Documents that are Part of this Agreement  
The Parঞes to this Agreement are (1) Contexture, a Colorado nonprofit corporaঞon, and (2) all 
individuals and enঞঞes listed as a Parঞcipant or Affiliate in any document that is part of the 
Agreement. Each Party acknowledges and agrees that this Agreement includes all the following 
documents, which are incorporated by reference and legally binding on all Parঞes:  
 
(1) This Cover Sheet. 
 
(2) HIE General Terms and Condiঞons. These are the general contract terms that govern 
the use of the HIE and Services by Parঞcipant and its Authorized Users. Contexture will 
noঞfy Parঞcipant of material changes to the HIE General Terms and Condiঞons by 
giving noঞce in accordance with Secঞon 1.4 (Changes to HIE General Terms and 
Condiࢼons) of the HIE General Terms and Condiঞons. 
 
(3) Trusted Exchange Addendum. This Addendum applies if Parঞcipant parঞcipates, 
through Contexture, in the exchange of health informaঞon through Trusted Exchange 
Networks. Contexture will noঞfy Parঞcipant of material changes to this Addendum by 
giving noঞce in accordance with Secঞon 13.2 (Noࢼce) of the HIE General Terms and 
Condiঞons. 
 
(4) Business Associate Agreement (“BAA”). The BAA applies to Parঞcipant’s access to and 
use of the HIE and Services. 
 
(5) Special Terms and Condiঞons, which provide specialized contract terms for certain 
enঞঞes, arrangements, and Parঞcipant Types:  
x 
Medical Examiners and Coroners 
x 
Organ Procurement Organizaঞons 
x 
Public Health Authoriঞes 
x 
Third-Party Interfaces 
x 
Value-Based Organizaঞons 
 
The applicable Special Terms and Condiঞons are any that are a‚ached to this 
Agreement, as well as any that are subsequently executed by the Parঞes. 
 
(6) Statement(s) of Work: All statement(s) of work executed by the Parঞes for access to or 
use of the HIE or any Service.  
 






	


		
	


Contexture HIE Parঞcipaঞon Agreement 
HIE PA Cover Sheet 
Revised 2/12/2026 
Page 3 of 3 
(7) HIE Support and Service Level Addendum, available on Contexture’s website. This 
Addendum describes the support and service levels Contexture will provide for the HIE 
and Services. Contexture may, at its discreঞon, update this Addendum from ঞme to 
ঞme. Parঞcipant is responsible for checking the Addendum for the current support and 
service levels. 
 
(8) Contexture Policies, available on Contexture’s website. These Policies govern the 
acঞviঞes of Contexture and HIE Parঞcipants related to the Services and HIE Data, 
including the Permi‚ed Purposes. Contexture will noঞfy Parঞcipant of material changes 
to the Contexture Policies by giving noঞce in accordance with Secঞon 2.7 (Contexture 
Policies; Changes) of the HIE General Terms and Condiঞons. 
 


All capitalized words and phrases that are not defined in this Cover Sheet have the meanings 
given to them in the HIE General Terms and Condiঞons and or elsewhere in the Agreement. 
 
Each of the individuals signing below represents and warrants that they are signing with full and 
complete authority to bind the Party to this Agreement. 

CONTEXTURE, a Colorado nonprofit 
corporation 
Signature: 
 
 
 
 
 
Printed Name:  
 
 
 
 
Title: 
 
 
 
 
 
 
Date:  
 
 
 
 
 
 
 
 
Signature: 
 
 
 
 
 
Printed Name:  
 
 
 
 
Title: 
 
 
 
 
 
 
Date:  
 
 
 
 
 

!)-
%
%%-(






	


		
	

Certificate Of Completion
Envelope Id: CCD26F61-C730-8E80-8124-3177B66C3727
Status: Sent
Subject: Complete with Docusign: City of Goodyear Fire. SOW Health Care Provider Gold Arizona 35 Subsidy 
Participant Name: City of Goodyear dba Goodyear Fire Department
Source Envelope: 
Document Pages: 22
Signatures: 0
Envelope Originator: 
Certificate Pages: 2
Initials: 0
Misty Kent
AutoNav: Enabled
EnvelopeId Stamping: Enabled
Time Zone: (UTC-07:00) Mountain Time (US & Canada)
2000 S Colorado Blvd
Ste 1200
Denver, CO  80222
misty.kent@contexture.org
IP Address: 2600:1011:a18a:
Record Tracking
Status: Original
             6/2/2026 11:21:28 AM
Holder: Misty Kent
             misty.kent@contexture.org
Location: DocuSign
Signer Events
Signature
Timestamp
Bryan Langley
bryan.langley@goodyearaz.gov
Security Level: Email, Account Authentication 
(None)
Sent: 6/4/2026 11:03:52 AM
Resent: 6/8/2026 12:23:50 PM
Resent: 6/11/2026 2:15:49 PM
Resent: 6/11/2026 3:28:39 PM
Electronic Record and Signature Disclosure: 
      Not Offered via Docusign
Kelly Procopio
kelly.procopio@contexture.org
Security Level: Email, Account Authentication 
(None)
Electronic Record and Signature Disclosure: 
      Not Offered via Docusign
In Person Signer Events
Signature
Timestamp
Editor Delivery Events
Status
Timestamp
Agent Delivery Events
Status
Timestamp
Intermediary Delivery Events
Status
Timestamp
Certified Delivery Events
Status
Timestamp
Nicole Teer
nicole.teer@goodyearaz.gov
Security Level: Email, Account Authentication 
(None)
Electronic Record and Signature Disclosure: 
      Not Offered via Docusign
Carbon Copy Events
Status
Timestamp
Contexture Contracts
contracts@contexture.org
Security Level: Email, Account Authentication 
(None)
Electronic Record and Signature Disclosure: 
      Not Offered via Docusign

Carbon Copy Events
Status
Timestamp
Misty Kent
misty.kent@contexture.org
Security Level: Email, Account Authentication 
(None)
Electronic Record and Signature Disclosure: 
      Not Offered via Docusign
Witness Events
Signature
Timestamp
Notary Events
Signature
Timestamp
Envelope Summary Events
Status
Timestamps
Envelope Sent
Hashed/Encrypted
6/4/2026 11:03:52 AM
Envelope Updated
Security Checked
6/11/2026 2:15:48 PM
Envelope Updated
Security Checked
6/11/2026 2:15:48 PM
Envelope Updated
Security Checked
6/11/2026 2:15:48 PM
Envelope Updated
Security Checked
6/11/2026 3:28:38 PM
Payment Events
Status
Timestamps