The autoverification of lab test results has an interesting history. This is a process by which algorithms installed within an LIS verify that selected results are correct and can be released to the test-ordering physician. If the LIS is doing its job properly and the algorithm is designed properly, autoverification is a task best performed by a computer rather than a human operator. You can read more about autoverification in a brochure entitled Autoverification of Clinical Laboratory Test Results; Approved Guideline that was published by the Clinical and Laboratory Standards Institute, formerly NCCLS. The lead author of this publication is Dr. William Neeley.
The AACC is presenting an audioconference entitled Leveraging Autoverification for Greater Lab Efficiency on Wednesday, April 22, 2009, at 2:00-3:30 pm Eastern time.
Major points to be covered in this presentation include the following:
- Add new layers to your autoverification program, learning from real-world examples of the rules and delta checks experts use
- Create time-saving and useful multi-component algorithms
- Optimize the capabilities of systems with and without middleware
- Manage QC frequency using autovalidation
- Verify autoverification ranges for CAP and other accrediting organizations
- Test and maintain your autoverification rules
Faculty include the following experts on the topic:
- Jay B. Jones, PhD, (Moderator), Director of Chemistry & Regional Labs, Geisinger Health System, Danville, PA
- William Neeley, MD, Medical Director of Laboratories, Detroit Medical Center, Detroit, MI
- Susan Dawson, MS, Clinical Lab Manager, Swedish Covenant Hospital, Chicago, IL
Earlier in my career, there was certain suspicion about autoverification caused, in part, by lab inspection guidelines that required human (i.e, medical technologist) verification of test results prior to release. My frustration about this regulation, subsequently changed, was that I believed that humans were inferior to computers in performing this task and it caused degradation of quality. In my opinion, some of the opposition to autoverification at that time was also the result of a concern for protecting FTEs. These days and with the well-documented shortage of medical technologists (see: A New Resource for Information about the Medical Technologist Shortage), there is no good excuse for not using autoverification in any lab.