ACTIVE_IND |
DOUBLE |
Y |
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. |
AUTHENTICATION_ID |
DOUBLE |
N |
Identification of person authenticating MDI feed. This column is no longer used and should be considered OBSOLETE. The AUTH table is an obsolete table. |
AUTO_EXPLODE_IND |
DOUBLE |
Y |
MDI flag which designates whether the order is automatically exploded or not. |
AUTO_VERIFY_FLAG |
DOUBLE |
Y |
Not Used |
AV_CHECK_PART_QC_FLAG |
DOUBLE |
N |
A value of 1 indicates that all QC for the run must be in control for autoverification to take place. A value of 2 indicates that if QC for an individual assay is out of control, assay processing for patient results will account for the QC when evaluating orderable parameters. A value of 3 indicates that if QC for an individual assay is out of control, assay processing for patient results will not account for the QC when evaluating orderable parameters and instead will only look at assays that |
AV_CHK_PART_QC_IND |
DOUBLE |
Y |
A value of 0 indicates that if the run for QC is out for the instrument then no autoverify will take place. A value of 1 indicates that if the run for QC is out for the instrument then check the individual assay to see if the instrument is performing the assay okay. |
AV_FLAG |
DOUBLE |
Y |
Determines how the results received from the instrument will automatically verify. |
AV_IND |
DOUBLE |
Y |
A value of 0 means that autoverify is currently turned on for the instrument. A value of 1 means that autoverify is currently turned off for the instrument. |
AV_PART_IND |
DOUBLE |
Y |
0 : Orderable level autoverification with assay results received in single message1: Orderable level autoverification with assay results received in multiple messages |
AV_QC_IND |
DOUBLE |
Y |
A value of 0 indicates that QC will not be autoverified if in control. A value of 1indicates that QC will be autoverifiedif in control. |
AV_QC_PART_IND |
DOUBLE |
Y |
A value of 0 will not allow verification of QC results if any of the results are out of control. A value of 1 will allow verification of each QC result that is in control. |
AV_REQ_QC_IND |
DOUBLE |
Y |
A value of 0 indicates that QC will not be checked before person results will be autoverified. A value of 1 indicates that QC will be checked before person results will be autoverified. |
CONTAINER_IND |
DOUBLE |
Y |
The type of container for the instrument |
CQM_ALIAS_NAME |
VARCHAR(48) |
Y |
The destination for inbound results. Applies to direct download and host query bidirectional interfaces. Similar to version 300's Transmit Queue (TQ) file. Used by the instrument interface team. |
CQM_APP_NAME |
VARCHAR(12) |
Y |
The destination for inbound results. Applies to direct download and host query bidirectional interfaces. Similar to version 300's Transmit Queue (TQ) file. Used by the instrument interface team. |
CQM_CONTRIB_NAME |
VARCHAR(48) |
Y |
Not currently being used as of March 1997 |
DISABLE_MICRO_PROBABILITY_IND |
DOUBLE |
N |
Indicates that the Microbiology Instrument will not send the probability percentage to the instrument interface for organism identification. |
GATE_IND |
DOUBLE |
Y |
For future use with gate indicator and gate codes. |
HOLIDAY_SCHEDULE_CD |
DOUBLE |
N |
The holiday schedule associated with this instrument for autoverification & clinical validation. |
IDENTIFIER_FLAG |
DOUBLE |
Y |
Identifies which type of identifier to use, e.g., accession no., tray/cup, sequence, etc. |
ID_MAP_JULIAN |
CHAR(18) |
Y |
This field represents which digits of the full Julian accession number should be used when generating the Instrument Id Number. The value should consist of a string of 0's and 1's with the 1's representing the digits that should be used to generate the Id number. Example for Vitek: "000000000011001111" This will generate an Id number with the last two digits of the Julian date and the last four digits of the sequence number. |
ID_MAP_PREFIX |
CHAR(18) |
Y |
This field represents which digits of the full prefixed accession number should be used when generating the Instrument Id Number. The value should consist of a string of 0's and 1's with the 1's representing the digits that should be used to generate the Id number. |
ID_NBR_SIZE |
CHAR(2) |
Y |
This field represents the size of the Id number that should be generated based on the limitations of the instrument. This does NOT include the isolate number when determining the size. For Vitek the value should be "06". |
ID_TYPE |
CHAR(1) |
Y |
This field represents whether the Id number should be numeric or alpha numeric based on the instrument limitations. For Vitek it should be "N". |
INSTRU_TYPE |
DOUBLE |
Y |
Indicates how the interface should write the outbound download record when duplicate procedures within an order. There are there option for the instrument type. 1 = insert download records with lock trigger and update logic turned on. This is normally use for direct download 2 = Insert download records with lock trigger and no update turned on. This is normally use for direct download 3 = Insert tq with no trigger but with update logic turned on. This is normally used with host query |
INSTR_ALIAS |
VARCHAR(100) |
Y |
Description of the instrument. User defined. |
INSTR_IDENTIFIER |
DOUBLE |
Y |
For future use with multiplexor logic. |
INSTR_NAME |
VARCHAR(20) |
Y |
For future use with multiplexor logic. |
INTFC_PROGNAME |
CHAR(15) |
Y |
Contains the interface program name for the service resource. |
ISOLATE_NBR_SIZE |
CHAR(1) |
Y |
This field represents the length of the isolate number. The isolate number will be appended to the end of the id number making the full id number that gets generated at susceptibility order time. For Vitek it should be "1". |
ISOLATE_TYPE |
CHAR(1) |
Y |
This field represents how the isolate number should be generated. If it is set to "0" then the isolate number will match with the organism number that the susceptibility is being ordered on. If the susceptibility is ordered on Organism number 2 then the isolate number will be 2. If it is set to "1" then the isolate number will be set to the number of susceptibilities that have been ordered for that accession. It will increment by one with each susceptibility order on the accession. |
LOG_FLAG |
DOUBLE |
N |
Controls log level journaling for MDI capture files |
MIC_AUTO_INTERP_FLAG |
DOUBLE |
Y |
This field is used to determine if interpretations should automatically take place when results are sent back from the instrument. This field is currently not used. |
MIC_DOWNLOAD_LEVEL_FLAG |
DOUBLE |
Y |
Not really sure what this field does, but will find out eventually from Dennis Boyer |
MIC_ID_PROB_LIMIT |
DOUBLE |
Y |
This represents a percentage threshold that the user will set which determine whether organism name changes should occur. If the instrument sends a percent probability of the organism that is greater than or equal to the value in this field then an isolate name change will automatically occur. |
MIC_SEC_INTERP_IND |
DOUBLE |
Y |
If this field is true then second level interps will be fired when results are received from the instrument. This field is currently not used. |
MULTIPLEXOR_ALIAS |
CHAR(20) |
Y |
Identifies the name/code that a multiplexor sends back to MDI via the MDI interface. |
MULTIPLEXOR_IND |
DOUBLE |
Y |
Used to identity if the instrument is a multiplexor. Is 1 if the instrument is a multiplexor, 0 if it is not. |
OPER_MODE |
CHAR(1) |
Y |
Identifies interface functionality with regards to bidirectional, unidirectional or Host Query. B, U, or Q respectively. |
POINT_OF_CARE_FLAG |
DOUBLE |
Y |
Indicates whether the instrument is at the point of patient care or whether it is located in a laboratory location. Filtering mechanism so the Point of Care applications will only display the appropriate instruments and not those in the lab. |
PRSNL_BEG_EFF_DT_TM |
DATETIME |
Y |
to be removed June 1997 |
PRSNL_END_EFF_DT_TM |
DATETIME |
Y |
to be removed June 1997 |
PRSNL_ID |
DOUBLE |
N |
to be removed June 1997 |
RESULT_FORMAT_CD |
DOUBLE |
N |
Identifies the format that will be used for packaging results. |
RMOD |
VARCHAR(20) |
Y |
This stores the revision modification value of the related interface. The value is determined by the type of device. |
ROBOTICS_ALIQUOT_DIGIT |
CHAR(1) |
Y |
Stores the aliquot digit to be appended to the accession for instruments associated to a robotics line. |
ROBOTICS_DEST |
DOUBLE |
Y |
Identifies default destination route/analyzer. |
ROBOTICS_NAME |
VARCHAR(20) |
Y |
Unique identifier for each analyzer connection to the robotics line. |
ROUTE_AT_COMPLETION_IND |
DOUBLE |
Y |
Delays container routing to destination until tests are completed. |
SCHEDULE_CD |
DOUBLE |
N |
The schedule associated with this instrument for autoverification and clinical validation. |
SERVICE_RESOURCE_CD |
DOUBLE |
N |
The internal identifier for the instrument. |
STATION |
CHAR(4) |
Y |
Defines the VMS logical that the interface will use to connect to the analyzer. |
STRT_MODEL_ID |
DOUBLE |
N |
The internal identifier for the instrument's Model. These model id's are a Cerner defined reference database |
UPDATE_REQUEST_NUMBER |
DOUBLE |
N |
Request Number used by MDI Order Server to call a script which formats tests when doing updates. |
UPDT_APPLCTX |
DOUBLE |
N |
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 |
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 |
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 |
N |
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 |
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. |
VERBOSITY |
CHAR(1) |
Y |
Defines the level of journaling by the interface program to the capture files. Off, On, or Debug levels. |
VERIFY_BARCODE_IND |
DOUBLE |
Y |
Enables automatic rerouting if barcodes are misread. |
WORKLIST_BUILD_FLAG |
DOUBLE |
Y |
Indicates how worklists should be built. Valid values are Automatically, Manually, Not used. Functionality is not currently available as of March 1997 |
WORKLIST_HOURS |
DOUBLE |
Y |
The maximum number of hours that a worklist is valid for accepting new accessions |
WORKLIST_MAX |
DOUBLE |
Y |
The maximum number of accessions for a worklist. |