Procedure note validation failed.

[adria...@gmail.com]

Hello, 

 I'm trying to validate my CCDA against the scenario  "170.315_b1_ToC_Amb" -> "170.315_b1_toc_amb_sample1_v1.pdf".

I'm particularly interested on adding following "Procedure Note": Dr Albert Davis examined Ms Alice Newman and found that the pacemaker is operating properly and the breathlessness is due to high fever and anxiety.

I'm doing that as a standalone entry on the procedures section (2.16.840.1.113883.10.20.22.2.7.1) of the CCDA. 

See below so you can see how that entry looks.

<entry typeCode="DRIV">  

    <act classCode="ACT" moodCode="EVN">  

    <templateId root="2.16.840.1.113883.10.20.22.4.202" extension="2016-11-01"/>  

    <code code="34109-9" codeSystem="2.16.840.1.113883.6.1" codeSystemName="LOINC" 

displayName="Note">  

      <translation code="28570-0" codeSystem="2.16.840.1.113883.6.1" codeSystemName="LOINC" 

displayName="Procedure note" />  

    </code>  

    <text>  

      <reference value="#ProcedureNote1" />  

    </text>  

    <statusCode code="completed"/>  

    <!-- Clinically-relevant time of the note -->  

    <effectiveTime value="20140203" />  

    <!-- Author Participation -->  

    <author>

     <templateId root="2.16.840.1.113883.10.20.22.4.119" /> 

            <time value="20150622" />

                <assignedAuthor>

                  <id root="2.16.840.1.113883.4.6" extension="1891798849" />

                  <assignedPerson>

                    <name>

                      <given>DR ALBERT</given>

                      <family>DAVIS</family>

                    </name>

                  </assignedPerson>

                </assignedAuthor>   

    </author>

   </act>  

 </entry>

I'm just getting one error: 

"The scenario requires a total of 0 Author Entries for Procedures Section/ProcedureActivityProcedure, however the submitted data had only 1 entries.

Line number: 0"

In this case I can not remove the author node. If I remove it I get the following error:

Error - Consol Note Activity SHALL contain [1..*] author such that it (3250-16913) Conforms to Author Participation (templateId: 2.16.840.1.113883.10.20.22.4.119)

/ClinicalDocument/component/structuredBody/component[2]/section/entry[6]/act

Line number: 362

Any ideas??

[adria...@gmail.com]

Any ideas on this issue. I did my implementation based implementation guide instructions for "Note Activity" I'm really stuck on this. Please help. 

[Dan Brown SITE]

Thank you for the information. There is no situation where we should be requiring 0 of something. So, this is certainly a bug. We will fix it, and, let you know when that fix will be available soon.

Thanks,

Dan

[adria...@gmail.com]

Thank you so much Dan. That helps a lot. 

[David Herman]

Is it safe to assume that I'm hitting this same bug?

The scenario requires a total of 0 Author Entries for Problem Section/ProblemConcern/ProblemObservation, however the submitted data had only 5 entries.

Line number: 0

[Dan Brown SITE]

Hi David,

Yes, this is the same bug. It will be resolved in the release this month.

Thanks,

Dan

[Matt Szczepankiewicz]

Hi Dan--we're still seeing this issue (or at least a related one) in some cases. For instance, the attached document produces the following error against the 170.315_e1_vdt_inp_sample1_v1.pdf scenario:

Error - The scenario requires a total of 4 Author Entries for Vital Signs Section/VitalSignsOrganizer/VitalSignsObservation, however the submitted data had only 10 entries.

The fact that the validator is throwing an error for "only" having 10 entries instead of the required 4 seems like a lingering bug.

- Matt

[Dan Brown SITE]

The original bug addressed was requiring 0 of something in these cases. Interesting that a version of it exists with more than 0 as well. We will look into resolving this soon. Thanks for bringing it to our attention, Matt.

[Matt Szczepankiewicz]

Hey Dan--can we expect to see a fix for this in the next validator update at the end of March?

- Matt

[Dan Brown SITE]

Hi Matt,

This issue should be resolved as part of a hotfix point release deployment done this past Monday night. Have you tested since then?

Thanks,

Dan

[Matt Szczepankiewicz]

Ah, good to know. After some retesting we're no longer seeing this issue. Thanks!