export files TOC

Author: shellyhaverkamp

articles/healthcare-apis/.openpublishing.redirection.healthcare-apis.json

@@ -487,6 +487,10 @@
         "redirect_url": "/azure/healthcare-apis/dicom/dicom-configure-azure-rbac",
         "redirect_document_id": true     
       },
+    {  "source_path_from_root": "/articles/healthcare-apis/dicom/export-dicom-files.md",
+       "redirect_url": "/azure/healthcare-apis/dicom/export-files",
+       "redirect_document_id": true     
+    },     
       {
           "source_path_from_root": "/articles/healthcare-apis/fhir/configure-azure-rbac-for-fhir.md",
           "redirect_url": "/azure/healthcare-apis/configure-azure-rbac",

articles/healthcare-apis/dicom/export-dicom-files.md renamed to articles/healthcare-apis/dicom/export-files.md

@@ -3,9 +3,9 @@ title: Export DICOM files by using the export API of the DICOM service
 description: This how-to guide explains how to export DICOM files to an Azure Blob Storage account.
 author: mmitrik
 ms.service: healthcare-apis
-ms.subservice: fhir
+ms.subservice: dicom
 ms.topic: how-to
-ms.date: 10/14/2022
+ms.date: 10/30/2023
 ms.author: mmitrik
 ---
 
@@ -37,7 +37,7 @@ The first step to export data from the DICOM service is to enable a system-assig
 
 It takes a few minutes to create the system-assigned managed identity. After the system identity is enabled, an **Object (principal) ID** appears.
 
-## Give storage account permissions to the system-assigned managed identity
+## Assign storage account permissions 
 
 The system-assigned managed identity needs **Storage Blob Data Contributor** permission to write data to the destination storage account.
 
@@ -67,7 +67,7 @@ Given a *source*, the set of data to be exported, and a *destination*, the locat
 
 Any errors encountered while you attempt to export are recorded in an error log. For more information, see the [Errors](#errors) section.
 
-## Request
+#### Request
 
 The request body consists of the export source and destination.
 
@@ -90,15 +90,15 @@ The request body consists of the export source and destination.
 }
 ```
 
-### Source settings
+#### Source settings
 
 The only setting is the list of identifiers to export.
 
 | Property | Required | Default | Description |
 | :------- | :------- | :------ | :---------- |
 | `Values` | Yes      |         | A list of one or more DICOM studies, series, and/or SOP instance identifiers in the format of `"<StudyInstanceUID>[/<SeriesInstanceUID>[/<SOPInstanceUID>]]"` |
 
-### Destination settings
+#### Destination settings
 
 The connection to the Blob Storage account is specified with `BlobContainerUri`.
 
@@ -107,7 +107,7 @@ The connection to the Blob Storage account is specified with `BlobContainerUri`.
 | `BlobContainerUri`   | No       | `""`    | The complete URI for the blob container |
 | `UseManagedIdentity` | Yes      | `false` | A required flag that indicates whether managed identity should be used to authenticate to the blob container |
 
-### Example
+#### Example
 
 The following example requests the export of the following DICOM resources to the blob container named `export` in the storage account named `dicomexport`:
 
@@ -140,7 +140,7 @@ Content-Type: application/json
 }
 ```
 
-## Response
+#### Response
 
 The export API returns a `202` status code when an export operation is started successfully. The body of the response contains a reference to the operation, while the value of the `Location` header is the URL for the export operation's status (the same as `href` in the body).
 
@@ -155,7 +155,7 @@ Content-Type: application/json
 }
 ```
 
-### Operation status
+#### Operation status
 
 Poll the preceding `href` URL for the current status of the export operation until completion. After the job has reached a terminal state, the API returns a 200 status code instead of 202. The value of its status property is updated accordingly.
 
@@ -180,7 +180,7 @@ Content-Type: application/json
 
 If there are any user errors when you export a DICOM file, the file is skipped and its corresponding error is logged. This error log is also exported alongside the DICOM files and the caller can review it. You can find the error log at `<export blob container uri>/<operation ID>/errors.log`.
 
-### Format
+#### Format
 
 Each line of the error log is a JSON object with the following properties. A given error identifier might appear multiple times in the log as each update to the log is processed *at least once*.
 
@@ -190,9 +190,4 @@ Each line of the error log is a JSON object with the following properties. A giv
 | `Identifier` | The identifier for the DICOM study, series, or SOP instance in the format of `"<study instance UID>[/<series instance UID>[/<SOP instance UID>]]"` |
 | `Error`      | The detailed error message |
 
-## Next steps
-
->[!div class="nextstepaction"]
->[Overview of the DICOM service](dicom-services-overview.md)
-
 [!INCLUDE [DICOM trademark statement](../includes/healthcare-apis-dicom-trademark.md)]

articles/healthcare-apis/dicom/toc.yml

@@ -3,7 +3,14 @@ items:
   href: index.yml
 - name: What is the DICOM service?
   href: overview.md
-- name: Quickstarts
+- name: DICOM conformance statements
+  expanded: false
+  items: 
+    - name: V2
+      href: dicom-services-conformance-statement-v2.md
+    - name: V1
+      href: dicom-services-conformance-statement.md
+- name: Get started
   expanded: true
   items: 
     - name: Get started with the DICOM service
@@ -14,28 +21,26 @@ items:
       href: get-access-token.md
     - name: Register a client application
       href: dicom-register-application.md
+- name: Tutorials
+  expanded: true
+  items: 
     - name: Use DICOM data in analytics workloads
       href: get-started-with-analytics-dicom.md
-- name: How-tos
-  expanded: false
-  items: 
-    - name: Import DICOM files
-      href: import-files.md
     - name: Use the DICOM service for digital pathology
       href: dicom-digital-pathology.md
+- name: Configuration & operations
+  expanded: true
+  items: 
     - name: Configure CORS
       href: configure-cross-origin-resource-sharing.md
     - name: Configure Azure RBAC
       href: dicom-configure-azure-rbac.md
     - name: Enable audit and diagnostic logging
       href: enable-diagnostic-logging.md
-- name: DICOM conformance statements
-  expanded: false
-  items: 
-    - name: V2
-      href: dicom-services-conformance-statement-v2.md
-    - name: V1
-      href: dicom-services-conformance-statement.md
+    - name: Import DICOM files
+      href: import-files.md
+    - name: Export DICOM files
+      href: export-files.md
 - name: API reference
   expanded: true
   items: