After my file being validated I see in the Status column an "error" message but without any description.
Message at the botton - "CCDA Validation complete: 0 errors, 3 warnings, 168 details."
What does this situation mean?
Thank you in advance, Igor
Travis,
There have been quite a few threads where this has come up. It is a display issue and the NIST TTT team has a fix to be delivered in the next release.
Hopefully it helps.
Thanks
Dragon
From: transport-t...@googlegroups.com [mailto:transport-t...@googlegroups.com] On Behalf Of Frosch, Travis R (GE Healthcare)
Sent: Thursday, June 13, 2013 5:03 PM
To: transport-t...@googlegroups.com
Subject: Phantom Error CCDA Validation - VDT Inpatient, VDT Ambulatory, And Transitions of Care Inpatient Summaries
For the following CCDA Document Validators we are seeing a new error, which isn’t mapped to anything in the documents. We were not seeing these errors a few days ago with the exact same documents. Is this a new, known issue?
· VDT Inpatient Summary - MU2 170.314 (e)(1) Inpatient Summary
· VDT Ambulatory Summary - MU2 170.314 (e)(1) Ambulatory Summary
· Transitions Of Care Inpatient Summary - MU2 170.314(b)(2) Transition of Care/Referral Summary - For Inpatient Care
Travis Frosch
Product Manager
Clinical Business Solutions
GE Healthcare IT
Internal 29591
GE imagination at work
--
You received this message because you are subscribed to the Google Groups "Transport Testing Tool" group.
To unsubscribe from this group and stop receiving emails from it, send an email to transport-testing...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Igor, I see this too, I think.
Are you talking about this very first red error?
I'm not sure what it means. I just thought it was some sort of key showing that errors would be reported in red.
Has anyone seen a case where the word error does not appear in read at the top of the list?
Lisa
Lisa R. Nelson, MSc, MBA | Consultant | Life Over Time Solutions | cell: 401.219.1165 | Westerly, RI | LisaR...@cox.net
Lisa,
Thanks for jumping in on this one.
Igor sent me offline the exact screen shot and yes, you are referring to the same thing. This is a documented error in the NIST validator (a display issue) that Dragon indicated would be fixed in the next release. For now, just ignore it.
Brian