IHERO UseCase Prescription Automatation: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
5. Discussion: Excerpt/Abstraction of specific items that might be included in a prescription
AAM (talk | contribs)
 
(5 intermediate revisions by 2 users not shown)
Line 31: Line 31:


==5. Discussion==
==5. Discussion==
'''What can currently be found in DICOM'''<BR>
I would like to put a different view of the world.
The DICOM Standard currently has a Prescription Module with specific elements that are  
<br>
used to convey some of the Dosimetric Intent. An attempt to summarize some of these
'''The Use Case of the Radiotherapy Prescription'''<br>
are listed below, but for full information, it is the RT Prescription Module, Sec C.8.8.10
In the world of ''image-based & dosimetric planning'', many of the parameters that were previously described & decided BEFORE planning (field size, field orientation) are now defined as a result of the planning. In fact there is good anecdotal evidence to suggest that NOT specifying field number and orientation can have a much better planned produced. "The plan" is now just one of many operationally defined and acceptable solutions where the field sizes/orientation/intensity map/etc are set long after the intended prescription is set. In fact the only reason the prescription MAY change is because dose constraints can't be met. But the point is that the prescription can no longer be viewed separate from the plan approved.
in  [http://medical.nema.org/dicom/2007/07_03pu.pdf DICOM PS3.3 - 2007]:
<BR>
Similarly, there is an RT Patient Setup Module (relating to imaging and patient setup).
This can be found in in the RT Patient Setup Module, Sec 8.8.12 in [http://medical.nema.org/dicom/2007/07_03pu.pdf DICOM PS3.3 - 2007]
<BR>


'''Relating to Dosimetric Intent'''<BR>
In accordance with this dosimetric planning paradigm, the prescription is a simple statement [e,g, "Prostate", IMRT, 6MV X, 78Gy in 38Fx, ICRU reference point] which can be easily assessed according to the modern paradigm of ICRU50/62.  
Dose Reference Structure Type (Point, ROI, Volume, Coordinates, Site)<BR>
Referenced ROI Number (if an ROI or a Volume is being prescribed to, this identifies which ROI or Volume)<BR>
Dose Reference Point Coordinates (if it is coordinates being prescribed to, e.g. if the Physician reviewed the CT and picked a pixel on the screen as the point to prescribe to).<BR>
Nominal Prior Dose (to this particular "thing" that is being referenced)<BR>
Dose Reference Type (Target, Organ at Risk)<BR>
Constraint Weight<BR>
Delivery Warning Dose<BR>
Delivery Maximum Dose<BR>
Target Minimum Dose<BR>
Target Prescription Dose<BR>
Target Maximum Dose<BR>
Target Underdose Volume Fraction  (Percent allowed to be underdosed)<BR>
Organ at Risk Full-volume Dose<BR>
Organ at Risk Limit Dose<BR>
Organ at Risk Maximum Dose<BR>
Organ at Risk Overdose Volume Fraction (Percent allowed to be overdosed)<BR>
<BR>


<br>
'''The Use Case of the Descriptors and Instructions associated with a Radiotherapy Plan'''<br>
If I am correct that the prescription can no longer be viewed separate from the plan approved, then within this realm of ''plan construction & treatment delivery'', there are a large number of specifications and instructions that relate to the plan, NOT the prescription. They are a necessary condition for treatment delivery but no the prescription. Some will be specified by RO, some by dosimetrist and some by sim RT. Instructions such as "empty rectum", "alpha cradle", "image fiducials" are not prescription ''per se''.


The issue of how to get ROs to specify issues relating to GTV, CTV and PTV are very very vexatious. One ASTRO voluming course will quickly demonstrate that its a jungle out there when it comes to voluming. Certainly some standardised nomenclature could be easily introduced by manufacturers purely by inserting a base list [Use Case for standardised nomenclature BELOW], and altering some of the characteristics of drawn lines [e.g., not permit normal tissue contours to overlap as in Eclipse, not permit a PTV to be drawn, not permit a PTV to be altered, permit auto-expansion of PTV according to departmental defined protocols]


'''Some of what can be found in a particular commercial system'''<BR>
''Sideline'' - '''Use Case for standardised nomenclature.'''<br>
The following are abstracted from a particular commercial system, and are only intended
GTV relates abnormal image of either primary, nodes or metastases, thus GTVp, GTVn, & GTVm
as an aid in enumerating the particular "elements". These have some overlap with the DICOM
CTV relates to either the areas immediately around the GTV where there is soft tissue involvement, thus CTVp, CTVn, & CTVm (1:1 transformation from GTV>CTV); or the nodal areas that look normal but are at risk of involvement, thus CTVn0.
RT Prescription mentioned above.
PTV is a geometric dose envelope that relates to a covering isodose related to a prescription dose, thus PTV60, PTV70, ....


<br>
'''The Use Case of Fractionation'''<br>
I have not worked out my thoughts completely on this yet. IGBTYL!


Site (Anatomic Name, Structure Name?)<BR>
<br>
Radiation Type (Photons, Protons, Electrons)<BR>
'''The Use Case of sequential plans (EBRT + brachytherapy boost)'''<br>
Technique (AP/PA, Four Field Box)<BR>
The fundamental issue in this Use Case is the images on which the dose grid lies and whether they are capable of fusion, and if not can images/dose be distorted. The issue is whether these sequential plans should be stored separately (2 files, 2 plans), coalesced (1 file, 1 plan) or linked (1 file, 2 plans; maybe even 1 file, 1 integral dose plan, 2+ individual plans).
Modality (MV Photons with Energy, Ortho, Electrons with Energy)<BR>
<BR>
Dose Specification Location (90%iso, D-Max, Depthdose, Isocenter, Isodose, Mid-plane, Plan, Point, Tumor) <BR>
Dose Specification Value (100, 90, 1)<BR>
Dose Specification Units/dimensionality (Percentage, centimeters)<BR>
<BR>
Total Dose (in units of Gray or Cobalt Gray Equivalent)<BR>
Number of Fractions<BR>
Dose Per Fraction<BR>
(note that Total Dose = Dose Per Fraction * Number of Fractions, so there is redundant information)<BR>
Dose Semantics (Physical Dose vs. Biologically Equivalent Dose)<BR>
<BR>
Fractionation Pattern (Start, End (# of times), Times Per Day, Daily, Weekly, Bi-Weekly,Every (n) Days, inclusion of Saturday,and/or Sunday, and/or Holidays<BR>
<BR>
Dose Limits (Total Cumulative) in units of Gray, e.g. When additional radiation may accumulate from a separately irradiated Site.<BR>
<BR>
Pattern?<BR>
Comment<BR>
<BR>
Status [change] (Pending, Approved, On Hold, Closed, Completed, Exclusive, Voided)<BR>
Status [change] Date/Time<BR>
Status changer (a person's name, username, initials...whatever identifies the person who made/authorized the change in status)<BR>


<BR>
What will the future hold? A whole body CT scan with the first sim and then fusion of all subsequent plans? If there is the ability to morph CT images + dose, then dose deposition can be tracked from child to adult and between dissimilar techniques.
'''Relating to Patient Setup'''


The RT Patient Setup module refers to
_________________________________________________<br>
Patient Position <BR>
"''Physician diagnoses the patient based on all information received from referring physician, imaging data, lab results, etc. He prescribes the treatment dose, OAR dose constraints, etc. (see the list of attributes above). The comprehensive prescription will be stored as part of the electronic medical record, and will be available electronically for dosimetry team to plan on. The original prescription will be also available for the rest of the care team, and will be used as a baseline for any changes, which will be done during the treatment course.''"
Setup Images <BR>
<br>
Fixation Devices <BR>
As a RO, I think that this Use Case straddles too many areas. Within the IHERO documentation, there is no mention of diagnosis, labs in relation to medical use. This Use Case needs to be specified by those involved, and I am thinking that it will be very complicated. One of our OISs can handle this type of stuff properly, and the other can't - mainly because ROs were not consulted. If a new Profile Proposal is needed for this, good, but deliberations here should start with the definition of the intended prescription.
Shielding Devices <BR>
I agree that the management of the prescription, which is the ROs province, should reside where the RO works, which is predominantly the OIS, not the TPS. OIS vendors should have a clear cut place for ROs to enter and sign their intended prescription, and sign it off again when the plan is acceptable, and TPS vendors should pull the prescription from the OIS and do a final QA check to make sure it is finally approved in the OIS before transfer out of the TPS.
<BR>
I would caution you however that the ''electronic '''medical''' record'' is not the ''electronic radiation record'' or ''electronic schedule''. It is a portion of the IMPAC/LANTIS/ARIA/OnCentras that deals with medical information (incidentally the commonly missing portion in these software!). Which is of course why it is called '''medical'''. This part of the system is not up to scratch at present and has the disconcerting problem that increasingly the radiation prescription is only entered into something like EPIC by the RO, and never comes near the OIS. So the question of whether the comprehensive prescription is stored in the EMR or EPR should be discussed also.
Setup Technique
For this reason, the RO Diagnosis Use Case has to be very generic and brief.
where the Setup Device Type may be one of the following: <BR>
LASER_POINTER <BR>
DISTANCE_METER <BR>
TABLE_HEIGHT <BR>
MECHANICAL_PTR <BR>
ARC<BR>
<BR>
Motion Synchronization and Respiratory Motion Compensation (Gating)<BR>
NONE <BR>
BREATH_HOLD <BR>
REALTIME = image acquisition shorter
than respiratory cycle <BR>
GATING = Prospective gating <BR>
TRACKING = prospective through-
plane or in-plane motion tracking  <BR>
PHASE_ORDERING = prospective phase
ordering <BR>
PHASE_RESCANNING = prospective
techniques, such as real-time averaging,  
diminishing variance and motion adaptive
gating <BR>
RETROSPECTIVE = retrospective gating <BR>
CORRECTION = retrospective image
correction <BR>
 
 
 
'''Comments on what might also be needed'''<BR>
For a number of the kinds of information mentioned above, it will also be of considerable value to know if there are particular defined
values that should be used, e.g. if in attempting to describe a target, one would want to use defined names such as PTV, CTV, GTV.
Many of these do have definitions in the DICOM standard, and not all were enumerated completely in the above...
In some cases the level of detail above is not critical to the description of the use case, but I hope that this detail will be helpful in guiding the editors/authors of the use case.  
<BR>

Latest revision as of 05:00, 14 December 2007


1. Proposed Workitem: Comprehensive/universal radiotherapy treatment prescription format

  • Proposal Editor: Sha Chang
  • Editor: Sha Chang, May Wahab
  • Date: N/A (Wiki keeps history)
  • Version: N/A (Wiki keeps history)
  • Domain: Radiation Oncology

2. The Problem

The problem: Current radiotherapy software systems do not have a consistent and comprehensive approach to record the treatment prescription, which describes the treatment intended by the patient’s physician. A comprehensive recording of the treatment prescription that is transferable and understandable by different RT software has become increasingly important today as the radiotherapy treatment technology as well as treatment objective becomes more complex and the need to consider previous treatments for today’s patient care increases.

The solution: To create a unified radiotherapy treatment prescription format that can be used by all RT systems (treatment planning systems and record & verify systems) to systematically record and interface treatment prescriptions of different complexity levels. For instance, it should work for the simplest form of treatment prescription – 6MV AP and PA fields, 200 cGy x 20 daily - and for complex treatment prescriptions that are anatomical structure specific and dose-optimized.

What are needed:

  1. define the content of the comprehensive treatment prescription
  2. define the format of the prescription.

Content: A comprehensive RT treatment prescription should contain all the information the physician would need in order to reconstruct the same treatment planning again). Suggested items in the comprehensive treatment prescription include: external/brachytherapy, total and fractional dose, fractionation scheme, treatment sites, treatment target volume names, margins to be used (in case of 3DCRT), dose constraints for organs at risk/normal tissue, beam energy, dose optimization and IMRT or not, gated treatment or not, immobilization to be used, image set(s) used for treatment planning, type of image-guided patient setup/treatment delivery (daily cone beam CT, radiographic, fluoro, ultrasound, etc.). Many of the above items can be extracted from the treatment planning system.

3. Key Use Case

  1. Physician diagnoses the patient based on all information received from referring physician, imaging data, lab results, etc. He prescribes the treatment dose, OAR dose constraints, etc. (see the list of attributes above). The comprehensive prescription will be stored as part of the electronic medical record, and will be available electronically for dosimetry team to plan on. The original prescription will be also available for the rest of the care team, and will be used as a baseline for any changes, which will be done during the treatment course.
  2. Patient comes in with prostate cancer having received external beam radiation using IMRT at another facility and is here for a brachytherapy boost. We need to integrate previous external beam plans with the brachytherapy plan and streamline the prescription as well. There should be a area in the prescription to reflect the previous dose. This also applies to head & neck re-treatment prescriptions, so the dose to the cord can be assessed in the current plan as well as cumulatively.


4. Standards & Systems

All treatment planning systems and record & verify systems will be involved in the problem and hopefully in the solution as well.
DICOM RT

5. Discussion

I would like to put a different view of the world.
The Use Case of the Radiotherapy Prescription
In the world of image-based & dosimetric planning, many of the parameters that were previously described & decided BEFORE planning (field size, field orientation) are now defined as a result of the planning. In fact there is good anecdotal evidence to suggest that NOT specifying field number and orientation can have a much better planned produced. "The plan" is now just one of many operationally defined and acceptable solutions where the field sizes/orientation/intensity map/etc are set long after the intended prescription is set. In fact the only reason the prescription MAY change is because dose constraints can't be met. But the point is that the prescription can no longer be viewed separate from the plan approved.

In accordance with this dosimetric planning paradigm, the prescription is a simple statement [e,g, "Prostate", IMRT, 6MV X, 78Gy in 38Fx, ICRU reference point] which can be easily assessed according to the modern paradigm of ICRU50/62.


The Use Case of the Descriptors and Instructions associated with a Radiotherapy Plan
If I am correct that the prescription can no longer be viewed separate from the plan approved, then within this realm of plan construction & treatment delivery, there are a large number of specifications and instructions that relate to the plan, NOT the prescription. They are a necessary condition for treatment delivery but no the prescription. Some will be specified by RO, some by dosimetrist and some by sim RT. Instructions such as "empty rectum", "alpha cradle", "image fiducials" are not prescription per se.

The issue of how to get ROs to specify issues relating to GTV, CTV and PTV are very very vexatious. One ASTRO voluming course will quickly demonstrate that its a jungle out there when it comes to voluming. Certainly some standardised nomenclature could be easily introduced by manufacturers purely by inserting a base list [Use Case for standardised nomenclature BELOW], and altering some of the characteristics of drawn lines [e.g., not permit normal tissue contours to overlap as in Eclipse, not permit a PTV to be drawn, not permit a PTV to be altered, permit auto-expansion of PTV according to departmental defined protocols]

Sideline - Use Case for standardised nomenclature.
GTV relates abnormal image of either primary, nodes or metastases, thus GTVp, GTVn, & GTVm CTV relates to either the areas immediately around the GTV where there is soft tissue involvement, thus CTVp, CTVn, & CTVm (1:1 transformation from GTV>CTV); or the nodal areas that look normal but are at risk of involvement, thus CTVn0. PTV is a geometric dose envelope that relates to a covering isodose related to a prescription dose, thus PTV60, PTV70, ....


The Use Case of Fractionation
I have not worked out my thoughts completely on this yet. IGBTYL!


The Use Case of sequential plans (EBRT + brachytherapy boost)
The fundamental issue in this Use Case is the images on which the dose grid lies and whether they are capable of fusion, and if not can images/dose be distorted. The issue is whether these sequential plans should be stored separately (2 files, 2 plans), coalesced (1 file, 1 plan) or linked (1 file, 2 plans; maybe even 1 file, 1 integral dose plan, 2+ individual plans).

What will the future hold? A whole body CT scan with the first sim and then fusion of all subsequent plans? If there is the ability to morph CT images + dose, then dose deposition can be tracked from child to adult and between dissimilar techniques.

_________________________________________________
"Physician diagnoses the patient based on all information received from referring physician, imaging data, lab results, etc. He prescribes the treatment dose, OAR dose constraints, etc. (see the list of attributes above). The comprehensive prescription will be stored as part of the electronic medical record, and will be available electronically for dosimetry team to plan on. The original prescription will be also available for the rest of the care team, and will be used as a baseline for any changes, which will be done during the treatment course."
As a RO, I think that this Use Case straddles too many areas. Within the IHERO documentation, there is no mention of diagnosis, labs in relation to medical use. This Use Case needs to be specified by those involved, and I am thinking that it will be very complicated. One of our OISs can handle this type of stuff properly, and the other can't - mainly because ROs were not consulted. If a new Profile Proposal is needed for this, good, but deliberations here should start with the definition of the intended prescription. I agree that the management of the prescription, which is the ROs province, should reside where the RO works, which is predominantly the OIS, not the TPS. OIS vendors should have a clear cut place for ROs to enter and sign their intended prescription, and sign it off again when the plan is acceptable, and TPS vendors should pull the prescription from the OIS and do a final QA check to make sure it is finally approved in the OIS before transfer out of the TPS. I would caution you however that the electronic medical record is not the electronic radiation record or electronic schedule. It is a portion of the IMPAC/LANTIS/ARIA/OnCentras that deals with medical information (incidentally the commonly missing portion in these software!). Which is of course why it is called medical. This part of the system is not up to scratch at present and has the disconcerting problem that increasingly the radiation prescription is only entered into something like EPIC by the RO, and never comes near the OIS. So the question of whether the comprehensive prescription is stored in the EMR or EPR should be discussed also. For this reason, the RO Diagnosis Use Case has to be very generic and brief.