HL7 2.4

[Gina Borden]

We are currently upgrading to Sorian from Siemen’s Invision for our HIS.  All of our ADT, Orders, and Results in Invision are done in HL7 2.3.  Sorian C4 is using HL7 2.4, and now will be sending OMG and OML for orders instead of ORM, and for corrected results it needs an ORU^R02 instead of R01 like we currently use.

As the only programmer for our facility, I am wonderin if I should contact every vendor to let them know they will need to make changes, or if I should try to take the OMG’s and make them ORM’s going to the vendor, so they don’t have to change anything.

I would just like some opinions on the best way to handle this.

Thanks in advance.

Gina Borden

Union Hospital, Inc.

Topic

[Jim Kosloskey]

Gina,

What you are likely to face with your vendors is at least a reluctance to change their message requirements.

Most likely if they are willing to change there will be a fee.

Normally that kind of activity is best performed on Cloverleaf(R). However being a one person shop may put a strain on the target dates.

Within Cloverleaf(R) I think a lot will depend on how you are doing the integrations now. For example, if currently deploying raw routes and you need to adapt to the receiving system, at a minimum Xlates will need to be constructed. Perhaps other activities will need to be undertaken as well.

If Xlates are currently deployed then the effort may not be that great.

It might be best to perform an impact analysis to determine just what the effort would be if the receiving systems did not want their world to change.

If Cloverleaf(R) needs to do the work in your determination and the time frames allotted do not allow a single person effort, perhaps contracted assistance might be in order.

Jim Kosloskey

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Author]

Replies