Does anyone have any suggestions for a handy referral guide I can get that shows the changes for HL7 2.5? As anyone seen any major problems? Our HIS system is converting to 2.5 so I have to test and/or reconfigure all my receiving systems due to this change.
I just use the HL/7 documentatin available from the HL/7 organization.
I would think the biggest thing to watch is if there is a big jump (say like from 2.3 to 2.5) and the newer Data Types are being exploited. Actually even a minor jump for the newest Data Types can cause an issue.
Is the vendor ‘really’ going to 2.5 or are they simply plunking 2.5 into the MSH (like so many vendors do)?
Generally I have found trying to resolve messages down to far in levels (like from 2.5 to 2.2 or 2.3) can be troublesome.
So you are really going to be challenged by the receiving systems if they are currently at a much lower level.
email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
McKesson is really going to 2.5 due to Meaningful Use requirements. I do have some lower versions and was concerned about this. Do I have to join the HL7 group to be able to download the documentation?
Yes I believe ytou need to be a member of hl7.org (or your institution can be a member) to get the specifications.
However, some of the Government required stuff (like the CCD) is available to the general public so maybe this is as well – it can’t hurt to go to the web site and see.
Honestly, I cannot see why every hospital organization that is doing any data intgeroperability does not have a yearly membership to the standards bodies for the various message sets. I know this can add up but the cost of attempting to do interoperability in the dark has to exceed the cost of memberships.
email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
Author
Replies
Viewing 2 reply threads
The forum ‘Cloverleaf’ is closed to new topics and replies.
.
