IHERO UseCase 2011 InformationFlow Mika: Difference between revisions

Latest revision as of 11:38, 21 March 2011

1. Proposed Workitem: Information Flow

Proposal Editor: Mika Miettinen, mika.miettinen@varian.com, +1 650 799 7665
Editor: Sidrah Abdul/Rishabh Kapoor on behalf of Mika Miettinen
Date: N/A (Wiki keeps history)
Version: N/A (Wiki keeps history)
Domain: Radiation Oncology

2. The Problem

No data compatibility between treatment planning, OIS/Treatment Management and treatment delivery system (machine) has been demonstrated in IHE-RO. Seemless flow of treatment information between the TPS , OIS and treatment delivery devices.

3. Key Use Case

With the help of the use cases (Compatibility problems) solved in the last couple of years by IHE-RO, good compatibility between different treatment planning systems have been demonstrated. This includes Plan Exchange, Contour exchange, Dose display and exchange and multi-modality Image registration information exhange between treatment planning systems. Also with treatment delivery workflow profile in IHE-RO there some compatibility between OIS and treatment delivery device.

But in a conventional workflow in a radiation oncology clinic, the information flows between the treatment planning system (TPS) to OIS / treatment management system / R & V to the Treatment delivery device (Linac etc.). This is one of the most important clinical uses cases.

This use case would help bridge the gap between the treatment planning and Treatment delivery based IHE-RO profiles.

4. Standards & Systems

<List existing systems that are/could be involved in the problem/solution.>

Use of DICOM Worklist (UPS) to address departmental scheduling and workflow has been defined.

This is purely a workflow profile - so data (specifically Plan) contents has to be defined in the transaction between TPS - TMS - TDD. The data content specified here would be critical to patient 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>

@@ Line 2: / Line 2: @@
-==1. Proposed Workitem: ''<Information Flow>''==
+==1. Proposed Workitem: Information Flow==
 * Proposal Editor: Mika Miettinen, mika.miettinen@varian.com, +1 650 799 7665
@@ Line 13: / Line 13: @@
 ==2. The Problem==
-''<Summarize the integration problem. What doesn’t work, or what needs to work.>''
-No data compatibility between treatment planning, OIS/Treatment Management and treatment delivery system (machine) has been demonstrated in IHE-RO.
+No data compatibility between treatment planning, OIS/Treatment Management and treatment delivery system (machine) has been demonstrated in IHE-RO. Seemless flow of treatment information between the TPS , OIS and treatment delivery devices.
 ==3. Key Use Case==
-''<Describe a short use case scenario from the user perspective.  The use case should demonstrate the integration/workflow problem.>''
+With the help of the use cases (Compatibility problems) solved in the last couple of years by IHE-RO, good compatibility between different treatment planning systems have been demonstrated. This includes Plan Exchange, Contour exchange, Dose display and exchange and multi-modality Image registration information exhange between treatment planning systems. Also with treatment delivery workflow profile in IHE-RO there some compatibility between OIS and treatment delivery device.
+But in a conventional workflow in a radiation oncology clinic, the information flows between the treatment planning system (TPS) to OIS / treatment management system / R & V to the Treatment delivery device (Linac etc.). This is one of the most important clinical uses cases.
-With the help of the use cases (Compatibility problems) solved in the last couple of years by IHE-RO, good compatibility between different treatment planning systems have been demonstrated. This includes Plan Exchange, Contour exchange, Dose display and exchange and multi-modality Image registration information exhange between treatment planning systems. Also with treatment delivery workflow profile in IHE-RO there some compatibility between OIS and treatment delivery device.
+This use case would help bridge the gap between the treatment planning and Treatment delivery based IHE-RO profiles.
-But in a conventional workflow in a radiation oncology clinic, the information flows between the treatment planning system (TPS) to OIS / treatment management system / R & V to the Treatment delivery device (Linac etc.). This is one of the most important clinical uses cases.
 ==4. Standards & Systems==
@@ Line 30: / Line 28: @@
 ''<List existing systems that are/could be involved in the problem/solution.>''
-''<If known, list standards which might be relevant to the solution>''
+Use of DICOM Worklist (UPS) to address departmental scheduling and workflow has been defined.
+This is purely a workflow profile - so data (specifically Plan) contents has to be defined in the transaction between TPS - TMS - TDD. The data content specified here would be critical to patient safety.
 ==5. Discussion==