docs(prior-auth): UM forwarding / pas-passthrough + submit-attachment contract fixes#22
Merged
Merged
Conversation
…-passthrough connector
… parameter contract
akim1995
approved these changes
Jul 17, 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
2 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.
Two commits:
1. UM forwarding documentation (new section in the PAS pillar page)
Closes the gap flagged in QA of prior-auth#172:
UMTenantConfig, connector dispatch, and thepas-passthroughconnector were undocumented. Documents routing byClaim.insurer, the connector table, key config elements (auth via env-resolved secrets, timeouts, retry/backoff defaults verified againstum/config.clj), and the delegate contract forpas-passthrough(PAS 2.1.0$submit/$inquire, identifier pass-through, TRN dedup on retries, manual review for ambiguous failures).⚠ Merge after prior-auth#172 ships — this section describes the connector added there.
2.
$submit-attachmentreference page fixesPOST <base>/fhir/$submit-attachment(shipped in prior-auth#177; the legacy root path still answers but is deliberately left undocumented to keep the contract clean for new integrations).Final; the server enforces four (TrackingId, AttachTo, MemberId, Attachment).Finalis 0..1 with defaulttrue.LineItemattachment sub-parameter. Verified against the handler and its validation error.Local pre-push lint skipped (no bun in the session environment) — relying on the PR docs workflow.