01
Where it fits and where it does not
Use these four checks before committing implementation time.
- Use it when
- Computable clinical concepts that connect protocol, collection design, tabulation metadata, and downstream automation.
- Limits
- Content is informative and incrementally curated; concept, specialization, terminology, and downstream standard versions must be pinned together.
- Best for
- Clinical teams working across Plan → Acquire → Harmonize.
- Maturity
- ScalingUsable now, but adoption or tooling is still developing. Pilot the exact stack first.
02
See it in the workflow
This view shows the input, the change the standard introduces, and the resulting output.
- InputWhat starts
Clinical source data, metadata, and local mappings
- CDISC BCsWhat changes
Use CDISC BCs as a pinned data model / schema across Plan → Acquire → Harmonize
- OutputWhat becomes possible
A handoff the next system or team can validate against the same release
03
A concrete example
A study standards team selects a versioned Biomedical Concept, binds its terminology, and reuses its SDTM Dataset Specialization in metadata-driven study build.
Why it matters: Makes clinical concepts and variable relationships more computable, but does not validate source data, labels, or model fitness.
04
What it fits with
Complements CDISC Foundational Standards and terminology; can support CRF, Define-XML, SDTM specialization, and cross-standard mappings.
- StandardCDISC
Both support Clinical work and meet around Plan, Acquire, Harmonize. Compare their roles before treating them as interchangeable.
Explore relationship - Metadata vocabularyDPV
Both support Clinical work and meet around Plan, Acquire, Harmonize. Compare their roles before treating them as interchangeable.
Explore relationship - Governance frameworkICH E6(R3)
Both support Clinical work and meet around Plan, Acquire, Harmonize. Compare their roles before treating them as interchangeable.
Explore relationship - Governance frameworkICH M14
Both support Clinical work and meet around Plan, Acquire, Harmonize. Compare their roles before treating them as interchangeable.
Explore relationship
05
Implementation starter
Start with one bounded handoff. Pin, test, and review it before scaling.
Define one handoff, its accountable owner, and the decision CDISC BCs must support.
Pin the exact version and companion artifacts: COSMoS semantic layer · current library releases.
Map one representative input to the required data model / schema artifacts.
Test the result against the canonical source and record every exception.
Preserve the source data, mappings, and review evidence before scaling.
06
Test the main limitation
Content is informative and incrementally curated; concept, specialization, terminology, and downstream standard versions must be pinned together.
Run one representative end-to-end pilot and record exactly where CDISC BCs loses context, needs an extension, or depends on another standard.
Machine-readable output may still be unfit for analysis or ML.
Test the output for missing context, provenance, terminology alignment, time leakage, and the intended downstream decision. Makes clinical concepts and variable relationships more computable, but does not validate source data, labels, or model fitness.
07
Official resources
Specifications, diagrams, examples, and guides from the organizations that maintain them.
CDISC Biomedical Concepts
Official publisher or steward guidance for this data model / schema profile.
- Publisher
- CDISC