Skip to content

Commit 58763ac

Browse files
author
Gunjit Chhatwal
committed
formatting changes
1 parent 366cff2 commit 58763ac

File tree

1 file changed

+16
-16
lines changed

1 file changed

+16
-16
lines changed

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

Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -491,12 +491,12 @@ We support searching the following attributes and search types.
491491

492492
We support the following matching types.
493493

494-
| Search Type | Supported Attribute | Example |
495-
| :------------- | :-------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
496-
| Range Query | `StudyDate`/`PatientBirthDate` | `{attributeID}={value1}-{value2}`. For date/ time values, we support an inclusive range on the tag. This range 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. |
497-
| Exact Match | All supported attributes | `{attributeID}={value1}` |
498-
| Fuzzy Match | `PatientName`, `ReferringPhysicianName` | Matches any component of the name that starts with the value. |
499-
| UID List Match | `StudyInstanceUID` | Matches studies identified by the values provided in the list. Supports comma (,) or a backslash (\\) as a valid separator. `{attributeID}=1.2.3,5.6.7,8.9.0` will return details associated with all the studies, given they exist. |
494+
| Search Type | Supported Attribute | Example |
495+
| ----------- | ------------------- | -------------------------------------------------------------- |
496+
| Range Query | `StudyDate`/`PatientBirthDate` | `{attributeID}={value1}-{value2}`. For date/time values, we support an inclusive range on the tag. This range 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. |
497+
| Exact Match | All supported attributes | `{attributeID}={value1}` |
498+
| Fuzzy Match | `PatientName`, `ReferringPhysicianName` | Matches any component of the name that starts with the value |
499+
| UID List Match | `StudyInstanceUID` | Matches studies identified by the values provided in the list. Supports comma (,) or a backslash (\\) as a valid separator. `{attributeID}=1.2.3,5.6.7,8.9.0` will return details associated with all the studies, given they exist. |
500500

501501
#### Attribute ID
502502

@@ -608,16 +608,16 @@ The following attributes are returned.
608608

609609
The query API returns one of the following status codes in the response.
610610

611-
| Code | Description |
612-
| :-------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
613-
| `200 (OK)` | The response payload contains all the matching resources. |
614-
| `204 (No Content)` | The search completed successfully but returned no results. |
615-
| `400 (Bad Request)` | The server was unable to perform the query because the query component was invalid. Response body contains details of the failure. |
616-
| `401 (Unauthorized)` | The client isn't authenticated. |
617-
| `403 (Forbidden)` | The user isn't authorized. |
618-
| `414 (URI Too Long)` | URI exceeded maximum supported length. |
619-
| `424 (Failed Dependency)` | The DICOM service cannot access a resource it depends on to complete this request. An example is failure to access the connected Data Lake store, or the key vault for supporting customer-managed key encryption. |
620-
| `503 (Service Unavailable)` | The service is unavailable or busy. Try again later. |
611+
| Code | Description |
612+
| -------------------------- | ------------------------------------------------------------- |
613+
| `200 (OK)` | The response payload contains all the matching resources. |
614+
| `204 (No Content)` | The search completed successfully but returned no results. |
615+
| `400 (Bad Request)` | The server was unable to perform the query because the query component was invalid. The response body contains details of the failure. |
616+
| `401 (Unauthorized)` | The client isn't authenticated. |
617+
| `403 (Forbidden)` | The user isn't authorized. |
618+
| `414 (URI Too Long)` | URI exceeded maximum supported length. |
619+
| `424 (Failed Dependency)` | The DICOM service can't access a resource it depends on to complete this request. An example is failure to access the connected Data Lake store, or the key vault for supporting customer-managed key encryption. |
620+
| `503 (Service Unavailable)` | The service is unavailable or busy. Try again later. |
621621

622622
### Notes
623623

0 commit comments

Comments
 (0)