UGHH
And I thought I wouldn't have to see HL7 data any more!
I too worked on a project, interfacing LabCorp (through DIALUP, for goodness sake)
with our server, parsing the HL7 files and then inserting data based on our client's
data model into the database.
I wrote a nifty parse routine that checks for all kinds of things, such as incomplete
fields, files, and erroneous data (because God forbid the files come across right 100%
of the time). The program makes extensive use of try/catch and sends errors/successe
emails to the appropriate people.
The standards manual I received was in itself a little daunting at first. I basically
printed out sample tests and then went through them with the manual in one hand and
the tests in the other. Then figured field requirements, etc based on the data schema
for the client database.
I stored all the data from 1 test file in a query, and when done looping through the
whole file (using switch and case for each line header), inserted the correct tests
into the database, and copied the text files to either an archive, anomalous or
incomplete folder.
It was sooooo fun, let me tell you.
- Andy
p.s. And I never thought I would never be able to share the pain...
> -----Original Message-----
> From: Lawrence B. Afrin, M.D. [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 16, 2001 2:14 AM
> To: CF-Talk
> Subject: Re: Anyone hear of the "HL7" protocol?
>
>
> Probably worth mentioning that HL7 version 3 includes specs not
> only for "old-style" HL7 messages (updated, of
> course, to include all the new stuff in version 3) but also a
> complete DTD for sending messages in XML, too. I
> know some of the people on the HL7 committee, and they fully
> recognize the importance of XML.
>
> -- Larry Afrin, M.D.
> Medical University of South Carolina
> [EMAIL PROTECTED]
>
>
> [EMAIL PROTECTED] wrote:
>
> > Al, this is a very timely question in many ways. HL7 stands for Health
> > Level 7 and is an attempt to bring in standardization into Medical
> > Applications. The theory is to create a protocol that can allow
> one medical
> > application to exchange data with another. It is fairly complex and is
> > still evolving. This may all sound a bit mundane but medical
> software is
> > generally woefully behind most other segments. As a sidenote,
> it is also
> > very expensive and proprietary.
> >
> > In reality XML is far more likely to truly enable data-exchange
> in medicine
> > but your client has probably been told that HL7 will be the cure to all
> > their connectivity issues.
> >
> > A major point to bear in mind is that HL7 can operate both in batch and
> > real-time modes, this is probably the single most important
> advantage of the
> > HL7 format.
> >
> > I say that your question is timely because Healthcare applications will
> > probably be the next major wave of web based revenue generating
> > opportunities for all of us.
> >
> > This is long winded but I hope it helps you.
> >
> > Kind Regards - Mike Brunt
> > Macromedia Consulting
> >
> > -----Original Message-----
> > From: Al Musella, DPM
> > To: CF-Talk
> > Sent: 5/15/01 4:07 PM
> > Subject: Anyone hear of the "HL7" protocol?
> >
> > I have to create a medical website that communicates with a program
> > that
> > uses the "HL7" protocol. I never heard of that, and I have to talk to
> > their programmers tomorrow and don't want to look that stupid:) Anyone
> > know what they are talking about?
> >
> > Al Musella, DPM
> > virtualtrials.com
> >
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
