incorp ketki's feedback about

Author: shellyhaverkamp

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

@@ -11,11 +11,11 @@ ms.author: kesheth
 
 # Import FHIR data
 
-The import operation allows you to ingest FHIR® data into the FHIR server with high throughput.
+The `import` operation allows you to ingest FHIR® data into the FHIR server with high throughput.
 
 ## Import operation modes
 
-The `$import` operation supports two modes: initial mode and incremental mode. Each mode has different features and use cases.
+The `import` operation supports two modes: initial mode and incremental mode. Each mode has different features and use cases.
 
 #### Initial mode
 
@@ -36,37 +36,37 @@ The `$import` operation supports two modes: initial mode and incremental mode. E
 - Allows you to ingest soft deleted resources. This capability is beneficial when you migrate from Azure API for FHIR to the FHIR service in Azure Health Data Services.
 
 > [!IMPORTANT]
-> The `$import` operation doesn't support conditional references in resources. 
+> The `import` operation doesn't support conditional references in resources. 
 >
 > Also, if multiple resources share the same resource ID, then only one of those resources is imported at random. An error is logged for the resources sharing the same resource ID.
 
 ## Performance considerations
 
-To achieve the best performance with the `$import` operation, consider these factors:
+To achieve the best performance with the `import` operation, consider these factors:
 
-- **Use large files for import.** The file size of a single import operation should be more than 200 MB. Smaller files might result in slower import times.
+- **Use large files for import.** The file size of a single `import` operation should be more than 200 MB. Smaller files might result in slower import times.
 
-- **Import FHIR resource files as a single batch.** For optimal performance, import all the FHIR resource files that you want to ingest in the FHIR server in one import operation. Importing all the files in one operation reduces the overhead of creating and managing multiple import jobs.
+- **Import FHIR resource files as a single batch.** For optimal performance, import all the FHIR resource files that you want to ingest in the FHIR server in one `import` operation. Importing all the files in one operation reduces the overhead of creating and managing multiple import jobs.
 
-- **Limit the number of parallel import jobs.** You can run multiple import jobs at the same time, but running multiple jobs might affect the overall throughput of the import operation. The FHIR server can handle up to five parallel import jobs. If you exceed this limit, the FHIR server might throttle or reject your requests.
+- **Limit the number of parallel import jobs.** You can run multiple `import` jobs at the same time, but running multiple jobs might affect the overall throughput of the import operation. The FHIR server can handle up to five parallel `import` jobs. If you exceed this limit, the FHIR server might throttle or reject your requests.
 
-## Perform the $import operation
+## Perform the import operation
 
 ### Prerequisites
 
-- You need the **FHIR Data Importer** role on the FHIR server to use `$import`. 
+- You need the **FHIR Data Importer** role on the FHIR server to use the `import` operation. 
 
-- Configure the FHIR server for `$import`. The FHIR data must be stored in resource-specific files in FHIR NDJSON format on the Azure blob store. For more information, see [Configure import settings](configure-import-data.md).
+- Configure the FHIR server. The FHIR data must be stored in resource-specific files in FHIR NDJSON format on the Azure blob store. For more information, see [Configure import settings](configure-import-data.md).
 
 - All the resources in a file must be the same type. You can have multiple files per resource type.
 
 - The data must be in the same tenant as the FHIR service.
 
-- The maximum number of files allowed per `$import` operation is 10,000.
+- The maximum number of files allowed per `import` operation is 10,000.
 
 ### Call $import
 
-Make a ```POST``` call to ```<<FHIR service base URL>>/$import``` with the request header and body shown.
+Make a `POST` call to `<<FHIR service base URL>>/$import` with the request header and body shown.
 
 #### Request header
 
@@ -80,14 +80,14 @@ Content-Type:application/fhir+json
 | Parameter Name      | Description | Card. |  Accepted values |
 | ----------- | ----------- | ----------- | ----------- |
 | inputFormat      | String representing the name of the data source format. Only FHIR NDJSON files are supported. | 1..1 | ```application/fhir+ndjson``` |
-| mode      | Import mode value | 1..1 | For an initial mode import,  use the `InitialLoad` mode value. For incremental mode import, use the `IncrementalLoad` mode value. If no mode value is provided, the `IncrementalLoad`` mode value is used by default. |
+| mode      | Import mode value | 1..1 | For an initial mode `import`,  use the `InitialLoad` mode value. For incremental mode `import`, use the `IncrementalLoad` mode value. If no mode value is provided, the `IncrementalLoad`` mode value is used by default. |
 | input   | Details of the input files. | 1..* | A JSON array with the three parts described in the table. |
 
 | Input part name   | Description | Card. |  Accepted values |
 | ----------- | ----------- | ----------- | ----------- |
 | type   |  Resource type of input file   | 1..1 |  A valid [FHIR resource type](https://www.hl7.org/fhir/resourcelist.html) that matches the input file. |
 |URL   |  Azure storage URL of the input file   | 1..1 | URL value of the input file. The value can't be modified. |
-| etag   |  Etag of the input file on Azure storage; used to verify the file content isn't changed after $import registration. | 0..1 |  Etag value of the input file. |
+| etag   |  Etag of the input file on Azure storage; used to verify the file content isn't changed after `import` registration. | 0..1 |  Etag value of the input file. |
 
 ```json
 {
@@ -139,9 +139,9 @@ Content-Type:application/fhir+json
 
 After an $import is initiated, an empty response body with a `callback` link is returned in the `Content-location` header of the response, together with an `202-Accepted` status code. Store the callback link to check the import status.
 
-The `$import` operation registration is implemented as an idempotent call. The same registration payload yields the same registration, which affects ability to reprocess files with the same name. Refrain from updating files in-place, instead we suggest you use different file name for updated data, or, if update in-place with same file name is unavoidable, add e-tags in the registration payload.
+The import operation registration is implemented as an idempotent call. The same registration payload yields the same registration, which affects ability to reprocess files with the same name. Refrain from updating files in-place, instead we suggest you use different file name for updated data, or, if update in-place with same file name is unavoidable, add e-tags in the registration payload.
 
-To check import status, make the REST call with the ```GET``` method to the `callback` link returned in the previous step.
+To check import status, make the REST call with the `GET` method to the `callback` link returned in the previous step.
 
 Interpret the response by using the table:
 
@@ -188,15 +188,15 @@ Table describes the important fields in the response body:
 }
 ```
 ### Ingest soft deleted resources
-Incremental mode import supports ingestion of soft deleted resources. You need to use the extension to ingest soft deleted resources in the FHIR service.
+Incremental mode `import` supports ingestion of soft deleted resources. You need to use the extension to ingest soft deleted resources in the FHIR service.
 
 Add the extension to the resource to inform the FHIR service that the resource was soft deleted. 
 
 ```ndjson
 {"resourceType": "Patient", "id": "example10", "meta": { "lastUpdated": "2023-10-27T04:00:00.000Z", "versionId": 4, "extension": [ { "url": "http://azurehealthcareapis.com/data-extensions/deleted-state", "valueString": "soft-deleted" } ] } }
 ```
 
-After the `$import` operation completes successfully, perform history search on the resource to validate soft deleted resources. If you know the ID of the deleted resource, use the URL pattern in the example.
+After the `import` operation completes successfully, perform history search on the resource to validate soft deleted resources. If you know the ID of the deleted resource, use the URL pattern in the example.
 
 ```json
 <FHIR_URL>/<resource-type>/<resource-id>/_history
@@ -207,13 +207,13 @@ If you don't know the ID of the resource, do a history search on the resource ty
 <FHIR_URL>/<resource-type>/_history
 ```
 
-## Troubleshoot the $import operation
+## Troubleshoot the import operation
 
-Here are the error messages that occur if the `$import` operation fails, and recommended actions to take to resolve the issue.
+Here are the error messages that occur if the `import` operation fails, and recommended actions to take to resolve the issue.
 
 #### 200 OK, but there's an error with the URL in the response
 
-**Behavior:**  The `$import` operation succeeds and returns `200 OK`. However, `error.url` is present in the response body. Files present at the `error.url` location contain JSON fragments similar to the example:
+**Behavior:**  The `import` operation succeeds and returns `200 OK`. However, `error.url` is present in the response body. Files present at the `error.url` location contain JSON fragments similar to the example:
 
 ```json
 {
@@ -236,7 +236,7 @@ Here are the error messages that occur if the `$import` operation fails, and rec
 
 #### 400 Bad Request
 
-**Behavior:** The `$import` operation failed and `400 Bad Request` is returned. The response body includes this content:
+**Behavior:** The import operation failed and `400 Bad Request` is returned. The response body includes this content:
 
 ```json
 {
@@ -256,7 +256,7 @@ Here are the error messages that occur if the `$import` operation fails, and rec
 
 #### 403 Forbidden
 
-**Behavior:** The `$import` operation failed and `403 Forbidden` is returned. The response body contains this content:
+**Behavior:** The import operation failed and `403 Forbidden` is returned. The response body contains this content:
 
 ```json
 {
@@ -278,7 +278,7 @@ Here are the error messages that occur if the `$import` operation fails, and rec
 
 #### 500 Internal Server Error
 
-**Behavior:** The `$import` operation failed and `500 Internal Server Error` is returned. The response body contains this content:
+**Behavior:** The import operation failed and `500 Internal Server Error` is returned. The response body contains this content:
 
 ```json
 {