Da Vinci PDex Plan-Net provider directory FHIR queries

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

  1. Target a Plan-Net conformant FHIR R4 server; the IG (hl7.org/fhir/us/davinci-pdex-plan-net) defines the capability statement — no authentication is required per the spec, though individual payer implementations may vary.
  2. Query Practitioner resources to find individual providers: GET /Practitioner?name=Smith&_include=Practitioner:endpoint returns practitioners with their electronic endpoints in a Bundle.
  3. Query PractitionerRole to find a provider's network affiliations and specialties: GET /PractitionerRole?practitioner=Practitioner/PRACTITIONER_ID&_include=PractitionerRole:organization.
  4. Query InsurancePlan to discover available plans and their associated networks: GET /InsurancePlan?_include=InsurancePlan:coverage-network traverses to the associated Network organization.
  5. Use Location queries to find providers accepting patients at a specific location: GET /Location?near=LATITUDE|LONGITUDE|RADIUS|mi&_include=Location:organization.
  6. Handle Bundle pagination using the next link in the Bundle.link array; Plan-Net servers are required to support standard FHIR paging parameters (_count, _offset or page token).

Known gotchas

Related routes

Query the Da Vinci Plan-Net provider directory for PractitionerRole and Network resources
hl7.org/fhir/us/davinci-pdex-plan-net · 6 steps · unrated
Query a Da Vinci PDex Plan-Net provider directory for Practitioner, Organization, and HealthcareService resources
hl7.org · 6 steps · unrated
Publish or query a health plan's provider network directory using the HL7 Da Vinci PDex Plan-Net FHIR API
hl7.org · 6 steps · unrated

Give your agent this knowledge — and 15,500+ 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?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans