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

Difference between revisions of "20120821 HL7 AP ConCall"

From HL7Wiki
Jump to navigation Jump to search
 
(2 intermediate revisions by the same user not shown)
Line 128: Line 128:
 
=================================================================--->
 
=================================================================--->
 
<!-- <br/> carriage break to copy  ******-->
 
<!-- <br/> carriage break to copy  ******-->
 
'''Review Governance Related Project Scope Statements '''
 
* [http://gforge.hl7.org/gf/download/trackeritem/2326/9518/HL7BAMPSSv3.doc ArB HL7 Business Architecture Model (HL7 BAM)] at [http://gforge.hl7.org/gf/project/tsc/tracker/?action=TrackerItemEdit&tracker_item_id=2326&start=0 TSC Tracker # 2326]
 
*[http://gforge.hl7.org/gf/download/trackeritem/2327/9538/HL7TSCBAMGovernanceSystemPSS.doc Project approval] *in committee* for ''TSC Governance System for HL7 Business Architecture''  at [http://gforge.hl7.org/gf/project/tsc/tracker/?action=TrackerItemEdit&tracker_item_id=2327&start=0 TSC Tracker # 2327]
 
*[http://gforge.hl7.org/gf/download/trackeritem/2325/9517/HL7ArchitectureProgramPSS.doc Project Scope update] for HL7 Architecture Program (HL7 AP) formerly the SAIF Architecture Program at [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=751 Project Insight #751], and [http://gforge.hl7.org/gf/project/tsc/tracker/?action=TrackerItemEdit&tracker_item_id=2325&start=0 TSC Tracker # 2325]
 
**See also Risk Assessment and Governance for HL7 Architecture Program at [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=901 Project Insight # 901]
 
 
 
 
  
 
'''Initial discussions of coordinating the interaction between the three Business Architecture projects '''
 
'''Initial discussions of coordinating the interaction between the three Business Architecture projects '''
 
#Governance/Management/Methodology
 
#Governance/Management/Methodology
 
#Expanding the business architecture throughout the organization   
 
#Expanding the business architecture throughout the organization   
 
  
 
*The projects are currently being voted on by the TSC.
 
*The projects are currently being voted on by the TSC.
 
 
*TSC discussed how to manage the boundaries between Governance/Management/Methodology.
 
*TSC discussed how to manage the boundaries between Governance/Management/Methodology.
 
*The ArB deliverables will be architectural-flavored documents with architecture as the focus.
 
*The ArB deliverables will be architectural-flavored documents with architecture as the focus.
Line 150: Line 139:
 
*Rick volunteered to assist with this work as part of the Project Coordination team.
 
*Rick volunteered to assist with this work as part of the Project Coordination team.
  
*Austin: Each precept for to governance/management/methodology is wrapped by a governance point, and we will need to identify the processing/methodology, etc. which will require coordination from the TSC, ArB and others.
+
*Austin: Each precept for to governance/management/methodology is wrapped by a governance point, and we will need to identify the processing/methodology, etc. which will require coordination from the TSC, ArB and others. For instance, take the architectural model and translate it into actionable terms, identify inputs, and flesh out governance points.
For instance, take the architectural model and translate it into actionable terms, identify inputs, and flesh out governance points.
 
  
 
*Austin presented the first draft of a [http://gforge.hl7.org/gf/project/saif-arch-pgm/docman/?subdir=426 slide that reflects the coordination needed between Governance/Management/Methodology].
 
*Austin presented the first draft of a [http://gforge.hl7.org/gf/project/saif-arch-pgm/docman/?subdir=426 slide that reflects the coordination needed between Governance/Management/Methodology].
 
*His first challenge is to find the best term for the 'coordination' necessary between Governance/Management/Methodology.  'Communication' may be the best term.
 
*His first challenge is to find the best term for the 'coordination' necessary between Governance/Management/Methodology.  'Communication' may be the best term.
  
*Austin presented the first draft of a http://gforge.hl7.org/gf/project/saif-arch-pgm/docman/?subdir=426 swim lane diagram as a more detailed step from the above slide].
+
*Austin presented the first draft of a [http://gforge.hl7.org/gf/project/saif-arch-pgm/docman/?subdir=426 swim lane diagram] as a more detailed step from the above slide.
 
*Austin has asked the ArB to complete the diagrams as part of their architecture modeling
 
*Austin has asked the ArB to complete the diagrams as part of their architecture modeling
  
Line 167: Line 155:
 
Adjourned 12:51 PM Eastern Time
 
Adjourned 12:51 PM Eastern Time
  
 +
<br/>
 +
===New Action Items ===
 +
<!-- <br/> carriage break to copy  ******-->
 +
Dave to add the following to the 2012 Sept WGM agenda:
 +
*High level review of the BAM and what the artifacts will look like. 
 +
*Discuss the educational needs around the BAM and it's artifacts
 
<br/>
 
<br/>

Latest revision as of 15:42, 22 August 2012

HL7 Architecture Program – 2012-08-21 Meeting

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


Meeting Logistics

Agenda

  1. Role Call
  2. Agenda Review
  3. Initial discussions of coordinating the interaction between the three Business Architecture projects
    1. Governance/Management/Methodology
    2. Expanding the business architecture throughout the organization
  4. Recurring Agenda Items
    1. Pilot Coordination updates (Rick Haddorff)
      1. Any new Coordination items? (Team)
      2. Project Schedule progress (Rick Haddorff)
  5. Action item review (see below)
  6. Next steps

Action Items to Review

  • Owner:
    • ID # and Description
      • Any update or other question?


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
X David Hamill HL7 HQ / Program Manager
X Jane Curry Tooling
Charlie Mead ArB
X John Quinn HL7 CTO
Lloyd McKenzie MnM Work Group / SAIF Implementation Guide Pjt
Lorraine Constable Composite Order Pjt / OO Behavioral Framework Pjt
Patrick Loyd OO Work Group / Composite Order Pjt
X Rick Haddorff Project Services WG / SAIF Pilot Coordination Pjt
Pat Van Dyke EHR WG
Steve Hufnagel ArB / SAIF Book Project / SOA
Wendy Huang Implementation Conformance WG
Freida Hall Project Services WG
Alean Kirnak Immunization IG Project
Ioana Singureanu Project Services WG
Lynn Laakso HQ Staff Support
Quorum Requirements Met: Yes

Minutes

Initial discussions of coordinating the interaction between the three Business Architecture projects

  1. Governance/Management/Methodology
  2. Expanding the business architecture throughout the organization
  • The projects are currently being voted on by the TSC.
  • TSC discussed how to manage the boundaries between Governance/Management/Methodology.
  • The ArB deliverables will be architectural-flavored documents with architecture as the focus.
  • The Architecture Program will take those documents and translate them into a more user friendly format so it's more readable by the bulk of the HL7 community, much like what Project Services did with the HDF.
  • Rick volunteered to assist with this work as part of the Project Coordination team.
  • Austin: Each precept for to governance/management/methodology is wrapped by a governance point, and we will need to identify the processing/methodology, etc. which will require coordination from the TSC, ArB and others. For instance, take the architectural model and translate it into actionable terms, identify inputs, and flesh out governance points.
  • Austin presented the first draft of a swim lane diagram as a more detailed step from the above slide.
  • Austin has asked the ArB to complete the diagrams as part of their architecture modeling
  • At the 2012 September WGM, we should have an initial cut of the BAM from the ArB for review by the HL7 AP team and discuss the Educational needs around the BAM.
  • Risk Assessment process: Identify the risk; triage the risk; develop a Mitigation strategy


Adjourned 12:51 PM Eastern Time


New Action Items

Dave to add the following to the 2012 Sept WGM agenda:

  • High level review of the BAM and what the artifacts will look like.
  • Discuss the educational needs around the BAM and it's artifacts