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

20141202 arb minutes

From HL7Wiki
Jump to navigation Jump to search

ARB - Meeting (Date in Title)


  1. Call to order
  2. Roll Call
  3. Approval of Agenda and Minutes
  4. Management
  5. Governance
    1. FHIR workgroup
  6. Methodology (30 minutes)
    1. BAM sections Review:
      1. Section 7 Business Architecture Bo, Lorraine
      2. Section 8 Implementation Lorraine
  7. Other business and planning
  8. Adjournment

Meeting Information

HL7 ArB Work Group Meeting Minutes

Location: Telcon

Date: 20141202
Time: 5:00pm U.S. Eastern
Facilitator Julian, Tony Note taker(s) Julian, Tony
Attendee Name Affiliation
X Bond,Andy NEHTA
X Constable, Lorraine Constable Consulting Inc.
R Dagnall, Bo HP Enterprise Services
. Hufnagel, Steve ?????
X Julian, Tony Mayo Clinic
X Knapp, Paul Pknapp Consulting
. Loyd, Patrick ICode Solutions
R Lynch, Cecil Accenture
X Milosevic, Zoran Deontik Pty Ltd
. Quinn, John Health Level Seven, Inc.
X Stechishin,Andy CANA Software and Service Ltd.
. Guests
. Kreisler, Austin Former HL7 TSC Chair
. Duteau, Jean Duteau Design, Inc
. Shakir, Abdul Malik City of Hope National Medical Center
. Laakso, Lynn HL7
. Legend
X Present
. Absent
R Regrets
Quorum Requirements (Co-chair + 3) Met: Yes


  1. Governance
    1. FHIR work Group
      1. Lorraine: FGB - Grahame - relationships with othere groups change Consult with to collaborate with. Asked the authors of the charter to modify charter to define the relationahips to other groups. Will go to FMG tomorrow.
      2. Lloyd: In FHIR, we typically don't have a conceptual or logical level. We focus on the implementable level only - and make that intuitive enough you can use it at the conceptual and logical levels. For example, FHIR doesn't have a separate conceptual or logical data types model - we just have the implementable level. We define exactly how the content will appear in the XML and JSON syntaxes as part of defining what the structures will be.
      3. Lorraine: Not true.
      4. Andy S: Only decide on serialization.
      5. Paul: M&M does the methodology.
      6. Zoran: Interesting: When I presented SAIF Grahame was there, and he did not like that FHIR is at the implementable level, Grahame thinks it is at the logical level.
      7. Paul: As an organization we would expect a logical level: Otherwise there would be no expection of patterns.
  2. Discussion: There needs to be a discussion at FMG: Clearly the delineation between logical and implementable needs to be thought about. If implementable only, then it is an ITS spec, from which the XML and JSON spec would be derived. This includes conceptual level architecture, logical architecture, and implementation architecture. Certainly the behavior is defined at the conceptual level as well as the logical level. An implementable spec still has a model.
  3. Methodology
    1. Discussion of Chapter 6.- RACI chart vs Product architecture diagrams.
    2. Families are internal - aligned to methodology. Adopted based on capability.
    3. Lines are the variety of families to an application. Align with domains. SD are organized by lines. Driven by customers, consistent message.
  4. Adjournment
    1. Adjourned at 6:10 Eastern

Tony Julian (talk) 14:47, 4 December 2014 (UTC)