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
Copy file name to clipboardExpand all lines: articles/healthcare-apis/fhir/troubleshoot-identity-provider-configuration.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,11 +12,11 @@ ms.author: namalu
12
12
13
13
# Troubleshoot identity provider configuration for the FHIR service
14
14
15
-
API version 2023-12-01 of the FHIR® service in Azure Health Data Services supports two identity providers in addition to [Microsoft Entra ID](/entra/identity/). To provide scoped access to users, you configure the two identity providers by populating the `smartIdentityProviders` section of the `authenticationConfiguration` object.
15
+
API version 2023-12-01 of the FHIR® service in Azure Health Data Services supports two identity providers in addition to [Microsoft Entra ID](/entra/identity/). To provide scoped access to users, configure the two identity providers by populating the `smartIdentityProviders` section of the `authenticationConfiguration` object.
16
16
17
17
## Error messages
18
18
19
-
Here are the error messages that occur if the FHIR service SMART identity providers fail, and recommended actions to take to resolve the issue.
19
+
Here are the error messages that occur if the FHIR service SMART identity providers fail, with recommended actions to take to resolve the issue.
20
20
21
21
| Error | Cause | Fix |
22
22
| --- | --- | --- |
@@ -27,7 +27,7 @@ Here are the error messages that occur if the FHIR service SMART identity provid
27
27
|**One or more SMART applications are null.**| The `applications` element for one or more identity providers is null or contains no applications. | Ensure all identity provider configurations have at least one application configured. |
28
28
|**One or more SMART application `allowedDataActions` contain duplicate elements.**| The `allowedDataActions` array in one or more application configurations contains duplicate values. | Remove any duplicate values in the `allowedDataActions` arrays. |
29
29
|**One or more SMART application `allowedDataActions` values are invalid.**| The only acceptable value in the `allowedDataActions` array is `Read`.| Remove any nonconforming values from the `allowedDataActions` arrays. |
30
-
|**One or more SMART application `allowedDataActions` values are null, empty, or invalid.**| The `allowedDataActions` array in one or more application configurations is null, empty, or malformed. | The only acceptable value in the `allowedDataActions` array is `Read`. |
30
+
|**One or more SMART application `allowedDataActions` values are nullor empty.**| The `allowedDataActions` array in one or more application configurations is nullor empty. | The only acceptable value in the `allowedDataActions` array is `Read`. |
31
31
|**One or more SMART application `audience` values are null, empty, or invalid.**| The `audience` string in one or more application configurations is null, empty, or malformed. | Ensure the `audience` string isn't null or empty and that the value is a string type. |
32
32
|**All SMART identity provider application client ids must be unique.**| The `clientId` value in one or more application configurations is the same value as another `clientId` value. | Ensure all `clientId` values are unique (including across identity provider configurations). |
33
33
|**One or more SMART application client id values are null, empty, or invalid.**| The `clientId` string in one or more application configurations is null, empty, or malformed. | Ensure the `clientId` string isn't null or empty and that the value is a string type. |
@@ -53,7 +53,7 @@ Follow these steps to verify the correct configuration of the `smartIdentityProv
53
53
54
54
4.**Verify the `clientId` string is correct**. Ensure the `clientId` string matches the client ID (or application ID) of the resource application defined in the identity provider.
55
55
56
-
5.**Verify the request method is GET**. The only supported request type is `GET`, because the `allowedDataActions` values only supports`Read`.
56
+
5.**Verify the request method is GET**. The only supported request type is `GET`, because the `allowedDataActions` values only support`Read`.
57
57
58
58
6.**Verify the JSON web token (JWT) claims**. If the access token is available, decode it by using online tools such as [jwt.ms](https://jwt.ms). After the token is decoded, the claims can be inspected for correctness.
59
59
@@ -82,7 +82,7 @@ Follow these steps to verify the correct configuration of the `smartIdentityProv
82
82
83
83
## Schema for configuring identity providers
84
84
85
-
The `smartIdentityProviders` element is a JSON array that contains one or two `identity provider configurations`. An `identity provider configuration` consists of:
85
+
The `smartIdentityProviders` element is a JSON array that contains one or two `identity provider configurations`. An `identity provider configuration` consists of
86
86
87
87
- An `authority` string value that must be the fully qualified URL of the identity providers token authority.
Copy file name to clipboardExpand all lines: articles/healthcare-apis/fhir/tutorial-member-match.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,30 +16,30 @@ ms.date: 06/06/2022
16
16
17
17
## Overview of $member-match
18
18
19
-
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:
19
+
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.
20
20
21
21
* Patient demographics
22
22
* The old coverage information
23
23
* The new coverage information (not required based on our implementation)
24
24
25
-
After the data is passed in, the FHIR service in Azure Health Data Services (hereby called FHIR service) 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.
25
+
After the data is passed in, the FHIR® service in Azure Health Data Services validates that it can find a patient that exactly matches the demographics passed in with the old coverage information. 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.
26
26
27
27
> [!NOTE]
28
28
> The specification describes passing in and back the new coverage information. We've decided to omit that data to keep the results smaller.
29
29
30
30
## Example of $member-match
31
31
32
-
To use $member-match, use the following call:
32
+
To use $member-match, use the following call.
33
33
34
34
`POST {{fhirurl}}/Patient/$member-match`
35
35
36
-
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).
36
+
You 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).
37
37
38
-
If a single match is found, you'll receive a 200 response with another identifier added:
38
+
If a single match is found, you receive a 200 response with another identifier added.
![prmerger-automator[bot]](https://avatars.githubusercontent.com/u/22479449?v=4&size=40){kind=avatar}
0 commit comments