HL7 Standards

[Robert Denny]

We have a client that is asking us to modify MDM type messages into ORU and mimic our Radiology format.

I am told I should only follow HL7 standards and if they want this level of modification they will have to do it. Is there a standard for changing MDM into ORUs?

I will research HL7.org, but I wanted to ask here since there is so much experience at the location.

Topic

[Jim Kosloskey]

Nothing I know of prohibits one from changing one Message/Event Type (like MDM) to another (Like ORU^R01).

As long as the data is still representative, does not change the meaning of the data, and is agreed upon by both trading partners then in mmy opinion it does not matteer who does it.

What if the receiving system had proprietary message structure or used a different standard, would the position be to refuse to do that?

After all isn’t this what a good Integration tool is for?

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

[Robert Denny]

Thanks Jim,

I think I will probably end up doing this modification, but I think they are asking do much of their work. We are trying to avoid getting in a position where we have to do their maintenance.

[Jim Kosloskey]

Robert,

Well that is the negotiation part. If they are capable of receiving an MDM then they should receive the MDM (perhaps with some adjustments).

However, if they are not able to receive an MDM that would require some negotiation – the result of which could be to convert the MDM to a Message/Event Type they can consume which is negotiated.

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

[Paul Bishop]

we regularly change message types from what one vendor sends to what is required for another vendor.  We have threads that change ORM messages to ADT messages, SCH to ADT, MDM to ORU, ORU to MDM, HL7 to flat files.  It just all depends on what is required on the receiving side and what is available on the sending side.  About the only time we then have to change something is when either system does an upgrade, and then it’s usually minor changes.

Paul Bishop
Carle Foundation Hospital
Urbana, IL

[Robert Denny]

Thanks you all for you input. We did push back and they agreed to accept MDMs.

[Kaley Grimes]

I have a situation which many people may relate to. I have no real issue with making translations or changes based on the needs of a system. Do I think the engine should be used to fix application issues, no. However, I do what’s in the best interest of my organization.

I’m currently being presented with a situation where a vendor provided information in a spec where they indicate they are looking for data in the HL7 standard field (PV1.44 for admission dt/tm). Then, they verbally tell me they want the data in PV1.44 to be put in EVN2. End of Story. We’ve been sending data to this vendor for well over six years and now want this change made. The vendor tells me they will not make a change to their base config, and that I need to make the change.

Again, I typically have no issue with moving data in a message but I started to think, “just because I can, does that mean I should?”

Any thoughts?

[Author]

Replies