Difference between revisions of "Profile Proposal Process"

From IHE Wiki
Jump to navigation Jump to search
Line 52: Line 52:
 
*** Some combinations make logical groups of work, e.g. due to efficiency, risk balancing, load balancing, etc.
 
*** Some combinations make logical groups of work, e.g. due to efficiency, risk balancing, load balancing, etc.
 
*** For examples of this "slate" approach, see [[Rad Plan Minutes 07.10.24|here]], [[Rad Plan Minutes 2008-10-22|here]] and [[Minutes Nov 2008 - Sep 2009#Recommendations for new work moving forward|here]].
 
*** For examples of this "slate" approach, see [[Rad Plan Minutes 07.10.24|here]], [[Rad Plan Minutes 2008-10-22|here]] and [[Minutes Nov 2008 - Sep 2009#Recommendations for new work moving forward|here]].
 
+
** This is also a good time to consider [[IHE Pipeline Impedence Matching]].
 
* Planning Committee announces selected Proposals
 
* Planning Committee announces selected Proposals

Revision as of 20:42, 9 September 2009

Announce Call for Profile Proposals

Keeping in mind that the mission of IHE Domains is to meet the global needs of their Domain, this is an important opportunity for the IHE Regions to influence the development process. Domains should do their best to solicit input from the Regional and National IHE Initiatives.

The call should be mailed to:

  • the domain Planning and Technical Committee mailing lists
  • the Domain Coordination Committee mailing list so domain cochairs can forward the call to their committees if appropriate
  • the Regional Cochairs mailing list so cochairs can forward the call

The call should be mailed at least 30 days before the deadline to allow other cochairs to put the topic on their agendas.

An example Call for Profile Proposals is here.


Select Short List

  • Submitter prepares a Brief Proposal using the template which details:
    • The current problem or currently unmet need
    • How it should work
    • A potential standard that might be applicable
  • Planning Committee reviews Brief Proposals and selects a short-list of proposals for further consideration
  • Proposals that don't make the cut may be resubmitted in later years


Perform Technical Evaluation

  • Submitter prepares a Detailed Proposal using the template which adds:
    • A more detailed use-case of the desired behavior
    • More details on relevant standards
    • A sketch proposal of what the IHE Supplement might include (new profile? new transactions? new actors?)
    • A list of potential risks (what might hang up development or implementation of such a supplement) to be managed
    • If possible, an estimate of the "business case" for addressing the problem
  • Planning Committee send Detailed Proposals to the Technical Committee
  • Technical Committee evaluates the Detailed Proposals, specifically filling in the sections for:
    • Estimate of Profile Development Effort & Product Implementation Effort
    • Candidate Editor
    • Likely development resources (who's going to help write) and information sources (who's going to tell us how it should work)
    • Clarifications and recommendations regarding scope of profile
    • General work budget including profile development and TF maintenance (CPs, editorial work, etc.)
    • Answers to Planning Committee questions
    • May participate jointly with Planning Committee in selection of Profiles and Profile slates for development
  • The updated Detailed Proposal is returned to the Planning Committee

Final Profile Selection

  • Planning Committee meets/votes to select Proposals for the next cycle
    • Consider voting on collections of proposals rather than individual proposals
      • Some combinations make logical groups of work, e.g. due to efficiency, risk balancing, load balancing, etc.
      • For examples of this "slate" approach, see here, here and here.
    • This is also a good time to consider IHE Pipeline Impedence Matching.
  • Planning Committee announces selected Proposals