Pin the suite and boundary
We record the endpoint class, FHIR version, implementation-guide claim, official test-kit version, selected groups, prerequisites and access route.
Methodology
A result is only useful when its boundary is reproducible.
FHIR Pilot records the version, profile claim, access route, checks, evidence and limitations before turning a run into a hand-off decision.
Decision rules
Scope first. Evidence second. Interpretation last.
Execute the confirmed scope
The complete agreed suite runs against an authorised non-production environment. When external credentials are not approved, execution stays with the customer and sanitised outputs enter the review.
Preserve useful evidence
Each finding records the check, observed signal, impact and next action. Sensitive resource identifiers and payload bodies are excluded from the stakeholder report.
Separate result states
Passed, blocker, skipped, unsupported and not executed have different meanings. A limited or missing check is never folded into a pass score.
State limitations
The report names what the selected suite cannot establish, including security posture, certification, clinical safety, regulatory compliance and behaviour outside the recorded environment.
Rerun against the same scope
When a rerun is included, the same test-kit version and recorded boundary are used unless both parties approve a scope change.
Status semantics
What every status does—and does not—mean.
StatusMeaningBoundary
PassedThe recorded evidence met this specific check at the recorded time.Does not prove overall interoperability, security or certification.
BlockerEvidence failed a check required by the selected hand-off scope.The recommended action must be assessed by the customer team.
UnsupportedThe requested claim could not be established by this checker or evidence route.Not silently converted into a pass or omitted from the report.
Not executedThe check was excluded, unsafe, unauthorised or unavailable.The reason stays visible in the scope and limitations.
Delivery capability
Complete where the suite is confirmed.
- Version-pinned official US Core Inferno suites
- Version-pinned official SMART App Launch Inferno suites
- Baseline FHIR metadata, declarations and discovery diagnostics
- Connected non-production or customer-controlled zero-access execution
- Full result inventory with evidence, skipped tests and remediation priorities
Public sample boundary
A complete recorded group, with explicit limits.
- The primary sample contains all 453 results from the official US Core FHIR API group
- It records US Core Server 6.1.0 and US Core Test Kit 1.1.5
- It ran against Inferno’s public synthetic reference server, not a customer system
- Optional SMART, EHR launch, granular-scope and certification workflows were not part of that run
- No report is certification, a penetration test or regulatory approval
Inspect the evidence
Read the complete public reference report.
The JSON, Markdown and PDF outputs show every check, limitation and source used for the sample.