Difference between revisions of "Cross-Domain Strategic Planning Work Group Tcon Minutes 2010-10-25"
Jump to navigation
Jump to search
Chrisdcarr (talk | contribs) |
Chrisdcarr (talk | contribs) |
||
| Line 11: | Line 11: | ||
==Minutes== | ==Minutes== | ||
| − | * | + | * Reviewed [[ITI Strategic Planning]] materials (Mike Nusbaum) |
:* Establishes personal liaisons with other domains and process to communicate | :* Establishes personal liaisons with other domains and process to communicate | ||
:* Other domains can submit work requests to ITI for needs they have | :* Other domains can submit work requests to ITI for needs they have | ||
| − | * | + | * Reviewed [[Process]] and [[IHE Profile Design Principles and Conventions]] wiki pages (Kevin O'Donnell) |
:* Education Materials, Wiki Pages intended to guide technical framework development processes | :* Education Materials, Wiki Pages intended to guide technical framework development processes | ||
:* The ways committees develop profiles has diverged--How to fix? | :* The ways committees develop profiles has diverged--How to fix? | ||
::* Document and ask compliance? | ::* Document and ask compliance? | ||
| − | ::* Establish liaison relationships ( | + | ::* Establish liaison relationships (with ITI; among all domains) |
| − | ::* Establish oversight group (like DICOM WG6, HL7 Architecture Review) | + | ::* Establish oversight group (like DICOM WG6, HL7 Architecture Review Board) |
| − | :::* Could be multiple | + | :::* Could be multiple review groups, each one based on different base standards (this could cause more "silo" issues) |
:* Early cross-domain or central review of proposed work items? | :* Early cross-domain or central review of proposed work items? | ||
:* Strategic review of overall existing [https://spreadsheets.google.com/ccc?key=0AkfpWndrzLS2dEJnTmo3VlVIbHpEbmowcG1pamxUN3c&hl=en&authkey=CID59tIJ inventory of profiles] at domain level and identify gaps/redundancies | :* Strategic review of overall existing [https://spreadsheets.google.com/ccc?key=0AkfpWndrzLS2dEJnTmo3VlVIbHpEbmowcG1pamxUN3c&hl=en&authkey=CID59tIJ inventory of profiles] at domain level and identify gaps/redundancies | ||
| Line 27: | Line 27: | ||
| − | * | + | * Identification of Problem |
| − | :* Uniformity of process | + | :* Uniformity of process across committees |
| − | :* Coordination of | + | :* Coordination of committee work items |
| − | ::* Coordination work between ITI and clinical specialties | + | ::* Coordination work between ITI and clinical specialties |
::* Coordination among clinical specialties (liaison between all committees | ::* Coordination among clinical specialties (liaison between all committees | ||
Revision as of 15:29, 25 October 2010
Attendees
- Chris Carr
- Emmanuel Cordonnier
- Mike Nusbaum
- Kevin O'Donnell
Minutes
- Reviewed ITI Strategic Planning materials (Mike Nusbaum)
- Establishes personal liaisons with other domains and process to communicate
- Other domains can submit work requests to ITI for needs they have
- Reviewed Process and IHE Profile Design Principles and Conventions wiki pages (Kevin O'Donnell)
- Education Materials, Wiki Pages intended to guide technical framework development processes
- The ways committees develop profiles has diverged--How to fix?
- Document and ask compliance?
- Establish liaison relationships (with ITI; among all domains)
- Establish oversight group (like DICOM WG6, HL7 Architecture Review Board)
- Could be multiple review groups, each one based on different base standards (this could cause more "silo" issues)
- Early cross-domain or central review of proposed work items?
- Strategic review of overall existing inventory of profiles at domain level and identify gaps/redundancies
- Identification of Problem
- Uniformity of process across committees
- Coordination of committee work items
- Coordination work between ITI and clinical specialties
- Coordination among clinical specialties (liaison between all committees