Submitted InfoPath form generates invalid HL7 message

[Charles Thompson]

I have a fresh install of Standalone 1.8.3 with the FormEntry server path properly configured. I've duplicated "Basic Form" and rebuilt its XSN so it appears in a patient's "Form Entry" tab. I can click the form's link and it loads in InfoPath without any problems. I fill it out and add an observation chosen at random, "URI", and it is submitted without error. However, it ends up in the HL7 queue with the label, "Trouble parsing HL7 message"

The stack trace turns up "HL7Exception: Invalid concept ID 'null' in hl7". You can see the whole thing here: http://pastebin.com/s8jRDgbJ

The HL7 message generated is this: http://pastebin.com/GqjK9dnj

When I inspect it with free HL7 tool I found online, it returns the following problems:

Description	Element	Line
Segment array not allowed at this position	OBR	5
Field required: OBR-4 (Universal Service Identifier)	OBR-4	5
Table #396 (Coding system) doesn't contain value '99DCT'	OBR-4-3	6
Table #396 (Coding system) doesn't contain value '99DCT'	OBX-3-3	7
Field required: OBX-11 (Observation Result Status)	OBX-11	7

When I submit the same form without any observations, I get only the problem about "Field required: OBR-4 (Universal Service Identifier)". Could these problems be the source of the HL7Exception? What can I do to remedy the situation? For now I'm sticking with 1.8.3 because there is no version of the MVP-CIEL concept dictionary for 1.8.4 and the FormEntry module isn't supported by 1.9.x.

[Jeremy Keiper]

Well ... you can start by loading the form with the latest sample XSLT.  However, I wonder if your form's schema is the reason for the nested OBR segments.  Can you post a screenshot of it, fully expanded?

Jeremy Keiper
OpenMRS Core Developer
AMPATH / IU-Kenya Support

--
OpenMRS Implementers: http://go.openmrs.org/implementers
Post: implem...@openmrs.org
Unsubscribe: implementers...@openmrs.org
Manage your OpenMRS subscriptions at https://id.openmrs.org/
 
 

[Charles Thompson]

Okay, here it is (see attached). I see the schema has a weight observation that does not appear on the form. It is not required, though. Might the have to do with the issue? I will try again with the latest XSLT and report back.

Charlie

[Jeremy Keiper]

Okay, PROBLEM LIST (and all other observations) should be under Obs.  That will probably fix your problem.  Let me know how it goes!

Jeremy Keiper
OpenMRS Core Developer
AMPATH / IU-Kenya Support

[Charles Thompson]

I moved PROBLEM LIST to Obs, saved, rebuilt the XSN, and now when I load the form and try to add a problem, it doesn't appear "Problems Added". I assume there is some design change I should make to the XSN.

Charlie

[Jeremy Keiper]

Yes, the references in the XSN to the schema fields will have to be updated to reflect their new location within the hierarchy.

Jeremy Keiper
OpenMRS Core Developer
AMPATH / IU-Kenya Support

[Charles Thompson]

Also, in this example, this "problem list" is not nested under "Obs":

http://www.youtube.com/watch?v=r7-dVV5K4kI

Charlie

[Stanisic, Lauren R.]

If you look at this wiki page, it describes form schema requirements: https://wiki.openmrs.org/display/docs/Administering+Forms

The problem list is described as not being nested under Obs. Also, we use Infopath at Ampath, and we do not move the Problem List under the Obs node.  

Additionally, the weight form field looks fine, it should not be a problem that this is under the Obs node in your schema but has not yet been added to the electronic form.  

Thanks,

-lauren

---

From: implem...@openmrs.org [implem...@openmrs.org] on behalf of Charles Thompson [char...@gmail.com]
Sent: Wednesday, February 06, 2013 10:29 AM
To: implem...@openmrs.org
Subject: Re: Submitted InfoPath form generates invalid HL7 message

[Jeremy Keiper]

Ah, so it's something else!  Did the latest XSLT work for you?

Jeremy Keiper
OpenMRS Core Developer
AMPATH / IU-Kenya Support