Difference between revisions of "IHERO UseCase Curves and BACs"
m (IHERO UseCase 2010 4 moved to IHERO UseCase Curves and BACs) |
|||
Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
− | + | ''This template is for one or two page IHE workitem proposals for initial review.'' | |
− | * Proposal Editor: '' | + | |
− | * Editor: '' | + | ''<Delete everything in italics and angle brackets and replace with real text> |
+ | |||
+ | |||
+ | ==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>'' | ||
* Date: N/A (Wiki keeps history) | * Date: N/A (Wiki keeps history) | ||
* Version: N/A (Wiki keeps history) | * Version: N/A (Wiki keeps history) | ||
Line 13: | Line 19: | ||
==2. The Problem== | ==2. The Problem== | ||
− | + | ''<Summarize the integration problem. What doesn’t work, or what needs to work.>'' | |
==3. Key Use Case== | ==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== | ==4. Standards & Systems== |
Revision as of 11:31, 20 May 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: <Name of author/editor/contact for the proposal>
- 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
<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>