You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[$member-match](http://hl7.org/fhir/us/davinci-hrex/2020Sep/OperationDefinition-member-match.html) is an operation that is defined as part of the Da Vinci Health Record Exchange (HRex). In this guide, we'll walk through what $member-match is and how to use it.
17
+
[$member-match](http://hl7.org/fhir/us/davinci-hrex/2020Sep/OperationDefinition-member-match.html) is an operation that is defined as part of the Da Vinci Health Record Exchange (HRex). In this guide, we walk through what `$member-match` is and how to use it.
18
18
19
19
## Overview of $member-match
20
20
21
-
The $member-match operation was created to help with the payer-to-payer data exchange, by allowing a new payer to get a unique identifier for a patient from the patient’s previous payer. The $member-match operation
22
-
requires three pieces of information to be passed in the body of the request:
21
+
The `$member-match` operation was created to help with the payer-to-payer data exchange, by allowing a new payer to get a unique identifier for a patient from the patient’s previous payer. The `$member-match` operation requires three pieces of information to be passed in the body of the request:
23
22
24
23
* Patient demographics
25
24
26
25
* The old coverage information
27
26
28
27
* The new coverage information (not required based on our implementation)
29
28
30
-
After the data is passed in, the Azure API for FHIR validates that it can find a patient that exactly matches the demographics passed in with the old coverage information passed in. If a result is found, the response will be a bundle with the original patient data plus a new identifier added in from the old payer, and the old coverage information.
29
+
After the data is passed in, the Azure API for FHIR validates that it can find a patient that exactly matches the demographics passed in with the old coverage information passed in. If a result is found, the response is a bundle with the original patient data plus a new identifier added in from the old payer, and the old coverage information.
31
30
32
31
> [!NOTE]
33
-
> The specification describes passing in and back the new
34
-
coverage information. We've decided to omit that data to keep the results smaller.
32
+
> The specification describes passing the new coverage information in and back. We've decided to omit that data to keep the results smaller.
35
33
36
34
## Example of $member-match
37
35
38
-
To use $member-match, use the following call:
36
+
To use `$member-match`, use the following call.
39
37
40
38
`POST {{fhirurl}}/Patient/$member-match`
41
39
42
-
You'll need to include a parameters resource in the body that includes the patient, the old coverage, and the new coverage. To see a JSON representation, see [$member-match example request](http://hl7.org/fhir/us/davinci-hrex/2020Sep/Parameters-member-match-in.json.html).
40
+
You need to include a parameters resource in the body that includes the patient, the old coverage, and the new coverage. For a JSON representation, see [$member-match example request](http://hl7.org/fhir/us/davinci-hrex/2020Sep/Parameters-member-match-in.json.html).
43
41
44
-
If a single match is found, you'll receive a 200 response with another identifier added:
42
+
If a single match is found, you receive a 200 response with another identifier added.
If the $member-match can't find a unique match, you'll receive a 422 response with an error code.
46
+
If the `$member-match` can't find a unique match, you receive a 422 response with an error code.
49
47
50
48
## Next steps
51
49
52
-
In this guide, you've learned about the $member-match operation. Next, you can learn about testing the Da Vinci Payer Data Exchange IG in Touchstone, which requires the $member-match operation.
50
+
In this guide, you learned about the `$member-match` operation. Next, you can learn about testing the Da Vinci Payer Data Exchange IG in Touchstone, which requires the `$member-match` operation.
53
51
54
52
>[!div class="nextstepaction"]
55
53
>[DaVinci PDex](../fhir/davinci-pdex-tutorial.md)
56
54
57
-
FHIR® is a registered trademark of [HL7](https://hl7.org/fhir/) and is used with the permission of HL7.
In the previous tutorial, you deployed and set up your Azure API for FHIR. Now that you have your Azure API for FHIR setup, we’ll register a public client application. You can read through the full [register a public client app](register-public-azure-ad-client-app.md) how-to guide for more details or troubleshooting, but we’ve called out the major steps for this tutorial in this article.
17
+
In the previous tutorial, you deployed and set up your Azure API for FHIR®. Now that you have your Azure API for FHIR setup, we register a public client application. You can read through the full [register a public client app](register-public-azure-ad-client-app.md) how-to guide for more details or troubleshooting. We call out the major steps in this tutorial.
@@ -37,15 +37,15 @@ If you’ve [written your web app](tutorial-web-app-write-web-app.md) to connect
37
37
38
38
1. To add a new platform configuration, select **Web**.
39
39
40
-
1. Set up the redirect URI in preparation for when you create your web application in the fourth part of this tutorial. To do this, add `https://\<WEB-APP-NAME>.azurewebsites.net` to the redirect URI list. If you choose a different name during the step where you [write your web app](tutorial-web-app-write-web-app.md), you’ll need to come back and update this.
40
+
1. Set up the redirect URI in preparation for when you create your web application. To do this, add `https://\<WEB-APP-NAME>.azurewebsites.net` to the redirect URI list. If you choose a different name during the step where you [write your web app](tutorial-web-app-write-web-app.md), you’ll need to come back and update this.
41
41
42
42
1. Select the **Access Token** and **ID token** check boxes.
43
43
44
44
:::image type="content" source="media/tutorial-web-app/web-app-authentication.png" alt-text="Screenshot of the app Authentication settings blade, with the steps to add a platform highlighted.":::
45
45
46
46
## Add API permissions
47
47
48
-
Now that you have set up the correct authentication, set the API permissions:
48
+
Now that you have set up the correct authentication, set the API permissions.
49
49
50
50
1. Select **API permissions** and select **Add a permission**.
51
51
1. Under **APIs my organization uses**, search for Azure Health Data Services.
@@ -60,4 +60,4 @@ You now have a public client application. In the next tutorial, we’ll walk thr
60
60
>[!div class="nextstepaction"]
61
61
>[Test client application in Postman](tutorial-web-app-test-postman.md)
62
62
63
-
FHIR® is a registered trademark of [HL7](https://hl7.org/fhir/) and is used with the permission of HL7.
In the previous tutorial, you deployed the Azure API for FHIR and registered your client application. You're now ready to test your Azure API for FHIR.
17
+
In the previous tutorial, you deployed the Azure API for FHIR® and registered your client application. You're now ready to test your Azure API for FHIR.
18
18
19
-
## Retrieve capability statement
19
+
## Retrieve the capability statement
20
20
21
-
First we'll get the capability statement for your Azure API for FHIR.
21
+
First we get the capability statement for your Azure API for FHIR.
22
22
1. Open Postman.
23
-
1. Retrieve the capability statement by doing`GET https://\<FHIR-SERVER-NAME>.azurehealthcareapis.com/metadata`. In the image below the FHIR server name is **fhirserver**.
23
+
1. Retrieve the capability statement by using`GET https://\<FHIR-SERVER-NAME>.azurehealthcareapis.com/metadata`. In the image below the FHIR server name is **fhirserver**.
Next we'll attempt to retrieve a patient. To retrieve a patient, enter `GET https://\<FHIR-SERVER-NAME>.azurehealthcareapis.com/Patient`. You’ll receive a 401 Unauthorized error. This error is because you haven't proven that you should have access to patient data.
28
-
29
-
## Get patient from FHIR server
27
+
Next we attempt to retrieve a patient. To retrieve a patient, use `GET https://\<FHIR-SERVER-NAME>.azurehealthcareapis.com/Patient`. You receive a `401 Unauthorized` error because you haven't proven you should have access to patient data.
Now you have access, you can create a new patient. Here's a sample of a simple patient you can add into your FHIR server. Enter this `json` into the **Body** section of Postman.
60
+
Now that you have access, you can create a new patient. Here's a sample of a simple patient you can add into your FHIR server. Enter this `json` into the **Body** section of Postman.
59
61
60
62
```json
61
63
{
@@ -81,10 +83,11 @@ Now you have access, you can create a new patient. Here's a sample of a simple p
81
83
"birthDate": "1960-12-25"
82
84
}
83
85
```
84
-
This POST will create a new patient in your FHIR server with the name James Tiberious Kirk.
86
+
This POST creates a new patient in your FHIR server with the name James Tiberious Kirk.
0 commit comments