- This topic has 3 replies, 4 voices, and was last updated 1 year, 6 months ago by
.
-
Topic
-
so in one of the SIU messages we process, one of the sub-fields is a comment field and the upstream system allows pipes (|) to come through. Of course when they do it messes up the entire segment because it pushes down every other field thinking the pipes in the comment field are separators. Basically it’s like SQL-injection but with HL7 messages.
is there anything I can do about this?
-
Replies
-
-
There’s really not much you can do in a case like this since you don’t know how many pipes they put in the field. You can try pushing back at the vendor who is creating the message and see if they can follow the HL7 standards for escaping any delimiter characters, which for the field separator would be “\E\” (assuming “|^~\&” in the MSH segment).
I did get to thinking though, is this in the NTE segment? If so, the number of fields is limited so you might be able to figure out which pipes are part of the comment.
Paul Bishop
Carle Foundation Hospital
Urbana, IL -
What version of HL7 is it using? HL7 v2.3 only has 3 fields defined in the NTE segment so you could, with a small risk, assume that any pipe character after the first 3 is part of the comment and use ‘string map’ within a tclproc to convert them to the appropriate escape sequence. HL7 v2.5 has a fourth field, but that could be accounted for as well if you know the valid comment types.
-
-
- You must be logged in to reply to this topic.
