OBX From Data Extract
- This topic has 17 replies, 5 voices, and was last updated 3 years, 3 months ago by
.
-
Topic
-
This may be a repeat of old information, but I can’t quite find what I need in searching the forums.
I have a file extract from a database which has data elements belonging in the OBX segments for vitals, progress notes, etc. Many of these elements are coming out as multiple lines which I need to combine into a single HL7 message. What is the best way to accomplish this? The data is currently mapped from the file via VRL through a translation to the HL7 which is fine, but I’ve toyed with an iteration in a translation and a little bit of Tcl, but I’m sort of stuck and hoping someone here can help me on the direction I need to take to get the multiple OBX segments in the message that I need – seems like I have the right pieces but can’t seem to fit them together appropriately.
-
-
do you have an example of what your source file looks like?
If the issue is just creating a single HL7 message with multiple OBX segments populated with the values of your source file, wouldn’t you just iterate through OBX segment with a MATH (add +1) at the beginning of the loop so everytime it has a variable to populate, it populates the OBX 1 field in sequence and fills OBX5 with that variable?
**disregard the attachment : I incorrectly read your post initially **
-
-
I see your sample file. should each line be a new message, or should this entire file create a single HL7 message? Its hard to tell from the example b/c mrn and acct numbers are the same for each line. However, your original post states that multiple lines may be required to create a single message. Can you clarify that? will the multiple lines also contain the same values in filler orderID and procedure ID? if not, you’ll need to create repeating obr,obx groups to keep the procedure data together.
-
so sometimes each line will be a new message and sometimes not? that is going to tricky. And i dont think you can reliable do that in an xlate. you’d wanted to be very clear on what is the trigger for creating a new message or appending the next line to the same message. it could be best to first re-create the source file, so that it contains all the data you need for a single outbound hl7 message.
-
-
-
-
It was a Meditech extract from it’s DR database and I think, if I remember correctly, we ultimately ended up splitting up the extract into multiple files and doing the following:
<code>
set RESULTID [lindex $s 7]
set systemTime [clock seconds]
set dateTime [clock format $systemTime -format %Y%m%d%H%M%S]### retrieve MRN from flat file
set pathfile “/opt/cloverleaf/cis6.2/integrator/_xcon_note01/data/Meditech/gbResultID.TXT”
set fileID [open $pathfile]
set prevRESULTID [read $fileID]
close $fileIDif {$RESULTID != $prevRESULTID && $pt != “” && [string range $MRN 0 2] == “HSM”} {
# normal logic here
} else {
### OBX logic
set obx “”
#echo “entering OBX logic…”
set MRN [lindex $s 0]
set OriginiationTimestamp [lindex $s 9]; set yyyymm [string range $OriginiationTimestamp 0 5]
#set OBSERVATIONVALUE [lindex $s 15]
set OBSERVATIONVALUE [lindex $s 36]
set OBSERVATIONVALUE [string map {$EndofSegment “~”} $OBSERVATIONVALUE]#set SEQNUM [lindex $s 16]
set SEQNUM “1”
#set OBX3VALUE [lindex $s 15];
set OBX3VALUE “”
set obx “OBX|$SEQNUM|TX|$OBX3VALUE||$OBSERVATIONVALUE”
if {$OBSERVATIONVALUE != “” && $OBSERVATIONVALUE != “ReportText” } {
#echo $obx
set fn_suffix “HOS_FR_SHMT_”;
append fn_suffix $yyyymm;
append fn_suffix “_HL7_”;
append fn_suffix $MRN;
append fn_suffix “.txt”
#set pathfile2 “/opt/cloverleaf/cis6.2/integrator/_xcon_note01/data/SHMT_HOSP/$fn_suffix”
#set pathfile2 “/opt/cloverleaf/cis6.2/integrator/_xcon_note01/data/2020/conv_MeditechNotesSampleHL7.txt”
#set pathfile2 “/home/hci/Conversions/epicextract07/Summit Conversion/_xcon_trans01/data_in/TRANS_DLTA_SHMT/Final/HL7_$fn_delta”set pathfile2 “/home/hci/Conversions/epicextract07/Summit Conversion/_xcon_trans01/data_in/TRANS_DLTA_SHMT/Final/HL7_$fn_delta.txt”
set HL7file [open $pathfile2 a+]
puts -nonewline $HL7file $obx; puts -nonewline $HL7file $EndofSegment
close $HL7file}
</code>
-
-
- You must be logged in to reply to this topic.
