On 9-Sep-08, at 4:43 PM, David Mackenzie wrote: What is a typical scenario for how HL7 messaging is used. Is it the following:
1) A system(s) sends an HL7 message to the Mirth Server
2) The Mirth Server processes the message, decodes it, and stores the data within the message in the GNUMed database
3) The GNUMed client can then access the data from the database
... will GNUMed ever be sending HL7 messages to the Mirth Server?
I checked with the people at the egadss project (where Egadss = EVIDENCE-BASED GUIDELINES AND DECISION SUPPORT SYSTEM).
I note note both the possibility that organizations like hospitals might possibly send out discharge summaries in HL7 CDA and wonder if thoese too could be importable by Mirth only placed into the document archive instead of in test-results.
I recall also among local doctors tremendous complaints that every consultation or registration request that they must complete, to different hospital or specialist or imaging or public or private health services administrations, demand that their own forms be completed. These all involve paper with the patient demographic, referring clinician, and clinical information with 90% overlap all to be put on a piece of paper but of paper of arbitrary colours and location of information on the page.
There is also clinician to clinician communication that could be a lot more effectively exchanged among systems, making me wonder if Mirth could be suitable for EMR-to-EMR intercommunication.
Date: September 10, 2008 11:25:25 AM PDT (CA) Subject: Re: [Egadss-devel] typical scenarios for how HL7 messaging is used
Hi Jim:
In general, I think of messages in a multi-clinical-system environment such as a hospital or other enterprise (communication within an organization). At least here, most EMRs make up the only clinical system in a single system environment. Any information exchange takes place with others outside of the organization (communication between organizations). For this I generally think of electronic documents (such as HL7 CDA). I know it is not the current state, but I wonder if things are swinging in that direction.
I've noticed this trend (message/inside, document/outside) more and more in the US with HITSP and the CCD Summary. The PHR gang (google health and microsoft healthvault) has rallied around the CCD. I've seen it used for other inter-organizational information sharing needs as well (e.g. http://geekdoctor.blogspot.com/2008/07/automating-disability-process-with.html). Note, HITSP also has a lab report electronic document.
In terms of scenarios: some of my more recent work is focused on timely notifications to physicians out in the community. So things like notification of admission to hospital, notification of discharge from hospital, notification of discharge from emergency.
regards, Glen On Tue, Sep 9, 2008 at 8:25 PM, J Busser < address@hidden> wrote: Hi all I happen to be a member of the open source EMR project GNUmed which is looking at Mirth Project ( www.mirthproject.org) to assist the import of lab data. Down the road we may also like to assess the goodness of fit with egadss :-) In the meantime someone who is assisting us asks about the scenarios (apart from receiving lab data) in which EMRs will be likely to use HL7 messages. If it is anything on which anyone from egadss might like to comment, any insights would be welcome. :-)
|