Decision support

Compare standards by the job they do

Place up to three profiles side by side. Compare their architectural role, lifecycle reach, and first limitation to test. No single standard covers every layer.

Choose profiles

1 of 3 selected

TMF Reference ModelMetadata profile

Compare roles before choosing an implementation.

The useful question is not “Which standard wins?” It is “Which job must this part of the architecture perform, and what remains uncovered?”

  1. Start with the job

    Decide whether you need guidance, a domain payload, exchange, semantics, governance, or a reusable release.

  2. Map lifecycle reach

    Use the matrix to see where each profile has a direct role. A filled cell is coverage, not a quality score.

  3. Test the boundary

    Read what each option leaves unresolved before judging maturity or implementation fit.

Review lifecycle coverage and practical fit.

Read left to right. Lifecycle reach comes first; a maturity label never overrides a scope mismatch.

Where each profile contributes directly

Coverage shows a recorded role at that readiness stage. It does not imply end-to-end implementation.

Readiness-stage coverage for CDISC Trial Master File Reference Model
ProfilePlanAcquireHarmonizeExchangeLearn + reuse
TMF Reference ModelMetadata profileCDISC Trial Master File Reference Model has a direct role in Plan.CDISC Trial Master File Reference Model has a direct role in Acquire.CDISC Trial Master File Reference Model has a direct role in Harmonize.CDISC Trial Master File Reference Model has a direct role in Exchange.CDISC Trial Master File Reference Model has no direct role recorded in Learn + reuse.
Direct role recordedNo direct role recorded

What each option does not cover

These are design boundaries, not faults. Use them to identify the companion layers your architecture still needs.

TMF Reference Model

Stage boundary
No direct role is recorded for Learn + reuse.
Known limitation
CDISC describes the model as adaptable rather than a formal enforceable standard. Company SOPs, jurisdictional requirements, and the upcoming successor model can change artifact selection and filing rules.

Check the fit and source behind the map

Use the official source, version, and limitation together. A higher maturity label does not erase a scope mismatch.

Detailed comparison of CDISC Trial Master File Reference Model
AssessmentTMF Reference ModelCDISC Trial Master File Reference Model
Purpose & coverage

A standardized taxonomy, artifact identifiers, zones, sections, levels, metadata, and filing conventions for essential clinical-trial records in sponsor and investigator files.

Best fitTrial record management, sponsor-CRO transfer, completeness assessment, inspection readiness, and reconstruction of trial conduct across organizations and systems.

Readiness stages
PlanAcquireHarmonizeExchange
AI-ready contributionStandardized record metadata improves document retrieval, audit evidence, and agent workflows, but TMF completeness does not make clinical observations or endpoints analysis-ready.
First limitation to testCDISC describes the model as adaptable rather than a formal enforceable standard. Company SOPs, jurisdictional requirements, and the upcoming successor model can change artifact selection and filing rules.
Maturity

Established

Long-running industry reference model with an active transition to the renamed successor model

Sources & links