Direct-to-Cloud-Constrained Devices - Detailed Proposal

1. Proposed Work Item: <initial working name for work item>

• Proposal Editor: Michael J. Kirwan
• Proposal Contributors: <List other proposal contributors, or just list all on the above line>
• Profile Editor: Tim Frost
• Profile Contributors: <Optionally, list other people who have volunteered to contribute significantly to drafting the Profile>
• Domain: DEVices

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 describes the technical scope of the work and the proposed approach 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. The Technical Committee may revise/expand this section when doing the effort estimation.>

<If any context or "big picture" is needed to understand the transaction, actor and profile discussion below, that can be put here>

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

<The material below also serves as the breakdown of tasks that the technical committee will use to estimate the effort required to design, review and implement the profile. It helps a lot if it is reasonably complete/realistic.>

<READ PROPOSER HOMEWORK IN Proposal Effort Evaluation FOR GUIDANCE ON POPULATING THE FOLLOWING SECTIONS >

Actors

• (NEW) <List possible new actors>
• <List existing actors that may be given requirements in the Profile.>

Transactions

• (NEW) <List 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.>
• <List existing transactions that may be used and which might need modification/extension.>

Profile

• <Describe the main new profile chunks that will need to be written.>
• <List existing profiles that may need to be modified.>

Decisions/Topics/Uncertainties

• <List key decisions that will need to be made, open issues, design problems, topics to discuss, and other potential areas of uncertainty>
• <Credibility point: A proposal for a profile with any degree of novelty should have items listed here. If there is nothing here, it is usually a sign that the proposal analysis and discussion has been incomplete.>

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 has indicated an interest in implementing/prototyping the Profile if it is published this cycle.>

7. Risks

<List real-world practical or political risks that could impede successfully fielding the profile.>

<Technical risks should be noted above under Uncertainties.>

8. 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):

• xx% for MUE
• yy% for MUE + optional

Editor:

TBA

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