Merge pull request #286787 from KendalBond007/FHIReditsBatch15_Sep24

FHIReditsBatch15_Sep24

Author: prmerger-automator[bot]

articles/healthcare-apis/fhir/fhir-service-diagnostic-logs.md

@@ -21,11 +21,11 @@ Access to diagnostic logs is essential for any healthcare service. Compliance wi
 
 3. Select **+ Add diagnostic settings**.
 
-   [ ![Screenshot of the diagnostic settings page in the Azure portal.](media/diagnostic-logs/fhir-diagnostic-settings-screen.png) ](media/diagnostic-logs/fhir-diagnostic-settings-screen.png#lightbox)
+   [![Screenshot of the diagnostic settings page in the Azure portal.](media/diagnostic-logs/fhir-diagnostic-settings-screen.png) ](media/diagnostic-logs/fhir-diagnostic-settings-screen.png#lightbox)
 
 4. Enter the **Diagnostic setting name**.
 
-   [ ![Screenshot of the destination details and the checkbox for enabling or disabling audit logs.](media/diagnostic-logs/fhir-diagnostic-settings-add.png) ](media/diagnostic-logs/fhir-diagnostic-settings-add.png#lightbox)
+   [![Screenshot of the destination details and the checkbox for enabling or disabling audit logs.](media/diagnostic-logs/fhir-diagnostic-settings-add.png) ](media/diagnostic-logs/fhir-diagnostic-settings-add.png#lightbox)
 
 5. Select the method that you want to use to access your logs:
 

articles/healthcare-apis/fhir/using-rest-client.md

@@ -69,7 +69,7 @@ grant_type=client_credentials
 @token = {{getAADToken.response.body.access_token}}
 ```
 
-[ ![Get access token](media/rest-config.png) ](media/rest-config.png#lightbox)
+[![Get access token](media/rest-config.png)](media/rest-config.png#lightbox)
 
 > [!NOTE] 
 > When the FHIR service audience parameter is not mapped to the FHIR service endpoint url, the resource parameter value should be mapped to the Audience value under the FHIR Service Authentication blade.
@@ -84,17 +84,17 @@ GET {{fhirurl}}/Patient/<patientid>
 Authorization: Bearer {{token}}
 ```
 
-[ ![GET Patient](media/rest-patient.png) ](media/rest-patient.png#lightbox)
+[![GET Patient](media/rest-patient.png)](media/rest-patient.png#lightbox)
 
 ## Run PowerShell or CLI
 
 You can run PowerShell or CLI scripts within Visual Studio Code. Press `CTRL` and the `~` key and select PowerShell or Bash. You can find more details on [Integrated Terminal](https://code.visualstudio.com/docs/editor/integrated-terminal).
 
 ### PowerShell in Visual Studio Code
-[ ![running PowerShell](media/rest-powershell.png) ](media/rest-powershell.png#lightbox)
+[![running PowerShell](media/rest-powershell.png)](media/rest-powershell.png#lightbox)
 
 ### CLI in Visual Studio Code
-[ ![running CLI](media/rest-cli.png) ](media/rest-cli.png#lightbox)
+[![running CLI](media/rest-cli.png)](media/rest-cli.png#lightbox)
 
 ## Troubleshooting
 

articles/healthcare-apis/includes/converter-redirect-statement.md

@@ -8,7 +8,7 @@ ms.author: jasteppe
 ---
 
 > [!NOTE]
-> In May 2024 we released a stand-alone FHIR converter API decoupled from the FHIR service and packaged as a [container (Docker) image](https://mcr.microsoft.com/product/healthcareapis/fhir-converter/about) for **preview**. In addition to enabling you to convert data from the source of record to FHIR R4 bundles, the FHIR converter offers many net new capabilities, such as:
+> In May 2024 we released a stand-alone FHIR® converter API decoupled from the FHIR service and packaged as a [container (Docker) image](https://mcr.microsoft.com/product/healthcareapis/fhir-converter/about) for **preview**. In addition to enabling you to convert data from the source of record to FHIR R4 bundles, the FHIR converter offers many net new capabilities, such as:
 > - Bidirectional data conversion from source of record to FHIR R4 bundles and back. For example, the FHIR converter can convert data from FHIR R4 format back to HL7v2 format.
 > - Improved experience for customization of default [Liquid](https://shopify.github.io/liquid/) templates. 
 > - Samples that demonstrate how to create an ETL (extract, transform, load) pipeline with [Azure Data Factory (ADF)](../../data-factory/introduction.md).

articles/healthcare-apis/includes/custom-header-auditlog.md

@@ -9,9 +9,9 @@ ms.author: kesheth
 ms.custom: "include file"
 ---
 
-In the Azure Fast Healthcare Interoperability Resources (FHIR) API, a user might want to include additional information in the logs, which comes from the calling system.
+In the Azure Fast Healthcare Interoperability Resources (FHIR®) API, a user might want to include additional information in the logs, which comes from the calling system.
 
-For example, when the user of the API is authenticated by an external system, that system forwards the call to the FHIR API. At the FHIR API layer, the information about the original user has been lost, because the call was forwarded. It might be necessary to log and retain this user information for auditing or management purposes. The calling system can provide user identity, caller location, or other necessary information in the HTTP headers, which will be carried along as the call is forwarded.
+For example, when the user of the API is authenticated by an external system, that system forwards the call to the FHIR API. At the FHIR API layer, the information about the original user is lost, because the call was forwarded. It might be necessary to log and retain this user information for auditing or management purposes. The calling system can provide user identity, caller location, or other necessary information in the HTTP headers, which is carried along as the call is forwarded.
 
 You can use custom headers to capture several types of information. For example:
 * Identity or authorization information

articles/healthcare-apis/includes/fhir-bulk-delete-operation.md

@@ -7,7 +7,7 @@ ms.date: 04/01/2024
 ms.author: kesheth
 ---
 
-The bulk delete capability allows you to delete resources from FHIR service asynchronously. Bulk delete capability in FHIR service is supported with operations: `$bulk-delete` and `$bulk-delete-soft-deleted`. `$bulk-delete` operation allows you to delete resources in the FHIR service, except soft deleted resources. To delete soft deleted FHIR resources, you need to use `$bulk-delete-soft-deleted` operation.
+The bulk delete capability allows you to delete resources from FHIR® service asynchronously. Bulk delete capability in FHIR service is supported with operations: `$bulk-delete` and `$bulk-delete-soft-deleted`. `$bulk-delete` operation allows you to delete resources in the FHIR service, except soft deleted resources. To delete soft deleted FHIR resources, you need to use `$bulk-delete-soft-deleted` operation.
 
 FHIR service requires specific headers and roles enabled to use bulk delete capability
 

articles/healthcare-apis/includes/healthcare-apis-azure-api-fhir-retirement.md

@@ -8,5 +8,5 @@ ms.author: jasteppe
 ---
 
 > [!IMPORTANT]
-> **Azure API for FHIR will be retired on September 30, 2026.** Follow the [migration strategies](../fhir/migration-strategies.md) to transition to **Azure Health Data Services FHIR service** by that date. Due to the retirement of Azure API for FHIR, new deployments won't be allowed beginning April 1, 2025. 
+> **Azure API for FHIR will be retired on September 30, 2026.** Follow the [migration strategies](../fhir/migration-strategies.md) to transition to **Azure Health Data Services FHIR® service** by that date. Due to the retirement of Azure API for FHIR, new deployments won't be allowed beginning April 1, 2025. 
 [Azure Health Data Services FHIR service](../healthcare-apis-overview.md) is the evolved version of Azure API for FHIR that enables customers to manage [FHIR](../fhir/overview.md), DICOM, and MedTech services with integrations into other Azure services.