Workflow integration

Keep a record of each remote correction in the Orthanc archive

Leave a line beside each corrected study in Orthanc saying when it was corrected, by which dcmage build, and which tags changed.

Desktop app only, 1.6.0 or newerdcmage pro

Problem

dcmage’s audit log stays on the computer that made the correction. Whoever administers the archive later sees a study that changed, with nothing in the archive saying when, how, or whether the change was checked.

Steps

  1. Ask the archive’s administrator to declare the record in Orthanc’s configuration:

    "UserMetadata": { "DcmageCorrection": 1024 }

    The number is the metadata’s index; 1024 is the first one Orthanc allows. Orthanc reads the setting at start, so it takes a restart.

  2. Commit corrections as usual. After each commit has been checked, dcmage adds one line to the corrected study’s DcmageCorrection metadata. A batch adds one line to each study.

What a line holds

The time, the dcmage version, whether the commit was verified, the archive’s resource for the study before and after, whether the identifiers were kept or regenerated, the names of the tags that changed, and whether the patient changed. It never holds a value, old or new. A line is at most 512 characters; when the list of tags would not fit, it gives their number instead.

Orthanc drops the metadata when it regenerates a study, so the line goes on the corrected study, not the one it replaced. A study corrected in place keeps its earlier lines, and the oldest ones go once the record passes 8 KB.

Result

Below the commit result, dcmage says whether the line was recorded in the study’s DcmageCorrection metadata, that the archive declares no such metadata, or why the archive refused the line. The record never changes the commit’s own result: a verified commit stays verified when the line could not be kept, so there is no reason to commit again. DICOMweb and DIMSE archives have no such record, so a corrected copy stored there gets none.