Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
General
GeneralCardiologyVisionDentistryPharmacyLaboratoryNutritionAlternative
Diseases and Disorders
AIDSAlzheimer'sArthritisAsthmaCancerBreast CancerDiabetesEpilepsyGlaucomaHepatitisHerpesLupusProstate BPHProstate CancerProstatitisSinusitisTinnitus

Medical Forum / General / Laboratory / February 2007

Tip: Looking for answers? Try searching our database.

interfacing with analyzers

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Timasmith - 11 Feb 2007 12:14 GMT
Hi,

Do manufacturers of Analyzers publish specifications on how to
automate communication with a healthcare information system?  So I as
I understand it generally one might barcode testtubes to have some
kind of numeric identifier which identifies the order/collection in
the information system.  The analyzer reads the barcodes, analyzes the
tube contents and outputs a report and/or interface communication.
The interface communication is I assume HL7.

But does each analyzer vendor use a different HL7 spec, and do you
have to be a customer to get that spec?

I randomnly found an analyzer e.g. http://www.abbottdiagnostics.com/
Products/Instruments_by_Platform/default.cfm?system=cell-
dyn&suffix=3700#5

thanks

Tim
Manky Badger - 11 Feb 2007 15:01 GMT
> Hi,
>
[quoted text clipped - 8 lines]
> But does each analyzer vendor use a different HL7 spec, and do you
> have to be a customer to get that spec?

I expect so. I've never seen an interfacing that seems to be "off the peg" -
they always seem to need a lot of fiddling.
John Gentile - 12 Feb 2007 02:56 GMT
> Hi,
>
[quoted text clipped - 16 lines]
>
> Tim

As the Information Manager for my lab, it falls on me to get the
various instruments linked up to our system. Sometimes it is a
struggle, and sometimes it goes like clockwork. Most of the instruments
we get come with a manual just for the interface with all the
parameters and variations of different LISs. The Veterans Affairs
hospital information system (VISTA) is unique and many instruments
can't cope (let alone the people trying to get it done). We rely on
Data Innovations to handle our interfaces  - each instrument sends and
receives information to the Data Innovations Instrument Manager and
that is the link to VISTA.
Microbiology is a sore spot for all VA labs. None of the micro
instruments (Vitek or Microscan) have any "official" interface set up.
I've tried some "unofficial" hook ups and ended up on 2 occations in
wiping out all interfaces for the rest of the lab. I still want to get
the Microscan on the interface, but need to proceed very carefully.
Microscan tells me that they have the necessary stuff, but the VA can't
make it happen. The VA for their part, have not assigned anyone to work
on micro interfaces in many years, and I've even met with the guy who
used to do it (over 10 years ago) and he provided me with that
unofficial code that messed me up.
So in short - if you have an instrument in mind you will have to talk
with their computer specialists - not the sales reps - and explain what
kind of LIS you have and can they link to it. BTW, the Abbott Interface
manual is a 2 inch thick binder! I don't recommend it for casual
reading!
Signature

John Gentile MS, M(ASCP)
Laboratory Information Mgr.
VA Medical Center
Providence, RI
yjgent@cox.net

JEDilworth - 15 Feb 2007 16:59 GMT
We are on Misys and our Vitek's are interfaced (thank goodness). I would
hate to have to hand-enter all that data. My condolences to your micro
department.

My husband is a systems analyst for another large local hospital. He manages
interfaces between the hospital's different systems. For example, they have
a registration system that has to send out its demographics to radiology,
lab, etc. They ditched their mainframe quite a number of years ago. These
interfaces allow for the transfer of data between departments. He uses a
commercial software program for this but it has to be fiddled with in order
to get it to work with the various systems. Nothing is easy. Everything in
computers is institution dependent on what else is running. He deals with
many many interfaces on a daily basis.

As far as an open-source LIS: our place has invested mega-bucks getting our
hospital and all the hospitals in our region on one system. I doubt that,
after these investments, they would go to something that is open source.
Also, there are big time security issues involved with any LIS (read that
HIPAA). You have to be able to prevent hackers from getting in. I'm sure
"open source" would sound too scary to most administrators. I would think
your market would be smaller independent labs. These, however, are rapidly
being gobbled up into large lab systems.

All our specimens are assigned an accession number that prints out bar coded
labels. When we put blood culture bottles onto our blood culture
instruments, for example, we scan the bar code for the type of bottle it is
(aerobic or anaerobic) and then scan the accession number bar code into the
instrument, then place the bottle into an available slot (chosen by the
instrument or the tech based on the available slots lighting up at the
time). When we accept a transport list for these blood culture, this
information is relayed to the BC instrument via an interface. This way we
can look up the bottle by accession number of name on the BC instrument's
data screen. Since we have the capability of nearly 500 bottle slots, we
could not possibly look for bottles by hand when a phone call comes in to
the effect of "do you have blood cultures on May Smith yet?" We get their
med record number and search for them that way, ideally, or by name if they
don't have a MR number.

Chemistry, Hematology, and virtually ever other lab department relies
heavily on bar coding as it prevents errors of hand entering numbers and
saves immense amounts of time. Bar coding in labs has been available since
the late 80's, I believe. I know that at my old lab they were bar coding
hematology specimens back then. I don't think bar coding for chemistry came
until a bit later, however. Printers have much improved, making the bar
codes much easier for the instruments to read. In the olden days they
smudged with handling quite often, making scanning a big problem. Better
labels and inks have helped this problem a lot.

I would guess that most of the information that Tim would like to get his
hands on is proprietary and held very close to the vest by the companies
that created it. This is BIG BIG business worth millions of dollars. There
would be no reason to release any of this closely guarded information out to
anyone, except in the parts people like John at their respective labs have
to deal with. I know when these big systems do upgrades, everything has to
go through the vendor, as my husband has dealt with numerous outages and
downtimes throughout his work career. I wouldn't begin to know how all this
stuff works, though :-). I know that some of the fixes we'd like in our
current system "have to wait until the next upgrade."

Judy Dilworth, M.T. (ASCP)
Microbiology
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.