Short answer: OpenCDISC for ADaM is applicable for ADSL and BDS data.
Long answer:
the OpenCDISC configurations are compliant with the
ADaM 2.1 Standard
ADaM 1.0 IG
ADaM v1.1 validation checks
This means they only validate ADSL and BDS data. To determine whether an arbitrary sas .xpt file is an ADSL is easy. The file must be named ADSL. To determine if it’s a BDS, the file must have at least one of the variables defined in the prototype element of the OpenCDISC config: PARAMCD,PARAM,AVAL,AVALC,ADT,ASTDT,ASTDTM
Can you give us an update on the logic used by Pinnacle21 for identifying the various dataset types? For BDS it indicates only one of the variables needs to be present, but does it check if it has at least PARAMCD/PARAM and AVAL/AVALC, and one of the date fields? How about ADMH? What are the minimum requirements to check ADMH as an OCCDS dataset? Any other updates for ADTTE, and ADAM OTHER? When will you be renaming ADAM OTHER to OCCDS?