ADaM Validation > System > Warning > Configuration Unavailable message

MISSING_CONFIG: Configuration Unavailable (System/Warning/)

You could get this for a couple reasons.    Either AD0061 couldn't execute because you didn't submit exposure domain with your data.

AD0061: SDTM.EX is present and neither ADSL TRTSDT nor TRTSDTM are present (Presence/Error/null)

Or you submitted a NON BDS file.  Basically a file that does not have at least one of these variables

PARAMCD,PARAM,AVAL,AVALC,ADT,ASTDT,ASTDTM 

Let me know which scenario it was.  

Thanks.

Mike DiGiantomasso

OpenCDISC community developer

Hello Mike. I got the same

Hello Mike.

I got the same "MISSING_CONFIG" note when i provided both DM & EX data sets while validating ADaM V1.0 datasets.

Regarding your second comment, do you mean that OpenCDISC for ADaM is only applicable for BDS data?

Thanks,

Nalin

ADaM BDS and ADSL

Short answer:  OpenCDISC for ADaM is applicable for ADSL and BDS data.

Long answer:

the OpenCDISC configurations are compliant with the

1. ADaM 2.1 Standard
2. ADaM 1.0 IG
3. ADaM v1.1 validation checks

---ORRES in character format

Hi,

May I know if it's allowed in AdAM to derive AVAL from character ---ORRES data and use AVALC to keep original ---ORRES data?

Thank you,

Hi! Why not? Until you still

Hi!

Why not? Until you still have one-to-one relationship between AVAL and AVALC.

Identifying ADAM BDS v. ADSL v. OCCDS or ADAM Other

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?