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

20081014 arb minutes

From HL7Wiki
(Redirected from 20081014 arb Telcon)
Jump to navigation Jump to search

Architecture Board


October 14, 2008

Attendees

NameWithAffiliationE-main address
Curry, Jane ArB Health Information Strategiesjanecurry@healthinfostrategies.com
Koisch, John ArB NCIkoisch_john@bah.com
Shakir, Abdul-Malik ArB Shakir ConsultingShakirConsulting@cs.com
Honey, AlanGuestII4SMaphoneysys@gmail.com
Connor, KathleenGuestMicrosoftkathleen.connor@microsoft.com

Call to order

The meeting was called to order at

  • Call to order
  • Behavioral Framework Introduction
  • Notes on Approach
  • Notes on Trajectory
  • Document Walkthrough
  • Next Steps
  • Adjournment

Approval of minutes

Agenda Item 1

JK welcomed the meeting and discussed the history and trajectory of the project.

Agenda Item 2

JK Walked through the relevant parts of the SAEAF document, as well as tying it the Behavioral Framework Paper

Agenda Item 3

JK Walked through the BF document. Essential concepts of Collaborations, Service Roles, and Contracts. Ties to other standards and frameworks discussed. Re: Service Classifications: JC - Informative service types - make sure the distinction is between the different types we're using and what the implications are when referring to each type, rather than having the names of the service types be normative. Group acknowledged the need to map this framework backwards to the HL7 DM work, as well as to the SOA ML work (from OMG).

Action Items and next steps

  1. Peer Review of document by COB Friday, October 17 for discussion during next week's ArB OOC virtual call
  2. AMS took task of modeling current HL7 DM concepts
    1. This model will facilitate the mapping from the BF to the DM
  3. JK, AH, and AMS will work jointly to map these artifacts to the existing SOA ML work, to extend where necessary, and to provide the profile to the HL7 community and the OMG community for harmonization. This communication should be two ways - HL7 has some additional things to say about SOA ML and needs to be informed about the gaps in our understanding of the SOA ML work.

Adjournment

Tony Julian