We would like to create a script similar to https://github.com/cdisc-org/cdisc-rules-engine/blob/main/.github/workflows/validate-published-rules.yml
Instead of running against the CDISC engine, it should run against the Verisian Engine.
- It should compare the Verisian "actual" results against cdisc-open-rules "expected" results.
- It should only run tests for rules that contain any of the two standards:
Authorities:
- Organization: CDISC
Standards:
- Name: SDTMIG
- Organization: FDA
Standards:
- Name: SDTMIG
- Because the Verisian engine might require Excel instead of CSV files, we may need to include a preprocessing step that converts CSV/.env-format data to the old Excel-format data.
- We will probably need a postprocessing step that converts from the Verisian output format to the cdisc-open-rules results.csv format.
With the comparison, we will review the differences and resolve any basic fallouts. For the remaining issues, we will summarize and provide leadership with an explanation to make a decision.
We would like to create a script similar to https://github.com/cdisc-org/cdisc-rules-engine/blob/main/.github/workflows/validate-published-rules.yml
Instead of running against the CDISC engine, it should run against the Verisian Engine.
With the comparison, we will review the differences and resolve any basic fallouts. For the remaining issues, we will summarize and provide leadership with an explanation to make a decision.