Open wreiske opened 5 years ago
@wreiske We're using the former (native JavaScript) package that this schematron-runner was based on (called cda-schematron here: https://www.npmjs.com/package/cda-schematron
I didn't check everything, but I did validate that the administrativeGenderCodeBAD issue is picked up with that package. May want to try that one out.
Hey Tim,
I've been working on a Browserify version of schematron-runner (to run validation 100% in a browser). It seems to be running with a few minor issues (line numbers and xml didn't show up). I fixed the xml output to show, but I haven't tried getting the line numbers working. Made some modifications to allow for using a file object in the browser instead of relying on fs.
I'm running into some issues with CCDA validation. I know this project wasn't designed for it, but I'm hoping there may be some easy code changes to add support for it. Here are the problems I'm currently running into (when ran from the command line, NodeJS on OSX):
Example: The following test checks to see if an element contains a templateId and a root of "2.16.840.1.113883.10.20.22.4.24". CCDA.sch
When schematron-runner is executed on the following xml, it shows in the "passed" object. xdrtest1.xml
Changing it to the following removes it from the "passed" object, but it does not add it to the "errors" object.
Also, there is a test in the SCR that looks like this:
When renaming all of the "administrativeGenderCode" elements in the XML to "administrativeGenderCodeBAD", schematron-runner doesn't show them as errors.
I've attached both the SCR and the XML we are testing with. Maybe I am doing something wrong?
ccda-test.zip
Thanks, Will