| Oracle® Healthcare Data Model Reference 11g Release 2 (11.2) Part Number E18026-02 |
|
|
View PDF |
| Oracle® Healthcare Data Model Reference 11g Release 2 (11.2) Part Number E18026-02 |
|
|
View PDF |
This chapter describes the Oracle Healthcare Data Model utilities.
This chapter includes the following sections:
The Calendar population script consists of a one-time installation package.
The Calendar population procedures are part of the following package:
calendar_population
Running this package does the following:
Prepares necessary changes for the ohdm_sys schema.
Creates the Calendar_Population package that contains the following procedures:
RUN(in_setup_start_date, in_setup_no_years, in_setup_day_of_week)
The main procedure to populate everything about calendar.
RBIW_Base_Time_Tables_ddl
Creates the base table needed to support multiple hierarchies.
RBIW_Populate_Time_Hier_Clndr(in_setup_start_date, in_setup_no_years, in_setup_day_of_week)
Sets up the data in base table for the Calendar hierarchy as specified in setup or install section.
RBIW_Time_hier_Star
Sets up the Time hierarchy reporting layer tables.
To populate calendar data:
Log in to OHDM_SYS user.
Execute the following SQL statement:
exec Calendar_Population.run(date, num_years, start_day_of_week);
where:
date is the start date with which you want to populate calendar data. The date is of type CHAR and should be input in the format 'YYYY-MM-DD' (for example,'2005-05-18').
num_years is the number of years to populate calendar data, which should be INTEGER.
start_day_of_week is the start day of the week, which should be VARCHAR2. Valid values are (case-insensitive): Sunday, Monday, Tuesday, and so on.
Note:
Calendar population starts from the first date of the month specified. For example, specifying '2005-05-18' as the
date input parameter starts Calendar population from the 1st of May, 2005. That is from 01-May-2005.The Oracle Healthcare Data Model metadata editor lets you view the Oracle Healthcare Data Model. The Oracle Healthcare Data Model metadata editor provides information on the data model, including:
All Entities and attributes
All physical tables and columns mapped with entities and attributes
All KPIs Mapped with physical tables
All KPIs Mapped with reports
All physical tables used in the reports
All Oracle Healthcare Data Model Intra-ETL, Mining Mappings using PL/SQL
The Oracle Healthcare Data Model Metadata Editor uses the following tables:
DWR_MD_ENTY Metadata Editor for Oracle Healthcare Data Model
DWR_MD_REF_ENTY_KPI Metadata Editor for Oracle Healthcare Data Model
The DWR_MD_ENTY table shows the entity, attribute, physical table, and column level descriptions.
Table 12-1 describes the DWR_MD_ENTY table columns and data types.
Table 12-1 DWR_MD_ENTY Metadata Table
| S.No | Column Name | Data Type | Column Description | Sample Data |
|---|---|---|---|---|
|
1 |
TABLE_NAME |
VARCHAR2(100 Bytes) |
This is logical entity name used in healthcare LDM. |
ASSET |
|
2 |
COLUMN_NAME |
VARCHAR2(200 Bytes) |
This is logical attribute name used in healthcare LDM |
ACQUISITION COST AMOUNT |
|
3 |
ENTITY_NAME |
VARCHAR2(100 Bytes) |
This is physical table name |
HDM_ASST |
|
4 |
ATTRIBUTE_NAME |
VARCHAR2(200 Bytes) |
This is physical column name |
ACQ_CST_AMT |
The DWR_MD_KPI table shows the KPI level descriptions and programs.
This table includes the KPI name, description, and the correspondence computation logic with associated physical area, and business area.
Table 12-2 describes the DWR_MD_KPI table KPI_ related columns and data types.
Table 12-2 DWR_MD_KPI KPI Metadata Table
| S.No | Column Name | Data Type | Column Description | Sample Data |
|---|---|---|---|---|
|
1 |
KPI_ID |
NUMBER(10,0) |
These are the id's of corresponding kpi's used in current health care data model |
1 |
|
2 |
KPI_NAME |
VARCHAR2(2000 BYTE) |
Name of the KPI |
Heart Failure: Beta-Blocker Therapy for Left Ventricular Systolic Dysfunction |
|
3 |
KPI_DESC |
VARCHAR2(2000 BYTE) |
Description of the KPI |
Percentage of patients aged 18 years and older with a diagnosis of heart failure who also have LVSD (LVEF < 40%) and who were prescribed beta-blocker therapy |
|
4 |
CMPUT_LOGIC |
VARCHAR2(500 BYTE) |
The computation logic |
(Numerator / Denominator) reported as a percentage |
|
5 |
BSNS_AREA |
VARCHAR2(100 BYTE) |
Business Area |
CE |
|
6 |
PHY_AREA |
VARCHAR2(100 BYTE) |
Nothing but subject areas |
OHDM |
The DWR_MD_PRG table also includes the programs in Oracle Healthcare Data Model; this includes the program type, for example Report or the ETL mapping from the SB_PRG_TYP column. The table also show the description for each program and the correspondence paths (this path shows the path where the saved reports in the answers for reports and for ETL mapping what is the Input(I) and the Output(O) for that mapping).
Table 12-3 describes the DWR_MD_PRG related columns and data types.
Table 12-3 DWR_MD_PRG Program Metadata Table
| S.No | Column Name | Data Type | Column Description | Sample Data |
|---|---|---|---|---|
|
1 |
PRG_TYP |
VARCHAR2(2000 BYTE) |
This is the program type used in healthcare weather it is Report or ETL mapping |
Report/ETL Mapping |
|
2 |
PRG_NAME |
VARCHAR2(2000 BYTE) |
Name of the program |
HF Patients that are Prescribed a Beta-Blocker |
|
3 |
PHY_TAB_NAME |
VARCHAR2(2000 BYTE) |
Table used in the program |
ORG_HORG_VIEW |
|
4 |
SB_PRG_TYP |
VARCHAR2(2000 BYTE) |
Nothing but subject area's |
OHDM |
|
5 |
PRG_MODEL_OR_PATH |
VARCHAR2(2000 BYTE) |
This is the corresponding program path /Input or Output |
For reports its /shared/Cardiac/HF Patients that are Prescribed a Beta-Blocker and for ETL it is Input/output |
|
6 |
SB_PRG_DESC |
VARCHAR2(2000 BYTE) |
Description of the corresponding Report or Mapping |
null |
The DWR_MD_REF_ENTY_KPI table provides the Fact table and contains the KPI name, physical table name, and column name associated with the KPI and the corresponding business area.
Table 12-4 describes the DWR_MD_REF_ENTY_KPI table columns and data types.
Table 12-4 DWR_MD_REF_ENTY_KPI Metadata Table
| S.No | Column Name | Data Type | Column Description | Sample Data |
|---|---|---|---|---|
|
1 |
KPI_ID |
NUMBER(10,0) |
These are the id's of corresponding KPIs used in current healthcare data model |
12 |
|
2 |
KPI_NAME |
VARCHAR2(2000BYTE) |
Name of the KPI |
Urinary Incontinence: Characterization of Urinary Incontinence in Women Aged 65 Years and Older |
|
3 |
PHY_AREA |
VARCHAR2(2000BYTE) |
Nothing but subject areas |
OHDM |
|
4 |
BSNS_AREA |
VARCHAR2(2000BYTE) |
Business Area |
CE |
|
5 |
PHY_TAB_NAME |
VARCHAR2(2000BYTE) |
This is the table name which is used in corresponding KPI in healthcare |
DWD_ENC |
|
6 |
PHY_COL_NAME |
VARCHAR2(2000BYTE) |
This is the column name which is used in corresponding KPI in healthcare |
SVCPRVPRCT_ID |
|
 Copyright © 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|