Decision support

Compare standards by the job they do

Place up to three profiles side by side. Focus on architectural role, evidence, and the first limitation to test—not on finding a single all-purpose standard.

Working set

Choose profiles

1 of 3 selected

Vulcan RWD IGMetadata profile

Add a profile

Decision lens

Compare roles before you compare maturity.

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

Start with the job
Decide whether you need guidance, a domain payload, exchange, semantics, governance, or a reusable release.
Map lifecycle reach
Use the matrix to see where each profile has a direct role. A filled cell is coverage, not a quality score.
Test the boundary
Read what each option leaves unresolved before judging maturity, confidence, or implementation fit.

Three-part assessment

See the reach, the gaps, and the evidence.

Read left to right. Lifecycle reach comes first; maturity remains an editorial roll-up, not certification.

01 · Lifecycle reach

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 HL7 Vulcan Retrieval of Real World Data for Clinical Research
Profile	Plan	Acquire	Harmonize	Exchange	Learn + reuse
Vulcan RWD IGMetadata profile	HL7 Vulcan Retrieval of Real World Data for Clinical Research has no direct role recorded in Plan.	HL7 Vulcan Retrieval of Real World Data for Clinical Research has a direct role in Acquire.	HL7 Vulcan Retrieval of Real World Data for Clinical Research has no direct role recorded in Harmonize.	HL7 Vulcan Retrieval of Real World Data for Clinical Research has a direct role in Exchange.	HL7 Vulcan Retrieval of Real World Data for Clinical Research has no direct role recorded in Learn + reuse.

Direct role recordedNo direct role recorded

02 · Boundaries

What each option does not cover

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

Vulcan RWD IG

Stage boundary: No direct role is recorded for Plan, Harmonize, Learn + reuse.
Known limitation: STU1 is limited to retrospective EHR RWD; prospective eSource, registries, payer data, downstream transformation, and analysis readiness are outside current scope.

03 · Detailed assessment

Check the fit and evidence behind the map

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

Detailed comparison of HL7 Vulcan Retrieval of Real World Data for Clinical Research
Assessment	Vulcan RWD IGHL7 Vulcan Retrieval of Real World Data for Clinical Research
Purpose & coverage	FHIR profiles and queries for finding cohorts and retrieving a minimal EHR-derived dataset for retrospective clinical research and potential regulatory use. Best fitResearch applications retrieving RWD from FHIR-capable EHRs through a named, testable research profile rather than unconstrained base resources.
Readiness stages	AcquireExchange
AI-ready contribution	A constrained retrieval contract improves reproducibility, but FHIR output still needs terminology normalization, longitudinal modeling, quality evidence, and bias assessment.
First limitation to test	STU1 is limited to retrospective EHR RWD; prospective eSource, registries, payer data, downstream transformation, and analysis readiness are outside current scope.
Evidence	E1 + E3 Medium confidence Formal statusCurrent published STU1 based on FHIR R4 ReviewSource-checked · watch
Maturity	Scaling Current published STU1 with deliberately iterative use-case coverage
Sources & links	HL7 Vulcan RWD IG 1.0.0 (opens in a new tab)Read full profile