Da Vinci Payer Data Exchange, published by HL7 International / Financial Management. This guide is not an authorized publication; it is the continuous build for version 2.1.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/davinci-epdx/ and changes regularly. See the Directory of published versions
Official URL: http://hl7.org/fhir/us/davinci-pdex/OperationDefinition/bulk-member-match | Version: 2.1.1 | |||
Standards status: Trial-use | Computable Name: BulkMemberMatch | |||
Copyright/Legal: Used by permission of HL7 International, all rights reserved Creative Commons License |
The $bulk-member-match operation that can be invoked by either a payer or an EHR or other system, allows one health plan to retrieve a unique identifier for a group resource containing matched members from another health plan using a member's demographic, coverage information with an accompanying consent record. This identifier can then be used to perform subsequent queries and operations. Health Plans implementing a deterministic match will require a match on member id or subscriber id at a minimum (i.e. A pure demographic match will not be supported by such implementations.).
Generated Narrative: OperationDefinition bulk-member-match
URL: [base]/Group/$bulk-member-match
Input parameters Profile:PDex $multi-member-match request
Output parameters Profile:PDex $multi-member-match response
Use | Name | Scope | Cardinality | Type | Binding | Documentation |
IN | MatchRequest | 1..1 | Reference (PDex $multi-member-match request) | Bundle of Member information. Repeat bundle for each member to be submitted to bulk member-match, as defined in PDex $multi-member-match request. | ||
OUT | MatchResponse | 1..1 | Reference (PDex $multi-member-match response) | Bundle of Groups returned from Member Match Operation. There can be up to three (3) groups: Matched, Not-Matched and ConsentConstrained. |