+1 on improving the HL7 services in OpenMRS. When it comes to RIS/PACS I'm not quite sure where the query/response model fits?
Would the RIS query OpenMRS for orders? Patients? --Marc -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Blaya, Joaquin Andres Sent: Monday, July 11, 2011 6:33 PM To: [email protected] Subject: Re: [OPENMRS-DEV] On the horizon, module to request HL7 messages, parse incoming messages and send other outbound messages Hi guys, Glad to see there's this much interest. The reason to have the task to query for HL7 messages is that the other system is a RIS/PACS so it only sends messages when queried, it can't send them on its own. And the reason for the question was so that we could build this functionality in the way that would help the most people and not just a specific module for us. So, is the best idea to use Mirth or to try and do this all within OpenMRS? In a week or two, I can get these comments and do an initial straw man to see if we all agree what should be core, what should be a module and what should be mirth. Joaquin ___________________________________________________________________ Chief Technology Officer, eHealth Systems Chile Research Fellow, Harvard Medical School/Partners In Health Moderator, GHDOnline.org -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Tammy Dugan Sent: Monday, July 11, 2011 14:16 To: [email protected] Subject: Re: [OPENMRS-DEV] On the horizon, module to request HL7 messages, parse incoming messages and send other outbound messages We should be up to 1.7 by the end of the year if everything goes as planned. Tammy On 7/11/2011 1:46 PM, Ben Wolfe wrote: Can't Mirth read json web service objects? How about using the soon-to-be released ws module? https://wiki.openmrs.org/display/projects/Webservices.rest+Module (Although we'd have to get you guys to upgrade to 1.8...or maybe 1.7 soon) Ben On Mon, Jul 11, 2011 at 8:37 PM, Anand, Vibha <[email protected]> wrote: The CHIRDL team is interested in creating a common serialized object for output that can be read by Mirth tool for sending an HL7. Meena Sheley currently has a working HL7 exporter module that can read a configuration file to assemble the message but it is not yet customizable to the receiver's spec. Therefore Mirth needs to come in between and Meena is working with Shahid et al at RG (Mirth experts) to get the project going. Is there any straw man for the common object that currently exists? Vibha Anand From: [email protected] [mailto:[email protected]] On Behalf Of Ben Wolfe Sent: Monday, July 11, 2011 10:42 AM To: [email protected] Subject: Re: [OPENMRS-DEV] On the horizon, module to request HL7 messages, parse incoming messages and send other outbound messages I started this page a while back, it needs to be filled out a little more before someone can just run with it though. https://wiki.openmrs.org/display/projects/HL7+Output+(Design+Page) <https://wiki.openmrs.org/display/projects/HL7+Output+%28Design+Page%29> Ben On Mon, Jul 11, 2011 at 5:35 PM, Darius Jazayeri <[email protected] <mailto:djazayeri%[email protected]> > wrote: I would like to get the machinery for sending outgoing HL7 messages from OpenMRS, and properly handling error messages and responses for incoming messages handled in core. (But I don't know much about how other systems do this, so I don't know how much design this would require.) The actual business logic for your use case will need to go in a module. -Darius On Mon, Jul 11, 2011 at 7:01 AM, Burke Mamlin <[email protected]> wrote: A scheduled task to query an external system would probably require a module to introduce the task. Any generic HL7 message handlers can go into core; otherwise, modules can register a their own handler. We have an ADTA28 handler <http://bit.ly/nGiI4Z> to create new patient records (along with the ORUR01 handler to accept incoming observations). Any work to make the ADTA28 handler more flexible (e.g., updating patient information) would be a wonderful addition to core. We haven't yet sent HL7 messages out from OpenMRS from within core. ADT events (patient creation, updates, registration, etc.) would be the place to start. But these would be generic notifications. If you need notifications based on specific business rules, then you'd need a module for them. Cheers, -Burke On Thu, Jul 7, 2011 at 8:20 PM, Blaya, Joaquin Andres <[email protected]> wrote: Burke, Ben and Darius (as well as anyone else who might be interested) We've been in discussion about connecting OpenMRS via HL7 to other systems and so I spoke with Darius about the effort and best way to create a way for OpenMRS to 1. Have a scheduled tak to query a system to ask for HL7 messages about the patient's demographic info, cell phone and date/time of appointment 2. Process the HL7 messages that it receives and place them into the OpenMRS database 3. Send HL7 messages back to the system depending on what the response was i.e. did patient confirm appointment We also talked about if or what would be useful to place into core as opposed to a module to improve OpenMRS. So I wanted to see if we end up going down this route, if we could have a conversation about what would be the best way to code this and what makes sense to place into core. Does this sound like something of interest? Thanks, Joaquin ___________________________________________________________________ Chief Technology Officer, eHealth Systems Chile Research Fellow, Harvard Medical School/Partners In Health Moderator, GHDOnline.org <http://www.GHDOnline.org> ________________________________ Click here to unsubscribe <mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l> from OpenMRS Developers' mailing list ________________________________ Click here to unsubscribe <mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l> from OpenMRS Developers' mailing list ________________________________ Click here to unsubscribe <mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l> from OpenMRS Developers' mailing list ________________________________ Click here to unsubscribe <mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l> from OpenMRS Developers' mailing list ________________________________ Click here to unsubscribe <mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l> from OpenMRS Developers' mailing list ________________________________ Click here to unsubscribe <mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l> from OpenMRS Developers' mailing list -- Tammy Dugan CHIRDL Technical Lead Children's Health Services Research IU School of Medicine ________________________________ Click here to unsubscribe <mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l> from OpenMRS Developers' mailing list _________________________________________ To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-devel-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l] _________________________________________ To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-devel-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
