"Answer key" files for content validation in local deploy

[Ben Warfield]

This topic has been raised a couple times recently but mostly as a footnote to other threads, so I wanted to give it a top-level thread in hopes that people who are now no longer furloughed or on stop-work will be able to respond to it. :-)

When setting up the C-CDA reference validator locally, the instructions explain how to configure the server to look for scenario files, but nothing is actually said about where the scenario files themselves can be obtained. Back in early October, I tried to find them without success (https://groups.google.com/g/edge-test-tool/c/is-hzu38f3k/m/jbeI4hKeBAAJ), as did Mat Davis, who documented the attempt a bit more thoroughly than I did (https://groups.google.com/g/edge-test-tool/c/gYLJ5yv62Kc/m/LqUfAvVQAQAJ).

These seem like they are a critical part of the reference implementation, so I would assume that they are intended to be available publicly, but they do not seem to be: can anybody say where/how to find them, or explain why we are wrong to think that they exist and can be found?

Thanks!

    --Ben Warfield

[Ben Warfield]

Happy New Year, everyone!

Given the possibility (however remote) of another government shutdown three weeks from now, this topic is of renewed interest—is anybody able to comment on where and how we might obtain the scenario files required to do on-site C-CDA scenario validation?

    --Ben Warfield

[nagesh.bashyam (Dragon)]

Currently the answer key files are not available publicly. You can still run the Reference Validator without the answer files.

[Ben Warfield]

Thank you for confirming that the files are not available—that was what I had suspected. Given that there is a very real chance that the ETT system will be shutting down again for an indefinite period on Sunday morning, I guess what I would like to know is if there is a reason why they *shouldn't* be available publicly, or if it's merely a process artifact (since I don't know what they look like, it's sort of hard for me to guess what that reason might be)—and if it's a process artifact, is there any way of making them available before everybody gets furloughed/stop-worked again?  We do, as you suggest, have a working instance of the validator that handles structural but not scenario-based validation, but having scenario-based validation be completely impossible during a lapse in appropriations is a bit of a strain on implementers.

    --Ben Warfield