Rad TF Maintenance 2008-09 - Detailed Proposal

Target: Prepare CP's for Ballot for March? Jan?

Number of outstanding CPs:

3 Completed CPs (which received comments during the last ballot period that couldn't be resolved in time for inclusion in TF v9.0, and thus will need some amount of rework)

15 New CPs submitted to "Incoming" that have not yet been reviewed/ assigned

List of "non-trivial" CPs:

CP-051 : Clarify Image Manager requirements in PGP profile (D.Heaney)
- Lots of missing requirements in the profile
  - what are the management requirements?
  - Is the Image Manager required to be a Display?
- Basically means writing PGP 2.0 to "fix" anything. The CP should simply clarify that there are no current specific requirements, but perhaps add some general "should have some way to do" requirements
- Really IHE has not done a good job yet downstream of the PACS. Using/Sharing Images more widely with consistent views and workflow support is a "gap".
CP-082 : Dependency Table: clarification of dependency requirements, and better understanding (C. Dickmann)
CP-117 : Addition of Cardiology CARD-1 Option (multi-modality support) to SWF (C. Lindop/ K. O'Donnell)
- Cancelled - deferred to SWF 2.0
CP-118 : Addition of Cardiology CARD-3 Option (intermittent modality support) to SWF (TBD)
- Cancelled - deferred to SWF 2.0
CP-137 : IM/IA receives more or less instances than it expects as per MPPS (C. Lindop)
CP-xxx (new) : Clarify grouping requirements for PDI Portable Media Importer (TBD)
CP-xxx (new) : Clarify semantics of R for RAD-14 Query Images
CP-xxx (new) : Clarify the attributes for distance measurements in Mammo Profile

List of outstanding items not yet submitted as CPs:

Harmonization work from the HL7 task force (when it becomes available) will affect the HL7 Implementation guide section(s) of the Framework.

List of other maintenance tasks:

7. Risks

Any technical or political risks related to expected maintenance items?

There are several "large" assigned or new CPs that could consume a large chunk of committee time if not managed properly. (E.g., CP-051)
Cross-domain coordination of the R2/ RE harmonization work will likely cause it to proceed at a slower pace than other maintenance items. Also true for the harmonization work being done by the cross-domain HL7 task force).

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

5-10% (Somewhat elastic. Most aren't urgent/critical. Some could be wrapped up post-cycle in April/June.)

Responses to Issues:

See italics in Risk and Open Issue sections

Candidate Editor:

Chris Lindop/David Clunie