Sheet1

For each requirement, Vendor shall select in Column H whether the proposed solution meets the requirement out of the box, with configuration, with customization, or does not meet the requirement. Vendors shall provide further explanation to their response for each requirement in Column I. In the case the requirement response type is "Does Not Meet", provide potential work arounds or if this is included in a future software release as an enhancement. For all other response types, provide further explanation "How the requirement is supported using the system".

How does your solution identify, manage, distribute, and provide other system access to ADT events?

2 Business Requirement Vendor System Functional ADT Tracking Improve care coordination for a single patient episode Capture ADT events from acute care facilities (hospitals, inpatient/ED, urgent care, immediate care, psychiatric residential treatment facilities, etc.).

What types of events, beyond ADT, can the system solution capture from acute facilities?

3 Business Requirement Vendor System Functional Encounter Tracking Improve care coordination for a single patient episode Capture encounter data from acute care facilities and ambulatory facilities.

What types of events, beyond encounter data, can the system solution capture in the interest of improving care-coordination for a single episode?

4 Business Requirement Vendor System Functional Member Mapping Improve medical outcomes for SC Medicaid Patients Match Beneficiaries once received from "upstream" systems against the SCDHHS list of Beneficiaries and route the ADT/Encounter event notification data to the corresponding managed care organizations (MCOs) while excluding non-matched and Fee for Service (FFS) Beneficiaries from being routed to any MCO.

Please explain how you map member data to existing MCOs? What data validations and data matching does your solution cover? How does your system handle proper routing of FFS related information?

5 Business Requirement Vendor System Functional Notifications Improve care coordination for a single patient episode Support the ability to send details such as events and/or notifications in near real-time to MCOs and/or SCDHHS.

How does your solution handle the ability to store and forward notifications?

What configurable attributes does your solution provide?

8 Business Requirement Vendor System Integration & Interoperability SOA Support Improve medical outcomes for SC Medicaid Patients The selected vendor system shall support common API/REST standards/protocols and have well documented APIs for third-party system integrations.

What data integration and API standards does the solution support and leverage?

9 Business Requirement Vendor System Integration & Interoperability Covered Entity Integrations Improve medical outcomes for SC Medicaid Patients Support integrations that are HIPAA and Medicaid Safeguarding compliant.

Provide a list of all MCOs and EMR/EHR system partners currently integrated for the State of South Carolina.

10 Business Requirement Vendor System Integration & Interoperability Third-Party Integration Improve medical outcomes for SC Medicaid Patients Interface with SCDHHS-MES Core platform providing ADT event data using HL7 FHIR standards (Da Vinci Notification Bundle) via approved interface protocols which include: Representational State Transfer (REST) API, Simple Object Access Protocol (SOAP) interface, or file-based interface using SFTP.

Does your system utilize HL7 FHIR standards? If not, what standards do you utilize?

11 Business Requirement Vendor System Integration & Interoperability Third-Party Integration Improve care coordination for a single patient episode Support interconnectivity between states Health Information Exchanges (HIE) and data aggregators to capture ADT event notifications when Beneficiaries visit facilities outside of South Carolina.

What States outside of South Carolina is your solution capable of integrating with?

12 Business Requirement Vendor System Compliance and Security Compliance Improve medical outcomes for SC Medicaid Patients Adhere to and remain in compliance with:

- The Centers for Medicare and Medicaid Services (CMS) regulations and prescribed architecture guidelines.

- The HL7 FHIR standards for ADT event notification messaging guidelines

What ADT Event Notification standards does the solution support and leverage? Is the solution certified by CMS leveraging architecture guidelines?

13 Business Requirement Vendor System Compliance and Security Security Improve medical outcomes for SC Medicaid Patients Develop, maintain, and provide SCDHHS a security and privacy program with effective security and privacy controls compliant with recognized security operating controls, including but not limited to:

- Health Insurance Portability and Accountability Act (HIPAA)

- CMS Acceptable Risk Controls for Affordable Care Act (ACA), Medicaid, and Partner Entities (ARC-AMPE)

- National Institute of Standards and Technology (NIST) Special Publication 800 series Recommended Security Controls for Federal Information Systems and Organizations

- South Carolina Division of Information Security (SCDIS) 201 Information Security and Privacy Incident Response Standards

- Federal Risk and Authorization Management Program (FedRAMP)

- System must be Section 508 compliant.

If applicable, please describe your access control measures.

Can you describe how your system would handle situations where member details contained within an ADT notification do not match historical records?

Does your system have any data quality checks or matching responsibility? If so, are you using national standard quality metrics? Which ones?

27 Business Requirement Vendor System Data Management Bed Capacity Tracking Improve preparedness in case of a disaster Record details related to acute care facility Beds in real time, including but not limited to:

- Total number of available Beds by acute care facility (e.g., hospital inpatient/ED, psychiatric residential treatment facilities, etc.)

- Total number of available Beds by type (e.g., in-state, out-of-state, Medicaid, Medicare, emergency, maternity, inpatient, rehabilitation, and psychiatric)

- Bed Status (e.g., closed, occupied, isolated, etc.)

Are there any other details surrounding Bed capacity tracking that the solution can capture such as gender assignments for psychiatric residential treatment facilities (PRTFs)?

How does your solution handle the ability to store and route appropriate notifications to dental plan providers based on diagnosis?

30 Business Requirement Vendor System Functional Bed Capacity Tracking Improve preparedness in case of a disaster Provide the ability to send Bed Capacity Tracking data in real-time to third party integrators such as Department of Public Health (DPH).

How does your solution handle the ability to store and send Bed Capacity Tracking information to SCDHHS and DPH?

-Modularity Standard -MITA Condition -Industry Standards Condition -Leverage Condition -Business Results Condition -Reporting Condition -Interoperability Condition

- Total number of available beds

- Total number of available beds by floor

- Total number of available beds by gender

- Total number of avaialable beds by age

Are there any other details surrounding PRTF beds that the solution can capture?

47 Business Requirement Vendor System Data Management Data Storage Data retention to meet audit requirements. The Contractor shall retain Event data acquired from Providers' systems for at least five (5) years for audit purposes.