This tool will display the data <entry> portion of your CDA.
Rules: You can only use this tool with de-personalized CDAs. But we have a personal desktop version you can use anyway you like, click here.
Questions and Answers ….
Q: How does this tool work?
You upload your CDA. Make sure it contains no personal information, like your name and address. We process the file. Then, we show you the contents of the <entry> components of your CDA. That’s where the data is stored. We show only the non-narrative components in a friendly format.
Q: What’s a CDA?
CDA stands for Clinical Document Architecture. It is a format clinicians use to share healthcare information. Here is a sample CDA for an imaginary patient. What you see is called the <Text> component, or the “human readable” part. This is not the data that will be imported into the receiving party’s computer.
Here’s a “human readable” snippet from a CDA.
There is another part, called the <entry> component, that is used to actually encode the medical data. This is what an <entry> component might look like:
This utility will enable you to see exactly what’s contained in the <entry> components of your CDA so you can compare it with the “human readable” part.
Let me share an example. Here is a “human readable” snippet from a CDA published on the internet, https://github.com/jmandel/sample_ccdas
I ran this CDA through our tool. Here is a snippet showing what was contained in the <entry> component of the CDA above.
The “Status” displayed to the clinician is NOT the same as the “Status” contained in the <entry> component.
To look at the <entry> component from the CDA, click here. The status clearly states “completed”, yet the clinician sees something totally different.
This is not good. Admittedly, this may not happen often, but if it happens at all, we should take notice.
Q: Why is this important?
Your healthcare data is stored in two separate parts of the CDA, and your clinician only reviews one part before sending it off to another clinician. What if there is an error in the data part? You would never know. And yes, computers do make errors.
What do you call a banker that sends out a financial transaction without first eyeballing the actual data? Unemployed.
Q: What’s De-Identified Data, and what is it good for?
Start here: https://nvlpubs.nist.gov/nistpubs/ir/2015/nist.ir.8053.pdf
We only show the parts of the CDA that do not contain personal information. We have removed names, addresses, phone numbers, etc.
Q: How do you handle “location”?
If the CDA zip-code has a population fewer than 10,000 people, then only the state is show in the output. If the population is greater than 10,000, then the first three digits of the zip-code are used, and zeros are appended.
Q: My output does not show some data that I can see in the “human readable” part. Why?
Three possibilities. First, we only show the following components: Advance Directives, Alerts, Functional Status, Hospital Admission, Immunizations, Medical Procedures, Medical Equipment, Medications, Problems, Results, Social History, Vital Signs. We do not show narrative data because it could include information that could identify the patient.
Second, your CDA could be “poorly formed”. That’s a nice way of saying the vendor made an error. But you cannot see that in the “human readable” portion of the CDA, can you?
There is a third reason … we made an error … but, I don’t think so. But if we did, please let us know and we will fix our tool pronto.
Q: My output says “No Data”, but the human readable part of my CDA clearly shows data.
The <entry> component was empty. The human readable component was not … Therein lies the problem with the CDA.