Splitting multiple FT1 segments into individual messages

[Ken Climer]

Hey there!  I have a situation that I’m sure has already been discussed, but I can’t find a good way to search the threads to find out.  So here goes.

This is a case of an HL7 billing-extract file, where there are multiple FT1 segments included in 1 message.  The patient has a visit-level and potential multiple procedures.  For example:

MSH|^~&|SUPER_APP|HOSPITALCODE|||200706211955|12|DFT^P03|205540|P|2.3

EVN|P03|200706211955

PID|1||N1234|238284|PATIENT^JOHN^Q||19800101|M||||||||||N4321|111223333

PV1|1|E|||||TEST^TEST^DOCTOR^|||||||||||||08||||||||||||||||HOM|||12|||||200706211016|200706211410

FT1|1|||200706211016|200706211955|CH|042967|||1|||ED|||||F|||||||99284|00

FT1|2|||200706211016|200706211955|CH|042940|||1|||ED|||||F|||||||XX065|00

FT1|3|||200706211016|200706211955|CH|042923|||1|||ED|||||F|||||||XX075|00

You’ll notice that this one message has three charges (FT1s).  Some billing systems don’t recognize multiple FT1s, so I’d like to know if anyone has translated this (through an ITERATE or just what) to become three individual messages, such as:

MSH|^~&|SUPER_APP|HOSPITALCODE|||200706211955|12|DFT^P03|205540|P|2.3

EVN|P03|200706211955

PID|1||N1234|238284|PATIENT^JOHN^Q||19800101|M||||||||||N4321|111223333

PV1|1|E|||||TEST^TEST^DOCTOR^|||||||||||||08||||||||||||||||HOM|||12|||||200706211016|200706211410

FT1|1|||200706211016|200706211955|CH|042967|||1|||ED|||||F|||||||99284|00

MSH|^~&|SUPER_APP|HOSPITALCODE|||200706211955|12|DFT^P03|205540|P|2.3

EVN|P03|200706211955

PID|1||N1234|238284|PATIENT^JOHN^Q||19800101|M||||||||||N4321|111223333

PV1|1|E|||||TEST^TEST^DOCTOR^|||||||||||||08||||||||||||||||HOM|||12|||||200706211016|200706211410

FT1|1|||200706211016|200706211955|CH|042940|||1|||ED|||||F|||||||XX065|00

MSH|^~&|SUPER_APP|HOSPITALCODE|||200706211955|12|DFT^P03|205540|P|2.3

EVN|P03|200706211955

PID|1||N1234|238284|PATIENT^JOHN^Q||19800101|M||||||||||N4321|111223333

PV1|1|E|||||TEST^TEST^DOCTOR^|||||||||||||08||||||||||||||||HOM|||12|||||200706211016|200706211410

FT1|1|||200706211016|200706211955|CH|042923|||1|||ED|||||F|||||||XX075|00

This may be a real simple ITERATE, or the like, and I may be over-analyzing it.  But, any assistance that is out there, would be greatly appreciated.

Topic

[Ryan Spires]

Ken,

Sounds like you are on the right track.

At the end of the FT1 iteration, you can do the SEND command.

Just make sure you have mapped all the “static” fields, fields you want sent in evey message prior to the iterate.

At the end of the FT1 iterate (but within in) do the SEND, this will generate a message and send it on.

At the end of the Xlate, use the SUPPRESS command to stop the original message.

Let me know if you need more info.

Ryan Spires

[Jim Kosloskey]

I would suggest you do CONTINUE rather than SEND.

Just remember to have one SUPRESS (I usually put it at the beginning of the Xlate) otherwise you will get one extra outbound message (unless that has been changed).

Jim Kosloskey

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

[Ryan Spires]

I agree with Jim,  Do the continue instead of the send.   Got the two backwards… thanks for the correction!!!

Ryan

[Author]

Replies