Table List

Database Tables

 Pages produced by a web-based metadata application,
which joins the database dictionary to
entity-level information entered by the analyst.
See the author's web page

Table Details :: LAB_RESULT

 

LAB_RESULT

Description:Results of lab tests. Each row is one result. Multiple results are linked to one sample drawn from the patient.
What defines a unique row:The logical key is CLINIC_ID, PATIENT_ID, DRAW_DATE, and RESULT_TYPE. Only one row with CURRENT_ROW_IND='Y' is expected for each logical key. The logical key and the INSERT_DATE consitute the database unique key.
Current rows:CURRENT_ROW_IND = 'Y'
Historical rows:CURRENT_ROW_IND = 'N'

 

Show more details

S.LAB_RESULT in DEMODB

 

view S.LAB_RESULT_VW in DEMODB

 
S.LAB_RESULT_VW
Column Name Type   Column Name Type  
PATIENT_IDComments:
Patient record number
Joins:
Join to table S.PATIENT on:
PATIENT_ID = PATIENT_ID
Sources:
Clinical System: clin.rslt.patient_number		 NUMBER(22)  PATIENT_IDComments:
Patient record number
Joins:
Join to table S.PATIENT on:
PATIENT_ID = PATIENT_ID
Sources:
Clinical System: clin.rslt.patient_number		 NUMBER(22) 
CLINIC_IDComments:
Clinic number
Joins:
Join to table S.CLINIC on:
CLINIC_ID = CLINIC_ID
Sources:
Clinical System: clin.rslt.clinic_number		 NUMBER(22)  CLINIC_IDComments:
Clinic number
Joins:
Join to table S.CLINIC on:
CLINIC_ID = CLINIC_ID
Sources:
Clinical System: clin.rslt.clinic_number		 NUMBER(22) 
RESULT_TYPEComments:
Hemoglobin, albumin, ... Linked to reference table
Joins:
Join to table S.LAB_RESULT_TYPE on:
RESULT_TYPE = S.LAB_RESULT_TYPE.LAB_RESULT_TYPE_CODE
Sources:
Clinical System: clin.rslt.result_type		 VARCHAR2(18)  RESULT_TYPEComments:
Hemoglobin, albumin, ... Linked to reference table
Joins:
Join to table S.LAB_RESULT_TYPE on:
RESULT_TYPE = S.LAB_RESULT_TYPE.LAB_RESULT_TYPE_CODE
Sources:
Clinical System: clin.rslt.result_type		 VARCHAR2(40) 
     LAB_RESULT_TYPE_DESCRIPTIONComments:
Available in the view based on join to the reference table		 VARCHAR2(18) 
DRAW_DATEComments:
The date when the sample was drawn from the patient
Sources:
Clinical System: clin.rslt.blood_draw_dt		 DATE(7)  DRAW_DATEComments:
The date when the sample was drawn from the patient
Sources:
Clinical System: clin.rslt.blood_draw_dt		 DATE(7) 
VALUEComments:
The value returned by the lab
Sources:
Clinical System: clin.rslt.result_value		 NUMBER(22)  VALUEComments:
The value returned by the lab
Sources:
Clinical System: clin.rslt.result_value		 NUMBER(22) 
UNITSComments:
Unit of measure for the value, also known as dimension
Sources:
Clinical System: clin.rslt.result_unit		 VARCHAR2(9)  UNITSComments:
Unit of measure for the value, also known as dimension
Sources:
Clinical System: clin.rslt.result_unit		 VARCHAR2(9) 
RANGEComments:
Range of acceptable values
Sources:
Clinical System: clin.rslt.result_range		 VARCHAR2(20)  RANGEComments:
Range of acceptable values
Sources:
Clinical System: clin.rslt.result_range		 VARCHAR2(20) 
INSERT_DATEComments:
Date row was inserted into the table
Sources:
ETL: audit_columns.g.system_date_at_insert		 DATE(7)  INSERT_DATEComments:
Date row was inserted into the table
Sources:
ETL: audit_columns.g.system_date_at_insert		 DATE(7) 
UPDATE_DATE DATE(7)     
CURRENT_ROW_IND VARCHAR2(5)     

 

Show sources for LAB_RESULT

Table Diagram:

Table diagram

Sample query script:

Highlight all, copy to clipboard, and paste as needed

 

 

 

 

Although I worked at the world's largest provider of dialysis services, this data model is my invention.
It is a simplified model that serves as an example for the metadata application that I built.
It does not describe the data model of the company.

Version 2.0, 2014-05-02 13:52:48,  Questions? Contact 'chris _ thullen (a) yekesys d0t c0m'