| ACTIVE_IND |
DOUBLE |
N |
The table row is active or inactive. A row is generally active unless it is in an inactive state such as logically deleted, combined away, pending purge, etc. |
| CONCEPT_IDENT |
DOUBLE |
Y |
This column will store the concept id of specimen. Corresponds to Concept_ID in NHSN terminology. Note! This column has been made obsolete. It was decided we needed a Varchar2 column to store this data. |
| CONCEPT_IDENT_TXT |
VARCHAR(60) |
Y |
This column will store the concept id of specimen. Corresponds to Concept_ID in NHSN terminology. This column replaces column CONCEPT_IDENT. It was determined we needed the data stored in a varchar2 data type column. |
| CREATE_DT_TM |
DATETIME |
Y |
The date/time when the specimen was created in the table. |
| IC_CNT_AR_SPEC_MAP_ID |
DOUBLE |
N |
Unique generated number that identifies a single row on the IC_CNT_AR_SPEC_MAP table. |
| SPECIMEN_BEG_EFFECTIVE_DT_TM |
DATETIME |
Y |
This column will store begin effective date of specimen. |
| SPECIMEN_CATEGORY_NAME |
VARCHAR(250) |
Y |
This column will store the category of specimen type(for all blood related it will hold blood and urine related it will hold Urine, etc). |
| SPECIMEN_END_EFFECTIVE_DT_TM |
DATETIME |
Y |
This column will store end effective date of specimen. |
| SPECIMEN_NAME |
VARCHAR(250) |
Y |
This column will store the name of the specimen. |
| UPDT_APPLCTX |
DOUBLE |
Y |
The application context number from the record info block. 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_CNT |
DOUBLE |
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 |
DATETIME |
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_ID |
DOUBLE |
Y |
The person_id of the person from the personnel table (prsnl) that caused the last insert or update of the row in the table. 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_TASK |
DOUBLE |
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. |
