| # | Name | Location | Type | Details | Index | Description |
|---|---|---|---|---|---|---|
| .01 | name(+) | 0;1 | FREE TEXT | B | Name of the load or work list. | |
| .02 | load transform | 0;2 | POINTER | 62.07 | This entry controls the algorithm for placing work on the list. Inquire to the EXECUTE CODES file (Loadlist types) for specifics. Leave this blank unless you want more sophisticated placement. | |
| .03 | type(+) | 0;3 | SET OF CODES | 0:SEQUENCE/BATCH 1:TRAY,CUP 2:POINT OF CARE | Determines if this list is a sequence/batch, tray,cup or Point of Care (POC) type of load/work list. | |
| .04 | cups per tray(+) | 0;4 | NUMERIC | Contains number of cups per tray if a tray,cup type. If you are using Sequence/Batch enter a Zero (0) | ||
| .05 | full tray's only(+) | 0;5 | BOOLEAN | 0:NO 1:YES | If you want to accept full trays only set this field to YES. | |
| .06 | expand panels on print | 0;6 | BOOLEAN | 0:NO 1:YES | If you want test panels expanded to display all tests when printed, this field must contain YES. | |
| .07 | initial setup | 0;7 | POINTER | 62.07 | This code would be used each time a load or work list is built for the first time after it has been "cleared". "Special" initialization may be customized through the EXECUTE CODE chosen. | |
| .08 | verify by | 0;8 | SET OF CODES | A:ACCESSION M:MACHINE SEQUENCE T:TRAY W:WORKLIST | Determines the method of verification for this list. | |
| .09 | suppress sequence # | 0;9 | BOOLEAN | 0:NO 1:YES | "YES" will suppress the sequence # listing. | |
| .1 | include uncollected accessions | 0;10 | BOOLEAN | 0:NO 1:YES | This field is used to tell the load list routine whether to include (if set to YES) ALL accessions that have the tests in the profile, or (if set to NO) only accessions that have ARRIVED in the lab. | |
| .11 | short test list | 0;11 | BOOLEAN | 0:NO 1:YES | If this field contains "YES" a short test list will be generated. | |
| .12 | auto micro edit template | 0;13 | POINTER | 62.07 | Select Execute Code to be associated with this Load/worklist. | |
| .14 | wkld method | SUF;1 | POINTER | 64.2 | This field will be used as default response when setting up WKLD code during verification. This field updated after the technologist confirm the method for this particular verification session. The name and suffix number are automatically stuff for the user. | |
| .15 | wkld code method name | SUF;2 | FREE TEXT | The field should contain the subsection which should receive credit for workload any time a user selects this worklist. | ||
| .16 | wkld code suffix | SUF;3 | FREE TEXT | This field indicates what is the standard default method used by this particular LOAD/WORK LIST. This suffix is appended to prefix or procedure wkld code for each test verified. | ||
| 1 | major accession area | SUF;7 | POINTER | 68 | This field contains the major accession area which should recieve the workload credit. Anytime a user selects this worklist the entry will be used to tally workload. NOTE: THIS FIELD IS ASSOCIATED WITH WORKLOAD. | |
| 1.5 | lab subsection | SUF;8 | POINTER | 68 | This is the next level down from the Major Accession area. An example might be, chemistry is the major accession area and Sp chemistry would be the lab subsection. | |
| 1.7 | work area | SUF;9 | POINTER | 68 | This is the lowest level of work distribution. Generally this would indicate the work bench where the work is to be done. An example might be Chemistry (major accession area), Sp Chemistry (lab sub section) and Drug screens (work area). Note: The default for, major accession area, lab sub section and work area is the entry above it. The order is as follows: Major accession area Default is the accession area of the test. Lab Subsection Default is the Major accession area. Work Area Default is the Lab Subsection. If none of these fields are filled in, then the default answer for all is the accession area of the test. This means the reports will not be broken down into separate areas for any management reports. | |
| 2 | run or tray number | 1;0 | MULTIPLE | 68.21 | All data in this multiple field is computer generated. | |
| 11 | date of setup | 2;1 | DATE-TIME | The date the load/work list was created is stored here. | ||
| 12 | first tray | 2;2 | NUMERIC | The first tray built on the last "build" is stored here. | ||
| 13 | starting cup | 2;3 | NUMERIC | The starting cup (or sequence number) on the last "build" is stored here. | ||
| 14 | last tray | 2;4 | NUMERIC | The last tray built on the last "build" is stored here. | ||
| 15 | last cup | 2;5 | NUMERIC | The last cup (or sequence number) on the last "build" is stored here. | ||
| 30 | building in progress | 3;1 | BOOLEAN | 0:NO 1:YES | While the load list is being built, the program sets this flag to YES. At the completion of building, this flag is returned to NO. The purpose is to keep multiple users from competing for the same load list at the same time. If the flag is left set, set to NO to continue building load lists. | |
| 50 | profile | 10;0 | MULTIPLE | 68.23 | Only ONE load or work list can exist at a time. But more than one profile can be defined to make "alternate" groupings of tests for the load/worklist which might be used on an infrequent or non-standard basis. | |
| 51 | user access authorization | 0;12 | POINTER | 19.1 | If left blank, any lab person may access this load/worklist. If filled in only lab person holding the authorization may use this load/worklist. | |
| 52 | additional lab tests | 4;0 | MULTIPLE | 68.3 | To used for any additional WKLD codes used for this particular W/L. |