13.07.2015 Views

Part 4 - Iowa Medicaid Enterprise

Part 4 - Iowa Medicaid Enterprise

Part 4 - Iowa Medicaid Enterprise

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

RFP MED-12-001 | Technical Proposal<strong>Iowa</strong> <strong>Medicaid</strong> <strong>Enterprise</strong> System Service Procurement | MMIS and Core MMIS OperationsHardware and Software DetailRFP Section 6.3.1.2, Requirement r.16Hardware and software details will be provided in the architecture team’s DSD. Team Nordian hasalready defined the hardware and software required for the new MMIS. This information and anymodifications will be added to the architecture team’s DSD for project life cycle support.High Level and Detailed Data Models and Entity Relationship DiagramRFP Section 6.3.1.2, Requirement r.17, r.18, and r.19Team Noridian’s solution is based on a relational database model using the ERwin tool. File and recordlayouts are presented as entities and attributes using relationship naming conventions. The ERwin modelincludes physical information such as data type, constraints, and referential integrity. Our rich datamodels that present over 1,500 entities that are organized by business areas.Team Noridian will provide a database schema design that will be managed using ERwin. ERwinprovides the capability to specify the metadata and layout for each table and column (e.g., NULL optionand data type). It has the capability to record narrative definitions for tables and columns.This information collectively is referred to as metadata and is vital to users and administrators. TeamNoridian will create a metadata report from ERwin to be used as content for ultimately publishing theinformation to end users. This information is the complete data dictionary for the system. The source ofeach element (i.e., column) in the data model will be included in the narrative definition of the column.The data dictionary generated through this process is voluminous and detailed. We have found thatincluding the information in DSD’s is often not productive as there is so much information that ourcustomers have not found the information useful. Hence, as a value added feature, the data dictionaryinformation is provided online via system functionality in eCAMS, as shown in Figure 8-48. The eCAMSfunctional provides users the capability to browse the data dictionary and perform searches. As dataelements are added or modified during operations, Team Noridian will re-generate the metadata reportand publish the update. In addition, Team Noridian will publish the data dictionary on the Project Portalfor Department access. Each business area DSD will include entity relationship diagrams (ERD) andreferences to where the information is available on the Project Portal. Figure 8-49 provides an example ofthe ERD diagram used on previous MMIS implementation.8 | 81

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!