For:Site users and site IT
AitriumOS updates from 2.2 straight to 2.3.4. Read For everyone, then the section for your trial.
For everyone
- “De-identify” everywhere. The step and the tools now say de-identify and de-identification. EORTC · RTQA
- Getting ready. Each imaging submission first checks disk space and the connection, picks a drive with room, and continues by itself once a problem is fixed. Troubleshooting
- A full disk asks, never fails. If the disk fills during de-identification, you choose what to do, and failed steps offer Copy details for support. Troubleshooting
- Documents submissions. Documents-only submissions have their own short flow, and AitriumOS checks each file’s format before you send. Documents submissions
- Multiple structure sets. A folder with several structure sets gets one step for each set that needs a decision (in RTQA trials, the set QA uses comes first). Multiple structure sets
- Unfinished sends. If AitriumOS closed during a send, the row says so after you reopen it. Troubleshooting
- Installing. AitriumOS is built for Windows x64 and Apple silicon Macs only. On Windows, the standard installer warns before it installs if AitriumOS is already installed for everyone on the computer. The first launch of 2.3 upgrades the local database one-way. Installing AitriumOS
If you submit to EORTC trials
- Patient list. Type an ID in Search or add ID to find or add a patient, and filter by status, for example Not started, In progress, or Complete. Add a patient
- Plain-language dataset check. Studies in this folder names each study by what it holds, and What [dataset type] requires shows what each required study needs. Before you send, Confirm Data Transfer states in one sentence whether everything the dataset type requires is in the folder. Check the dataset
- Missing items never stop you. The continue button says what happens, for example Continue without the missing items. Check the dataset
- Several plans in one folder. AitriumOS asks which plan belongs to the dataset type you’re sending. Check the dataset
- Registrations. A registration saved in another study counts for the study it references. Check the dataset
- Supporting documents. You choose the file for each document the dataset type names and confirm they contain no patient identifiers. Supporting documents
- Sent status. A sent dataset reads Sent or Sent · N required items missing, judged by what was recorded when you sent it, the same way the trial team sees it. Check the submission
- Send a new version. To correct a dataset, open its Sent cell and select Send a new version. This replaces Complete Required Items and Resubmit Dataset. Send a new version
- Instructions per dataset type. Submission complete shows the trial team’s instructions for the dataset type you sent. Upload to trial
If your trial uses RTQA (protocol trials)
- Plan and dose checks. The analyzer compares the plan with the patient’s regimen and shows Checking plan and dose… until it’s done. Plan and dose checks
- One question when the plan is outside the protocol. Submit it as planned, switch the patient’s regimen, or choose another folder. Everything uploads either way. Plan and dose checks
- Dose file choice. With several dose files and no plan sum that covers every plan, you choose the one QA evaluates. Plan and dose checks
- Courses of more than one plan. The trial’s QA team reviews them after submission. You don’t need to do anything. Plan and dose checks
- Clearer dataset check. Gaps are grouped as Missing or Needs your choice, and studies are named by what they contain. Check the dataset
- Structure mapping never blocks. If a required structure isn’t mapped, you can go back or continue without it. Map structures
- QA check. QA results come from Aitrium’s preview, grouped as Per protocol, Acceptable variation, Unacceptable, Not evaluated, and Assessed after submission. You can continue while the preview loads. QA check
- Patient setup. The setup badge counts only the items your trial requires. The randomization date can be optional. Set up a patient
- Re-submit. A re-submission becomes the latest send. The earlier send stays on record. Re-submit