Detailed Proposal Template

From IHE Wiki
Jump to: navigation, search


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

<Delete everything in italics and angle brackets and replace with real text>


1. Proposed Profile: <initial working name for profile>

  • Proposal Editor: <initial working name for profile>
  • Profile Editor: <Name of ONE candidate Lead Editor for the Profile>
  • Other Contributors: <List other people who have volunteered to contribute significantly to drafting the Profile>
  • Domain: <Domain name, E.g. Radiology>

Summary

<Many people find it easier to write this section last. Use simple declarative sentences. Avoid going into background. If it's more than a dozen lines, it's not a summary.>


<Summarize in one or two 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.">

2. The Problem

<Describe the integration problem: What doesn’t work, or what needs to work.>

<Now describe the Value Statement: what is the underlying cost incurred by the problem, what is to be gained by solving it. If possible provide quantifiable costs, or data to demonstrate the scale of the problem.>

3. Key Use Case

<Describe a short use case scenario from the user perspective. The use case should demonstrate the current integration/workflow problem. Consider a chonological bullet list of "A does X with Y".>

<Feel free to add a second use case scenario demonstrating how it “should” work. Try to show the people/systems involved, the tasks they are doing, the information they need, and hopefully where the information should come from.>

<Focus on the end user requirements, and not just the solution mechanism. Give concrete examples to help people trying to understand the problem and the nature of the solution required. Remember that other committee members reviewing the proposal may or may not have a detailed familiarity with this problem. Where appropriate, define terms.>

4. Standards & Systems

<List relevant standards, where possible giving current version numbers, level of support by system vendors, and references for obtaining detailed information.>

<List systems that could be involved/affected by the profile.>

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.>


Existing actors

<Indicate what existing actors could be used or might be affected by the profile.>

New actors

<List possible new actors>


Existing transactions

<Indicate how existing transactions might be used or might need to be extended.>

New transactions (standards used)

<Describe possible new transactions (indicating what standards would likely be used for each. Transaction diagrams are very helpful here. Feel free to go into as much detail as seems useful.>


Impact on existing integration profiles

<Indicate how existing profiles might need to be modified.>

New integration profiles needed

<Indicate what new profile(s) might need to be created.>


Breakdown of tasks that need to be accomplished

<A list of tasks would be helpful for the technical committee who will have to estimate the effort required to design, review and implement the profile.>

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 could impede successfully fielding the profile.>

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.>

<If there are no Open Issues at Evaluation Time, it is usually a sign that the proposal analysis and discussion has been incomplete.>

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 ...

Responses to Issues:

See italics in Risk and Open Issue sections

Candidate Editor:

TBA


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