Attribution

Data Sources & Licensing

Every fact on this site is sourced from an authoritative upstream — NEMA, HL7, IHE, cloud vendor docs, or an OSS project. This page lists each source, its license, and how we use it.

NEMA DICOM® Standard

License: © NEMA, all rights reserved. Factual content (tag IDs, keywords, VRs, VMs, type constraints) is used under the factual-data doctrine (Feist 1991). Short prose descriptions are used verbatim under fair use (17 USC § 107, educational/reference purpose) with attribution.

Used for: the entire PS3 data dictionary, module tables, CIOD definitions, SOP class UIDs, transfer syntax UIDs, and the short prose definitions on each attribute page.

Source: dicom.nema.org/medical/dicom/current/

Trademark: DICOM® is a registered trademark of the National Electrical Manufacturers Association.

HL7 FHIR Specification

License: CC0 1.0 (No Rights Reserved).

Used for: the FHIR ImagingStudy resource mapping block on each attribute page.

Source: hl7.org/fhir/imagingstudy-mappings.html

IHE Technical Framework

License: Royalty-free reproduction license from IHE. Factual mapping data used; original IHE prose not reproduced.

Used for: DICOM ↔ HL7 v2 mapping pairs.

Source: profiles.ihe.net/RAD/TF/

Cloud Vendor DICOM Conformance

License: Support-status data (which attributes are supported by AWS HealthImaging, Azure Health Data Services DICOM, Google Cloud Healthcare API) is factual and not copyrightable. Vendor explanatory prose is not reproduced.

Sources:

OSS DICOM Libraries (Reference / Cross-Validation)

  • dcmjs — MIT. Used for dictionary cross-validation.
  • pydicom — MIT (with BSD portions in private-dict files). Used for cross-validation.
  • innolitics/dicom-standard — MIT. Used for spot-check parity comparisons only; no code or data imported.

Mirth Connect Snippets & Operational Error Notes

The Mirth Connect transformer snippets and common operational error blocks under each attribute's Integration Notes are reference material drawn from our production DICOM/HL7v2 integration experience — starting points, not production-grade drop-ins.

Always validate before deploying. Every integration environment is different. Before using any snippet or acting on an error scenario:

Saga IT provides these snippets and notes with no warranty.

Corrections & Rights Inquiries

If you're a rights holder and see content you'd like corrected or removed, please email info@saga-it.com. We take these requests seriously and will respond as quickly as we can.