Disproportionate Share Hospital (DSH) Audit RFP 19-96006 Appendix 1

MITA Policy #1

Policy ID MITA IA Policy #1

Policy Name Logical Data Model Development Policy

Activation Date June 10, 2016

Policy All technical solutions that require a to be designed or redeveloped must develop a Logical Data Model that is derived from the Enterprise Logical Data Model (ELDM). This policy applies whether the database is for transactional or reporting purposes. Any deviation from the Enterprise Logical Data Model must meet DHCS Data Modification policies, procedures and standards. At a minimum, the Logical Data Model must include Entity Name, Entity Description, Entity Attributes, Data Type, Associated Business Process, and/or associated business requirement if applicable.

Purpose An Enterprise Logical Data Model provides a mechanism for understanding the information elements required for a new database system component, and serves to illustrate the information required to support the business goals and accurate reporting. The DHCS ELDM serves as a tool that enables the reengineering of Medicaid business processes. The following policy ensures that all new or redeveloped DHCS database systems will utilize a shared data model across departments and divisions to achieve true plug-and-play capabilities of services and interoperability.

Policy Owner DHCS Information Architecture Board

Stakeholders DHCS system owners, data custodians, and business-program-level data stewards.

Alignment with Use of the ELDM will improve the Department’s MITA maturity and support the goals MITA Maturity from the CMS MITA Framework: Goals • Develop seamless and integrated systems that communicate effectively to achieve common Medicaid goals through interoperability and common standards • Promote an environment that supports flexibility, adaptability, and rapid response to changes in programs and technology • Promote an enterprise view that supports enabling technologies that align with Medicaid business processes and technologies • Provide data that is timely, accurate, usable, and easily accessible in order to support analysis and decision making for health care management and program administration • Provide performance measurement for accountability and planning  Coordinate with public health and other partners, and integrate health outcomes within the Medicaid community

Scope The policy will apply to all DHCS technical solutions.

Page | 1 Disproportionate Share Hospital (DSH) Audit RFP 19-96006 Appendix 1

MITA Information Architecture Policy #1

1. Developer uses ELDM to create LDM for the technical solution. High-Level 2. Developer follows DHCS Data Modification Process for all deviations. Procedure for Use of ELDM 3. DHCS reviews and approves LDM. 4. DHCS reviews and approves all other Database Plans. 5. Developer creates PDM, based on DHCS-approved LDM for the technical solution. To support this policy, the following implementation steps will be taken: Implementation 1. Ensure awareness of the policy for vendor and DHCS staff, including in Support Steps procurement phases. 2. Provide technical and administrative support to project staff utilizing the ELDM: a. Maintain an intranet version of this policy and associated procedures for ELDM use and compliance with policy. b. Maintain an intranet version of the ELDM and associated meta-data. c. Allow access to the DHCS tool that allows easy extraction and conversion from LDM to PDM. d. Assign a DHCS Data Modeler to provide guidance on the use of the ELDM. 3. Ensure compliance with procedures for project-specific LDM development and review. 4. Ensure compliance with procedure for managing data modifications to the ELDM as proposed by project staff and approved by DHCS.  Technical solutions that were procured prior to the policy activation date will be Exceptions to excluded from this policy. Conformance  Technical solutions that use COTs products will be required to provide a map of data to the ELDM and maintain the mapping throughout the life of the data.  The IAB must approve exception in every other case, on a case-by-case basis.  IAB-approved exceptions must provide mapping of cross-referenced data elements at an attribute level to the attributes of the DHCS ELDM. Definitions Term Definition Attribute Descriptive data element; frequently a column in a database table (e.g., attribute Last Name for entity PERSON). DHCS Department of Health Care Services ELDM Enterprise Logical Data Model Entity Data concept; frequently implemented as a database table (e.g., PERSON, ORGANIZATION, ADDRESS). IA Information Architecture LDM Logical data model MITA Medicaid Architecture PDM Physical Data Model Approver Name Title Contact Signature Approval Date Linette Scott, M.D. Deputy Director, IMD (916) 552-8830 /s/ Linette Scott, M.D. June 10, 2016

Page | 2