Tweet
Hey,
Please have a look at this issue...We insert transcription message (from MySQL DB) in OBX 5.1.. Each section of the transcription separated by 'n' character (which is unavoidable). So we wrote a script to replace the 0x0D to '~'. Please have a look at the JavaScript that we use. And while applying the script in Non-strict parsing mode the transcription comes replacing 0x0D with ^. So we tried in Strict parsing. There some fields after OBX 5.1 is vomitted but we are getting the transcription in the desired way. We need to rectify this problem as soon as possible as we are upgrading from Mirth 1.3.1 to Mirth 1.6.1. The JavaScript and the OBX segment is pasted below. Please help.
JavaScript:
var segment = msg['obx.trans'].toString();
var segmentarray = segment.split('n');
var i = 0;
while (i<segarray.length)
{
tmp['OBX']['OBX.5']['OBX.5.1'][i] = segarray[i].replace(0x0D,"~"); //I tried 0x0D, 0x0B, 0x1C, ^ instead of using 0x0D and //that too globally /g
i = i + 1;
}
In actual HL7 message template...
OBX|1|TX|||Transcription||||||R
While Non-Strict parsing:
OBX|1|TX|||^^HISTORY OF PRESENT ILLNESS: A 36-year-old male...^^CURRENT MEDICATIONS: Motrin, Vicodin...^^ALLERGIES: None.^^PHYSICAL EXAMINATION: On exam.||||||R
While Strict parsing:
OBX|1|TX|||~~HISTORY OF PRESENT ILLNESS: A 36-year-old male...~~CURRENT MEDICATIONS: Motrin, Vicodin, and Seroquel.~~ALLERGIES: None
If you look closer, while in strict parsing, OBX11.1 was vomitted.
As mentioned above we are migrating to Mirth 1.6.1. For that we need to fix this problem. Please help on the issue. Thank you.
Regards,
Jemy J.
Post edited by: jemy_j, at: 10/06/2007 02:55
Post edited by: jemy_j, at: 10/06/2007 02:56
Post edited by: jemy_j, at: 10/06/2007 02:57
Please have a look at this issue...We insert transcription message (from MySQL DB) in OBX 5.1.. Each section of the transcription separated by 'n' character (which is unavoidable). So we wrote a script to replace the 0x0D to '~'. Please have a look at the JavaScript that we use. And while applying the script in Non-strict parsing mode the transcription comes replacing 0x0D with ^. So we tried in Strict parsing. There some fields after OBX 5.1 is vomitted but we are getting the transcription in the desired way. We need to rectify this problem as soon as possible as we are upgrading from Mirth 1.3.1 to Mirth 1.6.1. The JavaScript and the OBX segment is pasted below. Please help.
JavaScript:
var segment = msg['obx.trans'].toString();
var segmentarray = segment.split('n');
var i = 0;
while (i<segarray.length)
{
tmp['OBX']['OBX.5']['OBX.5.1'][i] = segarray[i].replace(0x0D,"~"); //I tried 0x0D, 0x0B, 0x1C, ^ instead of using 0x0D and //that too globally /g
i = i + 1;
}
In actual HL7 message template...
OBX|1|TX|||Transcription||||||R
While Non-Strict parsing:
OBX|1|TX|||^^HISTORY OF PRESENT ILLNESS: A 36-year-old male...^^CURRENT MEDICATIONS: Motrin, Vicodin...^^ALLERGIES: None.^^PHYSICAL EXAMINATION: On exam.||||||R
While Strict parsing:
OBX|1|TX|||~~HISTORY OF PRESENT ILLNESS: A 36-year-old male...~~CURRENT MEDICATIONS: Motrin, Vicodin, and Seroquel.~~ALLERGIES: None
If you look closer, while in strict parsing, OBX11.1 was vomitted.
As mentioned above we are migrating to Mirth 1.6.1. For that we need to fix this problem. Please help on the issue. Thank you.
Regards,
Jemy J.
Post edited by: jemy_j, at: 10/06/2007 02:55
Post edited by: jemy_j, at: 10/06/2007 02:56
Post edited by: jemy_j, at: 10/06/2007 02:57
Comment