CTR053289 A4.pdf

CONTRACT AMENDMENT

ARIZONA DEPARTMENT OF

HEALTH SERVICES

OFFICE OF PROCUREMENT

150 N 18th Ave., Ste. #530 Phoenix, Arizona 85007

CONTRACT NO.: CTR053289 AMENDMENT NO.: 4 Procurement Officer Nathaniel Thomas

The image part with relationship ID rId3 was not found in the file.

Emergency Medical Services (EMS) and Hospital Information Registry System

Effective upon signature by both parties it is mutually agreed that the Contract referenced in this Amendment Four (4) is amended as follows:

1. Pursuant to the Uniform Terms and Conditions, Provision Five (5) Contract Changes, Section 5.1 Amendments, the

Contract is hereby amended as follows:

1.1. The Scope of Work is revised and replaced; and

1.2. The Price Sheet is revised and replaced.

ALL CHANGES ARE REFLECTED IN RED

ALL OTHER PROVISIONS SHALL REMAIN IN THEIR ENTIRETY

Contractor hereby acknowledges receipt and acceptance of above amendment and that a signed copy must be filed with the Procurement Office before the effective date

The above referenced Contract Amendment is hereby executed this _____ day of __________ 2022 at Phoenix, Arizona

(To be filled out by Procurement Office) Contractor Signature

Contractor Signature Date

Authorized Signatory’s Name and Title

ImageTrend, Inc.

Contractor’s Name Procurement Officer Signature

Joseph T. Graw (Jan 10, 2024 14:09 CST)

Jan 10, 2024

Joseph T. Graw CGO Gina Corwin

Digitally signed by Gina Corwin Date: 2024.01.17 15:18:31 -07'00'

Scope of Work

CONTRACT NO.: CTR053289

1. Background

1.1. The Arizona Department of Health Services (ADHS) Bureau of Emergency Medical Services (EMS) and Trauma System (BEMSTS) is responsible for protecting and promoting the health and safety of residents and visitors to Arizona. ADHS coordinates this process by establishing and administering a statewide system of EMS and trauma care. The collection of EMS and trauma data through its registries allows for the functions of this responsibility (Arizona Revised Statutes § 36-2208);

1.2. The mission of the BEMSTS is to protect the health and safety of people requiring emergency medical services;

promote improvements in Arizona's EMS and trauma system through research and education of the public and EMS providers; and provide courteous, professional and responsible service to the public and EMS providers;

1.3. The State of Arizona consists of fifteen (15) counties with a total population of more than six (6.5) million residents.

Additionally, Arizona is the home to a diverse culture of American Indians. The twenty-two (22) tribes comprise approximately five-point-six percent (5.6%) of the population, and twenty-nine percent 29% of the land;

1.4. The State’s EMS and Trauma System is a combination of public, private, and tribal organizations that are committed to inter-organizational cooperation for the benefit of EMS patients in Arizona;

1.5. Arizona Prehospital Information and EMS Registry System (AZ-PIERS) allows EMS Arizona agencies to securely submit electronic Patient Care Reports (ePCR) individually or in batches. Arizona EMS agencies may use the enterprise license distributed by ADHS or their own National Emergency Medical Services Information System (NEMSIS) compliant ePCR software to transmit records. AZ-PIERS has helped transition Arizona EMS agencies away from their dependency on paper and toward an electronic data driven practice of care; and

1.6. An important component of AZ-PIERS is the Premier EMS Agency Program (PEAP), a quality assurance initiative that focuses on four (4) time sensitive injuries/illnesses (Stroke, ST- segment Myocardial Infarction (STEMI), Major Trauma, and Out-of-Hospital Cardiac Arrest). PEAP requires Arizona EMS agencies to submit data to AZ- PIERS, have leadership commitment, and ensure that data drives quality improvement processes internally.

2. Objective

2.1. Arizona Revised Statutes (A.R.S.) §36-2402 establishes quality assurance initiatives to improve systems of care in Arizona. The objective of this Contract is to provide, update, and maintain the AZ-PIERS. The Contractor’s prehospital registry software must meet all components of this Contract;

2.2. The Contractor shall provide all software, labor, supervision, tools, materials, training, and incidentals necessary to manage all of the successful day to day operations outlined below;

2.3. The Contract shall allow for the entry, collection, extraction, and analysis of prehospital data required to optimize the care of EMS patients. The following activities and tasks allow ADHS to describe and report on the EMS system in the State. Additionally, information gathered in the system will assist stakeholders to determine the best policies and interventions for treatment;

2.4. To provide ongoing maintenance and support of AZ-PIERS; the Contractor shall focus on low to no-cost methods that discourage the need for disparate systems; The State EMS database shall be scalable, redundant, and secure to protect against overload, security breaches, or operational failures; and

2.5. The Contractor shall provide a Licensing Management System (LMS) that provides a modernized approach to the EMS licensing and certification process. The LMS public portal shall be Americans with Disabilities Act (ADA) compliant, improve automation, validation, issuance, reporting, investigation, tracking and data organization efforts as well as allows for future interoperability and interconnectivity between the current AZ-PIERS and LMS.

3. Tasks

The Contractor shall:

3.1. Provide, manage, and support a fully functional statewide EMS enterprise license for distribution as determined by ADHS, that can collect prehospital patient care records, transmission to/from hospitals, and have the capability to provide analytics based on the Arizona defined dataset;

3.2. Successfully receive and maintain current NEMSIS certification;

3.3. Support all NEMSIS Versions currently accepted by NEMSIS;

3.4. Migrate from NEMSIS 3.X to future versions in accordance with the NEMSIS-TAC published/adopted implementation timeline/schedule, or as determined by ADHS;

3.5. Provide raw data to ADHS with the necessary logic, structure, relationship, schema requirements, and reasonable level of support to perform data extraction, analysis, and reporting as needed;

3.6. Provide any business logic/rules to ADHS to understand tables and relevant data elements to the State;

3.7. Receive data from stakeholders, other third party ePCR vendors, and ADHS. This includes any relevant schema requirements, or reasonable level of support to other programs or vendors so they may successfully submit data to AZ-PIERS from other NEMSIS compliant vendors;

3.8. Notify ADHS immediately in the event of a security breach;

3.9. Implement and follow the standards and guidelines required by ADHS for security;

3.10. Provide ADHS a system that can be managed via commonly used Internet browsers;

3.11. The system shall allow for:

3.11.1. Statewide assigned permission levels,

3.11.2. User accounts controlled at the agency level to assign permission levels, by an agency,

3.11.3. Security and restrictions at the applicable levels (EMS agency will only be able to view their own data, providers will only view their own runs; supervisors will be able to view their staff’s runs, base hospitals will be able to view their Arizona EMS agencies for medical direction),

3.11.4. The capability to activate/inactivate data elements, variables, users, permission groups, Arizona EMS agencies, hospitals, and other aspects of the system, and

3.11.5. The validation of incoming data based on rules determined by ADHS.

3.12. Provide a Project Manager who shall:

3.12.1. Serve as primary contact as requested by ADHS for any projects,

3.12.2. Attend, lead, and prepare materials for meetings as requested by ADHS,

3.12.3. Ensure all necessary operational components are completed prior to the embedded system,

3.12.4. Troubleshoot and correct problems prior, during, and after the embedded system, and

3.12.5. Designate an alternate contact for when the Project Manager is unavailable.

3.13. Provide training that includes but is not limited to the following:

3.13.1. User manual that is available online and in PDF format, and

3.13.2. Pre-recorded topic overviews in video format available to users at all times.

3.14. Ensure ADHS has the ability to populate data to an agency’s ePCR submission;

3.14.1. These populated fields must be locked and controlled solely by ADHS,

3.14.2. These populated fields must be able to be embedded into the analytical components of reports,

3.14.3. The populated fields must be able to automatically update as agreed upon by the Contractor and

ADHS, and

3.14.4. These populated fields must allow for a comment section that can provide AZ-PIERS with feedback from the providers on the accuracy of the values.

3.15. Ensure ADHS the ability to develop reports that can be shared with stakeholders through the system;

3.15.1. Examples may include but are not limited to performance improvement reports for STEMI, stroke, cardiac arrest, major trauma, sepsis, drownings, and

3.15.2. ADHS must be able to schedule and automatically run reports with stakeholders throughout the system.

3.16. The development and ability to provide an electronic method of communication of electronic patient care records from the state trauma vendor;

3.16.1. This communication tool would be able to search the appropriate patient is found, and have the pre-hospital elements in the trauma system be auto filled by AZ-PIERS, and

3.16.2. Ensure outcome elements in the Contractor’s application the ability to auto filled by ADHS, or its designee, after the linkage has been established.

3.17. Develop, support, and provide linkage capabilities for the Arizona Health Information Exchange, as determined by ADHS;

3.18. Provide an ability to communicate and perform State Quality Assurance initiatives in AZ-PIERS with participants including canned reports for PI tools as decided by ADHS. Examples include Segment Elevation Myocardial Infarction (STEMI), Stroke, Cardiac Arrest, Major Trauma, and any additional initiatives (the specific content and format for AZ-PIERS will be agreed upon by ADHS, AZ-PIERS participants, and the Contractor):

3.18.1. Allow for an automated, scheduling function for all reports (including canned) to be shared among participants,

3.18.2. Develop the ability to create reports that allow Arizona EMS agencies to compare themselves with a statewide aggregate, or various agency blinded grouping and benchmarks, as determined by the Contractor and ADHS, and

3.18.3. Create an additional export capability to allow reports to be exported to plain text.

3.19. Contractor shall provide its Health Information Hub (HIH) to transfer and transform pre-hospital data into hospital format that meets ADHS’s Elite EMS electronic patient care reporting system (Elite EPCR/AZ-PIERS) and Health Current, a non-profit organization providing secure platform for sharing electronic health information (HIE), defined as the HEALTH NETWORK so that HEALTH NETWORK can receive and transmit to hospitals;

3.20. The purchase of Contractor’s Health Information Hub (HIH) as an Integration as a Service (‘IaaS’). Integration as a Service (‘IaaS’) means a single integrated software and services package which includes:

3.20.1. Initial set-up of the software,

3.20.2. Configuration of the software as necessary to meet the Scope of Work,

3.20.3. Ongoing licensing to the software for the term of the contract,

3.20.4. Providing ongoing maintenance, support, monitoring of the connection, and

3.20.5. Providing necessary hardware, internet connectivity, and other resources necessary to keep the IaaS working.

3.21. Contractor shall work with ADHS to define the standard triggers needed to identify pre-hospital records to be exported out of Elite EPCR/AZ-PIERS to the HIH;

3.22. ADHS will help the Contractor test the exchange of data through test patients and pilot EMS agencies;

3.23. ADHS will facilitate compliance as necessary for AZ-PIERS to interchange data with HEALTH NETWORK;

3.24. ADHS shall pay such fees as mutually agreed upon in appropriate proposals or statements of work and supported by a Purchase Order as necessary to enable the parties to successfully complete the project;

3.25. Contractor’s obligations are limited to those outlined above; other obligations will be considered out-of- scope and require a separate mutually agreed Amendment to address any out-of-scope requests;

3.26. Contractor shall:

3.26.1. Configure ADHS’ Elite EPCR/AZ-PIERS for one (1) connection endpoint for export,

3.26.2. Set up and install HIH for ADHS,

3.26.3. Set up a standard HIH data connection to HEALTH NETWORK, as detailed under Technical Standards Used below,

3.26.4. Set up a standard HIH file format to send to HEALTH NETWORK, as detailed under Technical Standards Used below,

3.26.5. Set up triggers in Elite EPCR/AZ-PIERS for exporting data,

3.26.6. Configure connections in accordance with the HIH Integration Guide. The technical standards represent a selection in technical approach selected from the many technical approaches available under the HIH Integration Guide. ADHS, Contractor and HEALTH NETWORK may mutually agree to change technical approaches, if necessary, however, such changes must be incorporated in a written Amendment to this Contract. ADHS is advised that certain technical approaches may require additional work, or re-work, and Contractor at its option may withhold agreement if no new funding is committed to the increased workload due to a change as contemplated by this section. With the exception of any changes to data elements or functionality resulting from a change made by Contractor either due to altering ImageTrend custom elements or by a change required by NEMSIS due to updated versions or an update to Health Level Seven (HL7) standards. In that case, no cost would be incurred by ADHS and an additional scope of work would not be required, unless the Contractor deems an Amendment necessary for clarity of technical adjustments needed to maintain the integration and exchange of data between the HIH and HEALTH NETWORK.;

3.26.7. Technical Standards Used:

3.26.7.1 Connection;

3.26.7.2 Direct Virtual Private Network (VPN) for two (2) way communication:

3.26.7.2.1 Four (4) total ports opened,

3.26.7.2.2 UAT HL7 ADT A04,

3.26.7.2.3 Prod HL7 ADT A04,

3.26.7.2.4 UAT HL7 MDM Summary, and

3.26.7.2.5 Prod HL7 MDM Summary,

3.26.7.3 File format send from Elite EMS to HEALTH NETWORK 25.6.7.1.3.1

3.26.7.3.1 HL7 ADT A04 Message with the following fields:

3.26.7.3.1.1 First Name (ePatient.03),

3.26.7.3.1.2 Last Name (ePatient.02),

3.26.7.3.1.3 Date of Birth (ePatient.17), and

3.26.7.3.1.4 Gender (ePatient.13),

3.26.7.3.2 HL7 MDM Summary Message with the following fields:

3.26.7.3.2.1 First Name (ePatient.03),

3.26.7.3.2.2 Last Name (ePatient.02),

3.26.7.3.2.3 Date of Birth (ePatient.17), and

3.26.7.3.2.4 Gender (ePatient.13),

3.26.7.4 File format inbound from HEALTH NETWORK:

3.26.7.4.1 Hl7 v2.6 ADT A03 and ADT A08:

3.26.7.4.1.1 Required each message:

3.26.7.4.1.1.1 EMS Encounter Number

(itRecord.001), and

3.26.7.4.1.1.2 Agency Number (dAgency.02),

3.26.7.4.1.2 Optional in Each Message:

3.26.7.4.1.2.1 First Name (itOutcome.025),

3.26.7.4.1.2.2 Last Name (itOutcome.027),

3.26.7.4.1.2.3 Date of Birth (itOutcome.029),

3.26.7.4.1.2.4 Patient Address (itOutcome.032),

3.26.7.4.1.2.5 Patient City (itOutcome.035),

3.26.7.4.1.2.6 Patient State (itOutcome.036),

3.26.7.4.1.2.7 Patient Postal Code (itOutcome.037),

3.26.7.4.1.2.8 Hospital Admission Date

(eOutcome.11),

3.26.7.4.1.2.9 Hospital Discharge Date

(eOutcome.16),

3.26.7.4.1.2.10 Insurance Information

3.26.7.4.1.2.11 Insurance Name (ePayment.58),

3.26.7.4.1.2.12 Insurance Org Name (ePayment.10),

3.26.7.4.1.2.13 Insurance Group Number

(ePayment.17), and

3.26.7.4.1.2.14 Insurance Member Number

(epayment.18)

3.26.7.4.1.2.15 Diagnosis Information

(eOutcome.13),

3.26.7.4.1.2.16 Procedures (Appended to

itOutcome.024), and

3.26.7.4.1.2.17 Discharge Disposition

(eOutcome.02);

3.26.8. Provide project management necessary to project completion, including:

3.26.8.1 Communication between ADHS and HEALTH NETWORK;

3.26.8.2 Project Status updates:

3.26.8.2.1 Bi-weekly status updates between ADHS, HEALTH NETWORK and

Contractor stakeholders,

3.26.9. Provide hosting for the Contractor software, and

3.26.10. Provide application support for Contractor software.

3.27. ADHS, Contractor and HEALTH NETWORK agree based on the assumption that HEALTH NETWORK shall:

3.27.1. In cooperation with each entity, take such steps as reasonably necessary to enable the Contractor to successfully complete the project as outlined above insofar as it concerns interfaces, personnel, software, data, or other materials within HEALTH NETWORK’s control, such steps include but are not limited to:

3.27.1.1 Configuring and setting up HEALTH NETWORK software to receive a HL7 A01 and HL7 MDM message containing the pre-hospital data and to parse such data as necessary, and;

3.27.1.2 Work with the Contractor and ADHS to find and correct defects, including when it is not immediately clear which party controls the software causing the defects,

3.27.2. Take such steps as are reasonably necessary to support the completed project after each and all phases have gone into live production use,

3.28. Any task, deliverable, obligation, not contained or described in this Amendment Two (2) is not within the scope;

3.29. The Contractor is not responsible for any fee or charge originating from HEALTH NETWORK or any other third party, other than agreed upon within Amendment Two (2);

3.30. Develop, support, and provide the LMS to include the following key features and dashboards:

3.30.1. Personnel/Vehicle/Service Licensure: Internal and external stakeholders shall be able to manage multiple elements of personnel user profiles, licenses, applications, contact information and training(s) completed. Stakeholders shall be able to set up alerts and track statuses from start to finish:

3.30.1.1. Air and Ground Ambulance Registration shall include vehicle registration, initial and renewal ground and air registration applications, process ground and air ambulance applications with timeframe management, ambulance inspections, issue registration with official state seal and signatures, ability to refer or flag accounts for further review and/or enforcement action, online payment with the ability to assess late fees, and data reports;

3.30.2. Public Lookup: Online public service to lookup Emergency Medical Care Technician (EMCT), agency, and training courses,

3.30.3. Training and Course Management: Shall record and track training and exam information of approved courses associated with certifications and licenses. ADHS shall have the capability of recording the details of training courses that can be created from templates or manual process, course approval and denial options, attendee enrollment, audits, issue certificates, refer or flag training program accounts for further review and/or enforcement action, optional online payment and data reports. External and internal users shall be able to track continuing education credits and training completed to ensure requirements to obtain certifications are met,

3.30.4. Online Payments: LMS shall support online payments to be submitted by external users and received by ADHS for fees through the State of Arizona payment portal operated by jBilling via the public portal,

3.30.5. Inspections: Shall have the ability to conduct inspections and record deficiencies on facilities or vehicles. This functionality shall allow an internal user to create a library of checklists, schedule inspections, and record deficiencies. Optional inspection fees may be mandated and payment may be received through the payment portal. Automated inspection workflow shall be configured to add notes and alerts, update statuses, record deficiencies, schedule re-inspections, send correspondence, or set associated dates. The inspection dashboard shall be a tablet friendly module and capable of recording electronic consent,

3.30.6. Applicant Correspondence: Email correspondence that shall be available automatically or manually through the system. The LMS shall provide email templates to be built in that will automate manual processes by pulling specific data from people, places, or things. Correspondence sent through the LMS shall be saved with the record it was sent to for easy reference. LMS shall document who sent a message, as well as the time and date the message was sent,

3.30.7. Base Hospital and Trauma: Shall include base hospital and trauma applications and audit forms, process applications with time frame management, deficiency review and automated and manual correspondence, issue certificate with official state seal and signatures, ability to refer or flag accounts for further review and/or enforcement action, online payment with the ability to assess late fees, data reports,

3.30.8. Reporting Tools: Integrated data reporting tools that shall allow ADHS to gain insight on key performance indicators and metrics that play a critical role in improving processes and efficiencies,

3.30.9. Enforcement: Provide a dashboard that shall be available to record investigation for paper complaints

(electronic and manual entry option) and process complaints with timeframe management,

3.30.10. Dashboards: The LMS shall provide configurable dashboards/task lists that shall allow internal users to prioritize, track, and assess work based on the required completion date and volume. The dashboards shall be configured to meet one’s specific needs,

3.30.11. Provide an EMCT applications dashboard with application status and timeframe tracking capabilities, clock/time, issue electronic certification cards, individualized or mass EMCT correspondence by specific criteria, automated notifications including: expiration alerts, correcting application issues, application statutes, expiring certificates, etc., verification of National Registry Emergency Medical Technicians (NREMT) status and continuing education requirements for certification, ability to refer or flag EMCT accounts for further review and/or enforcement action, online payment with the ability to assess late fees, and data reports, and

3.30.12. Provide Ambulance Organization, including dashboards with timeframe tracking capabilities, Certificate of Necessity (CON) and rate adjustment applications (configurable forms or allow for upload of current form), air licensing applications, CON/Contract management (upload, review, and track status of multiple documents including: contracts, financial reports, proof of insurance, response times, etc.), process applications, deficiency review and automated and manual correspondence, ability to publish CON and rate application, issue certificates and licensing with official state seal and signatures, automated notifications regarding application statutes, expiring certificates, etc., ability to refer or flag accounts for further review, online payment with the ability to assess late fees, and enforcement action, and data reports.

3.31. Designate an implementation coordinator that shall:

3.31.1. Schedule a “kick-off” call with ADHS to outline the implementation process, and provide an overview.

3.32. Allow ADHS to have control over what data is visible to external users within the LMS;

3.33. Internal and external stakeholders shall have the ability to search for the following:

3.33.1. EMCT: Ability to search EMCT name (F/L), certification number, current cert level, active or inactive status, issue date and expiration date; and

3.33.2. ADHS: Ability to search an Agencies name, certification number (CON number), Organization profile, organization assignments (geographic area), review published license application (Certificate of Necessity), attachments and contract applications, and Ambulance Revenue and Cost Reports (ARCR).

3.34. Application Timeout: internal and external users should be automatically timed out after a specific timeframe;

3.35. Audit Logging: LMS shall have visibility into changes made to any object;

3.36. Role Management: LMS shall have the ability for specified ADHS users to increase or decrease the permissions of users which allows for specific information to be accessed, edited, and processed;

3.37. Data Migration: Contractor shall assist in the migration of current portal data to the LMS and provide to ADHS migration mapping documentation with explanation and instructions on multiple account consolidations;

3.38. Release Management & Infrastructure Upgrade: Shall include well-established communication strategy with information provided for major releases and prioritization of major enhancements, scheduled release management and release notes, vendor quality assurance, training guide updates, published downtimes.

3.39. Provide a single point of contact to review various facets of the application and provide guidance on best practices; includes a one hour per week phone check in, coordination of upgrades when/if needed and an advocate for non-support related items; and

3.40. Track and report any system issues or bugs and provide reporting and resolution information.

3.41. Develop and implement an urbanicity determination batch process solution on Elite to calculate urbanicity for

2022 and 2023 data for the ADHS Response Time Report.

3.42. Develop and implement a solution to take existing geocoded source data that has been encoded by ImageTrend as part of Continuum and process each instance to assign applicable urbanicity value based on shapefiles provided by ADHS.

3.42.1. This solution shall be created to allow data to be processed as needed. The solution shall be flexible enough to meet future needs.

3.43. The urbanicity value will be written to a supplemental question and optionally be moved to a custom element in Elite, ReportWriter and Continuum.

4. Deliverables

4.1. Provide a fully functional enterprise license that allows for the entry, collection, storage, extraction, and analysis of prehospital data;

4.2. Provide evidence that the product meets and maintains security standards (ADHS-ITS, ADOA-ASET, and

HIPAA);

4.3. Develop that all features of its applications provide multiple security levels, which can allow or deny access to different portions of the system capabilities such as reporting, data entry, and any other feature;

4.4. Provide additional functions, which include but are not limited to internal mailing, alerts, and managements of other users and system administration;

4.5. Provide technical support for all products and applications for ADHS staff and stakeholders;

4.6. Provide Software Agreement and Software Licensing Agreement;

4.7. Provide a copy of the LMS data base for download to ADHS upon the frequency agreed up after go-live (referred to as “Database Backups” on Price Sheet);

4.8. Provide a train the trainer model, that ADHS can record for future use, training guides for both internal and external users;

4.8.1. Four (4), two (2) hour long webinar training sessions, and

4.8.2. Three (3), on site training sessions for ADHS staff, and

4.9. Provide uniform resource locator (URL) to ADHS with login credentials for LMS.

4.10. Process 2022 incident data to assign urbanicity by January 1, 2024.

4.11. Process 2023 incident data to assign urbanicity within two weeks of the data being provided by ADHS.

5. Requirements

5.1. Ensure compliance with all Contract requirements;

5.2. Provide a system that is compliant with the State of Arizona Information Technology and Standards;

5.3. Provide an audit trail to record and monitor access to the application;

5.4. Comply with all provisions of the relevant Statewide Information Security and Privacy Office (SISPO) – Statewide Security Policies and Standards as are pertinent to the Contractor’s operation;

5.5. Comply with all applicable federal, state and local laws and regulations;

5.6. Provide a log of authorized users that will be accessing personal and protected health data. All access to the State system must be able to be tracked and monitored for breaches, issues, or problems that may arise. The Contractor accepts and acknowledges their responsibility in protecting health data and shall produce their processes and safety check as requested by ADHS;

5.7. Ensure the system shall be HIPAA complaint in all privacy and security rules as well as accepted data formats;

5.7.1. The system shall also include procedures for safeguarding the system from unauthorized modifications to the application programs and the data contained in the application.

5.8. Allow for an unlimited number of users as determined by ADHS in AZ-PIERS;

5.9. Provide, manage, and support a fully functional statewide EMS enterprise license for distribution as determined by ADHS, that can collect prehospital patient care records, transmission to/from hospitals, and have the capability to be analyzed based on the Arizona defined dataset at all times;

5.10. Maintain a NEMSIS compliant version as determined by ADHS;

5.11. Include all necessary costs incurred by the operation of the system. This includes but is not limited to updates, software costs, servers and other hardware;

5.12. Integrate with essential state systems software and host environments;

5.13. Maintain functionality and security to personalize access across individuals, Arizona EMS agencies, hospitals, regions, with the option to add participants at no additional charge, upon request by ADHS;

5.14. Support commonly used hardware which includes but not limited to desktop computers, laptops (i.e. standard and rugged laptops), and tablets;

5.15. Ensure the system allows real-time on-screen monitoring of all details of an ongoing call;

5.16. Track the dates and times a record was accessed or viewed by a participant;

5.17. Ensure the system has the ability to discriminate between a single EMS incident and multiple Arizona EMS agencies responding to an incident, regardless of ePCR vendor used by the Arizona EMS agencies;

5.18. Allow for an ePCR to be printed upon a participant’s needs;

5.18.1. Layout of the report should allow for a level of customization by participants, and

5.18.2. Customized reports should have the capability to be shared among users,

5.19. Ensure the system incorporates anatomical diagrams for ePCRs to easily capture assessments and findings;

5.20. Ensure the system includes an interface that allows for external sources of data to be imported on an agency level that includes but is not limited to Computer Aided Dispatch (CAD), Public Safety Answering Point (PSAP), and electronic medical equipment (cardiac monitors and automated external defibrillators);

5.21. Have a real time ePCR and reporting application that is easily deployable to all Arizona EMS agencies through a Web-based system;

5.22. Ensure the system application can be utilized with or without an internet connection;

5.23. Maintain that the ePCR functions are available at all times (exception of pre-planned software updates, as determined by the Contractor and ADHS);

5.24. At a minimum provide technical support for its data collection, analysis and reporting tool Monday through Friday, 8:00 am to 5:00 pm MST, excluding federal and state holidays;

5.25. Support should be offered through:

5.25.1. Toll free-phone line,

5.25.2. Email,

5.25.3. On-line support,

5.25.4. On-line base support, and

5.25.5. Provide twenty-four seven (24/7) support for ePCR users for any major issues that require immediate attention.

5.26. Maintain the requirements related to patches, upgrades (including any new versions of the software), and maintenance of the system including critical fixes dictated by NEMSIS’ update schedule;

5.27. Ability to send messages within the ePCR software to users. These messages should have a tracking mechanism for received messages;

5.28. Exhibit A, Service Level Agreement is referenced and hereby incorporated to this Contract;

5.29. Provide support for issues experienced by ADHS;

5.30. Allow for data analysis using logic statements (examples include but are not limited to: IF, AND, OR, IN

BETWEEN, EXCEPT, ETC.);

5.31. Ensure that the system runs effectively and efficiently (for access, exports, and analysis) regardless of file size, date range, or other filters;

5.32. Provide ADHS with written logic statements for all canned reports featured on AZ-PIERS;

5.33. Ensure the system will support the creations of reports that allow Arizona EMS agencies to compare themselves with a statewide aggregate, or various agency blinded grouping and benchmarks, as determined by the Contractor and ADHS;

5.34. Ensure ADHS has the ability to create groupings of Arizona EMS agencies that comprise an aggregate, as determined by ADHS (region, etc.);

5.35. Ensure the system allows for robust analysis of data with the ability to have detailed querying and statistical analysis (by permission level, unit, provider, region, conditions, level of service, etc.);

5.36. Provide a system where basic data transactions and queries can be handled by most relational database management systems (RDBMS);

5.37. Create an additional export capability to allow the capability of reports to be exported to plain text in common files (Excel, CSV);

5.38. Ensure the system includes multidimensional queries for data analysis and complex reporting over multi- year periods;

5.39. Provide Software as a Service for additional storage and agency level access for historical records (e.g.: V2 Vault, etc.);

5.39.1. Vault import NEMSIS 2.2.1 standardized Legacy Data with the following limitations:

5.39.1.1 NEMSIS 2.2.1 XML Legacy Data from non-ImageTrend vendors may be imported into

ImageTrend Vault provided the NEMSIS 2.2.1 XML Legacy Data is the same compatible format as the NEMSIS 2.2.1 XML Legacy Data System’s State NEMSIS submission and otherwise conforming with the NEMSIS Data Dictionary v2.2.1 available at https://nemsis.org/media/nemsis_v2/documents/NEMSIS_Data_Elements_Definitions_v 2.2.1.xls (“Conforming Legacy Data File”). It shall be the Client and/or Client Vendor’s responsibility to ensure ImageTrend is supplied with a conforming NEMSIS 2.2.1 XML Legacy Data file.

5.39.1.2 As part of the Contractor Vault product and service package, Contractor shall perform a one (1) time import of Legacy data by either:

5.39.1.2.1 Importing data from ADHS Contractor Version 2 Product(s) utilizing Contractor tools, or

5.39.1.2.2 Importing a conforming Legacy Data File. Additional uploads, corrections or modifications to uploaded data elements, or any other activity related to importing Legacy Data after Contractor has completed the one-time import is out of scope. Contractor may or may not choose to undertake this additional work at Contractor’s sole discretion. ADHS shall have the option to contract with the Contractor to undertake this work via a separate Statement of Work.

5.39.2. ADHS shall be granted a non-transferrable, non-exclusive license to use Vault for the Term of this

Contract, and such license shall expire simultaneously with this Contract; and

5.40. Provide a Software as a Service (SaaS) subscription to the Elite Data Mart. The Elite Data Mart will be delivered on an ongoing continuous basis via Microsoft SSIS over a VPN connection. ADHS must host and provision its own Microsoft SQL Server instance for the Elite Data Mart.

5.40.1. ADHS is entitled to use the Elite Data Mart listed Price Sheet for the duration of their paid subscription to use, reproduce, and distribute the Data Dictionary(s) solely to and for authorized employees and contractors to enable them to carry out their duties for ADHS, and for no other purpose.

5.40.2. CONFIDENTIALITY OF ELITE DATA MART(S) DATABASE(S) AND OTHER DATABASES The schema, data structure, and overall design of the Elite Data Mart(s) Database and other included databases, are hereby marked and declared Confidential Information which constitutes valuable and proprietary work product and trade secrets of the Contractor. While ADHS owns all its own data, ADHS shall not share with, describe to, detail to, or otherwise allow or aid a third party to reverse engineer the schema, data structure and overall design of the Elite Data Mart(s) or any other Software or database with third parties. ADHS agrees to take reasonable measures to maintain the secrecy of the schema, data structure, and overall design of the Elite Data Mart(s), or to protect the schema, data structure and overall design of the Elite Data Mart(s) in the same manner that ADHS protects its’ own trade secrets, whichever is greater.

5.40.3. CONFIDENTIALITY OF ELITE DATA DICTIONARY(S) The included Elite Data Dictionary which describes the Elite Data Mart(s) is hereby marked and declared Confidential Information which constitutes valuable and proprietary work product and trade secrets of IMAGETREND. ADHS shall not reproduce for, distribute to, grant access to, publicly display to, nor allow the data dictionary to be used by: third parties, and/or any employee or contractor who does not require the Elite Data Dictionary(s) to carry out their duties to ADHS. Upon expiry of the Elite Data Dictionary(s) license(s), ADHS shall destroy or return all copies of the Elite Data Dictionary(s) in ADHS’s control.

5.41. Ensure the LMS public portal is ADA compliant and has the ability to:

5.41.1. Add custom ADHS logo and color scheme to portal prior to go-live,

5.41.2. Send mass correspondence to all external users via email through the LMS,

5.41.3. Allow users to self-register, change and reset password, require strong password rules, lock account feature after five (5) failed attempts, unlock feature after ten (10) minutes, and retirement of inactive users; and

5.41.4. Audit changes made by internal and external users.

6. Notices, Correspondence, and Reports

6.1. Notices, correspondence, reports and CERs from the Contractor to ADHS shall be sent to:

Arizona Department of Health Services 150 North 18th Avenue, Suite 540 Phoenix, Arizona 85007 Attn: Julia Vinton Telephone: (480) 599-4145 Email: Julia.Vinton@azdhs.gov

6.2. Invoices shall be sent to: invoices@azdhs.gov for review and payment, a copy should be sent to Julia Vinton (Julia.Vinton@azdhs.gov); and

6.3. Notices, correspondence, and reports (and payments if sent to the same address) from ADHS to the Contractor shall be sent to:

ImageTrend, Inc.

Attention: Michael McBrady 20855 Kensington Boulevard Lakeville, MN 55044 Telephone: (952) 469-1589 Email: contracts@imagetrend.com

Pr ic e Sh ee t

CO

NT

RA

CT

N O

: C

TR

Pa ge

D es cr ip tio n

Ty pe o f

Fe e

Q ua nt ity

E ac h

1-

2-

3-

4-

5-

C us to m

D ev el op m en t H ou rs to b e us ed fo r fu tu re c us to m d ev el op m en t p ro je ct s O ne T im e

$1

.0

$5 ,0

.0

$0

.0

$0 .0

$0

.0

$0 .0

Ei gh t ( 8)

H ou rs o n si te tr ai ni ng /c on su lta tio n se ss io ns , a s re qu es te d by A

D H

S O ne T im e

$1

,5

.0

$3 ,0

.0

$0

.0

$0 .0

$0

.0

$0 .0

Tr ip s fo r 1 Im ag eT re nd

E du ca to r f or o ns ite tra in in g

/ c on su lta tio n se ss io

O ne T im e

$1

,7

.0

$3 ,5

.0

$0

.0

$0 .0

$0

.0

$0 .0

W eb in ar tr ai ni ng s es si on s th at m ee t t he n ee ds of u se rs , a s re qu es te d by A

D H

S th at a re re co rd ed fo r o n de m an d vi ew in g fo r a p er io d of tw o w ee ks fr om th e in iti al p re se nt at io n

O ne

T im

$3

.0

$3

,5

.0

$0 .0

$0

.0

$0 .0

$0

.0

C on tin uu m

An nu al

5, 0.

$0

.0

$3 6, 7, 1.

8, 5.

9, 2.

on tin uu m E

M S

C on te nt

P ac ka

$2 5, $2

5, 6, 7, 8.

7.

ol la bo ra tio n

Se rv es

N

/A

.0

$0 .0

$0

.0

$0 .0

$0

.0

$0 .0

An nu al

H os tin g fo r I m ag eT re nd E lit e

EM

S

An

8, 9.

3.

3.

0, 6.

al

S up po rt fo r I m ag eT re nd E lit e

EM

S, H os pi ta l H ub

0, 1, 2, al S up po rt fo r I m ag eT re nd

E lit e Fi el d

An

0, al

S up po rt fo r r eg is try li nk ag es u se d by

AD

H

S An

,6

.0

$1

,6

.0

$1 ,6

.0

$1

,6

.4

$1 ,7

.3

$1

,8

.8

Im ag et re nd E lit e

EM

S

D at a M ar t M on th ly F

TP

D el iv er

A nn ua l S aa S

Fe e

C lie nt

H os te d

FT

P

- R eg ul ar m on th ly d at a ex tra ct s by co in uo us V

PN

d el iv er y fo r A

Z-

PI

ER

S, o r a s re qu es te d b y A

D H

S

An

2, 3, 4, 4, Ve rs io n

Va ul t D at a

St or ag e

An

$5

,0

.0

$5 ,0

.0

$5

,1

.0

$5 ,3

.5

$5

,4

.6

$5 ,6

.5

C on tin uu m

L eg ac y

G eo co di ng

.0

$0 .0

$0

.0

$0 .0

$0

.0

$0 .0

H ea lth

In fo rm at io n

H ub

(H

IH

) A nn ua l S up po rt an d H os tin g An

1, 4.

Li ce ns e

M an ag em en t T ra in er S et up

T im e

$5

1, $1

,4

.0

$0 .0

$0

.0

$0 .0

Pa ym en t G at ew ay

S et up

T im e

$0 .0

$0

.0

$0 .0

$0

.0

$0 .0

$0

.0

D at ab as e Ba ck up

In st al lm en t

O ne

T im e

$2 5, $2

5, $0 .0

$0

.0

Li ce ns e

M an ag em en t S aa S

- T ra in er

$4 9, $9

9, ,2

.5

$1

,2

.3

$1

,4

.1

Pr e Sh ee t

CO

NT

RA

CT

N O

: C

TR

Pa

D es cr ip tio n

Ty pe o f

Fe e

Q ua

E ac h

1-

2-

3-

4-

5-

Sk ill

Ex am

M od ul e

An

.0

$0 .0

$0

.0

$0 .0

$0

.0

$0 .0

In ve st ig at io

.0

$0

.0

$0 .0

$0

.0

$0 .0

$0

.0

N R

EM

T

An

.0

$0 .0

$0

.0

$0 .0

$0

.0

$0 .0

Pa ym en t G at ew ay

.0

$0

.0

$0 .0

$0

.0

$0 .0

$0

.0

Ac co un t A dv is em en t S er vi ce s Le ve l 1

(e xc lu si ve ly fo r L M

S)

.0

$0 .0

$0

.0

$0 .0

$0

.0

$0 .0

W eb in ar

T ra in in g Se ss io ns (2 h r s es si on s ea ch

O ne T im e

$3

.0

$0

.0

$1 ,4

.0

$0

.0

$0 .0

$0

.0

O ns ite T ra in in g

(8 h ou rs

O ne T im e

$1

,4

.0

$0 .0

$4

,2

.0

$0 .0

$0

.0

$0 .0

Tr av el

T im e

$1

,7

.0

$0 .0

$1

,7

.0

$0 .0

$0

.0

$0 .0

St an da rd L eg ac y D at a

Im po rt O ne T im e

$5

,0

.0

$0 .0

$1

0, $0 .0

$0

.0

C us to m

D ev el op m en t H ou rs

U rb an

M i g ra tio n fo r R ep or tin g O ne T im

.0

$0 .0

$0

.0

$9 ,2

.0

$0

.0

$0 .0

O pt io na l:

C re at e N ew

IT

F ie ld

T im

.0

$0

.0

$0 .0

$5

,6

.0

$0 .0

$0

A nn ua l N

TE

A m ou s

,9

.2

$4

,6

.2

,6

.5

,9

.4

,3

.9 on tr ac t N

TE

A m ou

,3

,6

.4

Th pa rti es u nd er st an d th at w hi le th e sy st em c an b e in fin ite ly c on fig ur ed a nd re fin ed

, t ha t t he s of tw ar e sy st em m us t r ea ch a le ve l o f r ea di ne ss nd it us t “ go

-li ve

” f or u sa ge b y th e en d-us er s in it s in te nd ed u se c as es

. A D

H S m ay d es ire s ta ge d ro ll ou t o f d iff er en t f ea tu re s or p ro du ct s fo r l ar im pl em en ta tio ns

, o r A

D H

S m ay d es ire to h av e al l f un ct io ns g o liv e al l a t o nc e.

In th e in te re st o f d ef in in g a fa ir an d ob je ct iv e m ea su re m en t p oi nt , t hi s

G o

Li ve

M ile st on e w ill be c om pl et e w he n th e

C lie nt a ck no w le dg es a ll st an da rd

L eg ac y da ta h as s uc ce ss fu lly b ee n Im po rte d an d

AD

H S’ s So ftw ar e sy st em p ro ce ss es , r ec ei ve s, tr an sm its

, g en er at es , o r o th er w is e in te ra ct s w ith th e fir st n on -te st d at a re co rd , e xc lu di ng n on

-te st d at a w hi ch is m ig ra te d on a o ne

-ti m e ba si s fro m a no th er s ys te

1/17/24, 4:46 PM SAM.gov https://sam.gov/entities/view/J8BEN7WCLC61?versionId=0 1/3

An official website of the United States government Here’s how you know

Cease Using the Entity Management API for Reps and Certs Information Show Details Dec 13, 2023

Entity Validation Processing Show Details Jan 16, 2024

See All Alerts

Home Search Data Bank Data Services Help

ImageTrend, Inc. ID Assigned

The entity record has been validated as unique and existing, but is not registered in SAM.gov.

Unique Entity ID

J8BEN7WCLC61

Physical Address

20855 Kensington Blvd null Lakeville, MN

55044-7486, USA

Version

Current Record https://sam.gov/ https://sam.gov/ javascript:void(0) javascript:void(0) https://sam.gov/content/home https://sam.gov/search/ https://sam.gov/reports/awards/standard https://sam.gov/data-services https://sam.gov/content/help https://sam.gov/workspace/profile/feeds https://sam.gov/workspace/profile/feeds/notification https://sam.gov/workspace javascript:void(0) https://sam.gov/entities/view/J8BEN7WCLC61?versionId=0 2/3

WARNING

Our Website

About This Site

Our Community

Release Notes

System Alerts

Our Partners

Acquisition.gov

USASpending.gov

Grants.gov

More Partners

Policies

Terms of Use

Privacy Policy

Disclaimers

Freedom of Information Act

Accessibility

Customer Service

Help

Check Entity Status

Federal Service Desk

External Resources

Contact

This is a U.S. General Services Administration Federal Government computer system that is "FOR OFFICIAL USE ONLY." This system is subject to monitoring. Individuals found performing unauthorized activities are subject to disciplinary action including criminal prosecution.

https://sam.gov/content/about/this-site https://interact.gsa.gov/group/integrated-award-environment-iae-industry-community https://www.fsd.gov/gsafsd_sp?id=kb_category&kb_category=ccf4380a1ba67410fe314000f54bcb16&kb_id=f66d8e6cdb76d4100d73f81d0f9619c https://sam.gov/alerts https://acquisition.gov/ https://usaspending.gov/ https://grants.gov/ https://sam.gov/content/about/partners https://sam.gov/content/about/terms-of-use https://sam.gov/content/about/privacy https://sam.gov/content/about/disclaimers https://www.gsa.gov/reference/freedom-of-information-act-foia https://sam.gov/content/about/accessibility https://sam.gov/content/help https://sam.gov/content/status-tracker https://www.fsd.gov/gsafsd_sp/?id=gsa_landing https://sam.gov/content/about/external-resources https://sam.gov/content/about/contact https://www.gsa.gov/ https://sam.gov/entities/view/J8BEN7WCLC61?versionId=0 3/3

SAM.gov An official website of the U.S. General Services Administration

This system contains Controlled Unclassified Information (CUI). All individuals viewing, reproducing or disposing of this information are required to protect it in accordance with 32 CFR Part 2002 and GSA Order CIO 2103.2 CUI Policy.

1/17/24, 4:31 PM Arizona Corporations Commission https://ecorp.azcc.gov/EntitySearch/Index 1/2

SEARCH CRITERIA

SEARCH RESULTS

Entity Name:

ImageTrend Inc

Entity Type:

All

Statutory Agent Name:

N/A

Entity Status:

All

Principal Name:

N/A

Name Type:

All

Entity Number:

N/A

Entity County:

All

Entity ID Entity Name Entity Type Entity County

Agent Name

Agent Type

Entity Status

F16572740

IMAGE TREND, INC

(/BusinessSearch/BusinessInfo?

entityNumber=F16572740)

Foreign For- Profit (Business) Corporation

Maricopa

NATIONAL

REGISTERED

AGENTS INC

Statutory Agent

Inactive

23486502

IMAGE TREND, INC

(/BusinessSearch/BusinessInfo?

entityNumber=23486502)

Domestic

LLC

CT

Corporation System

Statutory Agent

Inactive

23486502

IMAGETREND, LLC

(/BusinessSearch/BusinessInfo?

entityNumber=23486502)

Domestic

LLC

CT

Corporation System

Statutory Agent

Active

Privacy Policy (http://azcc.gov/privacy-policy) ǀ Contact Us (http://azcc.gov/corporations/corporation-contacts) https://ecorp.azcc.gov/BusinessSearch/BusinessInfo?entityNumber=F16572740 https://ecorp.azcc.gov/BusinessSearch/BusinessInfo?entityNumber=F16572740 https://ecorp.azcc.gov/BusinessSearch/BusinessInfo?entityNumber=F16572740 https://ecorp.azcc.gov/BusinessSearch/BusinessInfo?entityNumber=23486502 https://ecorp.azcc.gov/BusinessSearch/BusinessInfo?entityNumber=23486502 https://ecorp.azcc.gov/BusinessSearch/BusinessInfo?entityNumber=23486502 https://ecorp.azcc.gov/BusinessSearch/BusinessInfo?entityNumber=23486502 https://ecorp.azcc.gov/BusinessSearch/BusinessInfo?entityNumber=23486502 https://ecorp.azcc.gov/BusinessSearch/BusinessInfo?entityNumber=23486502 http://azcc.gov/privacy-policy http://azcc.gov/privacy-policy http://azcc.gov/corporations/corporation-contacts

1/17/24, 4:31 PM Arizona Corporations Commission https://ecorp.azcc.gov/EntitySearch/Index 2/2

Page 1 of 1, records 1 to 4 of 4

Entity ID Entity Name Entity Type Entity County

Agent Name

Agent Type

Entity Status

F16572740

IMAGETREND, LLC

(/BusinessSearch/BusinessInfo?

entityNumber=F16572740)

Foreign For- Profit (Business) Corporation

Maricopa

NATIONAL

REGISTERED

AGENTS INC

Statutory Agent

Inactive

Return to Search

Privacy Policy (http://azcc.gov/privacy-policy) ǀ Contact Us (http://azcc.gov/corporations/corporation-contacts) https://ecorp.azcc.gov/BusinessSearch/BusinessInfo?entityNumber=F16572740 https://ecorp.azcc.gov/BusinessSearch/BusinessInfo?entityNumber=F16572740 https://ecorp.azcc.gov/BusinessSearch/BusinessInfo?entityNumber=F16572740 http://azcc.gov/privacy-policy http://azcc.gov/privacy-policy

1/17/24, 4:30 PM OIG Search Results https://exclusions.oig.hhs.gov/SearchResults.aspx 1/1

Visit our tips page to learn how to best use the Exclusions Database. If you experience technical difficulties, please email the webmaster at webmaster@oig.hhs.gov.

Exclusions Search Results: Exclusions Search Results: EntitiesEntities

No Results were found for

ImageTrend Inc

If no results are found, this individual or entity (if it is an entity search) is not currently excluded. Print this Web page for your documentation

Search Again

Search conducted 1/17/2024 6:30:19 PM EST on OIG LEIE Exclusions database.

Source data updated on 1/10/2024 9:00:00 AM EST

Return to Search

An official website of the United States government. Here's how you know > https://oig.hhs.gov/exclusions/exclusions-help.asp#generalSearch mailto:webmaster@oig.hhs.gov https://oig.hhs.gov/exclusions/exclusions-help.asp#entitySearch https://oig.hhs.gov/exclusions/exclusions-help.asp#entitySearch javascript:__doPostBack('ctl00$cpExclusions$lbGridBackToSearch','') javascript:__doPostBack('ctl00$cpExclusions$lbBackToSearch','') https://oig.hhs.gov/notices/official-site.asp