Skip to main content

Module dicom_source

Module dicom_source 

Source
Expand description

Exact original Part-10 custody, independent of pixel extraction/decoding.

Callers must exclusively control the storage root during publication. Paths are checked for containment and symlinks, but this is not an OS sandbox against an adversary concurrently replacing directory entries. Publication is write-once; retained objects are not a multi-file transaction with the existing pixel/WAL store.

Structs§

AcquisitionView
Both views borrow the retained source snapshot, not a reconstructed pixel file.
DicomIngestWithSource
Additive result; the existing public series-record layout stays unchanged.
DicomSourceArtifact
DicomSourceBudget
Admission limit for one original source object, before reading or publication. This is not an aggregate disk quota or a bound on metadata-parser scratch.
RetainedDicom
Cold-path acquisition owner. The source and byte identity cannot be replaced through this API after publication. Unsupported interpretation does not discard the original. This is not an IOD-conformance or clinical-validity assertion.

Enums§

DicomSourceError

Functions§

archive_part10_source
Archive original Part-10 bytes under explicit admission, independent of the current pixel/metadata parser. Only the preamble’s DICM marker is recognized; this does not establish dataset validity, SOP coverage, or pixel decoding. Unsupported transfer syntaxes and non-pixel objects remain exact originals.
source_for_record
Resolve a successful ingest’s durable association and verify the whole original object’s final-byte BLAKE3 before returning its canonical path. This also works for records obtained from the existing asynchronous worker snapshot/status APIs.
split_ingest_sync_with_source
Ingest admitted original bytes unchanged, preserving full source custody before reporting success. Pixel bytes retain the existing append-only representation. Metadata/encapsulated payloads are not decoded, deidentified or reserialized. On later pixel/WAL/registry failure an admitted immutable source may remain; this is not a transaction or aggregate retention/garbage-collection policy.