Assert a US Core 7.0.0 CapabilityStatement from a FHIR server and verify it declares all required US Core 7.0.0 profiles and search parameters
domain: hl7.org · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
In-depth guide
FHIR Bulk Data $export gotchas — the full failure-mode walkthrough related to hl7.org, checked against official docs, with linked verified routes.
Steps
GET /metadata (or /CapabilityStatement) from the FHIR server to retrieve the server CapabilityStatement
Inspect CapabilityStatement.rest[].resource[] entries to confirm each US Core 7.0.0 required resource type is listed with at least the required interaction types (read, search-type)
For each resource entry, check the supportedProfile[] array for the canonical URLs of the US Core 7.0.0 profiles that the server claims to support
Verify searchParam entries within each resource to confirm required US Core search parameters (e.g., patient, category, code, date for Observation) are listed with correct types
Check for new US Core 7.0.0 profiles not present in earlier versions (e.g., Screening and Assessment Observation, Average Blood Pressure) in the supportedProfile list
Programmatically compare the extracted profile and search parameter list against the US Core 7.0.0 conformance requirements matrix to identify gaps
Known gotchas
A server may declare a US Core profile in supportedProfile without actually enforcing must-support elements on write or returning complete data on read; CapabilityStatement claims are attestations, not guarantees — test with real resources
US Core 7.0.0 changed the must-support definition to include explicit obligations (SHALL populate, SHOULD populate) that are more precise than prior versions; servers implementing earlier US Core versions will not reflect these in their CapabilityStatement
Some servers auto-generate CapabilityStatements from framework configuration and may not include all supportedProfile entries even when the profiles are implemented; cross-verify with the server's developer documentation
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?