My .02 – the 3.0 ‘standard’ still leaves a fair amount of room for vendor deployment. Very similar to X12.
Thus vendor A might utilize certain nodes one way and another vendor use the same noodes or other nodes differently yet still be in compliance as long as they have conformed to the overall structure of the standard and have a published conformance statement.
I think much like Mark Twain the announcement of the demise of Integration Engineers is significantly premature.
But that does not address the question at hand.
I have not done any HL/7 3.0 integrations but I woulld start by requiring the vendor to provide its conformance statement. I would find and download the HL/7 schemas (I think they are available for download) or maybe the vendor can provide me with the schema they are requiring.
I would insist on a .xsd file rather than some printed document that ”represents’ the schema.
I would then validate the schema using an XML tool like OxYgen and compile it in Cloverleaf.
If the schemas don’t valiidate/compille cleanly then I would press the Vendor (if I received the schema from the vendor) to fix the schema.
Once compiled and validated successfully, then I would validate data against the schema.
In the case where the 3.0 is inbound I would require the vendor to provide data I coulld run against the schema to make sure the data/schema match (some times they do not). If they don’t match I would dump the whole thing back onto the vendor and tell hiim to get his schema/data to work.
In the case of the 3.0 being outbound, I would created data according to the specifications of where the data should come from in the inbound message to where it should reside in the outbound message and validate things are where they should be as I would in any other integration.
email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.
.
