CCDA Validator portal is NOT working

[Prasanna S]

Hi Team,

The CCDA Validator portal is NOT working since yesterday and gives below error, by when it will be available for testing ?

URL: https://site.healthit.gov/c-cda/uscdi-v3

Regards,

Prasanna

[Kyle Meadors]

The tool will be back up shortly after the US government shutdown ends, but until then, all of the ONC sites including testing tools are down. 

--
You received this message because you are subscribed to the Google Groups "Edge Test Tool (ETT)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to edge-test-too...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/edge-test-tool/32851ea5-a2dc-41b3-a476-fdef6b88f599n%40googlegroups.com.

--

Kyle Meadors
@kylemeadors

[Ben Warfield]

We are trying to set up our local instance of the reference validator to handle scenario-based content validation while we wait for somebody to switch the government back on, but I am not able to find the actual data files (at least, I don't think I've found them) that need to be made available in the scenarios directory in order to enable that validation.

By way of example, for the 170.315_b1_ToC_Amb objective, I can find the PDF documentation here: https://github.com/onc-healthit/ccda-uscdi-certification-testdata/tree/main/uscdi-v3-testdata/Sender%20SUT%20Test%20Data/170.315_b1_ToC_Amb
but it does not appear to be the case that there is structured data for the validator to consume in those files.

Looking into https://github.com/onc-healthit/content-validator-api/blob/master/src/main/java/org/sitenv/contentvalidator/service/ContentValidatorService.java convinces me that I should be looking for an XML file named along the same lines as the PDF files (e.g.  "170.315_b1_toc_amb_svap_uscdiv3_sample1_v1.xml")

but I can't find matching XML files anywhere in that repository, or anywhere else in the onc-healthit github organization. (The same situation appears to exist in https://github.com/onc-healthit/2015-edition-cures-update-data, for what it's worth).

Can anybody point us in the direction of the data files that we would need to deploy in order to get this validation working locally?

    --Ben Warfield

[David Suarez]

From looking at archive.org, the scenario files come from GitHub:
https://codeload.github.com/onc-healthit/ccda-uscdi-certification-testdata/zip/main

Which is this repo:
https://github.com/onc-healthit/ccda-uscdi-certification-testdata

[Ben Warfield]

Yeah, the PDF documents for human consumption are in that repo, but the validator code appears to be expecting XML, so either there is some clever mechanism for extracting the structured data from those PDFs, or the actual content validation process requires some files that aren't published in that location. Or I have fundamentally misunderstood something about how content validation works, which is a totally realistic possibility, but isn't my go-to theory.

   --Ben

[sridevi Brijesh]

When is the ETT  expected to be back online. As this is affecting certification of EHR?

[J T]

I believe it will not be

back online until after the government shutdown ends.

Get Outlook for iOS

---

From: edge-te...@googlegroups.com <edge-te...@googlegroups.com> on behalf of sridevi Brijesh <csrid...@gmail.com>
Sent: Tuesday, October 14, 2025 10:28:21 AM
To: Edge Test Tool (ETT) <edge-te...@googlegroups.com>
Subject: Re: CCDA Validator portal is NOT working

 

To view this discussion visit https://groups.google.com/d/msgid/edge-test-tool/da0110f7-5a9a-4e92-bf2c-1f66316fa9b4n%40googlegroups.com.

[Mat Davis]

Hey Ben.

Yeah, I'm inclined to agree with you.

Based on the Reference Validator code, looks like it went from XML scenario files to class files and internal, code specific validation but that's just my assumption.

I still haven't been successful with setting up the Content Validator though but I'll keep trying, making sure to review any previous ETT Google Group threads for guidance.

Thanks - Mat

[Mat Davis]

Hi all.

Historical Link

Please check out this historical thread from 2017.

https://groups.google.com/g/edge-test-tool/c/0ZpjVv8_O44/m/AT7BSfufAgAJ

Notes

1. It's from 2017 so take that with a grain of salt

Content / Scenario Validation

2. Notice the Postman example screenshot later in the historical, 2017 thread

• even though it's selecting CCDA_IG_Only, notice that reference file is pointing to a PDF sample in the URL params while the XML is listed in the Post Body
  
  
• I understand why the Post Body options are what they are because I've used the Postman route when the old, public validator was available
• That reference file name, however, may be expecting PDF for Ben's content validation expectations

No Scenario Screenshot

Scenario Screenshot

Building The WAR File Manually
3. The immediate blocker I experienced when trying to build my own WAR file using Maven locally, 2 years ago, was the dependency errors

• I couldn't figure them out 2 years ago so I moved on
• That historical 2017 thread (thanks to the great Dan Brown) touches on how to move pass / meet those dependency requirements
• This thread below,  also from Dan Brown, also touches on dealing with those dependency issues
• https://groups.google.com/g/edge-test-tool/c/Eh7LxPUZu_M/m/g-8GWoNvDAAJ
• MY POINT = if you can get pass the dependency issues and pass any other unknowns, we could hopefully build the WAR file locally using the latest source code but I'm not a Java developer so still muddling thru

Thanks - Mat

[Mat Davis]

Hi all - here's my final update for the efforts on my end.

1. Building The Latest WAR File

• See step by steps here - https://groups.google.com/g/edge-test-tool/c/n7AIXXWA0ns
• I had to learn how to build the dependency / JAR files for the CodeValidator and the ContentValidator using Maven (automation builder/compiler/tester)
• Only then, was I able to use Maven in order to build the WAR file for the C-CDA Reference Validator API using the Github latest source files

2. Implementing The Content Validator For Patient Specific Scenarios

• See more info here - https://groups.google.com/g/edge-test-tool/c/gYLJ5yv62Kc
• TLDR #1 - you need "answer key XMLs" with all the info for that target Patient Specific Scenario to compare to your submitted CCD when testing scenarios - for example, like USCDIv3 > b1 > Amb > 01
• TLDR #2 - you have to store all "answer key XMLs" in the your configured scenarios directory without any sub folders
• Basically, IMO, it's almost impossible to get true 1 to 1 Content Validation for SITE vs Local Validator Instance until the "answer key XMLs" are provided in the Github releases (not providing these "answer key XMLs" may be on purpose)
• Thanks again to Dan Brown's historical threads as well as the POVs from Ben Warfield and David Suarez from above

Thanks - Mat Davis

https://dynamichealthit.com