This Application Profile is based on the Media Storage Service Class (see PS3.4).
Table G.3-1. STD-GEN-MIME SOP Classes and Transfer Syntaxes
|
Information Object Definition |
SOP Class UID |
Transfer Syntax and UID |
FSC Requirement |
FSR Requirement |
|---|---|---|---|---|
|
Basic Directory |
1.2.840.10008.1.3.10 |
Explicit VR Little Endian Uncompressed 1.2.840.10008.1.2.1 |
Optional |
Optional |
|
Composite Image & Stand-alone Storage |
See PS3.4 |
Defined in Conformance Statement |
Defined in Conformance Statement |
Defined in Conformance Statement |
The SOP Classes and corresponding Transfer Syntax supported by this Application Profile are specified in the Table G.3-1. The supported Storage SOP Class(es) and Transfers Syntax(es) shall be listed in the Conformance Statement using a table of the same form.
The STD-GEN-MIME application profile requires the DICOM MIME medium as defined in PS3.12.
If the DICOMDIR is included, conformant Application Entities shall include in it the Basic Directory IOD containing Directory Records at the Patient and the subsidiary Study and Series levels, appropriate to the SOP Classes in the File Set.
All DICOM files in the File Set incorporating SOP Instances defined for the specific Application Profile shall be referenced by Directory Records.
DICOMDIRs with no directory information are not allowed by this Application Profile.
In the DICOMDIR each object may be referenced by a referenced file ID (e.g., 000/000) that contains multiple values corresponding to a path for physical system, since the MIME organization is flat. There is no requirement that this path will be used by the receiving application to create file hierarchy.
There may only be one DICOMDIR file per File Set. The Patient ID at the patient level shall be unique for each patient directory record in one File Set.