Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Optionally encode DS, IS, SV or UV values as JSON Number #2922

Closed
gunterze opened this issue Dec 16, 2020 · 0 comments
Closed

Optionally encode DS, IS, SV or UV values as JSON Number #2922

gunterze opened this issue Dec 16, 2020 · 0 comments
Assignees
@vrindanayak
Labels
enhancement New feature or request
Milestone
5.23.1

Comments

@gunterze
Copy link
Member

gunterze commented Dec 16, 2020 •
edited
Loading

Configurable by

Name Type Description (LDAP Attribute)
Encode as JSON Number(s) string VR encoded as JSON Number. If not listed, IS, DS, SV and UV values are encoded as JSON Strings. Enumerated values: IS, DS, SV, UV.
(dcmEncodeAsJSONNumber)

on Archive Device or Archive Network AE level

Rationale: There are DICOM JSON implementations (e.g. ohif-vewer) which are not compliant to CP 1861 ftp://medical.nema.org/medical/dicom/final/cp1861_ft_changeJSONvaluetypemappingISandDS.pdf

Related dcm4che/dcm4che#803
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vrindanayak vrindanayak

Labels
enhancement New feature or request
Projects
None yet
Milestone
5.23.1
Development

No branches or pull requests
2 participants
@gunterze @vrindanayak