IHERO UseCase 2010 2: Difference between revisions
Removing TEMPLATE category |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 9: | Line 9: | ||
==1. Proposed Workitem: ''<initial working name for profile/whitepaper/etc>''== | ==1. Proposed Workitem: ''<initial working name for profile/whitepaper/etc>''== | ||
* Proposal Editor: | * Proposal Editor: Steve Sapareto | ||
* 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: N/A (Wiki keeps history) | ||
* Version: N/A (Wiki keeps history) | * Version: N/A (Wiki keeps history) | ||
* Domain: | * Domain: Radiation Oncology | ||
[[Category:RO]] | [[Category:RO]] | ||
__NOTOC__ | |||
==2. The Problem== | |||
The current state of the art in Radiation Oncology is Image Guidance. The process involves imaging patients, comparing with reference positoning images to determine shifts required to match and implementing those shifts. Currently there are no real standards for documenting these shifts in a consistent manner. Different manufacturers use different coordinate systems for the shifts which involve different orientations (e.g. table shifts or isocenter shifts) and different labeling of axes (x,y,z or ap, lat, vert refering to either the table or the patient) | |||
''<Now describe the Value Statement: what is the underlying cost incurred by the problem, what is to be gained by solving it>'' | |||
==3. Key Use Case== | |||
''<Describe a short use case scenario from the user perspective. The use case should demonstrate the integration/workflow problem.>'' | |||
''<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.>'' | |||
==4. Standards & Systems== | |||
''<List existing systems that are/could be involved in the problem/solution.>'' | |||
''<If known, list standards which might be relevant to the solution>'' | |||
==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>'' | |||
Latest revision as of 15:39, 30 June 2010
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. Proposed Workitem: <initial working name for profile/whitepaper/etc>
- Proposal Editor: Steve Sapareto
- Editor: <Name of candidate Lead Editor for the Profile, if known>
- Date: N/A (Wiki keeps history)
- Version: N/A (Wiki keeps history)
- Domain: Radiation Oncology
2. The Problem
The current state of the art in Radiation Oncology is Image Guidance. The process involves imaging patients, comparing with reference positoning images to determine shifts required to match and implementing those shifts. Currently there are no real standards for documenting these shifts in a consistent manner. Different manufacturers use different coordinate systems for the shifts which involve different orientations (e.g. table shifts or isocenter shifts) and different labeling of axes (x,y,z or ap, lat, vert refering to either the table or the patient)
<Now describe the Value Statement: what is the underlying cost incurred by the problem, what is to be gained by solving it>
3. Key Use Case
<Describe a short use case scenario from the user perspective. The use case should demonstrate the integration/workflow problem.>
<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.>
4. Standards & Systems
<List existing systems that are/could be involved in the problem/solution.>
<If known, list standards which might be relevant to the solution>
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>
2. The Problem
<Summarize the integration problem. What doesn’t work, or what needs to work.>
3. Key Use Case
<Describe a short use case scenario from the user perspective. The use case should demonstrate the integration/workflow problem.>
<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.>
4. Standards & Systems
<List existing systems that are/could be involved in the problem/solution.>
<If known, list standards which might be relevant to the solution>
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>