Difference between revisions of "FTSD-F2F-20090112"

From HL7 TSC
Jump to navigation Jump to search
(New page: =Foundation and Technology Steering Division Workgroup Meeting= FTSD - Foundation & Technology Steering Division ==Attendees== *Implementable Technology Specifications (ITS) ** Dale Nelso...)
 
 
(13 intermediate revisions by the same user not shown)
Line 4: Line 4:
 
==Attendees==
 
==Attendees==
 
*Implementable Technology Specifications (ITS)
 
*Implementable Technology Specifications (ITS)
 +
** Charlie McCay
 +
** Paul Knapp
 
** Dale Nelson
 
** Dale Nelson
** Paul Knapp
 
** Charlie McCay
 
 
*Implementation/Conformance
 
*Implementation/Conformance
 
** Jason Rock
 
** Jason Rock
** Jenni Puyenbroek
 
 
** Frank Oemig
 
** Frank Oemig
** Dick Harding
 
 
*Infrastructure & Messaging (InM)
 
*Infrastructure & Messaging (InM)
** Graham Grieve
+
** Grahame Grieve
 +
** Sandy Stuart
 +
** Tony Julian
 
*RIM-Based Application Architecture (RIMBAA)
 
*RIM-Based Application Architecture (RIMBAA)
 
*Modeling & Methodology (MnM)
 
*Modeling & Methodology (MnM)
Line 22: Line 22:
 
** Mike Davis
 
** Mike Davis
 
** Bernd Blobel
 
** Bernd Blobel
 +
** Glen Marshall
 
*Service Oriented Architecture (SOA)
 
*Service Oriented Architecture (SOA)
 
**Ken Rubin
 
**Ken Rubin
**Juha Mykkanen
+
**Galen Mulrooney
 +
** Richard Soles soles@omg.org
 +
** John Koisch
 
*Templates
 
*Templates
 +
** Mark Shafarman
 
*Vocabulary
 
*Vocabulary
 
** Ted Klein
 
** Ted Klein
 
** Beverly Knight
 
** Beverly Knight
 +
** Russ Hamm
  
 
==Agenda==
 
==Agenda==
  
<p>1. ''(05 min)'' Roll Call</p>
+
<p>1. ''(05 min)'' Introductions</p>
<p>2. ''(05 min)'' [[FTSD-ConCall-20080610|Approve Minutes]] Ted/Beverly 17-0-0, Approve Agenda: Jenni/Mike - 17-0-0 </p>
+
<p>2. ''(10 min)'' Announcement: Work Group Health - spreadsheet
<p>2. ''10 min''Announcement: Work Group Health - spreadsheet
 
 
Ff the information in the spreadsheet is correct, then work groups that received a score of 5 or greater may need to investigate the root cause and let the SD know if there are any issues. Typically, our work groups appear to be working productively.</p>
 
Ff the information in the spreadsheet is correct, then work groups that received a score of 5 or greater may need to investigate the root cause and let the SD know if there are any issues. Typically, our work groups appear to be working productively.</p>
<p>3.''10 min'' Announcement: </p>
+
<p>3.''(10 min)'' Announcement: SWOT and Three-year planning: The TSC is looking for each committee to provide a SWOT analysis and a Three-year planning spreadsheet identifying the major projects and their milestones. Lynn Laakso has aligned the projects in the SD with to an objective in the HL7 Roadmap. We need to look at those project that are not aligned with a roadmap objective. Either the roadmap is incomplete or the project is not in the roadmap.</p>
<p>5.''(10 min)'' '''InM Work Group Mission Change''' [http://hl7projects.hl7.nscee.edu/docman/view.php/52/267/InM%20mission%20and%20Charter%20Revision.zip InM Mission Charter Change]- withdrawn, returned to WG</p>
+
<p>2. ''(05 min)'' Call for additional agenda items
Description: InM Mission Charter Change to represent recent changes: <br/>Java SIG realignment and reorganization, changes in scope, etc.
 
<p>6. (7.5 min) '''Scope issues ''' (Jason Rock)</p>
 
 
<ul>
 
<ul>
<li>
+
<li>"Security cookbook" for HL7: how do we adopt it? The cookbok for security threat assessment is intended to help committees evaluate their artifacts. </li>
Marketing WG initiated a project to establish a registry of CDA Implementation Guides even though ITC has an on-going registry project(s).
+
<li> Beverly Knight indicated that an ad-hoc "Glossary project" was initiated by Heather Grain who is active both in ISO members and a co-chair of Vocab work group. This informal project is intended to align glossary items between the two SDOs. Publishing work group is currently managing the glossary but the request for collaboration came to Vocabulary work group. Woody Beeler will work with Beverly and Heather to identify the best way to coordinate and publish the resulting artifacts.</li>
Steering Division is asked to raise the issue to the TSC regarding better cooperation and coordination across work groups. (Jason/Lloyd) 17-0-0
+
<li>Galen Mulrooney asked that the ArB representatives communicate clearly when they are making a request on behalf of the ArB and when they are simply submitting a personal request.</li>
<ul>
+
<li>Ken Rubin asked what is the procedure to extend the trial use period for a DSTU. Charlie McCay that this procedure should be documented in the GOM and it will added if it is not included in the GOM already. Publishing would initiate the removal of an expired DSTU by consulting the work group first.</li>
<li>We need to notify all co-chairs about proposed/intended projects (including Board-sponsored ones). A SD acceptance or rejection of proposed projects is expected.</li>
+
<li> Ken Rubin proposed a RASCI chart to roll out the SAEAF and manage the responsibilities of the various work groups in the steering division. Charlie indicated that the SAEAF is not as fast as expected.
<li>We need a better way to deal with board-sponsored vs. TSC sponsored project because they have a different approval process.</li>
+
</li>
<li>The TSC and SDs need to know if a work group is proposing something that affects the SD it should be communicated to the co-chairs and they should be provided an opportunity to raise any concerns.</li>
 
<li>RSS feed to automate the broadcast of change notifications to the "project scope statement" place.</li>
 
 
</ul>
 
</ul>
</li>
 
 
<p>7. (5 min) ''' Core Principles Doc''' (Ted Klein) witdrawn</p>
 
There is a question regarding reballoting "Core Principles" but Vocab is not willing to proceed with the Jan ballot due to the large number of comments. There may not be enough time to address the large number of substantive vocab comments.
 
* If any issues are raised across WGs in the SD, should they be raised to the SD?
 
<p>8.  (10 min) '''SAEAF Discussion''' (Charlie McCay)</p>
 
SD to endorse the distribution of the following candidate documents not later than two weeks prior to the January WGM:
 
* Plan documenting the acceptance and review process of the SAEAF.
 
* Plan documenting the organizational adoption of the SAEAF post acceptance including technical and organizational impact analysis.
 
* The proposed SAEAF including open issues and concerns.
 
Ken Rubin/Woody Beeler 17-0-1
 
<p>9.''(5 min)'' '''Other Business'''</p>
 
<p> All the WG in the SD should reserve Q3-Q4, Wed for a discussion of the SAEAF.</p>
 
 
  
 +
</p>
  
  

Latest revision as of 01:59, 13 January 2009

Foundation and Technology Steering Division Workgroup Meeting

FTSD - Foundation & Technology Steering Division

Attendees

  • Implementable Technology Specifications (ITS)
    • Charlie McCay
    • Paul Knapp
    • Dale Nelson
  • Implementation/Conformance
    • Jason Rock
    • Frank Oemig
  • Infrastructure & Messaging (InM)
    • Grahame Grieve
    • Sandy Stuart
    • Tony Julian
  • RIM-Based Application Architecture (RIMBAA)
  • Modeling & Methodology (MnM)
    • Ioana Singureanu
    • Lloyd McKenzie
    • Woody Beeler
  • Security
    • Mike Davis
    • Bernd Blobel
    • Glen Marshall
  • Service Oriented Architecture (SOA)
    • Ken Rubin
    • Galen Mulrooney
    • Richard Soles soles@omg.org
    • John Koisch
  • Templates
    • Mark Shafarman
  • Vocabulary
    • Ted Klein
    • Beverly Knight
    • Russ Hamm

Agenda

1. (05 min) Introductions

2. (10 min) Announcement: Work Group Health - spreadsheet Ff the information in the spreadsheet is correct, then work groups that received a score of 5 or greater may need to investigate the root cause and let the SD know if there are any issues. Typically, our work groups appear to be working productively.

3.(10 min) Announcement: SWOT and Three-year planning: The TSC is looking for each committee to provide a SWOT analysis and a Three-year planning spreadsheet identifying the major projects and their milestones. Lynn Laakso has aligned the projects in the SD with to an objective in the HL7 Roadmap. We need to look at those project that are not aligned with a roadmap objective. Either the roadmap is incomplete or the project is not in the roadmap.

2. (05 min) Call for additional agenda items

  • "Security cookbook" for HL7: how do we adopt it? The cookbok for security threat assessment is intended to help committees evaluate their artifacts.
  • Beverly Knight indicated that an ad-hoc "Glossary project" was initiated by Heather Grain who is active both in ISO members and a co-chair of Vocab work group. This informal project is intended to align glossary items between the two SDOs. Publishing work group is currently managing the glossary but the request for collaboration came to Vocabulary work group. Woody Beeler will work with Beverly and Heather to identify the best way to coordinate and publish the resulting artifacts.
  • Galen Mulrooney asked that the ArB representatives communicate clearly when they are making a request on behalf of the ArB and when they are simply submitting a personal request.
  • Ken Rubin asked what is the procedure to extend the trial use period for a DSTU. Charlie McCay that this procedure should be documented in the GOM and it will added if it is not included in the GOM already. Publishing would initiate the removal of an expired DSTU by consulting the work group first.
  • Ken Rubin proposed a RASCI chart to roll out the SAEAF and manage the responsibilities of the various work groups in the steering division. Charlie indicated that the SAEAF is not as fast as expected.


Agenda items

Action Item List

Back to Meetings