Difference between revisions of "IHERO UseCase 2011 1"

From IHE Wiki
Jump to navigation Jump to search
(New page: __NOTOC__ ''This template is for one or two page IHE workitem proposals for initial review.'' ''<Delete everything in italics and angle brackets and replace with real text> ==1. Prop...)
 
 
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
  
−
''This template is for one or two page IHE workitem proposals for initial review.''
 
  
 +
==1. Proposed Workitem: Flattening Filter Free-mode ==
  
−
''<Delete everything in italics and angle brackets and replace with real text>
+
* Proposal Editor: ''Mika Miettinen''
−
 
 
−
 
 
−
==1. Proposed Workitem: ''<initial working name for profile/whitepaper/etc>''==
 
−
 
 
−
* Proposal Editor: ''<Name of author/editor/contact for the proposal>''
 
 
* Editor: ''<Name of candidate Lead Editor for the Profile, if known>''  
 
* Editor: ''<Name of candidate Lead Editor for the Profile, if known>''  
−
* Date:    N/A (Wiki keeps history)
+
* Date:    March 9, 2011
 
* Version: N/A (Wiki keeps history)
 
* Version: N/A (Wiki keeps history)
 
* Domain: ''Radiation Oncology''  
 
* Domain: ''Radiation Oncology''  
Line 19: Line 14:
 
==2. The Problem==
 
==2. The Problem==
  
−
''<Summarize the integration problem. What doesn’t work, or what needs to work.>''
+
Some treatment delivery systems are capable of delivering so called “FFF” (Flattening
 +
Filter Free) beams. These beams differ from “standard flat”-beams so that beam profiles
 +
are not made “flat” using a flattening filter in the beam line. Thus FFF-beams are
 +
“pointed” (depending on the energy), and may enable significantly higher dose rates
 +
compared to the standard beams. Even if the nominal energy of the FFF beam is the
 +
same as the nominal energy of the standard beam from accelerator perspective, the FFF
 +
beam is little softer (when measured in water phantom) compared to the standard beam
 +
(with the same nominal energy) because of the missing flattering filter.
 +
As the beam characteristics of the FFF beams can be very different from standard
 +
beams, it is very important that these beams are recognized and handled properly by all
 +
systems contributing to the radiotherapy process. If plan is created using FFF beams,
 +
but treated as standard beam (or vice versa), the dose delivered to the patient may be
 +
significantly different.
 +
The purpose of this Proposal is to request IHE-RO to add FFF-beams to “Advanced RT
 +
Objects Interoperability” Integration Profile, so that the vendors will be able to implement
 +
the FFF-beam interoperability consistently, and test the connectivity as part of IHE-RO
 +
connecthaton.
 +
It is also important to acknowledge that the current “Advanced RT Objects
 +
Interoperability” integration profile addresses only the data content transfer between
 +
treatment planning systems and treatment management systems / information systems.
 +
IHE-RO does not currently have data content profiles to cover the data content transfer
 +
between treatment management system / information system and treatment delivery
 +
system. To ensure the interoperability of FFF-treatments, it is critical that IHE-RO will
 +
also look into developing these additional profiles. Author of this document is planning to
 +
submit a separate Proposal (per request from Planning Committee) to address this
 +
need.
  
  
 
==3. Key Use Case==
 
==3. Key Use Case==
−
 
+
Successful Use Case:
−
''<Describe a short use case scenario from the user perspective. The use case should demonstrate the integration/workflow problem.>''
+
1. A treatment plan using FFF beams (or mixed FFF and standard beams) is
−
 
+
created using treatment planning system. Treatment planning system uses the
−
''<Feel free to add a second use case scenario demonstrating how it “should” work. Try to indicate the people/systems, the tasks they are doing, the information they need, and hopefully where the information should come from.>''
+
data definitions required by IHE-RO Advanced RT Objects Integration profile to
−
 
+
differentiate the FFF beams and standard beams.
−
 
+
2. Clinicians Approve the plan
 +
3. Treatment planning system exports the plan to Treatment Management System
 +
(TMS) (or Archive).
 +
4. TMS imports the plan from Treatment Planning System (or Archive). TMS uses
 +
the data definitions required by IHE-RO Advanced RT Objects Integration profile
 +
to differentiate the FFF beams and standard beams.
 +
5. Clinicians approve the plan for treatment
 +
6. Treatment Delivery System (TDS) imports the plan for treatment. TDS uses the
 +
data definitions required by IHE-RO Advanced RT Objects Integration profile to
 +
identify and differentiate between the FFF beams and standard beams, and
 +
modes up the correct settings to deliver the dose.
 +
Technical committee shall consider how the applications in the process chain shall react
 +
to FFF-data, if they are not capable of handling these types of treatments.
 +
Some unsuccessful (potentially hazardous) scenarios:
 +
A. User configures an “FFF unaware” treatment planning system to use FFF beam
 +
depth dose curves, profiles and output factors, but treatment planning system is
 +
not capable of marking the beam as FFF when plans are exported to TMS. Thus
 +
there is a possibility that FFF beam would be treated using standard (flat) beam,
 +
and this could lead to misadministration of the dose.
 +
B. Treatment plan with FFF beams is imported to TMS that is not FFF-aware. Even
 +
if TPS had marked FFF beams in its data export, TMS drops the definitions, and
 +
imports the FFF beams as standard (flat) beams. This could lead to
 +
misadministration of the dose, if this plan was later treated.
 +
C. Treatment machine receives an FFF beam, but is not aware of the FFF
 +
definitions, and treats the beam as standard (flat) beam. This could lead to
 +
misadministration of the dose.
 
==4. Standards & Systems==
 
==4. Standards & Systems==
  
−
''<List existing systems that are/could be involved in the problem/solution.>''
+
DICOM RT WG-7 has created a mechanism that can be used to identify the FFF beams,
 +
and this proposal suggests that the DICOM RT definitions should be used to differentiate
 +
the FFF-beams from standard (flat) beams (see table 1). The problem with the current
 +
DICOM RT standard is that the “Primary Fluence Mode Sequence” is “Optional”, and
 +
thus it would be legal for e.g. receiving end to ignore it. Technical committee needs to
 +
define the integration profile in a way that each actor in the chain of radiotherapy
 +
process is aware of the different beam types, and is able to react to the data safely (e.g.
 +
prevent the “unsuccessful scenarios” listed above). One suggestion is to make the
 +
“Primary Fluence Mode Sequence” mandatory in IHE-RO Advanced RT Object
 +
Integration Profile for the actors creating and consuming dosimetric plans, but technical
 +
committee needs to make the final decision how to implement the DICOM RT standard
 +
to ensure the maximum inoperability.
  
−
''<If known, list standards which might be relevant to the solution>''
 
  
 +
Currently DICOM RT Standard defines “Primary Fluence Mode Sequence” as Optional
 +
(3)*, but this must be reconsidered in the IHE-RO integration profile. **) New, similar
 +
techniques can be described using the same mechanism.
 +
It is also suggested that the nominal energy of the FFF and standard (flat) beam shall be
 +
defined to be the same if the same energy is used to drive the electrons to the target,
 +
and only difference in the beam generation is that the standard (flat) beam has a
 +
flattening filter in the beam, and FFF beam doesn’t, and some steering parameters may
 +
be different. This definition might be beyond IHE-RO’s scope, but MITA group thought
 +
that this is worth of documenting in the proposal.
 +
Another guidance for the technical committee: FFF is the representative example in this
 +
proposal. However, in general this applies to all filters, which the machine can put into
 +
the beam line dynamically, and are different from the standard filters in the past. Thus
 +
the identifier could be something else than FFF. If possible the implementation should be
 +
generalized to ensure interoperability of the future techniques without compromising the
 +
safety.
  
 
==5. Discussion==
 
==5. Discussion==

Latest revision as of 12:37, 17 March 2011


1. Proposed Workitem: Flattening Filter Free-mode

  • Proposal Editor: Mika Miettinen
  • Editor: <Name of candidate Lead Editor for the Profile, if known>
  • Date: March 9, 2011
  • Version: N/A (Wiki keeps history)
  • Domain: Radiation Oncology


2. The Problem

Some treatment delivery systems are capable of delivering so called “FFF” (Flattening Filter Free) beams. These beams differ from “standard flat”-beams so that beam profiles are not made “flat” using a flattening filter in the beam line. Thus FFF-beams are “pointed” (depending on the energy), and may enable significantly higher dose rates compared to the standard beams. Even if the nominal energy of the FFF beam is the same as the nominal energy of the standard beam from accelerator perspective, the FFF beam is little softer (when measured in water phantom) compared to the standard beam (with the same nominal energy) because of the missing flattering filter. As the beam characteristics of the FFF beams can be very different from standard beams, it is very important that these beams are recognized and handled properly by all systems contributing to the radiotherapy process. If plan is created using FFF beams, but treated as standard beam (or vice versa), the dose delivered to the patient may be significantly different. The purpose of this Proposal is to request IHE-RO to add FFF-beams to “Advanced RT Objects Interoperability” Integration Profile, so that the vendors will be able to implement the FFF-beam interoperability consistently, and test the connectivity as part of IHE-RO connecthaton. It is also important to acknowledge that the current “Advanced RT Objects Interoperability” integration profile addresses only the data content transfer between treatment planning systems and treatment management systems / information systems. IHE-RO does not currently have data content profiles to cover the data content transfer between treatment management system / information system and treatment delivery system. To ensure the interoperability of FFF-treatments, it is critical that IHE-RO will also look into developing these additional profiles. Author of this document is planning to submit a separate Proposal (per request from Planning Committee) to address this need.


3. Key Use Case

Successful Use Case: 1. A treatment plan using FFF beams (or mixed FFF and standard beams) is created using treatment planning system. Treatment planning system uses the data definitions required by IHE-RO Advanced RT Objects Integration profile to differentiate the FFF beams and standard beams. 2. Clinicians Approve the plan 3. Treatment planning system exports the plan to Treatment Management System (TMS) (or Archive). 4. TMS imports the plan from Treatment Planning System (or Archive). TMS uses the data definitions required by IHE-RO Advanced RT Objects Integration profile to differentiate the FFF beams and standard beams. 5. Clinicians approve the plan for treatment 6. Treatment Delivery System (TDS) imports the plan for treatment. TDS uses the data definitions required by IHE-RO Advanced RT Objects Integration profile to identify and differentiate between the FFF beams and standard beams, and modes up the correct settings to deliver the dose. Technical committee shall consider how the applications in the process chain shall react to FFF-data, if they are not capable of handling these types of treatments. Some unsuccessful (potentially hazardous) scenarios: A. User configures an “FFF unaware” treatment planning system to use FFF beam depth dose curves, profiles and output factors, but treatment planning system is not capable of marking the beam as FFF when plans are exported to TMS. Thus there is a possibility that FFF beam would be treated using standard (flat) beam, and this could lead to misadministration of the dose. B. Treatment plan with FFF beams is imported to TMS that is not FFF-aware. Even if TPS had marked FFF beams in its data export, TMS drops the definitions, and imports the FFF beams as standard (flat) beams. This could lead to misadministration of the dose, if this plan was later treated. C. Treatment machine receives an FFF beam, but is not aware of the FFF definitions, and treats the beam as standard (flat) beam. This could lead to misadministration of the dose.

4. Standards & Systems

DICOM RT WG-7 has created a mechanism that can be used to identify the FFF beams, and this proposal suggests that the DICOM RT definitions should be used to differentiate the FFF-beams from standard (flat) beams (see table 1). The problem with the current DICOM RT standard is that the “Primary Fluence Mode Sequence” is “Optional”, and thus it would be legal for e.g. receiving end to ignore it. Technical committee needs to define the integration profile in a way that each actor in the chain of radiotherapy process is aware of the different beam types, and is able to react to the data safely (e.g. prevent the “unsuccessful scenarios” listed above). One suggestion is to make the “Primary Fluence Mode Sequence” mandatory in IHE-RO Advanced RT Object Integration Profile for the actors creating and consuming dosimetric plans, but technical committee needs to make the final decision how to implement the DICOM RT standard to ensure the maximum inoperability.


Currently DICOM RT Standard defines “Primary Fluence Mode Sequence” as Optional (3)*, but this must be reconsidered in the IHE-RO integration profile. **) New, similar techniques can be described using the same mechanism. It is also suggested that the nominal energy of the FFF and standard (flat) beam shall be defined to be the same if the same energy is used to drive the electrons to the target, and only difference in the beam generation is that the standard (flat) beam has a flattening filter in the beam, and FFF beam doesn’t, and some steering parameters may be different. This definition might be beyond IHE-RO’s scope, but MITA group thought that this is worth of documenting in the proposal. Another guidance for the technical committee: FFF is the representative example in this proposal. However, in general this applies to all filters, which the machine can put into the beam line dynamically, and are different from the standard filters in the past. Thus the identifier could be something else than FFF. If possible the implementation should be generalized to ensure interoperability of the future techniques without compromising the safety.

5. Discussion

<Include additional discussion or consider a few details which might be useful for the detailed proposal>

<Why IHE would be a good venue to solve the problem and what you think IHE should do to solve it.>
<What might the IHE technical approach be? Existing Actors? New Transactions? Additional Profiles?>
<What are some of the risks or open issues to be addressed?>


<This is the brief proposal. Try to keep it to 1 or at most 2 pages>

Retrieved from "http://wiki.ihe.net/index.php?title=IHERO_UseCase_2011_1&oldid=49200"