Well FHIR pretty much addresses all the issues I mentioned. Looks like this has been kicked around for quite some time - even though the project is 0.0.5, there is a lot of info on implementation of RESTful design patterns, etc. even Atom feed integration.
Thanks for sharing John. -- Paul Morris, Software Developer Northwestern Memorial Physicians Group<http://www.nmpg.com> 773.469.4330 | 312.926.6674 | pmor...@nmh.org From: <Moehrke>, "John (GE Healthcare)" <john.moeh...@med.ge.com<mailto:john.moeh...@med.ge.com>> Date: Monday, July 23, 2012 12:13 PM To: Rahul Somasunderam <r...@certifydatasystems.com<mailto:r...@certifydatasystems.com>>, James Agnew <ja...@jamesagnew.ca<mailto:ja...@jamesagnew.ca>> Cc: HAPI Devel List <hl7api-devel@lists.sourceforge.net<mailto:hl7api-devel@lists.sourceforge.net>> Subject: Re: [HAPI-devel] Replacing MLLP This is now an HL7 initiative called FHIR. http://wiki.hl7.org/index.php?title=FHIR From: Rahul Somasunderam [mailto:r...@certifydatasystems.com] Sent: Monday, July 23, 2012 11:52 AM To: James Agnew Cc: HAPI Devel List Subject: Re: [HAPI-devel] Replacing MLLP I would love that (HTTP/RESTish). That makes a lot of things easier. Add to the list of benefits, Load Balancing. We don't need a new protocol. We need to use a protocol that is widely used so we can reuse all the good stuff we've already got that works. I had read sometime back that someone was implementing a similar technique in Australia. The downside to it is a lot of vendors I deal with live in the 19th century, and might not start supporting this for several years from now. But a push for HTTP in HL7 from HAPI would be the right thing for healthcare. R, rahul On Jul 23, 2012, at 8:20 AM, James Agnew wrote: Hi All, I'd like to solicit opinions on something I've been thinking over for a while now. I'm wondering if there is any interest or opinions in the HAPI community to come up with a new transport for HL7 messages that can be used in place of the (horribly outdated) Minimal LowerLayerProtocol. I've got a blog post up (sorry for the blog-link email, it's just an easier way to include pictures and things than email) http://onintegration.blogspot.ca/2012/07/a-call-for-new-hl7-v2-transport-hl7.html which outlines a proposal to implement an HTTP based transport. I would love to hear opinions on the idea, counter proposals, criticisms, etc. Cheers, James ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________ Hl7api-devel mailing list Hl7api-devel@lists.sourceforge.net<mailto:Hl7api-devel@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/hl7api-devel This message and any included attachments are intended only for the addressee. The information contained in this message is confidential and may constitute proprietary or non-public information under international, federal, or state laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Hl7api-devel mailing list Hl7api-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hl7api-devel
