Detailed Proposal

From IHE Wiki
Revision as of 09:13, 18 November 2008 by Landenbain (talk | contribs) (New page: ==1. Proposed Profile: ''<initial working name for profile>''== * Proposal Editor: ''<Name of author/editor/contact for the proposal>'' * Profile Editor: ''<Name of candidate Lead Editor ...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

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

  • Proposal Editor: <Name of author/editor/contact for the proposal>
  • Profile Editor: <Name of candidate Lead Editor for the Profile, if possible>
  • Date: N/A (Wiki keeps history)
  • Version: N/A (Wiki keeps history)
  • 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.">