ePA APIs documentation — pillar vs reference split#2
Merged
Conversation
- Split Prior Auth pages (CRD, DTR, PAS) into thin conceptual pillars
and per-operation reference pages under api-reference/operations/
- Add 9 op-pages: questionnaire-package, claim-{submit,inquire},
submit-attachment, cds-services-discovery, cds-hook-{order-sign,
order-select,order-dispatch,appointment-book}
- Consolidate SMART Backend Services onboarding into authentication.md
- Pin IG versions: CRD STU 2.0.1, DTR STU 2.0.0, PAS STU 2.1.0
- Normalize op-page H1 to plain text (no backticks); apply uniformly
across new ePA pages and 3 existing PDex op pages
- Document Page types: Pillar vs Reference rule in CLAUDE.md
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Nesmeshnoy
force-pushed
the
epa-apis-review
branch
from
778e483 to
a33864a
Compare
glebmark
reviewed
May 13, 2026
| POST <base>/fhir/$provider-member-match | ||
| Authorization: Bearer <access-token> | ||
| Content-Type: application/fhir+json | ||
| Accept: application/fhir+json |
glebmark
reviewed
May 13, 2026
| POST <base>/fhir/$bulk-member-match | ||
| Authorization: Bearer <access-token> | ||
| Content-Type: application/fhir+json | ||
| Prefer: respond-async # optional; sync is the default |
There was a problem hiding this comment.
It's not optional, in current implementation request will fail without this header
glebmark
reviewed
May 13, 2026
|
|
||
| Submit one Parameters payload per member. For bulk matching across many members at once, use [`$bulk-member-match`](bulk-member-match.md) (that's Payer-to-Payer, not Provider Access). | ||
|
|
||
| ## Response |
There was a problem hiding this comment.
If we make true API reference then we should describe all operations and their response: POST <base>/fhir/$provider-member-match doesn't return Groups, it return id of Task. Then user should make another request and see whether Task is completed. And then they make third request where they'll see output.
Rost-is-love
approved these changes
May 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Refactors Prior Auth (ePA) APIs documentation into pillar (concept) and reference (per-operation) pages, per a new
Page types: Pillar vs Referencerule documented inCLAUDE.md.docs/api-reference/operations/covering DTR, PAS, and CRD CDS Hooksdocs/api-reference/authentication.md(was duplicated across CRD and PAS pillars)Page structure
docs/prior-auth/*): overview, lifecycle, decision-service framing, short JSON example, cross-links. No full parameter tables or per-operation reference content.docs/api-reference/operations/*): full Input/Output parameters, all Request/Response variants (JSON), error tables, current limitations.Verified against source
Cross-checked CDS Hooks endpoints and PAS operations against the
HealthSamurai/prior-authmanifest (services/core/src/app_manifest.clj):order-sign,order-select,order-dispatch,appointment-book) are implemented + Discovery (GET /cds-services)Claim/$submit,Claim/$inquire,$submit-attachment) — endpoints match docs$submit-attachmentis system-level (path["$submit-attachment"], not under/fhir/)Needs reviewer input
$submit-attachment— current educated guess:system/DocumentReference.c+system/Claim.u. App manifest specifies the operation but not scope policies — please confirm against Access Policies / Client config.api-reference/implementation-guides.md; please confirm these are the versions actually deployed.Test plan
🤖 Generated with Claude Code