Table Detail Report
LH_IMPORT_QRDA_ATTRIB
| Column Section | Relationship Section | Top of Page |
Table-level Detail
| Description: | LH_IMPORT_QRDA_ATTRIB |
| Definition: | Stores attribute information for data on the LH_IMPORT_QRDA table. |
| Table Type: | ACTIVITY |
Column Detail - LH_IMPORT_QRDA_ATTRIB
| Column Name | Type | Null? | Definition |
|---|---|---|---|
| CODE_DISPLAY | VC2(300) | Y | The human readable display of the code. |
| CODE_SYSTEM | VC2(40) | Y | The OID of the coding system the code is in. |
| CODE_SYSTEM_NAME | VC2(40) | Y | The name of the coding system the code is in. |
| CODE_SYSTEM_SDTC | VC2(100) | Y | The OID of the value set the code is in. |
| CODE_TXT | VC2(50) | Y | The qualifying code for the record. |
| COMP_CODE | VC2(50) | Y | The component code for an encounter attribute(Example: POA-Present On Admission component for a diagnosis). |
| COMP_DISPLAY | VC2(300) | Y | The component display name for an encounter attribute(Example: POA-Present On Admission component for a diagnosis). |
| EFFECTIVE_HIGH_DT_TM | DATE | Y | The high (end) date time associated to the record |
| EFFECTIVE_HIGH_UTC_OFFSET | VC2(5) | Y | Contains the UTC offset for the effective_high_dt_tm (e.g. -0500). |
| EFFECTIVE_LOW_DT_TM | DATE | Y | The low (start) date time associated to the record. |
| EFFECTIVE_LOW_UTC_OFFSET | VC2(5) | Y | Contains the UTC offset for the effective_low_dt_tm (e.g. -0500). |
| EH_CONDITION_MASK | NUMBER | N | A bitmask that identifies what conditions are associated to the record. The conditions correspond to the following numbers: AMI - 1, CAC - 2, ED - 4, EHDI - 8, PC - 16, STK - 32, VTE - 64 |
| HL7_TEMPLATE | VC2(50) | Y | The template defined by HL7 Implementation guide that encapsulates the record. |
| LH_IMPORT_QRDA_ATTRIB_ID | NUMBER | N | Unique generated number that identifies a single row on the LH_IMPORT_QRDA_ATTRIB table. |
| LH_IMPORT_QRDA_ID | NUMBER | N | Corresponds to the unique key on the LH_IMPORT_QRDA table. |
| LOGICAL_DOMAIN_ID | NUMBER | N | The unique identifier for a logical domain. This identifier allows the data to be grouped by logical domain. For example, If you assign clients a logical_domain_id this would allow you to store data for multiple clients on this table. |
| PERSON_ID | NUMBER | N | The primary key of the PERSON table for the person associated to the record. |
| QRDA_IMPORT_VERSION | VC2(10) | Y | Identifier for which version of Import was used to insert the record. |
| RESULT_DT_TM | DATE | Y | DATE and TIME the reut posted |
| RESULT_UNIT | VC2(40) | Y | The units of the numeric result value for the record. |
| RESULT_UTC_OFFSET | VC2(5) | Y | Contains the UTC offset for the result_dt_tm (e.g. -0500). |
| RESULT_VALUE | NUMBER | Y | The numeric result value for the record. |
| TEMPLATE_IDENT | VC2(300) | Y | Data from different sources is stored in different formats (templates). A few template names are Procedure Performed template, Encounter Performed template, Assessment Performed templates, and many more. The data from these templates will be stored in the lh_import_qrda* tables. Each of these templates will have its unique identifier. The template_ident column will store this identifier. |
| UPDT_CNT | NUMBER | N | Set to 0 on insert. Incremented by 1 on update. Used to recognize update conflict where data in a row updated by one application is at risk of being lost by a second application attempting to update the row. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
| UPDT_DT_TM | DATE | N | The date and time the row was last inserted or updated. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
| UPDT_SOURCE | VC2(50) | N | The name of the program that updated the record last. |
| UPDT_TASK | VC2(50) | N | The registered (assigned) task number for the process that inserted or updated the row. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
| VALUE_SET | VC2(255) | Y | The name of the value set the record corresponds to. |
Relationship Detail - LH_IMPORT_QRDA_ATTRIB
| Child Column in LH_IMPORT_QRDA_ATTRIB(FK) | Parent Table Name | Parent Column Name | |
|---|---|---|---|
| Parents: | LH_IMPORT_QRDA_ID | LH_IMPORT_QRDA | LH_IMPORT_QRDA_ID |
LH_IMPORT_QRDA_SUPP
| Column Section | Top of Page |
Table-level Detail
| Description: | LH_IMPORT_QRDA_SUPP |
| Definition: | Stores supplemental data from the QRDA Category 1 files being imported. |
| Table Type: | ACTIVITY |
Column Detail - LH_IMPORT_QRDA_SUPP
| Column Name | Type | Null? | Definition |
|---|---|---|---|
| LH_IMPORT_QRDA_SUPP_ID | NUMBER | N | Unique generated number that identifies a single row on the LH_IMPORT_QRDA_SUPP table. |
| LOGICAL_DOMAIN_ID | NUMBER | N | The unique identifier for a logical domain. This identifier allows the data to be grouped by logical domain. For example, If you assign clients a logical_domain_id this would allow you to store data for multiple clients on this table. |
| PARENT_ENTITY_ID | NUMBER | Y | Identifies the unique source within the delivery network responsible for supplying the data. |
| PARENT_ENTITY_NAME | VC2(30) | Y | The table name associated to the parent_entity_id column. Currently that is LH_IMPORT_QRDA |
| PERSON_ID | NUMBER | N | The primary key of the PERSON table for the person associated to the record. |
| SUPP_DATA_TXT | VC2(100) | Y | The value of the supplemental type stored on the record coming from the file. |
| SUPP_DATA_TYPE | VC2(50) | Y | Identifies the type of supplemental data that is being stored for this record |
| UPDT_CNT | NUMBER | N | Set to 0 on insert. Incremented by 1 on update. Used to recognize update conflict where data in a row updated by one application is at risk of being lost by a second application attempting to update the row. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
| UPDT_DT_TM | DATE | N | The date and time the row was last inserted or updated. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
| UPDT_SOURCE | VC2(50) | N | The name of the program that updated the record last. |
| UPDT_TASK | VC2(50) | N | The registered (assigned) task number for the process that inserted or updated the row. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
LH_PERFORMANCE_AUDIT
| Column Section | Relationship Section | Top of Page |
Table-level Detail
| Description: | LH_PERFORMANCE_AUDIT |
| Definition: | Contains performance data captured during the Lighthouse Reporting load process. |
| Table Type: | ACTIVITY |
Column Detail - LH_PERFORMANCE_AUDIT
| Column Name | Type | Null? | Definition |
|---|---|---|---|
| CATEGORY_MEAN | VC2(30) | N | Unique name given to each Category. This column corresponds to the CATEGORY_MEAN column on the BR_DATAMART_CATEGORY table. |
| DATE_RANGE_END_DT_TM | DATE | Y | The end date/time of the window used to determine the Population for a category |
| DATE_RANGE_START_DT_TM | DATE | Y | The start date/time of the window used to determine the Population for a category |
| ELAPSED_TIME | NUMBER | Y | The time (in seconds) it took for the query to complete |
| END_DT_TM | DATE | Y | The date/time the query finished |
| EXTRACT_DT_TM | DATE | Y | The date/time that the record was extracted from the source system. |
| FIRST_PROCESS_DT_TM | DATE | Y | The date/time that the first ETL process started that created this record. |
| HEALTH_SYSTEM_ID | NUMBER | N | The identifier of the health system |
| HEALTH_SYSTEM_SOURCE_ID | NUMBER | N | The identifier of the source of the health system. |
| LAST_PROCESS_DT_TM | DATE | Y | The date/time that the last ETL process started that updated this record. |
| LH_PERFORMANCE_AUDIT_ID | NUMBER | N | Unique identifier for the lighthouse Performance Audit |
| LOGICAL_DOMAIN_ID | NUMBER | N | The unique identifier for a logical domain. This identifier allows the data to be grouped by logical domain. For example, If you assign clients a logical_domain_id this would allow you to store data for multiple clients on this table. |
| MEASURE_DESC | VC2(50) | N | Name given to the query. A category can have numerous queries and this name will be unique per Category |
| PROCESS_DT_TM | DATE | Y | The date/time that the Category started processing. All queries per Category run will have the same process_dt_tm |
| RECORD_CNT | NUMBER | Y | The number of records used to drive the query. This will usually be the Population Count of the Category |
| START_DT_TM | DATE | Y | The date/time the query started |
| STATUS_FLAG | NUMBER | Y | 1 = Completed Successfully 2 = Completed with Errors 3 = Pending (query has not finished) |
| UPDT_CNT | NUMBER | N | Set to 0 on insert. Incremented by 1 on update. Used to recognize update conflict where data in a row updated by one application is at risk of being lost by a second application attempting to update the row. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
| UPDT_DT_TM | DATE | N | The date and time the row was last inserted or updated. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
| UPDT_SOURCE | VC2(50) | N | The script name responsible for updating the record. |
| UPDT_TASK | VC2(50) | N | The registered (assigned) task number for the process that inserted or updated the row. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
Relationship Detail - LH_PERFORMANCE_AUDIT
| Child Column in LH_PERFORMANCE_AUDIT(FK) | Parent Table Name | Parent Column Name | |
|---|---|---|---|
| Parents: | LOGICAL_DOMAIN_ID | LOGICAL_DOMAIN | LOGICAL_DOMAIN_ID |
LH_PROMPT_CCN_LIST
| Column Section | Top of Page |
Table-level Detail
| Description: | LH_PROMPT_CCN_LIST |
| Definition: | This table will contain the ccn informaiton needed for stage 3 prompt |
| Table Type: | REFERENCE |
Column Detail - LH_PROMPT_CCN_LIST
| Column Name | Type | Null? | Definition |
|---|---|---|---|
| BR_CCN_ID | NUMBER | N | The unique number for the organization coming from br_ccn table |
| CCN_NAME | VC2(100) | Y | The name of the organization** OBSOLETE COLUMN ** |
| EXTRACT_DT_TM | DATE | Y | Date and time when the load was run and the row qualified |
| FIRST_PROCESS_DT_TM | DATE | Y | The date/time that the first ETL process started that created this record. |
| HEALTH_SYSTEM_SOURCE_ID | NUMBER | N | Identifies the unique source within the delivery network responsible for supplying the data. |
| LAST_PROCESS_DT_TM | DATE | Y | The date/time that the last ETL process started that updated this record. |
| LH_PROMPT_CCN_LIST_ID | NUMBER | N | Unique generated number that identifies a single row on the LH_PROMPT_CCN_LIST table. |
| LOC_BEG_EFFECTIVE_DT_TM | DATE | Y | Begin Effective Date and Time coming from Location Table.** OBSOLETE COLUMN ** |
| LOC_END_EFFECTIVE_DT_TM | DATE | Y | End Effective Date and Time coming from Location Table.** OBSOLETE COLUMN ** |
| LOGICAL_DOMAIN_ID | NUMBER | N | The unique identifier for a logical domain. This identifier allows the data to be grouped by logical domain. For example, If you assign clients a logical_domain_id this would allow you to store data for multiple clients on this table. |
| ORGANIZATION_ID | NUMBER | N | Organization Id coming from Organization table. |
| ORG_BEG_EFFECTIVE_DT_TM | DATE | Y | Begin Effective Date and Time coming from Organization Table.** OBSOLETE COLUMN ** |
| ORG_END_EFFECTIVE_DT_TM | DATE | Y | End Effective Date and Time coming from Organization Table.** OBSOLETE COLUMN ** |
| PERSON_ID | NUMBER | N | Person Id coming from Prsnl table |
| TAX_ID_NBR_TXT | VC2(50) | Y | the number assigned for each organization |
| UPDT_CNT | NUMBER | Y | Set to 0 on insert. Incremented by 1 on update. Used to recognize update conflict where data in a row updated by one application is at risk of being lost by a second application attempting to update the row. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
| UPDT_DT_TM | DATE | Y | The date and time the row was last inserted or updated. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
| UPDT_SOURCE | VC2(50) | Y | The source which update/inserted the row |
| UPDT_TASK | VC2(50) | Y | The registered (assigned) task number for the process that inserted or updated the row. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
LH_PROMPT_EP_LIST
| Column Section | Top of Page |
Table-level Detail
| Description: | LH_PROMPT_EP_LIST |
| Definition: | This table contains the information about br_eligible_provider |
| Table Type: | REFERENCE |
Column Detail - LH_PROMPT_EP_LIST
| Column Name | Type | Null? | Definition |
|---|---|---|---|
| BR_ELIGIBLE_PROVIDER_ID | NUMBER | N | Br_eligible_provider_id |
| EP_NAME | VC2(100) | Y | Name of the provider |
| EXTRACT_DT_TM | DATE | Y | Date and time when the load was run and the row qualified |
| FIRST_PROCESS_DT_TM | DATE | Y | The date/time that the first ETL process started that created this record. |
| HEALTH_SYSTEM_SOURCE_ID | NUMBER | N | Identifies the unique source within the delivery network responsible for supplying the data. |
| LAST_PROCESS_DT_TM | DATE | Y | The date/time that the last ETL process started that updated this record. |
| LH_PROMPT_EP_LIST_ID | NUMBER | N | Unique generated number that identifies a single row on the LH_PROMPT_EP_LIST table. |
| LOGICAL_DOMAIN_ID | NUMBER | N | The unique identifier for a logical domain. This identifier allows the data to be grouped by logical domain. For example, If you assign clients a logical_domain_id this would allow you to store data for multiple clients on this table. |
| NPI_TXT | VC2(100) | Y | Unique number associated with the providers |
| ORGANIZATION_ID | NUMBER | N | Organization_ID coming from Organization Table. |
| PERSON_ID | NUMBER | N | Person id of the provider from prsnl table |
| POR_BEG_EFFECTIVE_DT_TM | DATE | Y | Beg Effective Dt tm coming from PRSNL_ORG_RELTN Table. |
| POR_END_EFFECTIVE_DT_TM | DATE | Y | End Effective Dt tm coming from PRSNL_ORG_RELTN Table. |
| PROVIDER_ID | NUMBER | N | Provider id from the br_eligible_provider table |
| UPDT_CNT | NUMBER | Y | Set to 0 on insert. Incremented by 1 on update. Used to recognize update conflict where data in a row updated by one application is at risk of being lost by a second application attempting to update the row. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
| UPDT_DT_TM | DATE | Y | The date and time the row was last inserted or updated. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
| UPDT_SOURCE | VC2(50) | Y | The source which updated/inserted the row |
| UPDT_TASK | VC2(50) | Y | The registered (assigned) task number for the process that inserted or updated the row. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |