updates for API Reference / $bulk-member-match page#3
Merged
Conversation
The 30-day validity window, hourly sweep, and 90-day hard-delete were never implemented. Replace with reality-aligned note: Groups remain active indefinitely until cancellation, which sweeps Task.output.
Admin sessions (Aidbox Console, no client NPI) derive the requesting payer from Coverage.payor[0]. Extend Auth section and adjust 403/422 error rows accordingly.
Payer-Org lookup rejects ambiguity (more than one Organization registered against the requesting payer's NPI) with 409 Conflict.
A later run landing the same (patient, payer) in ConsentConstrainedMembers flips the prior persisted Consent to status=inactive so $davinci-data-export?exportType=payertopayer does not honor stale rows.
The active provider-access deny-Consent test is structurally a fifth consent check. Move it from a separate paragraph into the consent-check table and keep a one-line note on the underlying Aidbox query.
A hard-deleted Task returns Aidbox 410 Gone on read; the operation maps that to 404 so clients stop polling/cancelling without retrying. Update both status-polling and cancel response tables.
Identifier-AND is bulk-only. $provider-member-match ignores submitted Patient.identifier entries to tolerate provider-side MRNs the payer does not store. Add a one-clause contrast in Demographic match.
Consent.organization is a 0..* array; the rewrite step today writes exactly one element.
…ncel rows The 410 Gone code is internal to the storage backend; integrators only see 404. Reword to "hard-deleted" so the table conveys the integrator-facing contract without exposing implementation plumbing.
…th + add 409 example - Opt-out search line said decision=deny; code uses provision-type=deny (R4 Consent.provision.type). Aligned with $provider-member-match doc. - Auth admin-session paragraph: spelled out the actual flow (Coverage.payor[0].reference must be Organization/<id>; Org is read; us-npi identifier becomes payer NPI) and the admin-client-ids allowlist gate. - Added a 409 response tab so integrators see the OperationOutcome shape for the new duplicate-NPI error.
Drop the internal :admin-client-ids / INTEROP_ADMIN_CLIENT_IDS detail — it is a deploy/ops knob, not integrator-facing — and shrink the explanation of how Coverage.payor[0] resolves.
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
1 participant
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.
No description provided.