Back to List
Module 50 Views

CDISC Conformance Validation Report — OBX319-301

July 12, 2026

📚 Part of the OBX-319 Regulatory Dossier — Reader's Guide. This article shows the live document; edits to the source appear here automatically.

🧪
Mock / simulation document

This is a mock / simulation document, made for a portfolio and for learning. The drug (GLPI-103), the sponsor, the people, and the data are all fictional. It is not a real regulatory submission and has no clinical, legal, or regulatory standing. What is real is the shape of the thing — the document structure, the standards it follows, and the analysis methods; the content inside is illustrative.

📄
About this document — a plain-language guide

What it is. CDISC Conformance Validation Report — OBX319-301

Why it exists. Clinical study documentation supporting the efficacy and safety of the program.

How it is produced here. The numbers come straight from the study's simulated Phase 3 dataset — they are calculated from the data, not typed in by hand. That is why you see the same figures repeated across the protocol, the analysis plan, the report, and the summaries: they all read from the same source.

Format & governing standard.


CDISC Conformance Validation Report — OBX319-301

Document ID: DEF-301-VAL Version: 1.0 Effective: 2026-07-09 Standard: CDISC SDTM-IG / ADaM-IG / Define-XML 2.1 (Pinnacle 21 rule subset)

Generated by tools/validate_cdisc.py — a documented subset of CDISC/Pinnacle 21 rules (required variables, controlled terminology, referential integrity, define↔data consistency). Not a substitute for an official Pinnacle 21 Community report (see SDRG §6).

Change History

VersionDateAuthorSummary
1.02026-07-09Data ManagementInitial automated subset validation

Summary — Errors: 0 · Warnings: 0 · Datasets checked: 9

No issues found across the implemented rule subset. ✅

Comments (0)

No comments yet. Be the first to say something!