Merge pull request #255438 from shellyhaverkamp/smh-dicom-includes-api

Add include to 4 API articles

Author: Jill Grant

articles/healthcare-apis/dicom/dicom-services-conformance-statement-v2.md

@@ -15,7 +15,7 @@ ms.author: mmitrik
 > [!NOTE]
 > API version 2 is the latest API version.  For a list of changes in v2 compared to v1, see [DICOM service API v2 changes](dicom-service-v2-api-changes.md)
 
-The Medical Imaging Server for DICOM® supports a subset of the DICOMweb™ Standard. Support includes:
+The Medical Imaging Server for DICOM® supports a subset of the DICOMweb Standard. Support includes:
 
 * [Studies Service](#studies-service)
     * [Store (STOW-RS)](#store-stow-rs)
@@ -602,7 +602,7 @@ The query API returns one of the following status codes in the response:
 
 ### Delete
 
-This transaction isn't part of the official DICOMweb™ Standard. It uses the DELETE method to remove representations of Studies, Series, and Instances from the store.
+This transaction isn't part of the official DICOMweb Standard. It uses the DELETE method to remove representations of Studies, Series, and Instances from the store.
 
 | Method | Path                                                    | Description |
 | :----- | :------------------------------------------------------ | :---------- |
@@ -671,7 +671,7 @@ required to be present, required to not be present, required to be empty, or req
 found [in this table](https://dicom.nema.org/medical/dicom/current/output/html/part04.html#table_CC.2.5-3).
 
 > [!NOTE]
-> Although the reference table says that SOP Instance UID shouldn't be present, this guidance is specific to the DIMSE protocol and is handled differently in DICOMWeb™. SOP Instance UID should be present in the dataset if not in the URI.
+> Although the reference table says that SOP Instance UID shouldn't be present, this guidance is specific to the DIMSE protocol and is handled differently in DICOMWeb. SOP Instance UID should be present in the dataset if not in the URI.
 
 > [!NOTE]
 > All the conditional requirement codes including 1C and 2C are treated as optional.

articles/healthcare-apis/dicom/dicom-services-conformance-statement.md

@@ -15,7 +15,7 @@ ms.author: mmitrik
 > [!NOTE]
 > API version 2 is the latest API version and should be used in place of v1. See the [DICOM Conformance Statement v2](dicom-services-conformance-statement-v2.md) for details.
 
-The Medical Imaging Server for DICOM® supports a subset of the DICOMweb™ Standard. Support includes:
+The Medical Imaging Server for DICOM® supports a subset of the DICOMweb Standard. Support includes:
 
 * [Studies Service](#studies-service)
     * [Store (STOW-RS)](#store-stow-rs)
@@ -514,7 +514,7 @@ The query API returns one of the following status codes in the response:
 
 ### Delete
 
-This transaction isn't part of the official DICOMweb™ Standard. It uses the DELETE method to remove representations of Studies, Series, and Instances from the store.
+This transaction isn't part of the official DICOMwe Standard. It uses the DELETE method to remove representations of Studies, Series, and Instances from the store.
 
 | Method | Path                                                    | Description |
 | :----- | :------------------------------------------------------ | :---------- |
@@ -583,7 +583,7 @@ required to be present, required to not be present, required to be empty, or req
 found [in this table](https://dicom.nema.org/medical/dicom/current/output/html/part04.html#table_CC.2.5-3).
 
 > [!NOTE]
-> Although the reference table says that SOP Instance UID shouldn't be present, this guidance is specific to the DIMSE protocol and is handled differently in DICOMWeb™. SOP Instance UID should be present in the dataset if not in the URI.
+> Although the reference table says that SOP Instance UID shouldn't be present, this guidance is specific to the DIMSE protocol and is handled differently in DICOMWeb. SOP Instance UID should be present in the dataset if not in the URI.
 
 > [!NOTE]
 > All the conditional requirement codes including 1C and 2C are treated as optional.

articles/healthcare-apis/dicom/dicom-services-faqs.yml

@@ -16,7 +16,7 @@ sections:
   - name: Ignored
     questions:
       - question: What is the DICOM service?
-        answer: The DICOM® service is a managed service within [Azure Health Data Services](../healthcare-apis-overview.md) that ingests and persists DICOM objects at multiple thousands of images per second. It facilitates communication and transmission of imaging data with any DICOMweb™ enabled systems or applications via DICOMweb Standard APIs like [Store (STOW-RS)](dicom-services-conformance-statement-v2.md#store-stow-rs), [Search (QIDO-RS)](dicom-services-conformance-statement-v2.md#search-qido-rs), [Retrieve (WADO-RS)](dicom-services-conformance-statement-v2.md#retrieve-wado-rs). It's backed by a managed Platform-as-a Service (PaaS) offering in the cloud with complete [PHI](https://www.hhs.gov/answers/hipaa/what-is-phi/index.html) compliance that you can upload PHI data to the DICOM service and exchange it through secure networks.
+        answer: The DICOM® service is a managed service within [Azure Health Data Services](../healthcare-apis-overview.md) that ingests and persists DICOM objects at multiple thousands of images per second. It facilitates communication and transmission of imaging data with any DICOMweb enabled systems or applications via DICOMweb Standard APIs like [Store (STOW-RS)](dicom-services-conformance-statement-v2.md#store-stow-rs), [Search (QIDO-RS)](dicom-services-conformance-statement-v2.md#search-qido-rs), [Retrieve (WADO-RS)](dicom-services-conformance-statement-v2.md#retrieve-wado-rs). It's backed by a managed Platform-as-a Service (PaaS) offering in the cloud with complete [PHI](https://www.hhs.gov/answers/hipaa/what-is-phi/index.html) compliance that you can upload PHI data to the DICOM service and exchange it through secure networks.
 
       - question: What are the key requirements to use the DICOM service?
         answer: The DICOM service needs an Azure subscription to configure and run the required components. These components are, by default, created inside of an existing or new Azure Resource Group to simplify management. Additionally, a Microsoft Entra account is required.
@@ -31,9 +31,9 @@ sections:
           
       - question: What data formats are compatible with the DICOM service?
         answer: |
-          The DICOM service exposes a REST API that is compatible with the [DICOMweb™ Standards](https://www.dicomstandard.org/using/dicomweb) specified and maintained by NEMA.
+          The DICOM service exposes a REST API that is compatible with the [DICOMweb Standards](https://www.dicomstandard.org/using/dicomweb) specified and maintained by NEMA.
           
-          The server doesn't support DICOM DIMSE, which works primarily over a local area network and is unsuited for modern internet-based APIs. DIMSE is an incredibly popular standard used by nearly all medical imaging devices to communicate with other components of a provider’s medical imaging solution, such as PACS (Picture Archiving and Communication Systems) and medical imaging viewers. However, many modern systems, especially PACS and viewers, have begun to also support the related (and compatible) DICOMweb™ Standard. For those systems which only speak DICOM DIMSE, there are adapters available which allow for seamless communication between the local DIMSE-supporting systems and the DICOM service.
+          The server doesn't support DICOM DIMSE, which works primarily over a local area network and is unsuited for modern internet-based APIs. DIMSE is an incredibly popular standard used by nearly all medical imaging devices to communicate with other components of a provider’s medical imaging solution, such as PACS (Picture Archiving and Communication Systems) and medical imaging viewers. However, many modern systems, especially PACS and viewers, have begun to also support the related (and compatible) DICOMweb Standard. For those systems which only speak DICOM DIMSE, there are adapters available which allow for seamless communication between the local DIMSE-supporting systems and the DICOM service.
           
       - question: What version of DICOM does the DICOM service support?
         answer: |
@@ -57,7 +57,7 @@ sections:
           
       - question: What is the difference between Retrieve, Query, and Store?
         answer: |
-          Query, Retrieve, and store are standard DICOMweb™ verbs. Query (QIDO) searches for DICOM objects. QIDO enables you to search for studies, series and instances by patient ID. Retrieve (WADO) enables you to retrieve specific studies, series, and instances by reference. Store (STOW-RS) enables you to store specific instances to a DICOM server. For more information about the specifics of QIDO, WADO, and STOW, see [DICOMweb™](https://www.dicomstandard.org/using/dicomweb).
+          Query, Retrieve, and store are standard DICOMweb verbs. Query (QIDO) searches for DICOM objects. QIDO enables you to search for studies, series and instances by patient ID. Retrieve (WADO) enables you to retrieve specific studies, series, and instances by reference. Store (STOW-RS) enables you to store specific instances to a DICOM server. For more information about the specifics of QIDO, WADO, and STOW, see [DICOMweb](https://www.dicomstandard.org/using/dicomweb).
       
       - question: What is REST API versioning in the DICOM service?
         answer: |

articles/healthcare-apis/dicom/dicomweb-standard-apis-c-sharp.md

@@ -1,26 +1,26 @@
 ---
-title:  Using DICOMweb™Standard APIs with C# - Azure Health Data Services
-description: In this tutorial, you'll learn how to use DICOMweb Standard APIs with C#. 
+title:  Use C# and DICOMweb Standard APIs in Azure Health Data Services
+description: Learn how to use C# and DICOMweb Standard APIs to store, retrieve, search, and delete DICOM files in the DICOM service. 
 author: mmitrik
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: tutorial
-ms.date: 05/26/2022
+ms.date: 10/18/2023
 ms.author: mmitrik
 ---
 
-# Using DICOMweb™ Standard APIs with C#
+# Use C# and DICOMweb Standard APIs
 
-This tutorial uses C# to demonstrate working with the DICOM service.
+This article shows how to work with the DICOMweb service using C# and [sample .dcm DICOM® files](https://github.com/microsoft/dicom-server/tree/main/docs/dcms).
 
-In this tutorial, we'll use the following [sample .dcm DICOM files](https://github.com/microsoft/dicom-server/tree/main/docs/dcms).
+Use these sample files:
 
-* blue-circle.dcm
-* dicom-metadata.csv
-* green-square.dcm
-* red-triangle.dcm
+- blue-circle.dcm
+- dicom-metadata.csv
+- green-square.dcm
+- red-triangle.dcm
 
-The file name, studyUID, seriesUID, and instanceUID of the sample DICOM files is as follows:
+The filename, studyUID, seriesUID, and instanceUID of the sample DICOM files are:
 
 | File | StudyUID | SeriesUID | InstanceUID |
 | --- | --- | --- | ---|
@@ -29,17 +29,17 @@ The file name, studyUID, seriesUID, and instanceUID of the sample DICOM files is
 |blue-circle.dcm|1.2.826.0.1.3680043.8.498.13230779778012324449356534479549187420|1.2.826.0.1.3680043.8.498.77033797676425927098669402985243398207|1.2.826.0.1.3680043.8.498.13273713909719068980354078852867170114|
 
 > [!NOTE]
-> Each of these files represent a single instance and are part of the same study. Also, the green-square and red-triangle are part of the same series, while the blue-circle is in a separate series.
+> Each of these files represents a single instance and is part of the same study. Also, the green-square and red-triangle are part of the same series, while the blue-circle is in a separate series.
 
 ## Prerequisites
 
-To use the DICOMweb™ Standard APIs, you must have an instance of the DICOM service deployed. If you haven't already deployed an instance of the DICOM service, see [Deploy DICOM service using the Azure portal](deploy-dicom-services-in-azure.md).
+To use the DICOMweb Standard APIs, you need an instance of the DICOM service deployed. If you haven't already deployed an instance of the DICOM service, see [Deploy DICOM service using the Azure portal](deploy-dicom-services-in-azure.md).
 
-After you've deployed an instance of the DICOM service, retrieve the URL for your App service:
+After you deploy an instance of the DICOM service, retrieve the URL for your app service:
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
 1. Search **Recent resources** and select your DICOM service instance.
-1. Copy the **Service URL** of your DICOM service. Make sure to specify the version as part of the url when making requests. More information can be found in the [API Versioning for DICOM service Documentation](api-versioning-dicom-service.md).
+1. Copy the **Service URL** of your DICOM service. Make sure to specify the version as part of the url when making requests. For more information, see [API versioning for the DICOM service](api-versioning-dicom-service.md).
 
 In your application, install the following NuGet packages:
 
@@ -49,7 +49,7 @@ In your application, install the following NuGet packages:
 
 ## Create a DicomWebClient
 
-After you've deployed your DICOM service, you'll create a DicomWebClient. Run the following code snippet to create DicomWebClient, which we'll be using for the rest of this tutorial. Ensure you have both NuGet packages installed as mentioned previously. If you haven't already obtained a token, see [Get access token for the DICOM service using Azure CLI](dicom-get-access-token-azure-cli.md).
+After you deploy your DICOM service, you create a DicomWebClient. Run the code snippet to create DicomWebClient, which you use for the rest of this tutorial. Ensure you have both NuGet packages installed. If you haven't already obtained a token, see [Get access token for the DICOM service using Azure CLI](dicom-get-access-token-azure-cli.md).
 
 ```c#
 string webServerUrl ="{Your DicomWeb Server URL}"
@@ -60,7 +60,7 @@ client.HttpClient.DefaultRequestHeaders.Authorization = new System.Net.Http.Head
 ```
 With the DicomWebClient, we can now perform the Store, Retrieve, Search, and Delete operations.
 
-## Store DICOM Instances (STOW)
+## Store DICOM instances (STOW)
 
 Using the DicomWebClient that we've created, we can now store DICOM files.
 
@@ -92,11 +92,11 @@ DicomWebResponse response = await client.StoreAsync(new[] { dicomFile }, "1.2.82
 
 Before moving on to the next part of the tutorial, upload the `green-square.dcm` file using either of the preceding methods.
 
-## Retrieving DICOM instance(s) (WADO)
+## Retrieve DICOM instance (WADO)
 
-The following code snippets will demonstrate how to perform each of the retrieve queries using the DicomWebClient created previously.
+The code snippets show how to perform each of the retrieve queries using the DicomWebClient created previously.
 
-The following variables will be used throughout the rest of the examples:
+The variables are used throughout the rest of the examples:
 
 ```c#
 string studyInstanceUid = "1.2.826.0.1.3680043.8.498.13230779778012324449356534479549187420"; //StudyInstanceUID for all 3 examples
@@ -106,8 +106,6 @@ string sopInstanceUid = "1.2.826.0.1.3680043.8.498.47359123102728459884412887463
 
 ### Retrieve all instances within a study
 
-Retrieve all instances within a study retrieves all instances within a single study.
-
 _Details:_
 
 * GET /studies/{study}
@@ -348,7 +346,7 @@ _Details:_
 DicomWebResponse response = await client.DeleteSeriesAsync(studyInstanceUid, seriesInstanceUid);
 ```
 
-This response deletes the green-square instance (it's the only element left in the series) from the server. If it's successful, the response status code will contain no content.
+This response deletes the green-square instance (it's the only element left in the series) from the server. If it's successful, the response status code contains no content.
 
 ### Delete a specific study
 
@@ -364,9 +362,4 @@ DicomWebResponse response = await client.DeleteStudyAsync(studyInstanceUid);
 
 This response deletes the blue-circle instance (it's the only element left in the series) from the server. If it's successful, the response status code contains no content.
 
-### Next Steps
-
-For information about the DICOM service, see
-
->[!div class="nextstepaction"]
->[Overview of the DICOM service](dicom-services-overview.md)
+[!INCLUDE [DICOM trademark statement](../includes/healthcare-apis-dicom-trademark.md)]