Contains one or more members with patient demographics and coverage information to be matched against the payer's member records. Each repetition SHALL conform to the MemberBundle slice defined in the Provider $multi-member-match Request profile.

A Group resource containing members successfully matched in the payer's records, for whom the provider's treatment attestation has been verified, and who have not opted out of Provider Access API data sharing. The Group Id returned in this parameter is the input to the $davinci-data-export operation for bulk data retrieval. This Group is the response artifact and is distinct from the long-lived Member-Provider Treatment Relationship Group (pdex-treatment-relationship) the payer maintains for governance and audit purposes. Cardinality 1..1 — emitted even when Group.member[] is empty, so the matched-Group identifier is always available for the subsequent $davinci-data-export step.

A Group resource containing members for whom no match could be found in the payer's records OR for whom the provider's treatment attestation could not be verified or does not meet the payer's requirements. Both failure types are reported in this single Group; consumers can distinguish the specific reason via the Group's characteristic code or the per-member context if required by the payer.

A Group resource containing members who were successfully matched in the payer's records but who have opted out of data sharing via the Provider Access API. Returned via the Member Opt-Out Group profile. Privacy default — SHOULD suppress when opt-out status is sensitive. A member who opts out of data sharing has, by definition, indicated that they do not want their data disclosed to the requesting provider via this API; the fact of opting out is itself information about that member. Where the payer determines that disclosing opt-out status to the requesting provider — i.e., distinguishing 'opted out' from 'not matched' — would itself constitute a disclosure the member did not authorize (whether under applicable state privacy law, the member's stated preference, or the payer's privacy policy), the payer SHOULD suppress this ConsentConstrainedMembers parameter and instead include the affected members in the NonMatchedMembers Group. This makes the response indistinguishable to the requester between a true no-match and a matched-but-opted-out outcome, protecting opt-out status from disclosure. Payers that determine no such concern applies (for example, in jurisdictions where opt-out disclosure is permitted, or where the member has not requested suppression) MAY continue to return this Group, which preserves the type-level distinction between opt-out and no-match outcomes for operational use by the requester.