markdown and edit updates, author update

KendalBond007 · KendalBond007 · commit 7c0e42c39b67 · 2024-08-29T12:38:09.000-07:00
diff --git a/articles/healthcare-apis/dicom/dicom-services-conformance-statement.md b/articles/healthcare-apis/dicom/dicom-services-conformance-statement.md
@@ -2,12 +2,12 @@
 title: DICOM Conformance Statement version 1 for Azure Health Data Services
 description: Read about the features and specifications of the DICOM service v1 API, which supports a subset of the DICOMweb Standard for medical imaging data. A DICOM Conformance Statement is a technical document that describes how a device or software implements the DICOM standard.
 services: healthcare-apis
-author: mmitrik
+author: varunbms
 ms.service: azure-health-data-services
 ms.subservice: dicom-service
 ms.topic: reference
 ms.date: 10/13/2023
-ms.author: mmitrik
+ms.author: varunbms
 ---
 
 # DICOM Conformance Statement v1
@@ -30,7 +30,7 @@ The Medical Imaging Server for DICOM&reg; supports a subset of the DICOMweb Stan
     * [Request Cancellation](#request-cancellation)
     * [Search Workitems](#search-workitems)
 
-Additionally, the following nonstandard API(s) are supported:
+Additionally, the following nonstandard APIs are supported:
 
 * [Change Feed](change-feed-overview.md)
 * [Extended Query Tags](dicom-extended-query-tags-overview.md)
@@ -393,7 +393,7 @@ We support the following matching types.
 
 | Search Type | Supported Attribute | Example |
 | ----------- | ------------------- | ------- |
-| Range Query | `StudyDate`/`PatientBirthDate` | `{attributeID}={value1}-{value2}`. For date/time values, we support an inclusive range on the tag. This is mapped to `attributeID >= {value1} AND attributeID <= {value2}`. If `{value1}` isn't specified, all occurrences of dates/times prior to and including `{value2}` are matched. Likewise, if `{value2}` isn't specified, all occurrences of `{value1}` and subsequent dates/times are matched. However, one of these values has to be present. `{attributeID}={value1}-` and `{attributeID}=-{value2}` are valid, however, `{attributeID}=-` is invalid. |
+| Range Query | `StudyDate`/`PatientBirthDate` | `{attributeID}={value1}-{value2}`. For date/time values, we support an inclusive range on the tag, which is mapped to `attributeID >= {value1} AND attributeID <= {value2}`. If `{value1}` isn't specified, all occurrences of dates/times prior to and including `{value2}` are matched. Likewise, if `{value2}` isn't specified, all occurrences of `{value1}` and subsequent dates/times are matched. However, one of these values has to be present. `{attributeID}={value1}-` and `{attributeID}=-{value2}` are valid, however, `{attributeID}=-` is invalid. |
 | Exact Match | All supported attributes | `{attributeID}={value1}` |
 | Fuzzy Match | `PatientName`, `ReferringPhysicianName` | Matches any component of the name that starts with the value. |
 
@@ -406,7 +406,7 @@ Tags can be encoded in several ways for the query parameter. We have partially i
 | `{group}{element}` | `0020000D`         |
 | `{dicomKeyword}`   | `StudyInstanceUID` |
 
-Here is an example query searching for instances:
+Here's an example query searching for instances:
 
 `../instances?Modality=CT&00280011=512&includefield=00280010&limit=5&offset=0`
 
@@ -659,7 +659,7 @@ This transaction retrieves a Workitem. It corresponds to the UPS DIMSE N-GET ope
 
 Refer to: https://dicom.nema.org/medical/dicom/current/output/html/part18.html#sect_11.5
 
-If the Workitem exists on the origin server, the Workitem will be returned in an Acceptable Media Type. The returned Workitem will not contain the Transaction UID (0008,1195) Attribute. This is necessary to preserve the attribute's role as an access lock.
+If the Workitem exists on the origin server, the Workitem is returned in an Acceptable Media Type. The returned Workitem won't contain the Transaction UID (0008,1195) Attribute. This is necessary to preserve the attribute's role as an access lock.
 
 | Method  | Path                    | Description   |
 | ------- | ----------------------- | ------------- |
@@ -680,15 +680,15 @@ The `Accept` header is required and must have the value `application/dicom+json`
 #### Retrieve Workitem response payload
 
 * A success response has a single part payload containing the requested Workitem in the Selected Media Type.
-* The returned Workitem will not contain the Transaction UID (0008, 1195) attribute of the Workitem, since that should only be known to the Owner.
+* The returned Workitem won't contain the Transaction UID (0008, 1195) attribute of the Workitem, since that should only be known to the Owner.
 
 ### Update Workitem
 
 This transaction modifies attributes of an existing Workitem. It corresponds to the UPS DIMSE N-SET operation.
 
 Refer to: https://dicom.nema.org/medical/dicom/current/output/html/part18.html#sect_11.6
 
-To update a Workitem currently in the `SCHEDULED` state, the `Transaction UID` attribute should not be present. For a Workitem in the `IN PROGRESS` state, the request must include the current Transaction UID as a query parameter. If the Workitem is already in the `COMPLETED` or `CANCELED` states, the response is `400 (Bad Request)`.
+To update a Workitem currently in the `SCHEDULED` state, the `Transaction UID` attribute shouldn't be present. For a Workitem in the `IN PROGRESS` state, the request must include the current Transaction UID as a query parameter. If the Workitem is already in the `COMPLETED` or `CANCELED` states, the response is `400 (Bad Request)`.
 
 | Method  | Path                            | Description           |
 | ------- | ------------------------------- | --------------------- |
@@ -723,9 +723,9 @@ found in [this table](https://dicom.nema.org/medical/dicom/current/output/html/p
 
 #### Update Workitem transaction response payload
 
-The origin server will support header fields as required in [Table 11.6.3-2](https://dicom.nema.org/medical/dicom/current/output/html/part18.html#table_11.6.3-2).
+The origin server supports header fields as required in [Table 11.6.3-2](https://dicom.nema.org/medical/dicom/current/output/html/part18.html#table_11.6.3-2).
 
-A success response will have either no payload, or a payload containing a Status Report document.
+A success response has either no payload, or a payload containing a Status Report document.
 
 A failure response payload might contain a Status Report describing any failures, warnings, or other useful information.
 
@@ -735,17 +735,17 @@ This transaction is used to change the state of a Workitem. It corresponds to th
 
 Refer to: https://dicom.nema.org/medical/dicom/current/output/html/part18.html#sect_11.7
 
-If the Workitem exists on the origin server, the Workitem will be returned in an Acceptable Media Type. The returned Workitem will not contain the Transaction UID (0008,1195) attribute. This is necessary to preserve this Attribute's role as an access lock as described [here.](https://dicom.nema.org/medical/dicom/current/output/html/part04.html#sect_CC.1.1)
+If the Workitem exists on the origin server, the Workitem is returned in an Acceptable Media Type. The returned Workitem won't contain the Transaction UID (0008,1195) attribute. This is necessary to preserve this Attribute's role as an access lock as described [here.](https://dicom.nema.org/medical/dicom/current/output/html/part04.html#sect_CC.1.1)
 
 | Method  | Path                            | Description           |
 | ------- | ------------------------------- | --------------------- |
 | PUT     | ../workitems/{workitem}/state	| Change Workitem State	|
 
 The `Accept` header is required, and must have the value `application/dicom+json`.
 
-The request payload will contain the Change UPS State Data Elements. These data elements are:
+The request payload contains the Change UPS State Data Elements. These data elements are:
 
-* **Transaction UID (0008, 1195)**. The request payload will include a Transaction UID. The user agent creates the Transaction UID when requesting a transition to the `IN PROGRESS` state for a given Workitem. The user agent provides that Transaction UID in subsequent transactions with that Workitem.
+* **Transaction UID (0008, 1195)**. The request payload includes a Transaction UID. The user agent creates the Transaction UID when requesting a transition to the `IN PROGRESS` state for a given Workitem. The user agent provides that Transaction UID in subsequent transactions with that Workitem.
 * **Procedure Step State (0074, 1000)**. The legal values correspond to the requested state transition. They are: `IN PROGRESS`, `COMPLETED`, or `CANCELED`.
 
 #### Change Workitem state response status codes
@@ -762,7 +762,7 @@ The request payload will contain the Change UPS State Data Elements. These data
 #### Change Workitem state response payload
 
 * Responses include the header fields specified in [section 11.7.3.2](https://dicom.nema.org/medical/dicom/current/output/html/part18.html#sect_11.7.3.2).
-* A success response will have no payload.
+* A success response has no payload.
 * A failure response payload might contain a Status Report describing any failures, warnings, or other useful information.
 
 ### Search Workitems
@@ -781,7 +781,7 @@ The following `Accept` header is supported for searching.
 
 The following parameters for each query are supported.
 
-| Key              | Support Value(s)              | Allowed Count | Description |
+| Key              | Support Values              | Allowed Count | Description |
 | ---------------- | ----------------------------- | ------------- | ----------- |
 | `{attributeID}=` | `{value}`                     | 0...N         | Search for attribute/ value matching in query |
 | `includefield=`  | `{attributeID}`<br/>`all`     | 0...N         | The other attributes to return in the response; Only top-level attributes can be included - not attributes that are part of sequences. Both public and private tags are supported. When `all` is provided, see [Search Response](#search-response) for more information about which attributes are returned for each query type. If a mixture of `{attributeID}` and `all` is provided, the server defaults to using 'all'. |
diff --git a/articles/healthcare-apis/dicom/dicomweb-standard-apis-c-sharp.md b/articles/healthcare-apis/dicom/dicomweb-standard-apis-c-sharp.md
@@ -1,12 +1,12 @@
 ---
 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
+author: varunbms
 ms.service: azure-health-data-services
 ms.subservice: dicom-service
 ms.topic: tutorial
 ms.date: 10/18/2023
-ms.author: mmitrik
+ms.author: varunbms
 ---
 
 # Use C# and DICOMweb Standard APIs
@@ -79,7 +79,7 @@ DicomWebResponse response = await client.StoreAsync(new[] { dicomFile });
 
 ### Store instances for a specific study
 
-Store instances for a specific study demonstrate how to upload a DICOM file into a specified study.
+Store instances for a specific study demonstrates how to upload a DICOM file into a specified study.
 
 _Details:_
 
@@ -96,7 +96,7 @@ Before moving on to the next part of the tutorial, upload the `green-square.dcm`
 
 The code snippets show how to perform each of the retrieve queries using the DicomWebClient created previously.
 
-The variables are 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
@@ -174,7 +174,7 @@ _Details:_
 DicomWebResponse response = await client.RetrieveSeriesMetadataAsync(studyInstanceUid, seriesInstanceUid);
 ```
 
-This series has two instances (green-square and red-triangle), so the response should return metadata for both instances. Validate that the response has a status code of OK and that both instances of the metadata are returned.
+The series has two instances (green-square and red-triangle), so the response should return metadata for both instances. Validate that the response has a status code of OK and that both instances of the metadata are returned.
 
 ### Retrieve a single instance within a series of a study
 
@@ -188,7 +188,7 @@ _Details:_
 DicomWebResponse response = await client.RetrieveInstanceAsync(studyInstanceUid, seriesInstanceUid, sopInstanceUid);
 ```
 
-This response should only return the instance red-triangle. Validate that the response has a status code of OK and that the instance is returned.
+The response should only return the instance red-triangle. Validate that the response has a status code of OK and that the instance is returned.
 
 ### Retrieve metadata of a single instance within a series of a study
 
@@ -202,7 +202,7 @@ _Details:_
 DicomWebResponse response = await client.RetrieveInstanceMetadataAsync(studyInstanceUid, seriesInstanceUid, sopInstanceUid);
 ```
 
-This response should only return the metadata for the instance red-triangle. Validate that the response has a status code of OK and that the metadata is returned.
+The response should only return the metadata for the instance red-triangle. Validate that the response has a status code of OK and that the metadata is returned.
 
 ### Retrieve one or more frames from a single instance
 
@@ -217,7 +217,7 @@ DicomWebResponse response = await client.RetrieveFramesAsync(studyInstanceUid, s
 
 ```
 
-This response should return the only frame from the red-triangle. Validate that the response has a status code of OK and that the frame is returned.
+The response should return the only frame from the red-triangle. Validate that the response has a status code of OK and that the frame is returned.
 
 ## Query DICOM (QIDO)
 
@@ -237,7 +237,7 @@ string query = $"/studies?StudyInstanceUID={studyInstanceUid}";
 DicomWebResponse response = await client.QueryStudyAsync(query);
 ```
 
-Validates that the response includes one study, and that the response code is OK.
+Validate that the response includes one study, and that the response code is OK.
 
 ### Search for series
 
@@ -252,7 +252,7 @@ string query = $"/series?SeriesInstanceUID={seriesInstanceUid}";
 DicomWebResponse response = await client.QuerySeriesAsync(query);
 ```
 
-Validates that the response includes one series, and that the response code is OK.
+Validate that the response includes one series, and that the response code is OK.
 
 ### Search for series within a study
 
@@ -267,7 +267,7 @@ string query = $"/studies/{studyInstanceUid}/series?SeriesInstanceUID={seriesIns
 DicomWebResponse response = await client.QueryStudySeriesAsync(studyInstanceUid, query);
 ```
 
-Validates that the response includes one series, and that the response code is OK.
+Validate that the response includes one series, and that the response code is OK.
 
 ### Search for instances
 
@@ -282,7 +282,7 @@ string query = $"/instances?SOPInstanceUID={sopInstanceUid}";
 DicomWebResponse response = await client.QueryInstancesAsync(query);
 ```
 
-Validates that the response includes one instance, and that the response code is OK.
+Validate that the response includes one instance, and that the response code is OK.
 
 ### Search for instances within a study
 
@@ -297,7 +297,7 @@ string query = $"/studies/{studyInstanceUid}/instances?SOPInstanceUID={sopInstan
 DicomWebResponse response = await client.QueryStudyInstanceAsync(studyInstanceUid, query);
 ```
 
-Validates that the response includes one instance, and that the response code is OK.
+Validate that the response includes one instance, and that the response code is OK.
 
 ### Search for instances within a study and series
 
@@ -312,7 +312,7 @@ string query = $"/studies/{studyInstanceUid}/series/{seriesInstanceUid}/instance
 DicomWebResponse response = await client.QueryStudySeriesInstanceAsync(studyInstanceUid, seriesInstanceUid, query);
 ```
 
-Validates that the response includes one instance, and that the response code is OK.
+Validate that the response includes one instance, and that the response code is OK.
 
 ## Delete DICOM
 
@@ -332,7 +332,7 @@ string sopInstanceUidRed = "1.2.826.0.1.3680043.8.498.47359123102728459884412887
 DicomWebResponse response = await client.DeleteInstanceAsync(studyInstanceUid, seriesInstanceUid, sopInstanceUidRed);
 ```
 
-This repose deletes the red-triangle instance from the server. If it's successful, the response status code contains no content.
+This reponse deletes the red-triangle instance from the server. If it's successful, the response status code contains no content.
 
 ### Delete a specific series within a study
 
@@ -346,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 contains no content.
+The response deletes the green-square instance from the server (it's the only element left in the series). If it's successful, the response status code contains no content.
 
 ### Delete a specific study
 
@@ -360,6 +360,6 @@ _Details:_
 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.
+The response deletes the blue-circle instance from the server (it's the only element left in the series). If it's successful, the response status code contains no content.
 
 [!INCLUDE [DICOM trademark statement](../includes/healthcare-apis-dicom-trademark.md)]
