Commit one correction to several remote studies
Send the same study-level correction to up to 50 studies on an Orthanc archive, each one checked before the next is sent.
Desktop app only, 1.6.0 or newerdcmage pro
Problem
The same mistake often reaches many studies at once: a modality sent the wrong institution name for a week, or a protocol left the same wrong description on every study it produced. Opening, correcting and committing each study by hand repeats the same edit dozens of times, and one slip in one of them leaves that study different from the rest.
Steps
-
Search the archive and tick the studies to correct in the results list. The tick boxes appear only on an Orthanc connection, which is the one archive that can replace a study without keeping a duplicate. A batch holds from 2 to 50 studies.
-
Select Correct N studies together. dcmage reads every ticked study, then opens the first one in the workspace. If any of them cannot be read, nothing opens.
-
Correct the study-level tags of the opened study in the tag editor. These edits are the correction for the whole batch.
-
Open the change preview. It lists the opened study’s changes as a single commit would, then a table of every study in the batch with its Study Instance UID, date, instance count, and the value it holds today for each tag you changed. Read that column before you commit: it is what each study is about to lose.
-
Select Commit correction to N studies. dcmage commits the studies one after another. Each study is read again just before it is written, committed as a single commit would be, and judged by the same five checks.
When a study is not verified
The run stops at that study, and the studies after it are not sent. Read its result first. If you decide the rest should still go, Continue with the remaining N sends only the studies that were never sent. The study that stopped the run is not sent again from the batch; open it on its own to check the archive and retry it there.
The remaining studies only go with the edits the run started with. If you change the edits after the run stops, the review says so and offers no way to continue. Put the edits back and the button returns.
When a study changed after the review
If a study gained or lost an instance, or was filed under another patient, between the review and its write, dcmage sends nothing to it and says what changed. The run stops there as it would for any study that is not verified.
What a batch cannot do
A batch carries study-level values only. A series-level value such as Laterality belongs to one series of the opened study, and no other study has that series, so the preview refuses the batch and asks you to correct series values one study at a time. A batch can file its studies under another Patient ID (see Move several remote studies to another patient in one batch), but it cannot change the name, birth date or sex a Patient ID is filed under. That goes to every study of the patient at once (see Correct the patient details of every remote study filed under one Patient ID). A batch also commits on Orthanc only: it does not store corrected copies or send IOCM rejection notes.
A batch sends tags only, as a single commit does. If the opened study holds changed pixels or a redaction box, the preview refuses the batch and says so in place of the button. Undo the change, or delete the box in Anon mode, or export the file instead.
Result
Each study in the batch reads Verified, Not verified with the checks that failed, Failed with the reason, Changed since review, or Not sent, and the run says how many of them were verified. The audit log records each commit, and where the run stopped and why. Where the archive declares the DcmageCorrection metadata, each study also gets its own line in it, and each row says whether it did.