Storage
Images and metadata
Evidence required before publicationAI / IMAGING
Governed assistance for professionals; no claims of autonomous diagnosis, guaranteed outcomes or regulatory approval.
Images and metadata
Evidence required before publicationReview visualization
Evidence required before publicationPrioritization support; no autonomous diagnosis
Evidence required before publicationDecision remains with the clinician
Evidence required before publicationMedical Imaging should preserve the identifiers and access context that let a viewer, report and external PACS refer to the same imaging episode without flattening everything into generic files.
Bind study identifiers, patient/encounter context, modality and acquisition time according to the deployed integration profile.
Preserve hierarchy and SOP/object identifiers needed for retrieval, viewer navigation and evidence; do not rename away source identity.
Viewer access is authorization-controlled and linked to report/worklist context; rendering does not change the authoritative imaging object.
DICOM/DICOMweb operations, PACS endpoints and supported modalities remain integration-dependent until verified for the deployment.
The workflow exposes where identifiers, authorization and evidence cross system boundaries.
Controls must address not only API authorization but also bulk transfer, viewer sessions, cache/export behavior and retention.
Scope access by user/workspace/patient context and avoid broad repository access where a narrower study context is sufficient.
Protect transport and make local/browser cache or export behavior explicit; sensitive imaging must not persist accidentally on shared workstations.
Record access, retrieval/export and material state-changing actions with correlation to user/session and imaging identifiers.
Align object, report, derived image and backup retention with the applicable repository policy and legal/clinical requirements.