DICOM PS3.18 2024d - Web Services |
---|
The syntax of Media Type usage in DICOM is:
dicom-media-type = (dcm-singlepart / dcm-multipart) [dcm-parameters]
dcm-singlepart = dcm-mt-name
dcm-multipart ;see Section 8.7.3.5.1
dcm-parameters = transfer-syntax-mtp ;see Section 8.7.3.5.2
/ charset-mtp;see Section 8.7.3.5.3
dcm-mt-name = dicom / dicom-metadata / bulkdata / pixeldata ;DICOM Media Type name
dicom = "application/dicom"
dicom-metadata = dicom-xml / dicom-json
dicom-xml = "application/dicom+xml"
dicom-json = "application/dicom+json"
bulkdata = octet-stream / pixeldata
octet-stream = "application/octet-stream"
pixeldata = image-pixel / video-pixel
rendered = image-pixel / video-pixel
image-pixel = "image/jpeg" / "image/dicom-rle" / "image/jls" / "image/jp2" / "image/jpx" / "image/jphc" / "image/jxl"
video-pixel = "video/mpeg" / "video/mp4" / "video/H265"
All Media Types used in DICOM may have a Transfer Syntax parameter, but its usage may be constrained by the service for which they are used.
The application/dicom+xml and application/dicom+json Media Types may have a Transfer Syntax parameter in order to specify the encoding of base64 data.
All Media Types used in DICOM may have a character set parameter, but its usage may be constrained by the service for which they are used.
The syntax of multipart media types is:
dcm-multipart = "multipart/related"
OWS ";" OWS "type" "=" dcm-mp-mt-name
OWS ";" OWS "boundary=" boundary
[dcm-parameters]
[related-parameters]
dcm-mp-mt-name = dicom-mt-name / rendered
See Section 8.6.1.2.1 for the definition of boundary and related-parameters.
Each multipart media type shall include a "type" parameter that defines the media type of the parts and shall also include a "boundary" parameter that specifies the boundary string that is used to separate the parts. For example:
Accept: multipart/related; type="application/octet-stream", multipart/related; type="image/*"; boundary=**, multipart/related; type="video/*"; boundary=**
DICOM PS3.18 2024d - Web Services |
---|