This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "20110622 SAIF AP ConCall"

From HL7Wiki
Jump to navigation Jump to search
 
Line 188: Line 188:
  
 
''Adjourned 10:59 AM Eastern Time
 
''Adjourned 10:59 AM Eastern Time
 +
 +
===New Action Items ===
 +
<!-- <br/> carriage break to copy  ******-->
 +
Dave – Send out a Doodle poll to move the call to Wednesdays at 11am
 +
<br/>
 +
Austin - Set up a Wiki page to gather input as to how the Strategic Initiatives are relative to SAIF AP work.  Quality planning/definition will be one aspect of this.

Latest revision as of 18:56, 22 June 2011

SAIF Architecture Program – 2011-06-22 Meeting

Return to SAIF Architecture Program Wiki Home Page<br\> Return to SAIF AP Meeting Minutes and Agendas


Meeting Logistics

  • Dates: Weekly on Wednesdays
  • Time: 10:00 - 11:00 Eastern
  • Phone Number: +1 (770) 657 9270
  • Participant Passcode: 124466
  • Web Coordinates: https://www2.gotomeeting.com/join/762026090 Meeting ID: 762-026-090
    • Note that this diffes from our usual GoToMeeting ID, as it was not available this week

Agenda

  1. Role Call
  2. Agenda Review
  3. Next step for Project Services Adoption Process document
    • From the Saturday Q4 TSC Meeting in Orlando, the following was in the meeting minutes:
      • Introducing new processes to HL7: Austin, at TSC Tracker # 1681
      • Status: Project Services is drafting Adoption Process document
      • folding into SAIF AP - close
  4. HL7 Strategic Initiatives driving Governance SAIF Governance and Strategic Initiatives Document
  5. OO Project Update (Patrick)
  6. Recurring Agenda Items
    1. Review project list to determine which should be brought in under the SAIF AP umbrella (#1855)
    2. Tooling/Enterprise Architecture Update (Jane Curry)
    3. Pilot Coordination updates (Rick Haddorff)
      1. Any new Coordination items? (Team)
      2. Project Schedule progress (Rick Haddorff)
  7. Action item review (see below)
  8. Next steps

Action Items to Review

  • None to review


Link to the Complete List of Action Items/Issues/Risks (GForge)

Meeting Attendees

X=Present on Call

Facilitator Austin Kreisler Note taker(s) David Hamill
Attendee Name Affiliation
X Austin Kreisler TSC Chair
Brian Pech Interested Participant
X David Hamill HL7 HQ / Program Manager
Ed Tripp Domain Experts SD \ TSC
Gregg Seppala Product Quality Plan Project
X Jane Curry Tooling
Jim McClay Emergency Care
John Moehrke Security Cookbook
John Quinn HL7 CTO
Lloyd McKenzie MnM Work Group / SAIF Implementation Guide Pjt
Lorraine Constable Composite Order Pjt \ OO Behavioral Framework Pjt
X Patrick Loyd OO Work Group / Composite Order Pjt
Rick Haddorff Project Services WG / SAIF Pilot Coordination Pjt
Robert Lario Object Management
X Steve Hufnagel ArB / SAIF Book Project / SOA
Wendy Huang Implementation Conformance WG
Gary Dickinson EHR WG
X Pat Van Dyke EHR WG
Quorum Requirements Met: Yes

Minutes

Minutes/Conclusions Reached:

Project Services Adoption Process document

  • Austin wants to wait for SAIF AP to look at this until after the TSC reviews the document.
  • The document will be reviewed by the TSC in the coming weeks, hence the document should be ready for the SAIF AP team to review it in late July.

HL7 Strategic Initiatives driving Governance SAIF Governance and Strategic Initiatives Document

  • Publishing Quality is focused on the technical quality -- i.e. the quality of the delivered product.
  • SAIF AP Quality will focus on quality of processes.
  • From the Strategic Initiatives document (Each of the items has ‘measure’ criteria):
  1. Product Quality Has improved
  2. Requirements traceability has been enabled
  3. HL7 Standards Implementation has gotten easier
  4. Cross-Artifact inconsistency has become measurable
  5. A plan for decreasing cross-artifact inconsistency has been developed
  6. Cross-Artifact inconsistency is reduced
  7. A matrix of EHR functional capabilities vs. HL7 products has been developed


  • Determining Quality Criteria is the first step.
  • Project Scope Statement is one identifiable quality item.
  • From the SAIF AP quality work, we may need to modify the Project Scope Statement with additional questions/fields.
  • Additional quality steps may require similar types of documents/deliverables. For instance, having requirements balloted or reviewed.
  • Next Steps:
  • Get a Wiki page set up to incorporate ideas for quality based on the Strategic Initiative points.
  • Jane: working on the business context artifact
  • Austin: Wrappers R2 requirements gathering project 772. This may be an early adopter of Jane’s business context artifact work.

OO Project Scope Statement Updates<br\>

  • OO approved all 3 PSS a couple of weeks ago.
  • The Lab Order Template lacked one implementer and working on closing this loop.
  • OO is meeting tomorrow. Patrick should have more updates next week for the SAIF AP call.
  • EA Software recently from v8 to v9; so Lorraine and Jane need to discuss what OO should do (stay on v8 or move to v9).
  • Jane: an upgrade to v9, should be seamless. Jane’s recommendation is to keep your version up to date.
  • Patrick: There has been issues with sharing of packages in the past with EA.
  • Jane wants to be kept informed of issues encountered so she can bring forward to Sparx.

Next Steps<br\> Steve: EHR System Functional Model be a SAIF AP project.

Gforge Accounts can be requested via: http://gforge.hl7.org/gf/account/?action=UserAdd

Adjourned 10:59 AM Eastern Time

New Action Items

Dave – Send out a Doodle poll to move the call to Wednesdays at 11am
Austin - Set up a Wiki page to gather input as to how the Strategic Initiatives are relative to SAIF AP work. Quality planning/definition will be one aspect of this.