[Brad Gollifer]

One of the fields contains the entire message.  We are passing this to an online registration project, they refuse to take the hl7.  When we pass back in anything that the patient updates via the webpage the people in control of our HIS only want certain fields to be updateable.  We do not have that kind of control, the HIS updates the fields we send and sometimes blanks out the fields we don’t send.  The solution was to pass the hl7 to the web people with some fields built out into their xml format so they can display them on the webpage.  Then if any of those fields are updated we will get the updated fields back in the xml format and retrieve the original message we sent them from one of the xml fields.  We then replace the updated fields in the origainal message and guarantee that we have not updated any other fields because they went back in as they were sent.  That is assuming they send us back the most up to date hl7 they received inside the xml field.

[Brad Gollifer]

code

[Brad Gollifer]

Probably not the best way but i wanted others that might not be as tcl savy to be able the just edit or add fields here or there to the xml if it ever needs to be modified.

[Brad Gollifer]

This is an outside company that we are dealing with that uses biztalk, elimating that probably is not going to be an option.

[Brad Gollifer]

awk ‘{gsub(/MSH/,”nMSH”);print}’  some_file >temp

puts each message on its own line and stores in file temp

then search or something else

awk ‘/some big reg ex here/’ temp

or to find a field

strings temp >temp1

grep PID temp1 |cut -f 6,20 -d “|”

returns patient_name and ssn from each message in the file

[Author]

Replies