Merge pull request #213132 from judegnan/Commit-for-Ruiyi

Commit for Riuyu

Author: prmerger-automator[bot]

articles/healthcare-apis/fhir/configure-import-data.md

@@ -6,7 +6,7 @@ ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: how-to
 ms.date: 06/06/2022
-ms.author: ruiyichen
+ms.author: mikaelw
 ---
 
 # Configure bulk-import settings (Preview)
@@ -25,7 +25,7 @@ The first step in configuring the FHIR service for import is to enable system wi
 
 In this step, browse to your FHIR service in the Azure portal, and select the **Identity** blade. Select the **Status** option to **On** , and then select **Save**. The **Yes** and **No** buttons will display. Select **Yes** to enable the managed identity for FHIR service. After the system identity has been enabled, you'll see a system assigned GUID value. 
 
-[ ![Enable Managed Identity](media/export-data/fhir-mi-enabled.png) ](media/export-data/fhir-mi-enabled.png#lightbox)
+[![Enable Managed Identity](media/export-data/fhir-mi-enabled.png)](media/export-data/fhir-mi-enabled.png#lightbox)
 
 
 ## Assign permissions to the FHIR service to access the storage account
@@ -36,7 +36,7 @@ For more information about assigning roles in the Azure portal, see [Azure built
 
 Add the role [Storage Blob Data Contributor](../../role-based-access-control/built-in-roles.md#storage-blob-data-contributor) to the FHIR service, and then select **Save**.
 
-[![Screen shot of the Add role assignment page.](media/bulk-import/add-role-assignment-page.png) ](media/bulk-import/add-role-assignment-page.png#lightbox)
+[![Screen shot of the Add role assignment page.](media/bulk-import/add-role-assignment-page.png)](media/bulk-import/add-role-assignment-page.png#lightbox)
 
 Now you're ready to select the storage account in the FHIR service as a default storage account for import.
 
@@ -51,15 +51,15 @@ To specify the Azure Storage account, you need to use [REST API](/rest/api/healt
 
 To get the request URL and body, browse to the Azure portal of your FHIR service. Select **Overview**, and then **JSON View**.
 
-[ ![Screenshot of Get JSON View](media/bulk-import/fhir-json-view.png) ](media/bulk-import/fhir-json-view.png#lightbox)
+[![Screenshot of Get JSON View](media/bulk-import/fhir-json-view.png)](media/bulk-import/fhir-json-view.png#lightbox)
 
 Copy the URL as request URL and do following changes of the JSON as body:
 - Set enabled in importConfiguration to **true**
 - add or change the integrationDataStore with target storage account name 
 - Set initialImportMode in importConfiguration to **true**
 - Drop off provisioningState.
 
-[ ![Screenshot of the importer configuration code example](media/bulk-import/import-url-and-body.png) ](media/bulk-import/import-url-and-body.png#lightbox)
+[![Screenshot of the importer configuration code example](media/bulk-import/import-url-and-body.png)](media/bulk-import/import-url-and-body.png#lightbox)
 
 After you've completed this final step, you're ready to import data using $import.
 

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

@@ -7,7 +7,7 @@ ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: overview
 ms.date: 08/15/2022
-ms.author: ruiyichen
+ms.author: mikaelw
 ms.custom: subject-rbac-steps
 ---
 
@@ -35,7 +35,7 @@ A `$convert-data` API call packages the health data for conversion inside a JSON
 | ----------- | ----------- | ----------- |
 | `inputData`      | Data payload to be converted to FHIR. | For `Hl7v2`: string <br> For `Ccda`: XML <br> For `Json`: JSON |
 | `inputDataType`   | Type of data input. | ```Hl7v2```, ``Ccda``, ``Json`` |
-| `templateCollectionReference` | Reference to an [OCI image ](https://github.com/opencontainers/image-spec) template collection in [Azure Container Registry (ACR)](https://azure.microsoft.com/services/container-registry/). The reference is to an image containing Liquid templates to use for conversion. This can be a reference either to default templates or a custom template image that is registered within the FHIR service. See below to learn about customizing the templates, hosting them on ACR, and registering to the FHIR service. | For ***default/sample*** templates: <br> **HL7v2** templates: <br>```microsofthealth/fhirconverter:default``` <br>``microsofthealth/hl7v2templates:default``<br> **C-CDA** templates: <br> ``microsofthealth/ccdatemplates:default`` <br> **JSON** templates: <br> ``microsofthealth/jsontemplates:default`` <br><br> For ***custom*** templates: <br> `<RegistryServer>/<imageName>@<imageDigest>`, `<RegistryServer>/<imageName>:<imageTag>` |
+| `templateCollectionReference` | Reference to an [OCI image](https://github.com/opencontainers/image-spec) template collection in [Azure Container Registry (ACR)](https://azure.microsoft.com/services/container-registry/). The reference is to an image containing Liquid templates to use for conversion. This can be a reference either to default templates or a custom template image that is registered within the FHIR service. See below to learn about customizing the templates, hosting them on ACR, and registering to the FHIR service. | For ***default/sample*** templates: <br> **HL7v2** templates: <br>```microsofthealth/fhirconverter:default``` <br>``microsofthealth/hl7v2templates:default``<br> **C-CDA** templates: <br> ``microsofthealth/ccdatemplates:default`` <br> **JSON** templates: <br> ``microsofthealth/jsontemplates:default`` <br><br> For ***custom*** templates: <br> `<RegistryServer>/<imageName>@<imageDigest>`, `<RegistryServer>/<imageName>:<imageTag>` |
 | `rootTemplate` | The root template to use while transforming the data. | For **HL7v2**:<br> "ADT_A01", "ADT_A02", "ADT_A03", "ADT_A04", "ADT_A05", "ADT_A08", "ADT_A11",  "ADT_A13", "ADT_A14", "ADT_A15", "ADT_A16", "ADT_A25", "ADT_A26", "ADT_A27", "ADT_A28", "ADT_A29", "ADT_A31", "ADT_A47", "ADT_A60", "OML_O21", "ORU_R01", "ORM_O01", "VXU_V04", "SIU_S12", "SIU_S13", "SIU_S14", "SIU_S15", "SIU_S16", "SIU_S17", "SIU_S26", "MDM_T01", "MDM_T02"<br><br> For **C-CDA**:<br> "CCD", "ConsultationNote", "DischargeSummary", "HistoryandPhysical", "OperativeNote", "ProcedureNote", "ProgressNote", "ReferralNote", "TransferSummary" <br><br> For **JSON**: <br> "ExamplePatient", "Stu3ChargeItem" <br> |
 
 > [!NOTE]
@@ -124,7 +124,7 @@ After creating an ACR instance, you can use the _FHIR Converter: Push Templates_
 Browse to your instance of the FHIR service in Azure portal and select the **Identity** blade.
 Change the status to **On** to enable managed identity in the FHIR service.
 
-[ ![Screen image of Enable Managed Identity.](media/convert-data/fhir-mi-enabled.png) ](media/convert-data/fhir-mi-enabled.png#lightbox)
+[![Screen image of Enable Managed Identity.](media/convert-data/fhir-mi-enabled.png)](media/convert-data/fhir-mi-enabled.png#lightbox)
 
 ### Provide ACR access to the FHIR service