Standards the code knows, and the ones it only names.

Knowing a standard’s name is not an implementation. This page separates the two. CDISC-shaped exports and ODM import and FHIR ingest are implementations with the limits written on their own pages. OMOP is a shape the real-world store resembles. It is not a certified OMOP conversion. DICOM is the file type for imaging ingest, not a certified de-identification.

What this covers

CDASH, SDTM, ADaM, Define-XML

Shaped outputs from a freeze. Not CORE-validated.

ODM

Form import.

FHIR

Bundle ingest with a hashed identifier.

OMOP

Tables for person, visit, condition, drug and measurement. Not a certified ETL.

DICOM

Upload and a documented de-identification profile. Not a PS3.15 certificate.

Terminology

Files a licensee loads. Not bundled.

How a team uses it

Pick the standard

Say which version.

Use what is built

Do not describe the rest as available.

Validate outside

A standards tool, if you require one, is separate.

Keep the version

The export names the specification hash.

Related reading

Questions

Is Define-XML schema-validated?

No.

Is OMOP a network?

No. One deployment only.

Available with limitations means the described software behavior exists. A professional service is work a person does under a separate scope. Nothing here is a certification.

See the workflow on your protocol.

The conversation is about your study design and what the software can and cannot do today.