XML to HL7: behavior with non tagged fields

[rods]

Let's say I delete the IN1 segment and then attempt to rebuild it with field data from scratch. i.e.,

delete msg['IN1'];
msg['IN1']['IN1.44']['IN1.44.5'] = '12345';

I would expect that the parser would take the XML and generate something like:

MSH| ...
...
IN1||||||||||||||||||||||||||||||||||||||||||||^^^^12345

but instead it gives me

MSG| ...
...
IN1|12345

Is there a way I can force it XML to HL7 function to "fill in the blanks?"

- Jeremy

Post edited by: rods, at: 08/24/2007 12:46

[chrisl]

Re:XML to HL7: behavior with non tagged fields

Not in the current release, however the parser will be updated soon to automatically handle this.

[rods]

Re:XML to HL7: behavior with non tagged fields

Ok. Looking forward to it in the next release.

Here's my Javascript workaround:

        
        // create fields prior to IN1.45
	for (var j = 1; j <= 44; j++) { 
		var field = "msg['IN1']['IN1." + j + "'] = '';";
		eval(field);
	}
	// create subfields prior to IN1.44.5
	for (var j = 1; j <= 4; j++) { 
		var subfield = "msg['IN1']['IN1.44']['IN1.44." + j + "'] = '';";
		eval(subfield);
	}
	msg['IN1']['IN1.44']['IN1.44.5'] = '12345';

BTW: Keep up the awesome work. Mirth Rocks! I can't wait to create some plugins.

Post edited by: rods, at: 08/24/2007 13:54