Invoke the DEQM $care-gaps operation to identify open gaps in care for a patient or population
domain: hl7.org · 5 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
POST /Measure/$care-gaps (or /Measure/{id}/$care-gaps) with parameters: periodStart, periodEnd, status (open-gap or closed-gap or prospective-gap), subject (Patient or Group reference), and optionally measure canonical URLs
Receive a Bundle of type 'document' containing a GuidanceResponse and one or more IndividualMeasureReport or GapsInCareDetectedIssue resources per measure
Parse the DetectedIssue resources to identify which measures have open gaps and review the evidence references pointing to missing or insufficient clinical data
Use gap information to drive care management outreach workflows, care coordination tasks, or supplemental data requests via CDex
Re-invoke $care-gaps after new data is submitted to confirm gap closure before the reporting deadline
Known gotchas
$care-gaps is defined in the DEQM IG and not universally implemented; verify the server CapabilityStatement includes the gaps-in-care operation before calling
The status parameter values (open-gap, closed-gap, prospective-gap) are specific to the DEQM IG and differ from general FHIR operation conventions; using wrong values returns no results rather than an error on some servers
For population-level calls with a Group subject, the operation can be computationally expensive; some servers impose a maximum Group size or require an async pattern with Prefer: respond-async
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?