Knowledge index
CMS-0057-F Index
The FHIR specifications and implementation guides CMS-0057-F requires healthcare plan providers to build against.
Works with
Claude Code, Codex, Claude, ChatGPT, Grok and any MCP client
Domain
Healthcare / Health IT
Size
1k websites
Coverage
FHIR R4 (v4.0.1), US Core STU 3.1.1, SMART App Launch, OpenID Connect Core 1.0, Da Vinci PAS, DTR and CRD (current STU releases).
Example questions
When a Da Vinci PAS server can't make an immediate prior authorization decision, what Bundle type and ClaimResponse outcome code does it return to the requesting system?
What FHIR extension does DTR use to mark a questionnaire item as auto-populated from the EHR rather than answered directly by the clinician?
What CDS Hooks hook does CRD define for a medication order, and what context fields does the request require?
Use cases
Check which FHIR resource or profile a CMS-0057-F requirement maps to before scoping the build.
Look up resource definitions, cardinalities and must-support elements across all seven guides without switching between separate specs.
Answer client questions about PAS, DTR and CRD workflows with a citation to the actual guide and section.
About this index
CMS-0057-F requires companies to stand up four FHIR-based APIs, Provider Access, Payer-to-Payer, Prior Authorization, and an updated Patient Access, by January 1, 2027. The rule points builders to a specific stack rather than leaving the technical approach open: the FHIR base specification, the US Core data profiles, the SMART App Launch authorization framework, OpenID Connect for identity, and three Da Vinci implementation guides covering prior authorization support (PAS), documentation requirements (DTR), and coverage discovery (CRD). Each of these is published separately by HL7 or the OpenID Foundation, so building against all of them means working across seven different sites with their own navigation and search. This Kapa index combines the resource definitions, profiles, workflows and examples from all seven into one searchable source, mirrored for agent search. All data belongs to HL7 and the OpenID Foundation.
Owner
HL7 FHIR, the Da Vinci Project, and the OpenID Foundation
Coverage
FHIR R4 (v4.0.1), US Core STU 3.1.1, SMART App Launch, OpenID Connect Core 1.0, Da Vinci PAS, DTR and CRD (current STU releases).
License and credit
Not an official HL7, CMS or OpenID Foundation product. Source content is openly licensed (CC0 for HL7 FHIR publications).
Caveats
This index holds the published specifications and implementation guides, not CMS's rule text or legal interpretation of it, and it is not compliance or legal advice. The guides are versioned and can be updated by HL7 ahead of the deadline, so confirm you are building against the current release before relying on an answer.
Add to your agent
Copy the setup prompt and paste into your agent.
Or add it manually
MCP URL
https://cms0057.mcp.kapa.ai
Claude Code
Codex
Claude
ChatGPT
Grok Bot
Other
claude mcp add --transport http
cms-0057-f
https://cms0057.mcp.kapa.ai
Then run /mcp and finish sign-in in the browser.
Example
With the MCP, Claude cites the actual records
Same question, same model (Opus 5.5, high effort). Left: Claude with web search. Right: Claude with this index.
Normal Claude
Web search
Wrong answer causing rework as "Pended" lives in the review action code (A4), not the outcome field.
With knowledge index
CMS-0057-F
MCP
Specific, accurate answer grounded in actual documentation, instead of a web search.
Frequently asked questions
What is a knowledge index?
−
A searchable index of a public data source, like NASA's aviation safety reports, that your agent can query over MCP.
How do I add one to my agent?
+
How is this different from web search?
+
Is it free?
+
Are these official connectors?
+
Can I create my own index?
+