Automation in Hospitals and Healthcare 77.3 Applications 1395
a National Health Information Network (NHIN) to
connect these RHIOs. Unfortunately, even at an insti-
tutional level there are numerous clinical and financial
applications that have difficultly communicating and
thus there are significant unmet needs even within a sin-
gle organization. Many countries across the globe are
issuing tenders to seek solutions for health information
exchange on national levels.
Putting aside the complex business model and or-
ganizational barriers that have been significant barriers
towards significant national and local information ex-
change, there continues to be significant technology
barriers. One of the fundamental challenges resides in
the prime directive of medical informatics in that most
systems store data rather than knowledge and as a re-
sult haveno external references to establish the meaning
of data that needs to be exchanged. For example, con-
sider allergies. Allergies represent one of the most acute
life threatening risks to an individual whenever he en-
counters a healthcare system, especially if he enters the
system unconscious. Surprisingly, there is no common
dictionary for allergies, and as a result most systems
have no method to exchange allergies in a form be-
yond simple free text. With free text allergies there is
no method to perform simple allergy checking before
prescribing or administering a drug.
Today organization such as Health Language 7
(HL7), Integrating the Healthcare Enterprise (IHE),
Healthcare Information Technology Standards Panel
(HITSP), and the Center for Healthcare Information
Technology are all working on establishing standards to
facilitate interoperability across institutions and across
vendors. Although there are emerging standards for
rudimentary exchange of information today there are
surprisingly few examples of information exchange
even at the level we have come to expect in the banking
industry. With patients continually changing healthcare
environments due to changes in health and changes
in insurance, the challenge of interoperability must be
solved to ensure that information technology has a sig-
nificant impact on the quality of care.
77.3.7 Enterprise Systems
Historically, patient access and financial systems were
the first to gain a foothold in healthcare. Driven by the
bottom line, these supported the back office and had no
access to (or need for) clinical data. Clinical systems
followed, designed to address specific needs in individ-
ual care areas such as labor and delivery, where there
was a need to record and store the massive amounts
of information generated by fetal heart monitors and
other devices. For the past two decades, lab systems
built around the workflow of technicians and pathol-
ogists have had the capability to collect results from
a wide array of tests and presentphysicians with a single
view of all the data for each patient (although in most
physician’s offices that information is still presented on
paper rather than electronically).
Because these systems were developed for specific
care areas, each tightly adhered to the workflow in one
particular area. Many healthcare organizations adhered
to a best-of-breed approach, buying a lab system from
one vendor, a pharmacy system from another, a peri-
operative system from a third, and so on. These care
area-specific systems can be more nimble, and can be
installed in a matter of weeks, but require complex in-
terfaces in order to share data with each other. As time
passed, clinicians recognized the need for enterprise-
wide systems, so some vendors of area-specific systems
began broadening their scope.
Other vendors took the approach of developing
enterprise-wide systems that allow information to eas-
ily cross the boundaries between care areas. Consider,
for example, what happens when a physician orders
medication for a hospital patient: the provider needs
to know whether the patient is allergic to that drug, or
has been given any other medication that should not
be combined with the new one, formularies must be
consulted to see whether the hospital is dispensing the
drug and whether the patient’s insurer will pay for it,
the order must be transmitted to the hospital pharmacy,
where the pharmacist double-checks the dose to make
sure it is appropriate for the patient’s age, weight, and
condition. After the pharmacist dispenses the drug, it
must be conveyed to the right location in the hospital,
where a nurse will pick it up, administer it to the pa-
tient, and document the time of administration (perhaps
using a barcode scanner to make sure the right patient is
being given the right medication).
The trade-off for the easy flow of information across
the enterprise is in specificity and implementation time.
The best area-specific systems do one thing only, and
do it better than the current generation of enterprise sys-
tems. Smaller, more discrete systems are also easier and
faster to install. As the technology matures, however,
we will see a convergence as enterprise systems acquire
the greater depth of area-specific capabilities.
Part H 77.3