LOINC, and why it matters to your HIS Interface

The Hospital Information Systems (HIS) at different medical centers have grown up mostly in isolation from each other. Even when an HIS is installed by a national vendor, each individual hospital has tended to make its own customizations and to follow past conventions. This is changing and it is changing because there are a number of issues driving rapid improvements in inter-hospital communication. The Meaningful Use (MU) Act is major factor and one that has been helping to set the pace, but because improved communication lowers costs and improves the quality of care insurers and medical institutions have been moving in this direction for their own reasons as well.

The regulations and standards for Health Information Exchange (HIE) are evolving rapidly. The overall framework for HIE resides in the Consolidated Clinical Data Architecture (C-CDA) and HL7 messaging protocols. This has given hospitals a unified approach towards managing their communication channels between physicians, clinics, other hospitals and insurers but one problem limiting the usefulness of this has been the different nomenclature used by different institutions for the same pieces of information.

When databases are grown in isolation they tend to end up with labels for data elements that are idiosyncratic and unique to each medical center. There needs to be a way to resolve this Tower of Babel and that is what the Logical Observation Identifiers Names and Codes (LOINC) organization is doing.

Continue reading

Using an HIS Interface as your report manager

The last several decades has seen a complete transition to the use of computers in pulmonary function testing. This has improved Lab efficiency, but it is also the new baseline. Further improvements in technology may improve the reliability and accuracy of test equipment and test results, but it is unlikely to improve PFT Lab efficiency any more than it already has.

Report management, which is really information management, has started but hasn’t yet completed the same technological transition and it is here that significant improvements can still be made. These improvement will not only improve the efficiency of the pulmonary function lab, but also its clinical effectiveness for the physicians and patients that are the lab’s customers.

To one degree or another most pulmonary function labs are still dominated by traditional reporting systems which are labor intensive and slow. Managing paper reports for a patient visit usually consists of:

  • Patient reports are kept in folders and either a new folder needs to be created or the patient’s existing folders need to be pulled from file cabinets.
  • Printing the test results and then collating the reports with patient’s lab folder.
  • Delivering a stack of reports and lab folders to a reviewer who makes penciled notes on the reports.
  • The stack of reports and lab folders is transferred to a typist who types the interpretation into the lab database.
  • The final reports are printed, collated with the patient lab folders and stack of lab folders and reports are delivered to the physician who then physically signs each report.
  • Reports are photocopied and snail-mailed to the ordering physician and medical records.
  • The lab folders are re-filed.

Not every pulmonary function lab still uses all of these steps to manage reports of course, but large parts of this overall process are often still major components in report management. So why are we still moving paper around when what we really want to do is to move the information that’s on the paper around?

Continue reading