Delta Proposal Template

<DO NOT EDIT THIS FILE DIRECTLY. See Templates for instructions on using templates.>

---

This Delta Proposal Template is for expanding copy of a Brief Proposal into a Detailed Proposal. This template and the Detailed Proposal Template should be updated in sync.

• Paste this text into a copy of your Brief Proposal
• Move the Summary section here to the end of Section 1 in your Brief Proposal
• Expand details in the Use Case Section of your Brief Proposal
• Distribute material in the Discussion Section of your Brief Proposal into the other bottom sections (5,6,7,8,9) here.

---

Summary

<Summarize in a few lines the existing problem . E.g. "It is difficult to monitor radiation dose for individual patients and almost impossible to assemble and compare such statistics for a site or a population.">

<Demonstrate in a line or two that the key integration features are available in existing standards. E.g. "DICOM has an SR format for radiation dose events and a protocol for exchanging them.">

<Summarize in a few lines how the problem could be solved. E.g. "A Radiation Dose profile could require compliant radiating devices to produce such reports and could define transactions to actors that collect, analyze and present such information.">

<Summarize in a line or two market interest & available resources. E.g. "Euratom and ACR have published guidelines requiring/encouraging dose tracking. Individuals from SFR are willing to participate in Profile development.">

<Summarize in a line or two why IHE would be a good venue to solve the problem. E.g. "The main challenges are dealing with the chicken-and-egg problem and avoiding inconsistent implementations.">

5. Technical Approach

<This section can be very short but include as much detail as you like. The Technical Committee will flesh it out when doing the effort estimation.>

<Outline how the standards could be used/refined to solve the problems in the Use Cases. The Technical Committee will be responsible for the full design and may choose to take a different approach, but a sample design is a good indication of feasibility.>

<If a phased approach would make sense indicate some logical phases. This may be because standards are evolving, because the problem is too big to solve at once, or because there are unknowns that won’t be resolved soon.>

Breakdown of tasks

<As the basis for the effort estimation, enumerate the tasks to develop the Profile text. E.g.>

• <Discuss/Confirm use case list (currently 5) to decide in/out of scope and details>
• <Analyze/choose which report guidelines to use>
• <Resolve open issue on the degree of computer parsability>
• <Draft/Review content definition for Oncology Report (profile use of CCDA)>
• <Draft/Review transaction for Retrieve Report>

6. Support & Resources

<List groups that have expressed support for the proposal and resources that would be available to accomplish the tasks listed above.>

<Identify anyone who as indicated an interest in implementing/prototyping the Profile if it is published this cycle.>

7. Risks

<List technical or political risks that will need to be considered to successfully field the profile. Demonstrate to the TC/PC your understanding/appreciation of the problem space>

8. Open Issues

<Point out any key issues or design problems. This will be helpful for estimating the amount of work and demonstrates thought has already gone into the candidate profile.>

9. Tech Cmte Evaluation

<The technical committee will use this area to record details of the effort estimation, etc.>

Effort Evaluation (as a % of Tech Cmte Bandwidth):

• 35% for ...

Candidate Editor:

TBA

<Delete this Category Templates line since your specific Profile Proposal page is no longer a template.>