search

microsoft / fhir-server

A service that implements the FHIR standard
MIT License
1.17k stars 499 forks source link

Add support for updated member-match operation #2490

Open CaitlinV39 opened 2 years ago

CaitlinV39 commented 2 years ago

User story As a user, I want to be able to use the $member-match operations in FHIR as defined in the updated HRex implemenation: https://build.fhir.org/ig/HL7/davinci-ehrx/OperationDefinition-member-match.html

Acceptance criteria I can use the $member-match with consent

sayansamanta2022 commented 2 years ago

We would like to ask a different question. Our understanding now is that per Da Vinci Member Match , UMB should be returned. The UMB can then be used to make subsequent retrievals **"After a successful $member-match the new health plan will use the unique member identifier provided by the Old Health Plan in the Patient.identifier field to query for any subsequent transactions related to payer-to-payer exchange.

For example, in PDex the new health plan will subsequently use the UMB identifier to request the member’s health records. This can be done by querying the US Core FHIR profile endpoints which will be constrained to the identified member. Alternatively, the new health plan can perform a $everything operation to the Patient/{ID}/$everything operation endpoint to receive a bundle of the member’s health records."**

Our ask of Microsoft: Please provide an ETA when UMB will be available in Member Match

CraigP68 commented 2 years ago

AB#89148