SDTM allows FA to be broken into FAxx datasets, just as SUPP can be broken into SUPPxx datasets. OpenCDISC will process SUPPxx datasets but not FAxx datasets. I can work around this by combining all my FAxx datasets into a single FA for the purposes of OpenCDISC checking, but that's a bit of a pain. Can the tool be enhanced to process both FA and FAxx datasets?
This was a known issue for 1.2.1. Good news is that we plan to release OpenCDISC Validator 1.3 middle of this month. This release will also have the following bundled with it..
ADaM 1.1 validation checks including community user feedback
SEND 3.0 validation checks
SDTM 3.1.2 Amendment 1
BTW, i sent a bunch of findings for the current ADaM 1.1/1.2 checks that may interest you.
Pinnacle 21 uses cookies to make our site easier for you to use. By continuing to use this website, you agree to our use of cookies. For more info visit our Privacy Policy.
SDTM allows FA to be broken into FAxx datasets, just as SUPP can be broken into SUPPxx datasets. OpenCDISC will process SUPPxx datasets but not FAxx datasets. I can work around this by combining all my FAxx datasets into a single FA for the purposes of OpenCDISC checking, but that's a bit of a pain. Can the tool be enhanced to process both FA and FAxx datasets?