Notifications
Clear all
Topic starter
A lot of CCDAs from Epic sites fail to import properly from secure messaging. We wind up with a document containing XML. Anyone else experienced this?
-Eric
Posted : May 16, 2016 2:28 am
Receiving CCDAs from other EHRs can be a nightmare... From what I understand, Surescripts runs the XML through a validator which determines if it saves correctly as CDA EMR document or it does not.
Try downloading the CCDA and run it through the NIST tool. It'll tell you what is missing from the XML and can be a conversation starter with the EPIC site.
Posted : May 16, 2016 9:07 am
Sorry, meant to share the link to the NIST validator: http://transport-testing.nist.gov/ttt/
Posted : May 16, 2016 9:08 am
Topic starter
It appears to be crapping out on ampersands in some of the fields. If I remove these, the NIST tool says the file is OK. I don't know enough about XML to know if ampersands are illegal characters. Seems like the sending EMR should compensate...
Posted : May 16, 2016 10:22 am
We have the same issue with receiving CCDAs from Cerner. Surescripts/GE does not like the xml file. We have been trying to get them to fix this for 2+ years. I am told Qvera has figured out a solution, but we don't want to pay for another product when Surescripts/GE should be able to import these as well.
Steph
Posted : May 24, 2016 9:36 am
