Skip to content

Commit 686cfa2

Browse files
author
Gunjit Chhatwal
committed
included acrolinx suggestions to get required score
1 parent 350de03 commit 686cfa2

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

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

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -69,11 +69,11 @@ This transaction uses the POST or PUT method to store representations of studies
6969

7070
Parameter `study` corresponds to the DICOM attribute StudyInstanceUID. If specified, any instance that doesn't belong to the provided study is rejected with a `43265` warning code.
7171

72-
The following `Accept` header(s) for the response are supported:
72+
The following `Accept` headers for the response are supported:
7373

7474
* `application/dicom+json`
7575

76-
The following `Content-Type` header(s) are supported:
76+
The following `Content-Type` headers are supported:
7777

7878
* `multipart/related; type="application/dicom"`
7979
* `application/dicom`
@@ -309,7 +309,7 @@ This Retrieve Transaction offers support for retrieving stored studies, series,
309309

310310
#### Retrieve instances within study or series
311311

312-
The following `Accept` header(s) are supported for retrieving instances within a study or a series:
312+
The following `Accept` headers are supported for retrieving instances within a study or a series:
313313

314314

315315
* `multipart/related; type="application/dicom"; transfer-syntax=*`
@@ -320,7 +320,7 @@ The following `Accept` header(s) are supported for retrieving instances within a
320320

321321
#### Retrieve an Instance
322322

323-
The following `Accept` header(s) are supported for retrieving a specific instance:
323+
The following `Accept` headers are supported for retrieving a specific instance:
324324

325325
* `application/dicom; transfer-syntax=*`
326326
* `multipart/related; type="application/dicom"; transfer-syntax=*`
@@ -387,7 +387,7 @@ Cache validation is supported using the `ETag` mechanism. In the response to a m
387387

388388
### Retrieve rendered image (for instance or frame)
389389

390-
The following `Accept` header(s) are supported for retrieving a rendered image an instance or a frame:
390+
The following `Accept` headers are supported for retrieving a rendered image an instance or a frame:
391391

392392
- `image/jpeg`
393393
- `image/png`
@@ -440,7 +440,7 @@ Query based on ID for DICOM Objects (QIDO) enables you to search for studies, se
440440
| GET | ../studies/{study}/instances?... | Search for instances in a study |
441441
| GET | ../studies/{study}/series/{series}/instances?... | Search for instances in a series |
442442

443-
The following `Accept` header(s) are supported for searching:
443+
The following `Accept` headers are supported for searching:
444444

445445
* `application/dicom+json`
446446

@@ -456,7 +456,7 @@ An attribute can be corrected in the following ways:
456456

457457
The following parameters for each query are supported:
458458

459-
| Key | Support Value(s) | Allowed Count | Description |
459+
| Key | Support values | Allowed Count | Description |
460460
| :--------------- | :------------------------ | :------------ | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
461461
| `{attributeID}=` | `{value}` | 0...N | Search for attribute/ value matching in query. |
462462
| `includefield=` | `{attributeID}`<br/>`all` | 0...N | The other attributes to return in the response. Both, public and private tags are supported.<br/>When `all` is provided, refer to [Search Response](#search-response) for more information.<br/>If a mixture of `{attributeID}` and `all` is provided, the server defaults to using `all`. |
@@ -892,15 +892,15 @@ This transaction enables you to search for Workitems by attributes.
892892
| :----- | :------------ | :------------------- |
893893
| GET | ../workitems? | Search for Workitems |
894894

895-
The following `Accept` header(s) are supported for searching:
895+
The following `Accept` headers are supported for searching:
896896

897897
* `application/dicom+json`
898898

899899
#### Supported Search Parameters
900900

901901
The following parameters for each query are supported:
902902

903-
| Key | Support Value(s) | Allowed Count | Description |
903+
| Key | Support values | Allowed Count | Description |
904904
| :--------------- | :------------------------ | :------------ | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
905905
| `{attributeID}=` | `{value}` | 0...N | Search for attribute/ value matching in query. |
906906
| `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'. |

0 commit comments

Comments
 (0)