UI reference

Send to archive

See what your edits would send back to the archive, then choose how to send them: a replacement on Orthanc, a corrected copy, or a replacement through IOCM.

Desktop app only, 1.6.0 or newerdcmage pro

Click Send to archive… in the bar under the top bar. Before anything is sent, the window names the archive and the study, and lists every tag you changed, with the archive’s value beside yours. A tag is highlighted when its current value differs between images, because sending writes your value into every image of the study.

A tag you removed shows as Removed, and it is taken out of every image in the same way a changed value is written to all of them. dcmage then checks the archive no longer holds it: on Orthanc it reads every image, and for a copy it reads one image of each series.

A series tag such as Series Description, Laterality or Body Part Examined is sent to the series you changed it in, not to the whole study. The Written to column names that series and how many images it holds, and the check afterwards reads the value back from that series. A study whose only change is a series tag still comes back as a new study with new identifiers, unless you keep them.

When the archive offers more than one way to send, the window asks you to choose. Your choice is fixed once anything has been sent, so the result you read always belongs to the way you chose.

Commit correction is offered on Orthanc and is the default there. dcmage writes your changes, then reads the study back to check that the archive holds one corrected study and no leftover copy. See Commit a corrected remote study.

If the Orthanc archive is set to overwrite stored images, the commit also offers Keep the study’s identifiers. It is off until you tick it. Ticked, the archive writes your changes into the images it holds, under the UIDs they already carry, and the check confirms the study kept them. Tick it only when other records point at the study by its UIDs: a viewer, router or other archive that already received the study keeps its old values under the same UIDs, and nothing tells it the study changed.

When you opened several studies together from the archive window, the commit goes to all of them. Below your changes, a table lists every study with what it holds now for each tag any of them would change. A move to another Patient ID can write a name, birth date or sex you did not edit to a study filed under other details, so those get a column too. Commit correction to N studies sends them one after another, reading each again just before it is written and checking it as a single commit. The run stops at the first study that is not verified, or that gained or lost images since you reviewed it. Continue with the remaining N sends the ones never sent; the study that stopped the run is not sent again from here. Change the edits after the run stops and Continue is refused with the reason; put them back and it returns. A batch takes study tags only, so a series tag change is refused with the reason. A batch can move its studies to another Patient ID after one patient confirmation, but a new name, birth date or sex under the same Patient ID is refused. See Commit one correction to several remote studies and Move several remote studies to another patient in one batch.

When your changes touch the Patient ID, name, birth date or sex, the window warns that every system reading the archive will show the images under the corrected patient, and shows a table: the patient the study is filed under now, after the correction, and in the archive’s record for the corrected Patient ID. Tick I have checked that these images belong to the patient under After correction to send. The box is offered only once the archive’s record is read and agrees, and changing any patient value afterwards asks for it again. See Correct the patient a remote study is filed under.

On Orthanc, with Commit correction chosen, a patient change also offers Correct every study filed under this patient. Tick it and dcmage lists every study the archive files under the patient, each with its UID, description, date, accession number and number of series. Correct N studies sends the four patient details to all of them in one request, after reading the archive again, and only if it still files exactly those studies. Other edited values are refused, because they belong to the opened study. The check afterwards verifies each study it made. See Correct the patient details of every remote study filed under one Patient ID.

On Orthanc, each commit also leaves a line in the corrected study’s DcmageCorrection metadata where the archive’s configuration declares it, and the result says whether it did. The line names the tags that changed, never their values. See Keep a record of each remote correction.

Store corrected copy is offered on every connection: Orthanc, DICOMweb and DIMSE. dcmage sends your corrected version as a new study and leaves the original in the archive, so you delete the original yourself once you have checked the copy. Tick the box to confirm you understand that, then click Store corrected copy. dcmage first reads every file the copy would send, and the window says Checking the files until that ends. Cancel store stops the send part way. If a send stops early, Send the rest finishes the same copy, on the same connection: after a disconnect the archive will not take the rest, so delete the incomplete copy in the PACS and start again. See Re-send after correction and Store instances via STOW-RS.

Replace original is offered on a DICOMweb or DIMSE connection when you ticked, at connect, that the archive removes images when it receives a rejection note for them (an IOCM rejection note). dcmage stores the corrected copy first. Only once the copy is checked does it send the archive a rejection note for the original (Incorrect Modality Worklist Entry), and then it searches the original study again. The result says Replaced only when the archive no longer lists any original image. If the archive still lists them, the result says so and offers Check again, which looks before it sends anything. A refused note leaves the original in place, and the result tells you to delete it in the PACS. The note itself stays in the original study.

dcmage sends tags only. If you changed the pixels of the study (a pixel operation, Replace Pixel Data, a compression change, or an edit to an RT structure set, a segmentation or a structured report), or drew a redaction box on it, the archive would keep its original pixels. So the window refuses, whichever way you send, and says so in place of the send button. Undo the change, or delete the box in Anon mode, to send the tags. To keep the changed pixels, export the file instead. Send the rest on a copy already started goes away too, until you undo the change. While a command is still rewriting a file, such as a compression, the window waits the same way and offers the send again when it ends.

For any other reason dcmage can’t send, the button stays on screen, greyed out, and the window says why and names the tags involved. The usual reasons:

  • Only some of the study’s series are open. Open whole study in the window fetches the rest.
  • You changed one of the study’s identifiers (its Study, Series or SOP Instance UID). dcmage won’t send those back.
  • You changed the patient and the archive files the corrected Patient ID under other details, or you kept the identifiers.
  • A batch changes a patient’s name, birth date or sex under the same Patient ID.
  • A correction of every study of a patient carries a study value, or the patient has more than 50 studies.
  • You set one tag to different values on different images of one series, or of the study for a study tag.
  • You edited a sequence or a private tag. A send only sets or removes a named tag, so the window lists the edit. Undo it in the workspace to send the rest.
  • You removed a tag the study needs in the archive: the patient’s details, an identifier, the Modality, the character set, or a tag that describes the images. The window names it. Undo it in the workspace to send the rest.
  • Nothing has changed yet.