Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Generating valid C-CDA
See original GitHub issueI am doing some FHIR -> CCDA transformation work and I thought this project might be a good source of test data. Unfortunately, when I ran the sample CCDA output through a validator (e.g. the one at https://sitenv.org/sandbox-ccda/ccda-validator), it pointed to a number of issues.
ERROR: Mu2consol US Realm Header SHALL contain at least one [1..*] recordTarget, where its type is Record Target each SHALL contain exactly one [1..1] patientRole, where patient Role SHALL contain exactly one [1..1] patient, where patient SHALL contain exactly one [1..1] ethnicGroupCode, where the @code SHALL be selected from OMB Standards for the Classification of Federal Data on Race and Ethnicity.
ERROR: Consol US Realm Header SHALL contain at least one [1..*] author, where its type is Author (CONF:5444) each SHALL contain exactly one [1..1] assignedAuthor, where (CONF:5448) each SHALL contain at least one [1..*] addr (CONF:5452, R2.1=CONF:1198-5452) addr SHALL contain at least one and not more than 4 streetAddressLine (CONF:7291, R2.1=CONF:81-7291)
ERROR: Consol US Realm Header SHALL contain at least one [1..*] author, where its type is Author (CONF:5444) each SHALL contain exactly one [1..1] assignedAuthor, where (CONF:5448) each SHALL contain at least one [1..*] addr (CONF:5452, R2.1=CONF:1198-5452) addr SHALL contain exactly one [1..1] city (CONF:7292, R2.1=CONF:81-7292)
...
Any plans to address those? Or maybe I’m missing something?
Issue Analytics
- State:
- Created 6 years ago
- Comments:16 (14 by maintainers)
Top Results From Across the Web
Consolidated Clinical Document Architecture (CCDA)(BCCD)
The CCDA application accesses RPMS data through classes generated by the ... status to TS (for Transmission Started), and transforms it into a...
Read more >Generating a CCDA - TRAKnet Wiki
To generate a CCDA from the patient's encounter, complete the Visit Note and sign the encounter. Once the Sign and Close button is...
Read more >CDA: Generate Document - iNTERFACEWARE Help Center
We will simplify the code to only create a “Minimal CDA”, i.e., the simplest possible CCD compliant document that only contains the minimum...
Read more >170.315(g)(6) Consolidated CDA creation performance
This Certification Companion Guide (CCG) is an informative document designed to assist with health IT product development.
Read more >CCDA Generation using Everest API - CodeProject
A CCDA document is an XML document that has a set structure. We have to ensure that we make a document that adheres...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
In case it helps, I just pushed a 1-class project that will invoke the MDHT validator on a directory of files: https://github.com/lmsurpre/mdht-validator The only part I forgot to mention above is that you need to load the MDHT EMF “packages” before calling the validator.
I confirm that with these updates, the generated files are passing validation. I don’t have the power to close the issue, but please do. Thanks!