Thanks Ian. 2.7.1 included a bunch of datatype replacements... which affects the XML structure (but not the pipe structure) in non-backwards compatible ways. If I were so motivated, what changes are required to get HAPI processing a 2.7.1 schema? Note that, due to field withdrawals, this basically *must* be a custom schema?
I was hoping the "build from source" process would be enlightening... but tests are failing because XSD files are missing. I have those files (both for stock versions and 2.7.1), but errors like "Schema file not found on disk: dgjkn(/º$&f09e/ACK.xsd" aren't exactly clearing up my confusion. Thanks, Clayton Daley Ambassador Software Works On Wed, Nov 5, 2014 at 11:40 PM, Ian Vowles <ian.vow...@health.qld.gov.au> wrote: > In HAPI vs 2.2 the maximum HL7 version supported with complete structures > is 2.6. > > > > However, HAPI is quite able to deal with messages that don’t exactly match > against a versions structure, so you are likely to still be able to meet > your requirements. > > > > So, point one is certainly possible, given that 2.6 is the maximum fully > supported version of structures at the moment. We do something like this, > where all our vendors sned HL7 versions 2.3, 2.3.1 and a couple of 2.4. All > of them are ‘upshifted’ to 2.4 or 2.5, and handled as such from then on. > > > > Given that point one is covered, point two happens as a result, since all > the messages conform to the representation we ‘upshifted’ them to. Fields > that have changed from a string to a datatype still have the fields > accessable. > > > > Using HAPI you can access XML representation of the HL7 if it is sent to > you in the old bar delimited form. If you are already dealing with XML, > things should be good. > > > > Which leaves the third point as the ball that is in your court. If you > need to transform a message you have received into another form, or change > values based on some specification, that’s the work in front of you. > > > > Whilst I’m not using any XML, all bar delimited stuff here, I do what you > are asking about all day every day. HAPI is a very useful library. > > > > Hope this helps > > > > Ian > > Systems Integration Team > > Dept of Health > > Queensland > > Australia > > > > *From:* Clayton Daley [mailto:clay...@ambsw.com] > *Sent:* Thursday, 6 November 2014 10:22 AM > *To:* hl7api-devel > *Subject:* Re: [HAPI-devel] Customized (v2.7.1 based) Parsing Schema > > > > Good Afternoon, > > > > We're a Healthcare IT SaaS startup using HAPI indirectly through Mirth > Connect. > > > > As a service provider, we will need to process messages from many > different HL7 versions. In brief, our idea is to: > > · Feed messages of any version into a single parser (currently, based on > 2.7.1), > > · Get a message in a uniform structure (avoiding, for example, > differences arising from datatype replacements), and > > · Build one set of (internal) XML interpreters for that output. > > Can someone clarify details like: > > · How much of this can be achieved using HAPI "out of the box", > > · Is it enough that I can generate an XSD schema or is this the wrong > format, and > > · What changes would be required inside HAPI > > ... and I suppose "are there any other questions I should have asked"? > > > > Thanks, > > > > Clayton Daley > > Ambassador Software Works > > > ******************************************************************************** > > This email, including any attachments sent with it, is confidential and > for the sole use of the intended recipient(s). This confidentiality is not > waived or lost, if you receive it and you are not the intended > recipient(s), or if it is transmitted/received in error. > > Any unauthorised use, alteration, disclosure, distribution or review of > this email is strictly prohibited. The information contained in this email, > including any attachment sent with it, may be subject to a statutory duty > of confidentiality if it relates to health service matters. > > If you are not the intended recipient(s), or if you have received this > email in error, you are asked to immediately notify the sender by telephone > collect on Australia +61 1800 198 175 or by return email. You should also > delete this email, and any copies, from your computer system network and > destroy any hard copies produced. > > If not an intended recipient of this email, you must not copy, distribute > or take any action(s) that relies on it; any form of disclosure, > modification, distribution and/or publication of this email is also > prohibited. > > Although Queensland Health takes all reasonable steps to ensure this email > does not contain malicious software, Queensland Health does not accept > responsibility for the consequences if any person's computer inadvertently > suffers any disruption to services, loss of information, harm or is > infected with a virus, other malicious computer programme or code that may > occur as a consequence of receiving this email. > > Unless stated otherwise, this email represents only the views of the > sender and not the views of the Queensland Government. > > > ********************************************************************************** > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Hl7api-devel mailing list > Hl7api-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/hl7api-devel > >
------------------------------------------------------------------------------
_______________________________________________ Hl7api-devel mailing list Hl7api-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hl7api-devel
