This wiki has undergone a migration to Confluence found Here
Difference between revisions of "20140902 arb minutes"
Jump to navigation
Jump to search
m (→Minutes) |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 15: | Line 15: | ||
--> | --> | ||
=ARB - Meeting (Date in Title)= | =ARB - Meeting (Date in Title)= | ||
| − | |||
==Agenda== | ==Agenda== | ||
#Call to order | #Call to order | ||
| Line 118: | Line 117: | ||
==Minutes== | ==Minutes== | ||
| + | #Agenda and minute approval: | ||
| + | ##'''Motion''' To approve minutes and agenda (andy s, cecil) | ||
| + | ##'''Vote''' 3-0-1 | ||
| + | #Methodology: | ||
| + | ##DAM: Information and Behavior are optional | ||
| + | ##Normative: Information and behavior are expected: | ||
| + | ##Andy: Absent Behavior and information the DAM is incomplete. | ||
| + | ##Cecil: Example of Behavior? Is it the attributes associated between the objects. | ||
| + | ##Lorraine: LAB model defines Behavior. | ||
| + | ##AndyB: DAM not bound to particular behavioral expectations should state no binding to Behavior. If there is no behavior did you just miss it? | ||
| + | ##Cecil: LAb dam is more thatn a DAM. | ||
| + | ##Lorraine: Nutritional order behavior is around use cases. Ideally behavior is a SHOULD, not a SHALL. | ||
| + | ##Proposal to state INFORMATION is required, and Behavior is a SHOULD. | ||
| + | ##Behavioral constraints SHALL be explicitly stated, or specifically excluded. | ||
| + | ##Information requirement SHALL be explicitly stated, or specifically excluded. | ||
| + | ##Tony will edit the document and circulate. | ||
| + | #Adjournment | ||
| + | ##Meeting adjourned at 6:00pm Eastern | ||
| + | [[User:Ajulian|Tony Julian]] ([[User talk:Ajulian|talk]]) 16:07, 3 September 2014 (UTC) | ||
[[Category:2014 Arb Minutes]] | [[Category:2014 Arb Minutes]] | ||
Latest revision as of 21:05, 9 September 2014
ARB - Meeting (Date in Title)
Agenda
- Call to order
- Roll Call
- Approval of Agenda and Minutes
- Management
- Governance
- Methodology (30 minutes)
- Review of changes to the DAM definition
- BAM sections Review:
- Section 7 Business Architecture Bo, Lorraine
- Section 8 Implementation Lorraine
- Other business and planning
- Next week: Ron will join us to work on the BAM
- 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 | ||||||
Minutes
- Agenda and minute approval:
- Motion To approve minutes and agenda (andy s, cecil)
- Vote 3-0-1
- Methodology:
- DAM: Information and Behavior are optional
- Normative: Information and behavior are expected:
- Andy: Absent Behavior and information the DAM is incomplete.
- Cecil: Example of Behavior? Is it the attributes associated between the objects.
- Lorraine: LAB model defines Behavior.
- AndyB: DAM not bound to particular behavioral expectations should state no binding to Behavior. If there is no behavior did you just miss it?
- Cecil: LAb dam is more thatn a DAM.
- Lorraine: Nutritional order behavior is around use cases. Ideally behavior is a SHOULD, not a SHALL.
- Proposal to state INFORMATION is required, and Behavior is a SHOULD.
- Behavioral constraints SHALL be explicitly stated, or specifically excluded.
- Information requirement SHALL be explicitly stated, or specifically excluded.
- Tony will edit the document and circulate.
- Adjournment
- Meeting adjourned at 6:00pm Eastern
Tony Julian (talk) 16:07, 3 September 2014 (UTC)
