01
Where it fits—and where it doesn’t
Use these four checks before committing implementation time.
- Use it when
- Research applications retrieving RWD from FHIR-capable EHRs through a named, testable research profile rather than unconstrained base resources.
- Do not use it as
- Do not treat Vulcan RWD IG as a complete solution on its own. STU1 is limited to retrospective EHR RWD; prospective eSource, registries, payer data, downstream transformation, and analysis readiness are outside current scope.
- Best for
- Teams working with Clinical and Real-world evidence and Regulatory data across Acquire → Exchange.
- Maturity
- ScalingUsable today, with adoption or tooling still scaling; pilot the exact stack you plan to run.
02
See it in the workflow
A standard creates value by changing a handoff, not by existing in a catalog.
- InputWhat starts
Clinical and Real-world evidence and Regulatory data, metadata, and the local decisions around them
- Vulcan RWD IGWhat changes
Vulcan RWD IG applies a shared metadata profile across Acquire → Exchange
- OutputWhat becomes possible
A more consistent, reviewable handoff for the next system or team
03
A concrete example
A research service applies the guide’s cohort searches and must-support elements to retrieve versioned condition, medication, observation, and encounter data from an EHR.
Why it matters: A constrained retrieval contract improves reproducibility, but FHIR output still needs terminology normalization, longitudinal modeling, quality evidence, and bias assessment.
04
What it fits with
Builds on International Patient Access and can combine with jurisdictional core guides; downstream CDISC or OMOP conversion is handled by separate mappings.
- StandardFHIR®
Both support Clinical and Real-world evidence work and meet around Acquire, Exchange. Compare their roles before treating them as interchangeable.
Explore relationship - StandardCDISC ODM
Both support Clinical and Regulatory work and meet around Acquire, Exchange. Compare their roles before treating them as interchangeable.
Explore relationship - TerminologyLOINC
Both support Clinical and Real-world evidence work and meet around Acquire, Exchange. Compare their roles before treating them as interchangeable.
Explore relationship - TerminologySNOMED CT
Both support Clinical and Real-world evidence work and meet around Acquire, Exchange. 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.
Name an accountable owner and the decision Vulcan RWD IG must support.
Pin the exact version and companion artifacts: 1.0.0 · STU1 · FHIR R4 · active 2023-05-26.
Map one representative input to the required metadata profile artifacts.
Test the result against the canonical source and record every exception.
Preserve the source data, mappings, and review evidence before scaling.
06
Limitation to test first—and the tests that catch it
STU1 is limited to retrospective EHR RWD; prospective eSource, registries, payer data, downstream transformation, and analysis readiness are outside current scope.
Run one representative end-to-end pilot and record exactly where Vulcan RWD IG loses context, needs an extension, or depends on another standard.
A structured or machine-readable result can still be unfit for analysis or AI.
Test the output for missing context, provenance, terminology alignment, time leakage, and the intended downstream decision. A constrained retrieval contract improves reproducibility, but FHIR output still needs terminology normalization, longitudinal modeling, quality evidence, and bias assessment.
07
Why we believe this
Checked against the canonical source plus implementation or adoption evidence reported by the steward or its community.
Evidence notation: E1 + E3. The code is shorthand; the plain-language statement above is the claim.
08
Source shelf
Official diagrams, examples, specifications, and explainers. Nothing external loads until you choose to open it.
HL7 Vulcan RWD IG 1.0.0
The canonical publisher or steward source used to verify this metadata profile profile.
- Publisher
- HL7 Biomedical Research & Regulation Work Group · Vulcan
- Rights
- Rights remain with the publisher; this knowledge base links to the source rather than copying it.
- Access
- Opens the publisher's source in a new tab; no external media loads on this page.
- Verified
- 2026-07-13