markdown and edits for clarity

Author: KendalBond007

articles/healthcare-apis/fhir/troubleshoot-identity-provider-configuration.md

@@ -12,11 +12,11 @@ ms.author: namalu
 
 # Troubleshoot identity provider configuration for the FHIR service
 
-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.
+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.
 
 ## Error messages
 
-Here are the error messages that occur if the FHIR service SMART identity providers fail, and recommended actions to take to resolve the issue.
+Here are the error messages that occur if the FHIR service SMART identity providers fail, with recommended actions to take to resolve the issue.
 
 | Error | Cause | Fix |
 | --- | --- | --- |
@@ -27,7 +27,7 @@ Here are the error messages that occur if the FHIR service SMART identity provid
 | **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. |
 | **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. |
 | **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. |
-| **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`. |
+| **One or more SMART application `allowedDataActions` values are null or empty.** | The `allowedDataActions` array in one or more application configurations is null or empty. | The only acceptable value in the `allowedDataActions` array is `Read`. |
 | **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. |
 | **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). |
 | **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
 
 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.
 
-5. **Verify the request method is GET**. The only supported request type is `GET`, because the `allowedDataActions` values only supports `Read`.
+5. **Verify the request method is GET**. The only supported request type is `GET`, because the `allowedDataActions` values only support `Read`.
 
 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.
 
@@ -82,7 +82,7 @@ Follow these steps to verify the correct configuration of the `smartIdentityProv
 
 ## Schema for configuring identity providers
 
-The `smartIdentityProviders` element is a JSON array that contains one or two `identity provider configurations`. An `identity provider configuration` consists of:
+The `smartIdentityProviders` element is a JSON array that contains one or two `identity provider configurations`. An `identity provider configuration` consists of
 
 - An `authority` string value that must be the fully qualified URL of the identity providers token authority.
 

articles/healthcare-apis/fhir/tutorial-member-match.md

@@ -16,30 +16,30 @@ ms.date: 06/06/2022
 
 ## Overview of $member-match
 
-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:
+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.
 
 * Patient demographics
 * The old coverage information
 * The new coverage information (not required based on our implementation)
 
-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.
+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.
 
 > [!NOTE]
 > The specification describes passing in and back the new coverage information. We've decided to omit that data to keep the results smaller.
 
 ## Example of $member-match
 
-To use $member-match, use the following call:
+To use $member-match, use the following call.
 
 `POST {{fhirurl}}/Patient/$member-match`
 
-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).
+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).
 
-If a single match is found, you'll receive a 200 response with another identifier added:
+If a single match is found, you receive a 200 response with another identifier added:
 
 :::image type="content" source="media/centers-medicare-services-tutorials/two-hundred-response.png" alt-text="200 hundred response code.":::
 
-If the $member-match can't find a unique match, you'll receive a 422 response with an error code.
+If the $member-match can't find a unique match, you receive a 422 response with an error code.
 
 ## Next steps
 
@@ -48,4 +48,4 @@ In this guide, you've learned about the $member-match operation. Next, you can l
 >[!div class="nextstepaction"]
 >[DaVinci PDex](davinci-pdex-tutorial.md)
 
-FHIR® is a registered trademark of [HL7](https://hl7.org/fhir/) and is used with the permission of HL7.
+[!INCLUDE [FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]

articles/healthcare-apis/fhir/use-custom-headers-diagnosticlog.md

@@ -16,10 +16,10 @@ ms.date: 06/03/2022
 
 ## Next steps
 
-In this article, you learned how to add data to audit logs by using custom headers in the FHIR service. For information about FHIR service, see
+In this article, you learned how to add data to audit logs by using custom headers in the FHIR® service. For information about FHIR service, see
 
 >[!div class="nextstepaction"]
 >[FHIR Overview](overview.md)
 
-FHIR® is a registered trademark of [HL7](https://hl7.org/fhir/) and is used with the permission of HL7.
+[!INCLUDE [FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]