hi, As always, the reality is somewhat complicated. HL7v3 is (unlike HL7v2) more of a modelling framework - based on a basic information model and modelling processes you design your domain models which you can then serialize into XML messages or documents or whatever. The standard defines a whole batch of domain models for various purposes related to medicine (like patient administration, Lab, Medical Records, Pharmacy, and many many more. Most prominently is the CDA (clinical documents architecture) standard based on HL7v3 along with its content profiles.
Said that, HL7v3 is not a finitely bounded standard that you can simply "support". You can always address only an implementation of a small fraction of the HL7v3 world, and it depends on what your concrete needs are and how much you are satisfied with only dealing with syntactic aspects of such a implementation (e.g. XML schemata of HL7v3 message instances) or also need to understand the semantics behind it (including domain code systems...). Note that HL7v3 is complicated and has been seen quite critically recently (e.g. see http://www.healthintersections.com.au/?p=476). After this preface, here's some more concrete advice: * As already mentioned, Mirth has basic HL7v3 support. * The original HL7v3 reference implementation (from Regenstrief Institute, http://aurora.regenstrief.org/~javasig) appears to be dead, or at least dormant. * If you deal with CDA documents, have a deep look at the MDHT project ( https://www.projects.openhealthtools.org/sf/projects/mdht/), with support for a lot of normative CDA content profiles and an Eclipse-based modelling tool to define your own HL7v3 models and generate code out of it. The IPF project (http://openehealth.org/display/ipf2/Home) has some small Camel wrappers around MDHT parsers and validators, so you can use Camel's DataFormats (marshal/unmarshal) and Validators for working with CDA documents. IPF also provides Camel components for some more common HL7v3 messages from the patient administration domain, specified through IHE ( www.ihe.net) * There is supposed to be a HL7v3 standards compliant message creation tool on http://everest.marc-hi.ca/, but as of writing the site does not respond. * You can always use the XML schema files of a domain model and feed your JAXB compiler, but don't be suprised about the 1000+ classes it will spit out! hope this helped a bit Christian 2013/9/12 Hadrian Zbarcea <hzbar...@gmail.com> > Ed and I had a presentation at OSEHRA last week showing (among other > things) how to use HL7 with Mirth and Camel. It's a bit tricky. As other > said the camel-hl7 component is based on the hapi api with supports the > version 2.x of HL7 wich is an EDI format, not xml. > > Afaik, most of the industry is on hl7 2.x with no clear plans to > transition to 3.x. And here lies the Camel opportunity to provide some > value added, transformation, validation, etc. > > If you could share more about what you're trying to do, I may be able to > help you more. > > Cheers, > Hadrian > > > > > On 09/04/2013 06:06 PM, capzulu wrote: > >> Hello Hadrian, >> >> >> >> I don't remember what was my last message. >> >> But I can tell you that I've used Mirth Connect to work with HL7 v3 >> messages. I've used a Java library to validate a XML message against a >> XSD. >> >> Send me another message if you want some more details. >> >> >> >> Best regards, >> >> Miguel Castilho >> >> >> >> De: TechieDeep [via Camel] [mailto:ml-node+** >> s465427n5738665h46@n5.nabble.**com<ml-node%2bs465427n5738665...@n5.nabble.com> >> ] >> >> Enviada: quarta-feira, 4 de Setembro de 2013 11:33 >> Para: capzulu >> Assunto: Re: HL7 v3 >> >> >> >> Hadrian, >> >> I am working on an integration where I have to send HL7 outbound messages >> to >> an openlink from a web service. Can you please elaborate more on your last >> message. >> >> How you worked with xsd and camel >> >> _____ >> >> If you reply to this email, your message will be added to the discussion >> below: >> >> http://camel.465427.n5.nabble.**com/HL7-v3-tp5732915p5738665.**html<http://camel.465427.n5.nabble.com/HL7-v3-tp5732915p5738665.html> >> >> To unsubscribe from HL7 v3, click here >> <http://camel.465427.n5.**nabble.com/template/**NamlServlet.jtp?macro=** >> unsubscrib<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscrib> >> e_by_code&node=5732915&code=**bWlndWVsY2FzdGlsaG9Ac2Fwby5wdH** >> w1NzMyOTE1fC0xNzA0 >> NDkxMjAz> . >> >> <http://camel.465427.n5.**nabble.com/template/** >> NamlServlet.jtp?macro=macro_**view<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_view> >> er&id=instant_html%21nabble%**3Aemail.naml&base=nabble.naml.** >> namespaces.BasicNa >> mespace-nabble.view.web.**template.NabbleNamespace-** >> nabble.view.web.template.No<http://mespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.No> >> deNamespace&breadcrumbs=**notify_subscribers%21nabble%** >> 3Aemail.naml-instant_ema >> ils%21nabble%3Aemail.naml-**send_instant_email%21nabble%**3Aemail.naml> >> NAML >> >> >> >> >> >> -- >> View this message in context: http://camel.465427.n5.nabble.** >> com/HL7-v3-tp5732915p5738704.**html<http://camel.465427.n5.nabble.com/HL7-v3-tp5732915p5738704.html> >> Sent from the Camel - Users mailing list archive at Nabble.com. >> >>
