RPLOBXFL is Expected in v4.0 but is not declared in this RP dataset

Rule

CORE-002

Category

Variables changed

Basis

Draft Read from the public-review draft. The draft can still change before v4.0 is final, and this rule changes with it.

Detectability

Define-XML conclusive The Define-XML settles this one way or the other. No further evidence is needed to know whether it applies.

Finding type

Impact

Applies to

SDTMIG 3.2, 3.3, 3.4

What changes in v4.0

In v4.0 the core designation of RPLOBXFL (Last Observation Before Exposure Flag) in Reproductive System Findings moves from Permissible to Expected, so Section 4.2.4 requires the column to be present even where the study has no such observation. This RP dataset does not declare it. RPLOBXFL records a timing fact — the last observation before exposure — and is not an analysis baseline flag: Section 4.8 states that "the SDTM variable --LOBXFL can be copied to ADaM for traceability and transparency, but only the ADaM variable ABLFL would be used to signify baseline for analysis", and that the two carry the same content only "when the SAP specifies that the baseline used for analysis is the last non-missing value prior to RFXSTDTC in the DM domain". The core change is visible in the specification tables; Appendix E marks the whole RP section "Unchanged", so CDISC has not narrated it, which is why this rule is `draft`.

What to do about it

Derive and populate RPLOBXFL from exposure timing, which requires EX or EC and agreement on which reference start applies, and retire RPBLFL in the same pass (VAR-001). Two things make this more than a metadata edit: the derivation needs the exposure reference settled, and where ADaM copies --LOBXFL across for traceability the result has to be reconciled against the SAP's own baseline definition rather than assumed to match it. Get the statistician to confirm that reconciliation. This rule, VAR-001 and VAR-002 are one baseline-transition workstream, turning on the same reference start and the same baseline definition, so do this alongside the rest of the baseline work rather than as a separate exercise.

What the scan can and cannot see

An RP dataset is declared and RPLOBXFL is not, which under Section 4.2.4 is the finding. What the derivation costs - exposure reference, SAP reconciliation - is remediation, not detection.