Community
Participate
Working Groups
Created attachment 261126 [details] Bad Header templateID MDHT Validation tool unable to detect the invalid document that does not contain a US Realm Header templateId element. Attached template (NT_Bad_USRealmHeaderTemplate_r11_v1.xml).
Assuming your tests are correct, then for R1.1 this does sound like a bug or a feature that is required. Will need to confirm. Just to have some data here for reference: R1.1: According the Brett Marquard, HL7 C-CDA co-chair C-CDA R1.1 requires BOTH the USRH and the BASE DOC whether MU or not R2.1 C-CDA R2.1 requires the BASE DOC only, whether MU or not. It MAY have the USRH as well. So for R2.1 this would not be an issue to not fire an error. For R1.1 it would be an issue if it does not fire an error.
by 'your tests are correct' - i mean that the results are using the latest build of MDHT - not the XML itself, that should be fine. Where have you been testing by the way? In a local environment? I believe I have experienced the same issue for R1.1.
Dan per your comment R1.1: According the Brett Marquard, HL7 C-CDA co-chair C-CDA R1.1 requires BOTH the USRH and the BASE DOC whether MU or not Was this a decision part of some of the errata ? I remember lots of conversations about this If the parent template is required - we need to set the "requires parent template id" flag on the generalization stereotype
I don't think there is anything specific such as errata to support it. It's possible there is a line in the IG but I was never given it as a reference. Wish we did have something more solid to go on but I don't have any aversion to the enforcement either. Seeing as C-CDA is ever-changing we should probably ask Brett again. I had previously enforced this in the web app code after validation via parsing the serialized object so that's why it came up. At this point SITE (and therefore TTT as well) is no longer processing that JSON result though. We can try the "requires parent template id" flag internally and see how that goes.
