Skip to content

Commit ee716fe

Browse files
authored
Resolved PR comments.
1 parent 46f0322 commit ee716fe

File tree

4 files changed

+5
-4
lines changed

4 files changed

+5
-4
lines changed

articles/healthcare-apis/fhir/convert-data-troubleshoot.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ Default template implementations for many common scenarios can be found on the [
4141
## Debugging and testing
4242
In addition to testing templates on an instance of the service, a [Visual Studio Code extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-health-fhir-converter) is available. The extension can be used to modify templates and test them with sample data payloads. There are also several existing test scenarios in the [FHIR Converter GitHub repository](https://github.com/microsoft/FHIR-Converter/tree/main/src/Microsoft.Health.Fhir.Liquid.Converter.FunctionalTests) that can be used as a reference.
4343

44-
## Troubleshoot Azure Container Registry
44+
## Troubleshooting Azure Container Registry
4545

4646
## The AHDS FHIR Service should work with Azure Container Registry (ACR) for custom template storage, but it encounters a "Failed to get access token for Azure Container Registry" error when reading templates.
4747

articles/healthcare-apis/fhir/fhir-faq.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -94,7 +94,7 @@ No. You can't change the URL for the FHIR service.
9494
### What are the limits associated with Azure FHIR service?
9595

9696
Please refer
97-
[Azure FHIR service limits](fhir-features-supported#service-limits)
97+
[Azure FHIR service limits](fhir-features-supported.md#service-limits)
9898

9999
## FHIR Implementations and Specifications
100100

@@ -143,7 +143,7 @@ To perform a health check on a FHIR service, enter `{{fhirurl}}/health/check` in
143143

144144
If there are errors, you may receive an error response with HTTP status code 404 (Not Found) or status code 500 (Internal Server Error), and detailed information in the response body.
145145

146-
**What are the recommended methods for syncing data between Azure FHIR Service and a database?**
146+
**What are the recommended methods for syncing data between Azure FHIR Service and a Dataverse?**
147147

148148
To connect FHIR services with Dataverse, we have introduced a new capability known as the Dataverse Health APIs.
149149
[Dataverse healthcare APIs](https://learn.microsoft.com/en-us/dynamics365/industry/healthcare/dataverse-healthcare-apis-overview)

articles/healthcare-apis/fhir/overview-of-search.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -160,7 +160,7 @@ As previously mentioned, the results from a FHIR search are available in paginat
160160

161161
Currently, the FHIR service in Azure Health Data Services only supports the `next` link and doesn’t support `first`, `last`, or `previous` links in bundles returned from a search.
162162

163-
### Recommendation section
163+
## Troubleshooting FHIR Search
164164
**Is the HL7 FHIR API, specifically the lastN operation for observations, supported by Microsoft?**
165165

166166
This option is not supported. Please refer to the alternative approach provided below:

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

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,7 @@ Here are the error messages that occur if the FHIR service SMART identity provid
3131
| **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. |
3232
| **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). |
3333
| **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. |
34+
| **An authorization failure with the Azure Health Data Services FHIR API using OKTA.** | FHIR SMART user role will cause this issue as it adds an authentication layer. | Ensure that the FHIR SMART user role is not assigned. |
3435

3536
## FHIR API request errors
3637

0 commit comments

Comments
 (0)