Planned Parenthood Federation of America, Inc.

Transcription

1 Planned Parenthood Data Warehouse Project System Specification Volume 2 Data Model Prepared by The Data Organization 1 July 2002 DRAFT 12/14/2008 Page 1

2 TABLE OF CONTENTS 1. CHANGE LOG INTRODUCTION PURPOSE OF THE DOCUMENT SCOPE OF THE DOCUMENT ORGANIZATION OF THE DOCUMENT DATA MODEL OVERVIEW INTRODUCTION DATA MODEL DESIGN CRITERIA PROTOTYPE CONCEPTUAL MODEL VALIDATION TABLES INTRODUCTION A CHARGE TYPE A COMMENT TYPE C CONTRACEPTION TYPE C CPT CODE C DIAGNOSIS TYPE C ETHNICITY TYPE C EXPENSE TYPE C GENDER TYPE C IDENTIFIER TYPE C LANGUAGE TYPE C MARITAL TYPE C MODIFIER TYPE C PAYER SOURCE C PROVIDER TYPE C RVU GROUP C WEEKDAY CTBLMEDICALCATEGORY CTBLPOVERTYREGION CTBLSERVICECATEGORY CTBLSERVICEGROUP CTBLVISITTYPE TRANSLATION TABLES INTRODUCTION A CONTRACEPTION TYPE A DIAGNOSIS TYPE A ETHNICITY TYPE A EXPENSE TYPE A GENDER TYPE A LANGUAGE TYPE A MARITAL STATUS TYPE A PAYER SOURCE A PROVIDER TYPE ATBL VISIT TYPE /14/2008 Page 2

3 6. PPFA ORGANIZATION DATA INTRODUCTION DATA MODEL T AFFILIATE D CENTER D CENTER LOCATION HISTORY D CLINIC D CLINIC RVU HISTORY D HOURS OF OPERATION PATIENT DATA INTRODUCTION DATA MODEL D PATIENT D PATIENT COMMENTS D PATIENT HISTORY T PATIENT TRANSLATION PRODUCT DATA INTRODUCTION DATA MODEL D PRODUCT AFFILIATE D PRODUCT PPFA D PRODUCT VALUE HISTORY PROVIDER DATA INTRODUCTION DATA MODEL D PROVIDER R WORKS AT T PROVIDER TRANSLATION TASK DATA INTRODUCTION DATA MODEL D TASK D TASK PPFA VISIT DATA INTRODUCTION DATA MODEL F CLINIC COST F PAYMENT DETAIL F VISIT DETAIL IMPLEMENTED DATA MODEL COMPLETE DATA MODEL DDL SOURCE DATA DICTIONARY /14/2008 Page 3

4 13. REFERENCE MATERIALS IMPORT FILE FORMATS EXPORT FILE FORMATS /14/2008 Page 4

5 1. CHANGE LOG Date Description Author 9 March 02 Created document Rainer Schoenrank 1 July 02 Updated attributes and inserted diagrams Rainer Schoenrank 2. INTRODUCTION 2.1 Purpose of the Document The Data Architecture describes the Data Mart data model and its implementation. This report describes the results of the policy decisions that created the data model, the database implementation, the data base concepts, and the organization of the business data. 2.2 Scope of the Document The scope of the document is limited to the data model for the Data Mart application. The details of the application, implementation and functionality are described in various files on the Data Mart servers. 2.3 Organization of the Document INTRODUCTION specifies the purpose, scope and organization of this document. DATA MODEL OVERVIEW describes the context of the Data Mart data model, its functionality, and the organization of the business data. SUBSCHEMA DATA the table and data chapters describe the detailed tables that make up the major components of the data model. There is a chapter for the validation tables, for each of the dimensions of the database and for each of the fact tables of the database. IMPLEMENTATION OVERVIEW describes the environment for the development of the Data Mart application and the processes used to distribute the application to its users. IMPLEMENTED DATA MODEL describes the environment for the development of the Data Mart application and the processes used to distribute the application to its users. 12/14/2008 Page 5

6 3. DATA MODEL OVERVIEW 3.1 Introduction The Data Mart data model is based on the model for a business processing application that uses a database. The data model provides a common data definition for the data required by the application. The data model is a set of entities (or tables) that contain data produced by users within the business. The entities are described in a data dictionary that produces a file of Data Definition Language (DDL) commands for the target data base management system (DBMS). 3.2 Data Model Design Criteria The goal of the data modeling process is to create a database that models the reality of the business data, is expandable as business changes and allows the data to be shared among business processes (different application system). The design principles of the data model and database are: The model and implementation of the database will use Declarative Referential Integrity to ensure that orphan records cannot be created in the database. Company policy (business rules) will not be modeled or implemented into the database. The application owner will have full control of the data base update processing The criteria used for designing the database are: Simplicity Clarity Ease of use Generality. For simplicity, data modeling constructs that are not implemented in the DBMS are not used in the data model (such as, sub typing, super typing, and relationship roles). For clarity, validation tables are not modeled in the diagrams and separated from the model tables in the database implementation. For ease of use, a data item will be modeled in only one place in the data model. This will avoid data synchronization problems and data redundancy (i.e., the data model will be in third normal form). For generality, the requirements of the more general concept of a data item will be analyzed. For example, using telephone number, the requirements of the international phone system will be examined rather than just the North American telephone-numbering plan. 12/14/2008 Page 6

7 3.3 Prototype Conceptual Model A data model is the logical view of the business data. It is physically implemented within a DBMS, but the model is independent of any particular DBMS implementation. Provider ProviderKey Time Clinic ClinicKey Visit Detail TaskID PatientKey ProductKey Patient Product Affiliate Task maps to maps to Product PPFA Task PPFA Legend: Other Entity one to many relationship Associative Entity (many to many) many to one relationship Entity (table) one to many relationship Attributive Entity (child of Entity) 12/14/2008 Page 7

8 4. VALIDATION TABLES 4.1 Introduction To implement the data model using declared referential integrity we use validation tables. The validation (code) tables have defined relationships to some of the attributes of the data model. The attributes that reference the validation tables are only allowed a limited set of values. The validation tables contain those allowed values. For completeness, each validation table contains codes for SLCT (the default value) and UNKN (correct value not in list). The values in the validation tables are never deleted; they are marked as not in use. The referential integrity requirement of the database means that deleting a validation value may delete multiple rows in the data tables. Since the function of all of the validation tables is identical, the structure of all of the tables is the same. The structure is shown in the table below. Code ID Number (Long) AutoNumber An identifier attribute type created by the DBMS and used as a primary key. Short Code Text 10 The mnemonic code which the application users use for this row value and used as a primary key (i.e., no duplicate values allowed). Description Text 255 The long description of the value that was identified by the short code. Sort Order Number (Long) The order in which the table rows will be displayed In Use Yes/No Yes A flag to indicate whether or not to show the row in a pull down list when entering data. Audit Trail Event Date/Time Now() The date and time at which this table row was last updated Audit Trail Process Text 50 NT Logon ID The user id or process name that last updated this table row 12/14/2008 Page 8

9 4.2 A Charge Type The code Court Name table contains the names of courts allowed for a matter. Examples of the values of Court Name are shown in the table below. 0 SLCT Please select a Court Type Yes 1 UNKN Unknown Court Type Yes 3 9CA 9 th Circuit Court of Appeal Yes 4 SCAC Superior Court of Alameda County Yes 5 USSC United States Supreme Court Yes 4.3 A Comment Type The code Court Name table contains the names of courts allowed for a matter. Examples of the values of Court Name are shown in the table below. 0 SLCT Please select a Court Type Yes 1 UNKN Unknown Court Type Yes 3 9CA 9 th Circuit Court of Appeal Yes 4 SCAC Superior Court of Alameda County Yes 5 USSC United States Supreme Court Yes 4.4 C Contraception Type The code Address Type table contains the types of address allowed for a Client. Examples of the values of Address Type are shown in the table below. 0 SLCT Please select a Client Address Type Yes 1 UNKN Unknown Client Address Type Yes 3 HO Head Office Yes 4 BA Billing Address Yes 5 SA Client Primary Address Yes 6 RGN1 Region 1 Address Yes 7 RGN2 Region 2 Address Yes 12/14/2008 Page 9

10 4.5 C CPT Code The code Appearance Type table contains the types of appearances allow for a matter before a court. Examples of the values of Appearance Type are shown in the table below. 0 SLCT Please select a Appearance Type Yes 1 UNKN Unknown Appearance Type Yes 4.6 C Diagnosis Type The code Arbiter Role Type table contains the types of roles allowed for an Arbiter. Examples of the values of Arbiter Role are shown in the table below. 0 SLCT Please select an Arbiter Role Type Yes 1 UNKN Unknown Arbiter Role Type Yes 3 J Judge Yes 4 M Mediator Yes 5 A Arbitrator Yes 4.7 C Ethnicity Type The code Bill Contents table contains the types of billing contents (level of billing detail) available for a Matter. Examples of the values of Bill Content are shown in the table below. 0 SLCT Please select a Bill Contents Type Yes 1 UNKN Unknown Bill Contents Type Yes 12/14/2008 Page 10

11 4.8 C Expense Type The code Bill Format table contains the types of billing layout formats available for a Matter. Examples of the values of Bill Format are shown in the table below. 0 SLCT Please select a Bill Format Type Yes 1 UNKN Unknown Bill Format Type Yes 4.9 C Gender Type The code Bill Frequency table contains the values for how often a bill is sent to a Client. Examples of the values of Bill Frequency are shown in the table below. 0 SLCT Please select a Bill Frequency Type Yes 1 UNKN Unknown Bill Frequency Type Yes 4.10 C Identifier Type The code Charge Type table contains the types of charges that appear as line items on the Matter Bill Detail table. Examples of the values of Charge Type are shown in the table below. 0 SLCT Please select a Charge Type Yes 1 UNKN Unknown Charge Type Yes 3 P Partner hours Yes 4 A Associate hours Yes 5 P Paralegal hours Yes 6 C Court Appearance Yes 7 F Filing Yes 12/14/2008 Page 11

12 4.11 C Language Type The code Charge Type table contains the types of charges that appear as line items on the Matter Bill Detail table. Examples of the values of Charge Type are shown in the table below. 0 SLCT Please select a Charge Type Yes 1 UNKN Unknown Charge Type Yes 3 P Partner hours Yes 4 A Associate hours Yes 5 P Paralegal hours Yes 6 C Court Appearance Yes 7 F Filing Yes 4.12 C Marital Type The code Client Role Type table contains the types of relationships allowed between two clients. Examples of the values of Client Relationship Type are shown in the table below. 0 SLCT Please select a Client Relationship Type Yes 1 UNKN Unknown Client Relationship Type Yes 3 S Super Client Yes 4 SUB Subsidiary of Yes 5 P Partner of Yes 6 I Insurer of Yes 4.13 C Modifier Type The code Client Role Type table contains the types of relationships allowed between two clients. Examples of the values of Client Relationship Type are shown in the table below. 0 SLCT Please select a Client Relationship Type Yes 1 UNKN Unknown Client Relationship Type Yes 3 S Super Client Yes 4 SUB Subsidiary of Yes 5 P Partner of Yes 6 I Insurer of Yes 12/14/2008 Page 12

13 4.14 C Payer Source The code Client Role Type table contains the types of roles allowed for a client in connection with a matter. Examples of the values of Client Role Type are shown in the table below. 0 SLCT Please select a Client Role Type Yes 1 UNKN Unknown Client Role Type Yes 3 P Plaintiff Yes 4 D Defendant Yes 5 PY Payer Yes 6 BC Billing Contact Yes 7 BA Budget Approver Yes 4.15 C Provider Type The code Client Role Type table contains the types of roles allowed for a client in connection with a matter. Examples of the values of Client Role Type are shown in the table below. 0 SLCT Please select a Client Role Type Yes 1 UNKN Unknown Client Role Type Yes 3 P Primary Contact Yes 4 PY Payer Yes 5 BC Billing Contact Yes 6 BA Budget Approver Yes 4.16 C RVU Group The code Compensation Type table contains the types of compensation allowed for an employee. Examples of the values of Compensation Type are shown in the table below. 0 SLCT Please select a Compensation Type Yes 1 UNKN Unknown Compensation Type Yes 3 R Regular Yes 4 YEB Year End Bonus Yes 5 PB Performance Bonus Yes 6 OT Overtime Yes 12/14/2008 Page 13

14 4.17 C Weekday The code Conflict Type table contains the types of conflicts allowed for a matter. Examples of the values of Conflict Type are shown in the table below. 0 SLCT Please select a Conflict Type Yes 1 UNKN Unknown Conflict Type Yes 3 C Client Yes 4 A Adverse Yes 5 PA Potentially Adverse Yes 6 OP Other Party Yes 7 CC Co Client Yes 4.18 ctblmedicalcategory The code Client Role Type table contains the types of roles allowed for a client in connection with a matter. Examples of the values of Client Role Type are shown in the table below. 0 SLCT Please select a Client Role Type Yes 1 UNKN Unknown Client Role Type Yes 3 P Primary Contact Yes 4 PY Payer Yes 5 BC Billing Contact Yes 6 BA Budget Approver Yes 4.19 ctblpovertyregion The code Client Role Type table contains the types of roles allowed for a client in connection with a matter. Examples of the values of Client Role Type are shown in the table below. 0 SLCT Please select a Client Role Type Yes 1 UNKN Unknown Client Role Type Yes 3 P Primary Contact Yes 4 PY Payer Yes 5 BC Billing Contact Yes 6 BA Budget Approver Yes 12/14/2008 Page 14

15 4.20 ctblservicecategory The code Client Role Type table contains the types of roles allowed for a client in connection with a matter. Examples of the values of Client Role Type are shown in the table below. 0 SLCT Please select a Client Role Type Yes 1 UNKN Unknown Client Role Type Yes 3 P Primary Contact Yes 4 PY Payer Yes 5 BC Billing Contact Yes 6 BA Budget Approver Yes 4.21 ctblservicegroup The code Client Role Type table contains the types of roles allowed for a client in connection with a matter. Examples of the values of Client Role Type are shown in the table below. 0 SLCT Please select a Client Role Type Yes 1 UNKN Unknown Client Role Type Yes 3 P Primary Contact Yes 4 PY Payer Yes 5 BC Billing Contact Yes 6 BA Budget Approver Yes 4.22 ctblvisittype The code Client Role Type table contains the types of roles allowed for a client in connection with a matter. Examples of the values of Client Role Type are shown in the table below. 0 SLCT Please select a Client Role Type Yes 1 UNKN Unknown Client Role Type Yes 3 P Primary Contact Yes 4 PY Payer Yes 5 BC Billing Contact Yes 6 BA Budget Approver Yes 12/14/2008 Page 15

16 5. TRANSLATION TABLES 5.1 Introduction To implement the data model using declared referential integrity we use validation tables. The validation (code) tables have defined relationships to some of the attributes of the data model. The attributes that reference the validation tables are only allowed a limited set of values. The validation tables contain those allowed values. For completeness, each validation table contains codes for SLCT (the default value) and UNKN (correct value not in list). The values in the validation tables are never deleted; they are marked as not in use. The referential integrity requirement of the database means that deleting a validation value may delete multiple rows in the data tables. Since the function of all of the validation tables is identical, the structure of all of the tables is the same. The structure is shown in the table below. Code ID Number (Long) AutoNumber An identifier attribute type created by the DBMS and used as a primary key. Short Code Text 10 The mnemonic code which the application users use for this row value and used as a primary key (i.e., no duplicate values allowed). Description Text 255 The long description of the value that was identified by the short code. Sort Order Number (Long) The order in which the table rows will be displayed In Use Yes/No Yes A flag to indicate whether or not to show the row in a pull down list when entering data. TranslatedCode Long Integer 0 The validation code used to translate this affiliate code. Audit Trail Event Date/Time Now() The date and time at which this table row was last updated Audit Trail Process Text 50 NT Logon ID The user id or process name that last updated this table row 12/14/2008 Page 16

17 5.2 A Contraception Type The code Address Type table contains the types of address allowed for a Client. Examples of the values of Address Type are shown in the table below. 0 SLCT Please select a Client Address Type Yes 1 UNKN Unknown Client Address Type Yes 3 HO Head Office Yes 4 BA Billing Address Yes 5 SA Client Primary Address Yes 6 RGN1 Region 1 Address Yes 7 RGN2 Region 2 Address Yes 5.3 A Diagnosis Type The code Appearance Type table contains the types of appearances allow for a matter before a court. Examples of the values of Appearance Type are shown in the table below. 0 SLCT Please select a Appearance Type Yes 1 UNKN Unknown Appearance Type Yes 5.4 A Ethnicity Type The code Arbiter Role Type table contains the types of roles allowed for an Arbiter. Examples of the values of Arbiter Role are shown in the table below. 0 SLCT Please select an Arbiter Role Type Yes 1 UNKN Unknown Arbiter Role Type Yes 3 J Judge Yes 4 M Mediator Yes 5 A Arbitrator Yes 12/14/2008 Page 17

18 5.5 A Expense Type The code Bill Contents table contains the types of billing contents (level of billing detail) available for a Matter. Examples of the values of Bill Content are shown in the table below. 0 SLCT Please select a Bill Contents Type Yes 1 UNKN Unknown Bill Contents Type Yes 5.6 A Gender Type The code Bill Format table contains the types of billing layout formats available for a Matter. Examples of the values of Bill Format are shown in the table below. 0 SLCT Please select a Bill Format Type Yes 1 UNKN Unknown Bill Format Type Yes 5.7 A Language Type The code Bill Frequency table contains the values for how often a bill is sent to a Client. Examples of the values of Bill Frequency are shown in the table below. 0 SLCT Please select a Bill Frequency Type Yes 1 UNKN Unknown Bill Frequency Type Yes 12/14/2008 Page 18

19 5.8 A Marital Status Type The code Client Role Type table contains the types of relationships allowed between two clients. Examples of the values of Client Relationship Type are shown in the table below. 0 SLCT Please select a Client Relationship Type Yes 1 UNKN Unknown Client Relationship Type Yes 3 S Super Client Yes 4 SUB Subsidiary of Yes 5 P Partner of Yes 6 I Insurer of Yes 5.9 A Payer Source The code Client Role Type table contains the types of relationships allowed between two clients. Examples of the values of Client Relationship Type are shown in the table below. 0 SLCT Please select a Client Relationship Type Yes 1 UNKN Unknown Client Relationship Type Yes 3 S Super Client Yes 4 SUB Subsidiary of Yes 5 P Partner of Yes 6 I Insurer of Yes 5.10 A Provider Type The code Client Role Type table contains the types of roles allowed for a client in connection with a matter. Examples of the values of Client Role Type are shown in the table below. 0 SLCT Please select a Client Role Type Yes 1 UNKN Unknown Client Role Type Yes 3 P Plaintiff Yes 4 D Defendant Yes 5 PY Payer Yes 6 BC Billing Contact Yes 7 BA Budget Approver Yes 12/14/2008 Page 19

20 5.11 Atbl Visit Type The code Client Role Type table contains the types of roles allowed for a client in connection with a matter. Examples of the values of Client Role Type are shown in the table below. 0 SLCT Please select a Client Role Type Yes 1 UNKN Unknown Client Role Type Yes 3 P Plaintiff Yes 4 D Defendant Yes 5 PY Payer Yes 6 BC Billing Contact Yes 7 BA Budget Approver Yes 12/14/2008 Page 20

21 6. PPFA ORGANIZATION DATA 6.1 Introduction The company organization is the structuring of the positions in the firm into an organizational chart. The basis of the company organization is the Position data object that contains the identification and description of all the Positions (or offices) that are planned by the business. 6.2 Data Model Affiliate AffiliateID Center CenterKey Center Location History CenterKey Clinic ClinicKey ClinicKey Hours Of Operation Clinic RVU History 6.3 t Affiliate The table contains the relationship between a position and a node in the company organization chart. AffiliateID Name Text 255 The description of this table row InUse BooleanFlag PovertyRegion Enumerated /14/2008 Page 21

22 6.4 d Center The table contains the list of all of the physical location utilized by an Affiliate to hold clinics. AffiliateID An identifier attribute type created by the DBMS used as the primary key CenterID Text 255 The description of this table row CenterKey Autonumber Name Text 255 The description of this table row InUse BooleanFlag 6.5 d Center Location History The table contains all of the company organization charts. CenterKey ChangeDate Date OfficialName Text 100 Street Text 50 City Text 50 State Enumerated ZIPCode Text 10 CenterSize Float CenterSizeUoM Enumerated 6.6 d Clinic The table contains the reason why the company organization chart was created. AffiliateID ClinicID ClinicKey AutoNumber Name Text 255 The description of this table row CenterKey InUse BooleanFlag TitleTen BooleanFlag 12/14/2008 Page 22

23 6.7 d Clinic RVU History The table contains history of the status changes of the position from the position inception to its redundancy. ClinicKey StartDate Date EndDate Date WorkRVUFactor Float PracticeRVUFactor Float PLIRVUFactor Float 6.8 d Hours of Operation The table contains history of the status changes of the position from the position inception to its redundancy. ClinicKey ChangeDate Date WeekDay Enumerated StartTime ClockTime EndTime ClockTime ElapsedTime Float ElapsedTimeUoM Enumerated 12/14/2008 Page 23

24 7. PATIENT DATA 7.1 Introduction Client is a data object that contains all of the data (identification and detailed description) of all the legal entities (companies and individuals) that pay for the products sold by the business. Client is a list of the legal entities that have paid for products produced by the business. When a business institutes a charge back program, the business becomes its own client. 7.2 Data Model Affiliate AffiliateID Patient Translation PatientKey Patient PatientKey PatientKey Patient History Patient Comments 7.3 t Patient Translation The table contains the relationship between the matter and the client contact. AffiliateID Number (Long) 0 ClinicID Text 0 PatientID Text 0 PatientKey Autonumber 0 12/14/2008 Page 24

25 7.4 d Patient This table contains the list of all the clients. PatientKey Number (Long) FirstName Text 255 MiddleName Text 255 LastName Text 255 DateOfBirth Date FirstVisit Date Gender Enumerated Ethnicity Enumerated Hispanic Yes/No No ExtractedDate Date 7.5 d Patient Comments The table contains the list of addresses where the Client can be reached. PatientKey Number (Long) CommentDate Date CommentType Enumerated Comments Memo ExtractedDate Date 7.6 d Patient History The table contains the list of people who work for the Client and their involvement (roles) at the Client. PatientKey Number (Long) ChangeDate Date VisitType Enumerated ContraceptionMethod Enumerated FamilySize Number (Long) SeasonalWorker Boolean GrossIncomeAmount Currency GrossIncomeCurrency Enumerated GrossIncomeRate Enumerated 50 MaritalStatus Enumerated ZIPCode Text 10 PrimaryPayer Enumerated LanguageUsed Enumerated ExtractedDate Date 12/14/2008 Page 25

26 8. PRODUCT DATA 8.1 Introduction Product is a data object that contains all of the data (identification and detailed specifications) of all the tangible goods, information or services that the business plans to sell. Product is a list of the items available to be sold by the business. 8.2 Data Model Product Affiliate maps to Product PPFA PPFAProductKey Product Value History 8.3 D Product Affiliate The table contains the list of all the Affiliate s products. ProductKey An identifier attribute type created by the DBMS used as the primary key AffiliateProductKey Text 255 Description Text 255 The description of this table row BillingCode Text ChargeCode Enumerated DoNotReport BooleanFlag PPFAProductKey InUse BooleanFlag 12/14/2008 Page 26

27 8.4 D Product PPFA The table contains the relationship between the matter and the product. PPFAProductKey The identifier for each PPFA product in the table Description Text 255 The description of this table row InUse BooleanFlag A flag to indicator that this PPFA product is still in use Gender Text 6 A flag to indicator that this PPFA product is still in use ServiceCategory Enumerated The AASC category for this PPFA product ServiceGroup Enumerated The group for this PPFA product MedicalCategory Enumerated Judie s idea CategoryDetail Text 255 The line item description of the AASC category CPTCode Text 5 r The CPT code for this PPFA Product ModifierCode Text 5 The CPT code modifier for this PPFA Product IdentifierCode Text D Product Value History The table contains the relationship between the practice group and the product. PPFAProductKey StartDate Date EndDate Date RelativeValueUnit Float WorkRVU Float PracticeRVU Float PLIRVU Float StAnthonyRVU Float PriceAmount Currency r PriceCurrency Enumerated PriceRate Enumerated 12/14/2008 Page 27

28 9. PROVIDER DATA 9.1 Introduction Employee is a data object that contains all of the data (identification and detailed description) of all the individuals that provide labor for the business. Employee is a list of the individuals who have been paid for their labor. These individuals are directors, partners, full-time employees, part-time employees, contractors, temporaries, etc. 9.2 Data Model The data required for employee is so extensive, that the data model is shown in three parts, generic employee (on this page), employment history (on the next page), and Brobeck s additional data. Affiliate Employs Provider Translation ProviderKey Provider ProviderKey Works At ClinicKey Clinic 9.3 t Provider Translation The table contains the list of employees current addresses. AffiliateID Number (Long) 0 ProviderID Number (Long) ProviderKey Number (Long) 12/14/2008 Page 28

29 9.4 D Provider Planned Parenthood The table contains the list of all the employees. ProviderKey Number (Long) FirstName Text 50 MiddleName Text 50 LastName Text 50 ProviderType Enumerated LicenseID Text LicenseIssuer Enumerated ExtractedDate Date 9.5 r Works at The table contains the list of employees current addresses. ProviderKey Number (Long) ClinicKey Number (Long) ChangeDate Date 0 WeekDayCode Enumerated AmountAssigned Float r AmountAssignedUoM Enumerated AmountPaidAmount Currency r AmountPaidCurrency Enumerated AmountPaidRate Enumerated ExtractedDate Date 12/14/2008 Page 29

30 10. TASK DATA 10.1 Introduction The business processes are the organization of the activities performed in delivering the Products to the Clients. Activity is a data object that contains the identification and description of all the Activities that are planned by the business. These Activities can be processes, functions, tasks, etc Data Model Task maps to Task PPFA 10.3 D Task The table contains the list of the Brobeck activities. TaskID Text Description Text 255 The description of this table row PPFATaskID Text 10.4 d Task PPFA The table contains history of the activity status. PPFATaskID Text Description Text 255 The description of this table row 12/14/2008 Page 30

31 11. VISIT DATA 11.1 Introduction Time Card is the data object that collects the measurements of the time transactions involved in operating the business. The transactions are measurement of the workflows in the operational procedures. Time Cards contains all of the records created in the CMS Time Entry processes Data Model Patient PatientKey Task TaskID Clinic ClinicKey Visit Detail ProductKey Product Affiliate ProviderKey Provider 12/14/2008 Page 31

32 11.3 F Clinic Cost The table contains all of the time spent on the matter PatientKey DateOfService CalendarDate TaskID ProductKey ProviderKey ClientKey ExpenseType Enumerated AmountUsedSize Double AmountUsedUoM Enumerated CostAmount Money CostCurrency Enumerated CostRate Enumerated ExtractedDate CalendarDate 11.4 f Payment Detail The table contains all of the time spent on the matter PatientKey DateOfService CalendarDate TaskID ProductKey ProviderKey ClientKey PaymentSource Enumerated PaymentDate CalendarDate PaymentAmount Money PaymentCurrency Enumerated PaymentRate Enumerated ExtractedDate CalendarDate 12/14/2008 Page 32

33 11.5 f Visit Detail The table contains all of the time spent on the matter PatientKey DateOfService CalendarDate TaskID ProductKey ProviderKey ClientKey DiagnosisCode Enumerated AmountUsedSize Double AmountUsedUoM Enumerated AmountChargedAmoun Money t AmountChargedCurren Enumerated cy AmountChargedRate Enumerated ActualRVU Double ExtractedDate CalendarDate 12/14/2008 Page 33

34

35 12. IMPLEMENTED DATA MODEL 12.1 Complete Data Model Provider_Translation ProviderKey AffiliateID [FK] ProviderID Employs ProviderKey Works_At [As] ClinicKey [FK] ChangeDate ProviderKey [FK] AmountAssigned_size AmountAssigned_uofm AmountPaid_amount AmountPaid_currency AmountPaid_rate ExtractedDate ProviderKey Provider [At] ProviderKey [FK] FirstName MiddleName LastName ProviderType LicenseID LicenseIssuer ExtractedDate PPFA Data Warehouse June 5, 2002 Affiliate AffiliateID Name InUse PovertyRegion AffiliateID AffiliateID Center CenterKey CenterID Name InUse AffiliateID [FK] Center_Location_History [At] ChangeDate CenterKey [FK] OfficialName Street City State ZipCode CenterSize_size CenterSize_uofm CenterKey CenterKey ClinicKey ClinicKey Clinic_RVU_History [At] StartDate ClinicKey [FK] EndDate WorkRVUFactor PracticeRVUFactor PLIRVUFactor Clinic ClinicKey AffiliateID ClinicID Name InUse TitleTen CenterKey [FK] ClinicKey Hours_Of_Operation [At] ClinicKey [FK] ChangeDate WeekDay StartTime EndTime ElapsedTime_size ElapsedTime_uofm ClinicKey PatientKey ProviderKey Payment_Detail PatientKey [FK] DateOfService TaskID [FK] ProductKey [FK] ProviderKey [FK] ClinicKey [FK] PaymentSource PaymentDate AmountPaid_amount AmountPaid_currency AmountPaid_rate ExtractedDate TaskID ProductKey ProviderKey PatientKey ProviderKey Visit_Detail [As] PatientKey [FK] DateOfService TaskID [FK] ProductKey [FK] ProviderKey [FK] ClinicKey [FK] DiagnosisCode ClinicKey AmountUsed_size AmountUsed_uofm AmountCharged_amount AmountCharged_currency AmountCharged_rate ActualRVU ExtractedDate TaskID ProductKey PatientKey Clinic_Cost PatientKey Date_of_Service TaskID ProductKey ProviderKey ClinicKey ExpenseType AmountUsed_size AmountUsed_uofm Cost_amount Cost_currency Cost_rate ExtractedDate ProductKey ClinicKey TaskID Patient_Translation PatientKey AffiliateID [FK] ClinicID PatientID PatientKey Patient_History PatientKey [FK] ChangeDate VisitType ContraceptionMethod FamilySize SeasonalWorker GrossIncome_amount GrossIncome_currency GrossIncome_rate MaritalStatus ZipCode PrimaryPayer LanguageUsed ExtractedDate PatientKey Patient PatientKey [FK] FirstName MiddleName LastName DateOfBirth FirstVisit Gender Ethnicity Hispanic ExtractedDate PatientKey Patient_Comments CommentDate CommentType PatientKey [FK] Comments ExtractedDate Product_Value_History [At] PPFAProductKey [FK] StartDate PPFAProductKey EndDate RelativeValueUnit WorkRVU PracticeRVU PLIRVU StAnthonyRVU Price_amount Price_currency Price_rate Product_Affiliate ProductKey AffiliateProductKey Description BillingCode ChargeCode DoNotReport PPFAProductKey [FK] maps to Product_PPFA PPFAProductKey Description InUse ServiceCategory ServiceGroup MedicalCategory CategoryDetail CPTCode ModifierCode IdentifierCode Task TaskID Description PPFATaskID [FK] maps to Task_PPFA PPFATaskID Description Time DateOfService WeekDay Holiday CalendarQuarter FiscalYear FiscalQuarter FiscalMonth 12/14/2008 Page 35

36

37 12.2 DDL Source The DDL source files can be reverse engineered from the MS SQL Server implementation of the Data Mart database on the SFRSANDBOX5 server Data Dictionary See the document Data Mart-DataDictionary.doc 12/14/2008 Page 37

38 13. REFERENCE MATERIALS 13.1 Import File Formats The data files that are imported into and exported out of the Data Mart database during the Operational Procedures are contained in comma-delimited text files. The first row contains the column header labels in comma-delimited strings. The individual file formats are displayed below ExtractAffiliateCenterList Uses the format of the d Center table ExtractAffiliateCenterLocationHistory Uses the format of the d Center Location History table ExtractAffiliateClinicList Uses the format of the d Clinic table ExtractAffiliateClinicHourOfOperation Uses the format of the d Hours of Operation table ExtractAffiliateClinicRVUHistory Uses the format of the d Clinic RVU History ExtractProvider Uses the format of the d Provider table joined to the t Provider Translation table ExtractPatient Uses the format of the d Patient table joined to the t Patient Translation table ExtractPatientHistory Uses the format of the d Patient History table ExtractPatientVisit Uses the format of the f Visit Detail table ExtractPatientPayment Uses the format of the f Payment Detail table 12/14/2008 Page 38

39 ExtractClinicCost Uses the format of the f Clinic Cost table 13.2 Export File Formats The data files that are imported into and exported out of the Data Mart database during the Operational Procedures are contained in comma-delimited text files. The first row contains the column header labels in comma-delimited strings. The individual file formats are displayed below ExportPovertyData The poverty data is contained in the Client Cube database. When the poverty data changes, the affiliates are sent a new copy of the Client Cube database, which they will then load with their reporting data ExportCPTList Uses the format of the c CPT Code table ExportIdentifierList Uses the format of the c Identifier table ExportModifierList Uses the format of the c Modifier table ExportProductPPFAList Uses the format of the d PPFA Product table ExportProductValueHistory Uses the format of the d Product Value History table 12/14/2008 Page 39