ETT Validation results for 170.315_b1_toc_amb_sample2_v13

[Georgia Fortun]

Error - 

The scenario contains problem observation for Problem Code: 55607006 , however there is no matching observation in the submitted CCDA.

Line number: 0

Error - 

The scenario does not require data related to Encounter Diagnosis, but the submitted C-CDA does contain Encounter Diagnosis data.

Line number: 0

Since yesterday's update, the above error occurred today. This file passed prior to the update. 

The above results are returned for the attached file. 

This appears to not be correct, the file does not include Code 55607006, but does have the dx required 699134002. Please advise. 

Thank you

[Nagesh Bashyam]

Georgia

 

Thanks for pointing this out.

 

1.     The first issue is something that you can resolve by representing “No Known Problems” per HL7 guidance here:

a.     http://hl7-c-cda-examples.herokuapp.com/examples/view/7353a215efda8dfe3fbacb19abbb90756ce14bab           

 

2.     The second issue, I have applied a fix which should be available now. Let us know if your issues is not fixed yet.

 

Thanks

Dragon

--
You received this message because you are subscribed to the Google Groups "Edge Test Tool (ETT)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to edge-test-too...@googlegroups.com.
To post to this group, send email to edge-te...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/edge-test-tool/58924058-53e2-402a-910e-975d8fd132ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Ryan Durham]

Hey Nagesh,

We are actually experiencing the same issue for b6_de_toc_amb_sample2_v13 and we do have an encounter dx of SNOMED 699134002 as per the test scenario.

Thanks,

-Ryan

[Ipc Dev]

Hi,

We are also facing the same issue when we generate Encounter Diagnosis with CCDA

and Generate Error Message when no generate Encounter section for RN

So, Do we generate Encounter Diagnosis section for Both CCD, RN and DS Document Type.

[Nagesh Bashyam]

Hello

 

Enounter Diagnosis element is required per the regulations, so it needs to be included in the C-CDA that is created.

 

Thanks

Dragon

 

From: edge-te...@googlegroups.com [mailto:edge-te...@googlegroups.com] On Behalf Of Ipc Dev

Sent: Friday, August 04, 2017 8:56 AM
To: Edge Test Tool (ETT)

--

You received this message because you are subscribed to the Google Groups "Edge Test Tool (ETT)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to edge-test-too...@googlegroups.com.
To post to this group, send email to edge-te...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/edge-test-tool/b17cc210-4d7d-43e1-9d5a-f77408b4cd50%40googlegroups.com.

[Ryan Durham]

Right, so why are we getting an error when we include it that says it's not required but exists (see Ipc Dev's first screenshot or my post).

This started yesterday by the way.

-Ryan

[Nagesh Bashyam]

Ryan

 

Did you test today …or yesterday after we put in a fix for this issue ?

 

If so , can you attach your sample.

 

Thanks

Dragon

To view this discussion on the web visit https://groups.google.com/d/msgid/edge-test-tool/fa8f3ec2-35d2-4014-9f14-2797d0299fe0%40googlegroups.com.

[Ryan Durham]

Tried yesterday and today.

Attached is the file

[Nagesh Bashyam]

Ryan

 

I just ran your file and I don’t see any errors.

 

To view this discussion on the web visit https://groups.google.com/d/msgid/edge-test-tool/f2a2f26a-8045-4f1a-b58e-d98d9d3fbfe7%40googlegroups.com.

[Ryan Durham]

Run it against this scenario: b6_de_toc_amb_sample2_v13

[Nagesh Bashyam]

Ryan

 

Good catch, there was a typo in the DE Scenario that I have corrected.  The problem will be fixed once I restart the validator which I  will do tonight.

 

The other Ambulatory Sample 2 scenarios were fine (CCDS/VDT).

To view this discussion on the web visit https://groups.google.com/d/msgid/edge-test-tool/7e88ddf1-752d-4c0f-b716-89e8fe5a3834%40googlegroups.com.