This wiki has undergone a migration to Confluence found Here

20130113 arb Phoenix-F-F

From HL7Wiki
Jump to navigation Jump to search

ARB - Meeting (Date in Title)

Logistics

Pointe Hilton Hotel, Phoenix AZ, USA

At a Glance

DayDateTimeIconEventChairScribeRoom
SaturdayJanuary 12, 2013Q1-Q4technical iconBAM Focus GroupTBDTBDTBD
SundayJanuary 13, 2013Q1-Q3technical iconBAMRonTonyPhoenix 2
SundayJanuary 13, 2013Q5technical iconTSC ReportN/ATonyGeronimo
TuesdayJanuary 15, 2013Q4technical iconAs comes up in the WGMRonTBDSonora
ThursdayJanuary 17, 2013Q3technical iconBusiness med.gifTBDRonTonyPalo Verde
ThursdayJanuary 17, 2013Q4NoMeetingN/ARonN/AN/A

Icons:

  • wiki business icon business icon
  • wiki ballot reconciliation icon ballot reconciliation icon
  • wiki technical icontechnical icon
  • wiki no meeting Icon No meeting

Saturday

Agenda Q1-Q4

  • Focus group on the Business Architecture model

Sunday

Meeting Information

HL7 ArB Work Group Meeting Minutes

Location: Phoenix WGM

Date: 20130113
Time: 4:00pm U.S. Eastern
Facilitator Parker, Ron Note taker(s) Julian, Tony
Attendee Name Affiliation
X Bond,Andy NEHTA
X Constable, Lorraine Constable Consulting Inc.
X Curry, Jane Health Information Strategies
X Dagnall, Bo HP Enterprise Services
. Grieve, Grahame Health Intersections Pty Ltd
X Hufnagel, Steve U.S. Department of Defense, Military Health System
X Julian, Tony Mayo Clinic
. Loyd, Patrick ICode Solutions
X Lynch, Cecil Accenture
X Mead, Charlie National Cancer Institute
X Milosevic, Zoran Deontik Pty Ltd
X Parker, Ron CA Infoway
. Quinn, John Health Level Seven, Inc.
. Guests
. Shakir, AbdulMalik
X Walker, Mead
. Legend
X Present
. Absent
R Regrets
Quorum Requirements Met: Yes

Agenda - Q1

  1. Call to order
  2. Roll Call
  3. Approval of Agenda
  4. Approval of Previous Minutes
  5. Report from Architecture Project
  6. FHIR
    1. Management
    2. Governance Board
  7. BAM(Moved to Q2/Q3)
  8. Item2
  9. Other business and planning
  10. Adjournment

Minutes - Q1

  • Plan to turn DAM over to TSC.
  • Adopt UML version.
  • Discussion
    • Andy: There is a problem with sequencing in the flattened version.
    • Steve: Can do data-flow in UML
    • Ron: Dont have a authority to model some of the data flows. Need to agree on the level of the pitch - with ArB as methodologist.
    • Charlie: We can use internally whatever representation we want. John Quinn wants the initial publishing format to be UML.
    • Andy: No problem with that.
    • Charlie: We were to build an exemplar that the organization could flesh out. I outlined with John Quinn. Unfortunate that there is no transform. Tonight present to the TSC the metamodel, walk through, explain why it is not exactly like the RIM, show the commonalities, breakdown of the three products.
    • Jane: Agenda to revist step 1 - the ends are another form of artifact, means are behaviours. Define process of means to achieve the ends.
    • Ron: Seque to Step 4. Yesterday had interesting conversation mapping persons to role. What does this mean for co-chairs, steering divisions, etc. Next step for TSC. Avoid prescription at this point.
    • Jane: Distinguish roles.
    • Bo: Include meta-model and profiles tonight.
    • Ron: Get enough start this morning to determine who is doing what q2/q3. One group may need to go away to do the narrative.
    • Bo: Presented model: yellow are original classes.White are additions. Who participates how to create what artifacts. Addition of conformance criteria to measure quality. Product collections are either product lines or product families. Used to create a profile. Profile has classes based on base classes. Role is specialized to bring in Manager, Consult, Methodoligist, Governor.
    • Charlie: Does this address proponents and champions?
    • Jane: Not resolved. Proponent is an influencer who tends to be external, while champion tends to be internal.
    • Bo: Specialized behaviours as management, Governance, Methodologist. Then created the flattened view - may be teased out into a more dynamic model. Who, How, and what are modelled. Why and When are not modeled. Step 0 is proposal, Step 3 is design.
    • Ron: Need to provide reframing of spreadsheet to extend the model - in Q3.
    • Charlie: We need them to give us this information in another form.
    • Ron: When we get to ballot, we ballot DAM's. Usually informative. We declare difference between Informative and Normative. We had to introduce the balloting cycle.
    • Charlie: Specialize ballot into state machine.
    • Jane: The internal publication is a process of putting together intentions. Does not have the step where the conceptual goes to ballot. Modelled as processes.
    • Charlie: Dont want to make the state machine into a process.
    • Jane: Internal publication process needs link to the portions of the model.
    • Bo: There is a pattern, but the inputs/outputs change.
    • Jane: Different activity models.
    • Lorraine: Quality criteria for one phase is an input to the Quality criteria for the next state.
    • Andy: Not necessarily a sequential set of steps.
    • Ron: All governance points are an assessment of risks, and determination of need to escalate - a checkpoint.
    • Charlie: There are types of governance points.
  • The remainder of the quarter was spent on modeling the BAM.

Agenda Q2

  1. Mission and charter reference to SAIF
  2. BAM

Minutes - Q2

  • Mission and charter reference to SAIF
    • Motion: To approve the wording of mission and charter requirement and forward to TSC(Jane/Bo):
    • The [workgroup name] will develop specifications using the principles and language of the SAIF CD and the restrictions and specializations of the HL7 SAIF IG to ensure traceability from Conceptual to Logical to Implementable specifications.
    • Those workgroups involved in submitting artifacts or methodology to the HL7 SAIF IG will develop this content in compliance with the principles and language of the SAIF CD.
    • Vote: (9-0-1)
  • The remainder of the quarter was spent on modeling the BAM.

Agenda Q3

  1. BAM

Minutes - Q3

  • The quarter was spent on modeling the BAM.

Q5 - Joint with TSC

  1. BAM!

Tuesday

Meeting Information

HL7 ArB Work Group Meeting Minutes

Location: Phoenix WGM

Date: 20130113
Time: 4:00pm U.S. Eastern
Facilitator Charlie Mead/ Parker, Ron Note taker(s) Julian, Tony/????
Attendee Name Affiliation
. Bond,Andy NEHTA
. Constable, Lorraine Constable Consulting Inc.
. Curry, Jane Health Information Strategies
. Dagnall, Bo HP Enterprise Services
. Grieve, Grahame Health Intersections Pty Ltd
. Hufnagel, Steve U.S. Department of Defense, Military Health System
. Julian, Tony Mayo Clinic
. Loyd, Patrick ICode Solutions
. Lynch, Cecil Accenture
. Mead, Charlie National Cancer Institute
. Milosevic, Zoran DEONTIK
. Parker, Ron CA Infoway
. Quinn, John Health Level Seven, Inc.
. Guests
.
. Legend
X Present
. Absent
R Regrets
Quorum Requirements Met: Yes

Agenda Q4

Thursday

Meeting Information

HL7 ArB Work Group Meeting Minutes

Location: Phoenix WGM

Date: 20130117
Time: 4:00pm U.S. Eastern
Facilitator Parker, Ron Note taker(s) Julian, Tony
Attendee Name Affiliation
X Bond,Andy NEHTA
X Constable, Lorraine Constable Consulting Inc.
X Curry, Jane Health Information Strategies
. Dagnall, Bo HP Enterprise Services
. Grieve, Grahame Health Intersections Pty Ltd
. Hufnagel, Steve U.S. Department of Defense, Military Health System
X Julian, Tony Mayo Clinic
. Loyd, Patrick ICode Solutions
X Lynch, Cecil Accenture
. Mead, Charlie National Cancer Institute
. Milosevic, Zoran Deontik Pty Ltd
X Parker, Ron CA Infoway
. Quinn, John Health Level Seven, Inc.
. Guests
.
. Legend
X Present
. Absent
R Regrets
Quorum Requirements Met: Yes

Thursday Q3

Agenda

  1. BAM Follow through
    1. Completion of artifacts
    2. Transition and faciliatation
  2. Things arising from Update on SAIF Architecture
  3. Things arising from Product Line Kickoff Meeting
  4. Completion of SAIF-CD
  5. Meeting Schedule for Atlanta

Minutes Q3

  1. BAM follow through
    1. Figure out how we are going to deploy EA within ArB and manage repository versioning.
    2. Completion of BAM artifacts
      1. Review Frieda’s process model and update process lifecycle diagram. Charlie and Bo
      2. Create proper activity diagrams and state transition diagrams. Charlie and Bo
      3. Update meta-model profiles, spreadsheets, and models so far to reflect i and ii.
      4. Embed definitions for the data capture tool items in the reference section of the spreadsheet
      5. Further segment the lists of roles / behaviours etc… by life-cycle stage
      6. Harmonize the lists of things in the reference section to the work done by AMS in the product catalog and Ron has done for FHIR
      7. From ii harvest the reusable process patterns such as publications, balloting, project scope planning
      8. Steps 1 and 2 need to be redone in new data collection tool
      9. Take the outputs of iv and put it into the model
      10. Pass 1 – just for artifacts, behaviours, participants, roles, and parties
      11. TSC to assign responsibilities to fill out data collection tool for remaining lifecycle stages for ballotable products
      12. ArB models the work resulting from TSC assignments
      13. Map flattened UML to proper UML
      14. Using TSC Risk Assessment identify organizational and typical product Governance Points and corresponding precepts, metrics, and processes (who?)
      15. Need to add to the model and the spreadsheets constructs for the why (means and ends) values in the value statements and the criteria which is the conformance content and realization of the value statements
      16. Pass 2 by repeating steps x through xii Pass 2
      17. Model Vitality process
      18. Conformity assessment processes to guide current or imminent new product development
      19. Start creating exemplary instances from the BAM
      20. Model processes for context neutral components (data types, cmets, harmonization processes)
      21. Create a high-level product hierarchy / taxonomy
        1. Product Lines
        2. Product families
        3. Product family sub-components
    3. Transition and Facilitation
  2. Things arising from SAIF Architecture Program Meeting
  3. Things arising from Product Line Kickoff Meeting
  4. Completion of SAIF CD
    1. Complete Glossary
  5. Meeting schedule for Atlanta
    1. Sunday q1-q4
    2. Tuesday Q4
    3. Thursday q3&q4