dicom-rs
dicom-rs copied to clipboard
Tracker issue for standard data dictionaries
Let this issue be used to keep track of how the project is currently encoding and providing data dictionaries, as specified in DICOM PS3.6 - Data Dictionary.
- [x] File Meta group attributes
- Available, manually introduced
- [x] Command elements
- Defined in PS3.7 chapter E
- Available just like any other standard data element, via #8
- [x] Data element / Attributes (tags to name plus info such as VR and VM)
- API in
dicom-core - Currently provided at run-time by the
dicom-dictionary-stdcrate. - [x] Code constants to Tag instances
- API in
- [x] Transfer Syntax unique identifiers
- Registry in
transfer-syntax-registry - Can retrieve implementation status and TS name by UID
- [x] See if this can be easily integrated with dcmdump, so as to present the alias instead of the UID (resolved in #61)
- Registry in
- [x] SOP Class dictionary
- [ ] Directory Structuring Elements
- Not implemented, should probably be done alongside an implementation of DICOMDIR.
- [ ] Other unique identifiers: Context Group values, LDAP OID, Frames of Reference, Coding Schemes, ...
- Only implemented as UID constants
- [ ] Dynamic RTP Payload Elements
- Not implemented, very specific to RTP payloads
- [ ] Color palettes
- Not implemented, not worth thinking about before writing the pixel data abstraction (see #31).