This wiki has undergone a migration to Confluence found Here

20140902 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
  6. Methodology (30 minutes)
    1. Review of changes to the DAM definition
    2. BAM sections Review:
      1. Section 7 Business Architecture Bo, Lorraine
      2. Section 8 Implementation Lorraine
  7. Other business and planning
    1. Next week: Ron will join us to work on the BAM
  8. Adjournment

Meeting Information

HL7 ArB Work Group Meeting Minutes

Location: Telcon

Date: 20140902
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 Curry, Jane Health Information Strategies
. Dagnall, Bo HP Enterprise Services
. Hufnagel, Steve U.S. Department of Defense, Military Health System
X Julian, Tony Mayo Clinic
. Loyd, Patrick ICode Solutions
X Lynch, Cecil Accenture
. Milosevic, Zoran Deontik Pty Ltd
. Parker, Ron CA Infoway
. Quinn, John Health Level Seven, Inc.
X Stechishin,Andy CANA Software and Service Ltd.
. Guests
. Duteau, Jean Duteau Design, Inc
. Shakir, Abdul Malik City of Hope National Medical Center
. Legend
X Present
. Absent
R Regrets
Quorum Requirements (Co-chair + 3) Met: Yes


  1. Agenda and minute approval:
    1. Motion To approve minutes and agenda (andy s, cecil)
    2. Vote 3-0-1
  2. Methodology:
    1. DAM: Information and Behavior are optional
    2. Normative: Information and behavior are expected:
    3. Andy: Absent Behavior and information the DAM is incomplete.
    4. Cecil: Example of Behavior? Is it the attributes associated between the objects.
    5. Lorraine: LAB model defines Behavior.
    6. AndyB: DAM not bound to particular behavioral expectations should state no binding to Behavior. If there is no behavior did you just miss it?
    7. Cecil: LAb dam is more thatn a DAM.
    8. Lorraine: Nutritional order behavior is around use cases. Ideally behavior is a SHOULD, not a SHALL.
    9. Proposal to state INFORMATION is required, and Behavior is a SHOULD.
    10. Behavioral constraints SHALL be explicitly stated, or specifically excluded.
    11. Information requirement SHALL be explicitly stated, or specifically excluded.
    12. Tony will edit the document and circulate.
  3. Adjournment
    1. Meeting adjourned at 6:00pm Eastern

Tony Julian (talk) 16:07, 3 September 2014 (UTC)