The Patients page displays:
- The Patients list (1) shows all patients stored in the SW database (Section 4.1.1)
- The Plan list (2) shows plan details of the selected patient in the Patients list (Section 4.1.2)
- The Import DICOM (3) button (Section 4.1.3)
Patients List
Each row in the Patients list corresponds to a patient in the database. It displays the following patient information: ID, name, birth date, and sex (1).
- In the Actions column, click the Trash icon (2) to delete a patient.
A pop-up will appear asking to confirm the deletion. Click Delete to confirm the deletion.
This completely erases the patient from the database by deleting all the DICOM files associated to this
patient.IMPORTANT NOTICE: DELETED INFORMATION CANNOT BE RECOVERED
Please exercise caution; by clicking Delete all information will be deleted, including DICOM files, logfiles, and any analysis files associated with the patient. Once deleted there is no possibility of recovery.- Easily find a patient using the Filter patients search box (3).
Plan List
The Plan list shows a list of current treatment plans for a patient. The patient name and ID is displayed at the top left (1).
Each row shows the following plan details (2): overall QA status, plan label, plan name, physician of the patient, and the treatment room / machine. Except for the Overall status and Actions columns, the data are extracted upon importation of the DICOM files.
- Click on the arrow (3) to expand the status summary of the calculation results (4) for each plan.
Table 4.1. Patients page - Plan List - Overall Status column
| Icon | Overall Status | Description |
Plan Approved | The plan has been approved by a user | |
Plan Rejected | The plan has been rejected by a user | |
Pending Approval | The test has passed | |
| There is a warning about the test | ||
| There was an error during calculation or the test has failed | ||
| Analysis has not yet been performed | ||
Measurement needed | Measurement data (logs data) are missing | |
Missing DICOM data | At least one of the mandatory DICOM files (Section 4.1.3) is missing | |
Corrupted data | The imported DICOM data are not supported or errors in DICOM files have been detected |
Table 4.2. Patients page - Plan List - Actions column
| Icon | Actions | Description |
Export to PDF | Click to exported a PDF of the Patient QA report. Default filename: “YYYY-MM-DDPatient first name-Patient last name”. | |
Delete | Click to delete a patient plan. The plan and its related data (i.e., associated DICOM, measurement and report data) are deleted. If a task is still open, the Delete button is disabled. |
DICOM Import
myQA iON supports both manual and automatic import of DICOM files. If files already exist in myQA iON and the user imports them again, the existing files will be kept. Please note, files names must include date and time stamp.
If multiple calculations are running in the background during the import of DICOM files, a “DICOM data missing” error may appear under Overall status on the Plan list. This error will be resolved when the calculations are complete.
IMPORTANT NOTICE: DICOM FILES MUST HAVE CORRECT NOMENCLATURE
Only the DICOM files compliant with the DICOM Conformance Statement can be imported into the myQA iON database. All other IODs (Information Object Definition) will be rejected by the SW during the import.
Mandatory DICOM files for QA analysis
The following DICOM files are mandatory to perform patient QA:
- Patient CT Image(s)
- Associated RT Structure Set
- RT Plan (RT) / RT iON Plan (PT)
- RT Dose (plan dose for Independent Dose, and beam doses for Irradiation Logs)
IMPORTANT NOTICE: MINIMAL DATASET FOR PATIENT QA
All four mandatory DICOM entities are required to create a Patient QA Report and perform QA.
- As soon as any of these files are imported, a patient is created in the Patients list.
- Once all mandatory files are successfully imported a patient QA report is generated and an analysis is launched (Section 4.1.5). If parts of the mandatory data set are not present in the SW, the patient plan will have an overall status set to Missing DICOM data.
myQA iON requires additional DICOM files to perform all analyses. These files can either be uploaded together with the mandatory dataset or at a later stage. If these files are absent, the analysis is blocked until the DICOM dataset is completed.
The additional DICOM files supported by myQA iON are:- RT Record (plan dose for Independent Dose, and beam doses for Irradiation Logs)
Required to perform a MatriXX measurement analysis: - RT Ion plan (Patient QA verification plan, PT Only) for MatriXX Analysis
- The RT Dose of each QA verification beam associated with the Patient QA verification plan for
comparison with the MatriXX measurement for each beam - The Patient QA verification phantom and its associated RT Structure Set (see Section 3.2.2.2)
If myQA iON receives two DICOM files related to the same dataset, but is not able to associate them together (e.g., the patient initial treatment plan and the RT Dose related to the QA plan), these two files will be considered one item in the Patients list but two separate items in the Plan list. Once the QA RT Ion plan is uploaded myQA iON will what remove the duplicated item from the Plan list.
- RT Record (plan dose for Independent Dose, and beam doses for Irradiation Logs)
IMPORTANT NOTICE: REJECTED DICOM DOSES
Imported DICOM which do not satisfy the DICOM Conformance Statement shall be rejected. The rejected DICOM and the reason for rejection will appear in the System Events list on the History page (see Section 5.3).
IMPORTANT NOTICE: ERROR IMPORTING HALCYON PATIENT PLAN DATA
If an error is encountered while importing Patient Plan data from Halcyon, the orthanc file can be updated to allow the import (see Section 6.6).
IMPORTANT NOTICE: ERROR IMPORTING PATIENTS WITH DIFFERENT SLICE THICKNESS
myQA iON does not support patients with different slice thickness. If a patient plan with different slice thickness is imported, the calculation will fail with an error.
IMPORTANT NOTICE: INITIAL PLAN VERIFICATION
myQA iON performs initial verification of the patient treatment plan to guarantee its compatibility with the SW. If any of these verification checks fail, the status of the patient will be "Missing dicom data" and the reason for the rejection will be listed on the History page (Section 5.3). myQA iON verifies the following:
- For RT:
- SOP class uid: "1.2.840.10008.5.1.4.1.1.481.5" or "1.2.246.352.70.1.70"
- For each beam, the primary dosimeter unit is "MU" or "MINUTE"
- If a wedge sequence is present, each wedge type is "DYNAMIC" or "MOTORIZED"
- The radiation type is "ELECTRON" or "PHOTON"
- For PT:
- SOP class uid: "1.2.840.10008.5.1.4.1.1.481.8"
- Plan intent: "CURATIVE", "PALLIATIVE", "PROPHYLACTIC", "RESEARCH", or "VERIFICATION"
- For each beam that is not of delivery type "SETUP":
- Scan mode: "MODULATED"
- Beam type: "STATIC"
- Radiation type: "PROTON" (There shouldn't be any value for a range
modulator id in the range modulator sequence)
- For Carbon:
- SOP class uid: "1.2.840.10008.5.1.4.1.1.481.8"
- Plan intent: "CURATIVE", "PALLIATIVE", "PROPHYLACTIC", "RESEARCH", or
"VERIFICATION" - For each beam that is not of delivery type "SETUP"
- Scan mode: "MODULATED"
- Beam type: "STATIC"
Radiation type: "ION"
To indicate to the SW that this is a Carbon plan, the radiation mass number has to be "12", the radiation atomic number has to be "6", the radiation charge state has to be "6"
Manual DICOM Import
Click the Import Patient button on the Patients page and select Dicom patient-study from the
dropdown.- In the Open browser, select the files to be imported and click OK.
Automatic DICOM Import
Automatic import of DICOM files is performed by pushing the files from the PACS of treatment planning system, using the C-store command. This configuration needs to be performed in the TPS but not in myQA iON. Contact the installation team for the IP address and TCP ports if the TPS has not been configured before installing myQA iON.
Cyberknife data Import
Click the Import Patient button on the Patients page and select Cyberknife dataset
A tool tip will appear informing the user that the entire patient dataset must be imported all at the same
time if the patient plan contains non-DICOM files.Supported Dataset:
- RT Dose or RT Dose Raw (only one can be imported; it will depend on the individual patient)
- RT Structure set
- CT Image set
- XML (Reports, CKPlanDetails)
- In the Open browser, select the files to be imported and click OK.
- A progress bar at the top of the Patients screen will appear to show the import progress.
- Once complete, the new patient will appear in the Patients list.
Note: For Cyberknife plans, Precision TPS can export the SKIN type as "External", which is optional for the MC calculation in myQA iON. To ensure accurate dose scaling when generating a dose difference map, it is recommended to set an external density threshold if the SKIN data is not imported into myQA iON (see Section 3.2.3.3).
IMPORTANT NOTICE: PLAN NAME IS MANDATORY WHEN UPLOADING CYBERKNIFE DATASET
The plan name is mandatory in the XML while uploading a Cyberknife Dataset. If the XML is uploaded without a plan name, SciMoCa will generate an error and the dataset will need to be deleted and re-uploaded.
When naming Cyberknife plans, please avoid using empty spaces, non-English language characters (i.e., Ä, Ö, Ü, ß), and the following characters: & < >
If a Cyberknife dataset is uploaded with unsupported characters it will be rejected by myQA iON.
IMPORTANT NOTICE: MISSING DATA ERROR
When importing a Cyberknife dataset, if a Missing data error occurs, please delete the patient and re-import the necessary files.
Automatic Analysis
After the required files have been imported and validated, the SW will start the independent dose computation in the back-end automatically. If RT Ion Treatment Records have been imported, an irradiation logs analysis will be launched in the back-end automatically. The results are displayed in the Patient QA Report page (Chapter 5) where various QA tasks can be performed.
Please note, if a calculation is running (for RT, Cyberknife, Carbon, or PT 3D Gamma) when the server
connection is interrupted, the calculation will run indefinitely. The calculation cannot be canceled, the
patient must be deleted and re-uploaded to stop the calculation.