Notifications
Clear all
General Discussion
7
Posts
2
Users
0
Reactions
133
Views
Topic starter
I currently have a CCDA export interface running through Qvera and going to an HIE. I'm getting some errors like this:
Document Data # does not exist.
No row with the given identifier exists: [com.gehcit.cp.chart.data.DocumentData#1618744960080760]
Has anyone ever seen this?
Posted : April 11, 2017 6:48 am
I have seen similar issues although not on the docdata table.
Can you check the docdata table to see if a record exists?
select * from docdata where sdid = 1618744960080760
If not, check to see if the document exists and check to see if it is signed because nothing exists in docdata if the document is not signed.
select status from document where sdid = 1618744960080760
Is the status "S"? If it is blank, it means there is no document with that ID, if it is anything besides S or U it likely means that the document is not signed yet which means there should not be a docdata entry. I would then check to see if the document is viewable within EMR.
select p.firstname, p.lastname, p.patientid, d.summary, ml.convert_id_to_date(d.clinicaldate) clndate from document d
inner join person p on d.pid = p.pid
where d.sdid = 1618744960080760
Posted : April 11, 2017 2:41 pm
Topic starter
I've tried these. The database seems to think the document does not exist when in fact it does. The CCDA matches an office visit document in EMR. When I search the office visit SDID, it is a different number. I'm not sure what could have caused the issue.
Posted : April 11, 2017 11:52 pm
Topic starter
I've tried these. The database seems to think the document does not exist when in fact it does. The CCDA matches an office visit document in EMR. When I search the office visit SDID, it is a different number. I'm not sure what could have caused the issue.
Posted : April 12, 2017 12:10 am
Do all of the above results return nothing? If so, the EMR Timestamp could be for another column in the database. It is quite often caused by either users that don't exist or PVIDs in tables set to 0.
Do you believe 1618744960080760 to be an SDID from the documents table or PVID from the USR table?
If you know which document is causing the issue, can you email me the details from that row in the database minus any PHI? Specifically I would be looking for document.sdid, document.did, document.pubuser, document.usrid
I have fixed a few issues almost identical to this one recently.
Also, have you run the GE script that is supposed to fix some of the CCDA generation issues? You would have had to sign a waiver to run it.
Posted : April 12, 2017 1:23 am
Topic starter
I've deleted all PHI info.
This is the row that does exist.
Posted : April 12, 2017 2:50 am
Topic starter
I've deleted all PHI info.
This is the row that does exist.
Posted : April 12, 2017 3:15 am
