Problem: convert all ADT types frm v2.4 to v2.2 in a week!

[John Harvey]

Hi group,

I have something of a problem that could turn into a bigger problem.  is there a way for me to convert all ADT event types from ADT version 2.4 to version 2.2?  We are upgrading our ADT to version 2.4 for one particular vendor, but not all vendors we feed to can take 2.4 and need to remain at version 2.2…and we only have one feed that will forever be 2.4 by weeks end.

I remember asking if this could be done way back at training time, I was told yes, use a wild card route, but that was as far as it got.  Is there a way to do this without creating a translation configuration for each message type?  I only have a week to do this, as this one vendor needing 2.4 is very pushy for us to move it live and I’m forced to deal with this however I can…

Any advice?  Thanks to all in advance!!

John Harvey

😯

Topic

[Robert Kersemakers]

Hi John,

So your incoming messageflow has always been in ADT 2.2 and all your outgoing flows have also been 2.2, but now you get an extra receiving system which needs ADT 2.4. And for that you’re going to upgrade your incoming flow to ADT 2.4?

I would stay with the incoming 2.2 messages (which you’re familiair with) and add an extra translation form 2.2 to 2.4 to accomodate your new system. This is much easier then upgrading your incoming flow (and having to tackle all those nasty little problems you can’t foresee) and then having to downgrade these 2.4 messages into 2.2 for all your existing systems.

I have included a ‘standard’ (ie written to fit our own messages) translation from 2.2 to 2.4 as an example. But be aware it is written based on the Dutch HL7 ADT 2.2/2.4 definition. And it would help if you can read Dutch…

Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands

[John Harvey]

Thanks Robert, that was my original thought, but our Meditech ADT version 2.2 feed (actually 2.1) does not supply all of the segments the recieving system needs (it’s for a billing system).  I asked if we could just have an individual 2.4 feed by itself, but apperantly Meditech won’t let us do that.  Therefore, we are forced to upgrade our current 2.1 to 2.4 to get from Meditech all of the segments the recieving billing system needs (it’s not so much a vendor as it is another hospital within our network I found out).

I’ve have a pretty good handle on the conversion so far, but like you said, I’m sure I’m going to run into some unforseen complications!

[Author]

Replies