Maintenance of the RPMS Lab Package LAB for Non-Laboratorians Resource Patient Management System

Laboratory Software Maintenance Goals Upon completion of this objective, you should be able to: Perform preventative maintenance for the Laboratory Software Package Troubleshoot common problems Understand the interactions of the Laboratory/Patient Care Component/Third Party Billing Applications

Preventative Maintenance for the Laboratory Software Package Daily: Check the Link Transaction Processor Status. The Link Transaction Processor Status (LS) option is located in the BLR Menu. This option checks the status of the link between the Laboratory software package and PCC.

Preventative Maintenance for the Laboratory Software Package (cont.) Select LS from the BLR Menu

Preventative Maintenance for the Laboratory Software Package (cont.)

To access the report: CORE  LAB  SUPERVISOR  CUMULATIVE MENU Quarterly or as needed: Check Diagnostic routine for Lab Reports file (64.5) (Supervisor’s Menu/Cumulative Menu). This option checks the LAB REPORTS File (64.5) for erroneous entries and gives fatal and warning messages when problems are found. Problems reported by this option can be fixed by editing the appropriate fields in the LAB REPORTS file (#64.5) or if necessary by the Re-cross Reference Indexes in the Lab Report file option. After any change to the Cumulative, you should run the diagnostic Routine for Lab Report file (64.5).

Preventative Maintenance for the Laboratory Software Package (cont.)

Bi-annual: Check Files For Inconsistencies (located on the Supervisors’ Menu/Lab Liaison Menu). Run this option at least once every six months. This option generates a report of potential inconsistencies in various files. You can consult with your local IT staff on how to clear these errors.

Preventative Maintenance for the Laboratory Software Package (cont.)

Yearly: Purge old orders & accessions (located on the Supervisor’s Menu). This option, looks at the Grace Period For Orders field in Laboratory Site file (69.9). It is suggest that at least 30 days worth of orders be maintained.

Preventative Maintenance for the Laboratory Software Package (cont.)

Re-Cross-Reference Indexes in LAB REPORTS These options will allow the user to re-cross reference selected indexes from the LAB REPORTS file (#64.5). Mumps A Index of the LAB REPORTS File: This option does a re-cross LAB REPORTS file reference on the mumps “A” index on the Lab Test subfield of the LAB REPORTS file (#64.5). The “A” cross reference contains reference ranges, critical ranges, and units from the LABORATORY TEST file (#60). Mumps AC Index of the LAB REPORTS File: This option does a re-cross LAB REPORTS file reference on the mumps “AC” index on the Test Location subfield of the LAB REPORTS file (#64.5). The “AC” cross reference is to identify the tests in the file that have data names (atomic tests) in the LAB DATA file (#63).

Re-Cross-Reference Indexes in LAB REPORTS (Cont.) Mumps AR Index of the LAB REPORTS File: This option does a re-cross LAB REPORTS file reference on the mumps “AR” index on the Lab Test subfield of the LAB REPORTS file (#64.5). The “AR” cross reference holds the site/specimen for each test in the file. Mumps A, AC, & AR Indexes of the LAB REPORTS File: This option does a re-cross LAB REPORTS file reference on the “A” and “AR” indexes of the Lab Test subfield and the “AC” index of the Test Location subfield within the LAB REPORTS file (#64.5). All three indexes are re-cross referenced.

Re-Cross-Reference Indexes in LAB REPORTS

Interactions of the Laboratory/Patient Care Component/Third Party Billing IHS LAB TRANSACTION LOG Accessioning a lab creates an entry in the IHS Lab Transaction Log. Resulting the test will update the Transaction Log. PCC The lab transaction is entered in the V. lab file of PCC. The V lab entry is updated with each change in the lab order 3PB Third party billing will capture labs in PCC that have the status of “Resulted”, a POV, and provider.

Questions & Discussion