LIS Accession Assignment Rule
This rule provides a way to assign or receive the LIS Accession and Container ID. The LIS, or lab, accession is defined as the accession number that the clinical testing system requires for operation. The lab accession number is a separate identifier from the FAST accession number and the container ID, CID, value.
FAST can be configured to create an alphanumeric accession number and export it to the LIS as its own accession number.
The Lab Accession value created in FAST can be sent across interfaces and printed in labels.
The FAST outbound interface and the LIS interfaces must be modified to export the lab accession value to the LIS. (how do we do this, to where can we refer the reader for more info about modifying the interfaces?)
With the assistance of Rhodes, the system and its interfaces can be configured to:
- create a lab accession and send it to the LIS.
- have the lab accession value sent to FAST from the LIS. (how do we do this, to where can we refer the reader for more info?)
The system can also operate in mixed mode; it can assign and receive lab accession values from the client LIS.
The lab accession assignment process is inherited by the Container Management process built into the system. FAST assigns the lab accession value as the last step of the container management process. The system provides two different options for grouping tests into an accession.
Before choosing and activating an option, you must define, enter values for, these parameters for creation of the lab accession number.
- FO_LabInfo.LabAccessionFormat: Defines the format for creation of lab accession values. Use the Rhodes recommended value of 1A,8N. The format '1A,8N' generates lab accessions that are one alpha character followed by 8 numeric characters.
- FO_LabInfo.LABAccessionAlphaCharacters: Determines which alpha characters will be utilized for the lab accession. If this field is left blank then the default is all, any, 26 letters of the English alphabet. (if this field is defaulted to all 26 letters, is there any order in which they are assigned?)
- FO_Users.LabelExpirationSeconds: Defines the number of seconds the system will wait for the LIS to return a lab accession value before qualifying a label to print. Enter an integer for the number of seconds. Enter a 1 if FAST will be assigning the accession number.
- FO_MergeTable_Definition.LabAcc: Provides a valid column name for lab accession number. This establishes an alias or cross reference for this data elements in the merge process since the same data element might be posted to multiple tables.
- Determine usage of, and use, if needed, the zerofillabacc permission. When this permission is used, the lab accession number generated by FAST will be left-zero filled, or prefixed with zeroes.
See the FO_LabInfo
for more information about field definitions and allowed values.
See the FO_Users
for more information about field definitions and allowed values.
See the FO_MergeTable_Definitions
for more information about field definitions and allowed values.
The two options for grouping tests into an accession number are shown below:
Assign one lab accession for each container ID created.
A lab accession number is created for the tests contained in each container ID, CID, when the container ID is assigned during the order process. This mode can be used when you want to create a CID-like environment on an LIS that does not support container management. (but above states that the Container management process is built into the system. are there legacy systems that don’t have that process or do some sites just choose not to use it and to do this instead.)FAST ensures that each accession in the LIS matches a unique container.
The lab accession number is created when the system assigns a container ID to a test code during the order process.
Note: This logic path is only activated when the system creates container ID values. If a user is not assigned permission to create containers, then that user cannot create lab accessions.
To activate this rule, you must:
- assign permission assignlabacc to a user group.
Grouping Code Lab Accessing Assignment
Create a lab accession number and group tests to that lab accession number based on a grouping code assigned at test level. (Is it true that this option also creates a lab accession number?, if not, how does it get created?)
Note: This function should NOT be used if you create container ID specific lab accessions.
This function should be considered where the LIS accepts a container ID separately from the lab accession.
To activate this rule, you must:
- assign permission makelabaccgrp to a user group.
- FO_Tests.LISAccGrpCode: Determines how the system should group tests to a lab accession. Enter a valid grouping code. This grouping code will allow the system to group multiple containers in a single lab accession. All tests that have the same value for the FO_Tests.LISAccGrpCode field are grouped together into one lab accession value.
See FO_Tests
for more information about field definitions and allowed values.