Você está na página 1de 7

pPlus Logical Data Model

Lance Lu August 1st, 2008

pPlus Logical Data Model

IMPORTANT NOTICE
This document is to capture ideas related to subject area model, conceptual data model, logical data model and physical data model within the context of Lash Group business offering.

06/27/2013

THE LASH GROUP, INC.-CONFIDENTIAL

Page 2 of 7

pPlus Logical Data Model

DATA MODEL HIERARCHY


There are multiple types of data models. Each type of data model has characteristic that make it more useful than other types for a particular purpose.

SUBJECT AREA MODEL


A subject area is a useful partitioning of business offering, it is a cohesive collection of entities and relationships in the conceptual data model. A subject area model minimizes technical details and focus instead on delineating and defining subject area of interest to executive and high-level decision-makers, is usually served for high-level planning and setting of project scope. The definition of the subject area model is out-of the scope of this document, and examples of subject areas are: Enrollment Administration Subject Area Web Enrollment Phone Enrollment Fax Enrollment AWD Benefit Verification Subject Area

06/27/2013

THE LASH GROUP, INC.-CONFIDENTIAL

Page 3 of 7

pPlus Logical Data Model

Status Changes To_Dos Missing Information Correspondence Subject Area Letter Manager Document Management Distribution Subject Area Inbound Outbound Fulfillments Nursing Service Subject Area

CONCEPTUAL DATA MODEL - CONCEPTUAL ENTITIES AND RELATIONSHIPS


Conceptual data model has sufficient detail to be useful as a definition of information requirements. The intended audiences for this model are decision-makers, subject matter experts and information technology experts responsible for requirement analysis. The conceptual data model is technology-independent, and applicable to multiple logical models. For example, a set of classes and relationships could be designed for an object-oriented application, a well-normalized logical data model could be designed for transactional database, a star-schema could be designed for analysis database. Over the years, a set of vocabulary is developed to describe the activities that are associated with various subject areas. In the conceptual data model, these vocabularies are formalized as conceptual entities, attributes, relationships and constraints: _Contacts _Patients _Providers _Sites _Pharmacies _Contact_Programs _Contact_Program_Products _Program_Products _Programs _Products _Contact_Insurances _Plans _Payers _PBMs _Contact_Program_Services

06/27/2013

THE LASH GROUP, INC.-CONFIDENTIAL

Page 4 of 7

pPlus Logical Data Model

_Contact_Program_Product_Contacts _Status_Codes _Status_Code_Explanations _Contact_Status_Informations _Contact_Program_Product_Orders _Contact_Program_Fulfillment_Orders _Contact_Program_Product_Claims _Contact_Program_Product_AWD _Contact_Program_Product_Messages _Contact_Program_GNSS _Contact_Web _Contact_Call_Logs _Contact_To_Dos and etc.

Conceptual Entities
The conceptual entity is represented as an entity by using Microsoft Visio, and named with a leading _ to differentiate it from the main entity name in the pPlus logical data model. The primary key of the conceptual entity represents the primary key of the main entity in pPlus logical model. The conceptual entity consists of major pPlus entities, associated entities and relationships. Only primary keys are foreign keys are listed as attributes.

Conceptual Relationships
The relationship between conceptual entities is presented by those of the main entities within the respective conceptual entities.

is to describe

06/27/2013

THE LASH GROUP, INC.-CONFIDENTIAL

Page 5 of 7

pPlus Logical Data Model

PPLUS LOGICAL DATA MODEL - PPLUS ENTITIES AND RELATIONSHIPS


pPlus logical data model is derived from the conceptual data model, with all of the details regarding the conceptual entity. Each conceptual entity is a cohesive collection of entities, attributes and relationships in pPlus logical data model. Each conceptual entity is represented by 3 panels: Left Panel: the description and constraints regarding this conceptual entity, Middle Panel: the entities that are referenced by this conceptual entity, Right Panel: the ER diagram for the conceptual entity. Logical Data Model Maintenance: The data model is documented by using Visio for Enterprise Architects, and is based on the current implementation of pPlus .NET demo. When changes are been made in the source database, it is required to refresh the logical data model from the source database: If additional tables are created in the source database, reverse engineer wizard will bring in all the new tables. However, it is required to manually add the new tables into the appropriate conceptual entities. If no new tables are created, refresh will sync the data model and source database.

Find the Difference: Since the documented data model is based on a specific implementation of pPlus, changing source database will provide the difference of the logical data models between 2 database sources. This provides a way document the difference between a specific implementation and the standard pPlus. The steps to compare a specific implementation of pPlus and the standard pPlus logical model: 1. Make a copy of the standard pPlus logical data model, 2. Choose Database -> Update to start Update Database Wizard, a. Select Generate a text file with the DDL script, and specify the filename, b. Do NOT select Update the database, c. Select Detect changes in the database, d. Select Log conflicts to file, and specify the filename, 3. Select Next,

06/27/2013

THE LASH GROUP, INC.-CONFIDENTIAL

Page 6 of 7

pPlus Logical Data Model

4. Choose the data source that points to the new pPlus implementation, and Select Next. The Update Database Wizard will compute the conflicts between selected database and the standard pPlus database. 5. Select Refresh for all conflicts, and make sure do NOT update database, 6. Select Finish to complete the update database wizard, 7. Review the content of DDL file, 8. Update logical data model with the content of the conflict file, a. Review what objects are been removed from the data model, b. Review new tables and foreign keys, and manually add them to the data model.

PPLUS PHYSICAL DATA MODEL - PPLUS DDL


The documented pPlus data model includes all tables, views, indices, foreign keys, triggers and store procedures. Therefore, a physical data model could be generated by using the generate DDL feature from Visio, and be checked into source control.

06/27/2013

THE LASH GROUP, INC.-CONFIDENTIAL

Page 7 of 7