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