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

Difference between revisions of "20090922 arb Atlanta wgm"

From HL7Wiki
Jump to navigation Jump to search
Line 122: Line 122:
  
 
DN: Publishing governance of ITS.
 
DN: Publishing governance of ITS.
 +
  Tony will post list of facilitators
 +
 +
 +
=== List of facilitators ===
 +
 +
* NCI - Charlie & John
 +
# CaEHR - cancer Ambulatory Care EHR
 +
# SMS - Specification Management System
 +
 +
* Infoway - Ron parker
 +
# Blueprint 2015
 +
 +
* Gov. Projects, DOD - Charlie
 +
# EHR FM Mapping
 +
 +
* SD
 +
# Oregon Procedure Report Implementation Guide - Cecil
 +
# CDA R3 - Patrick
 +
 +
* Security - AMS
 +
# PASS - confirmed project
 +
 +
* OO - Patrick
 +
# OO Dynamic Model
 +
 +
* ITS - Dale
 +
# XML ITS R2 for Data types R2
 +
# ITS simplified
 +
 +
* Vocabulary - Cecil
 +
# CTS II - confirmed project
  
 
== BF==
 
== BF==

Revision as of 20:23, 22 September 2009

Minutes Template


Architecture and Review Board Meeting Minutes

September 22, 2009

Back to Agenda-minutes

Name PresentWith AffiliationE-mail address
Curry, Jane Yes ArB Health Information Strategiesjanecurry@healthinfostrategies.com
Grieve, Grahame ? ArB Kestral Computinggrahame@kestral.com.au
Julian, Tony ? ArB Mayo Clinicajulian@mayo.edu
Koisch, John ? ArB NCIkoisch_john@bah.com
Loyd, Patrick ?ARBGordon point Informatics LTD. patrick.loyd@gpinformatics.com
Lynch, Cecil ? ArB ontoreason LLCclynch@ontoreason.com
Mead, Charlie ? ArB Booz Allen Hamiltoncharlie.mead@booz.com
Nelson, Dale ?Arb II4SMdale@zed-logic.com
Ocasio, Wendell ?ArBAgilex Technologieswendell.ocasio@agilex.com
Parker, Ron ? ArB CA Infowayrparker@eastlink.ca
Quinn, John ? ArB Health Level Seven, Inc.jquinn@HL7.org
Shakir, Abdul-Malik ? ArB Shakir ConsultingShakirConsulting@cs.com
Bear, Yogi(template)?Guest US Dept. Interior, Park Serviceyogi@jellystonepark.gov

Call to order

The meeting was called to order at

Agenda approval

MMS to approve the agend below <name/name> Vote:(0-0-0)

  • Call to order
  • Approval of agenda
  • Approval of minutes
  • PASS - Cecil
  • BF
  • Governance - Jane

mms to approve the agenda. Tony/Loyd 9-0-

PASS

CL: Question is they are doing a services profile for user authentication: How do they map it to SAEAF? Want it to be reusable across any industry. They have a DAM, and will create rim-based instantiation, which will get them to Platform Independent. They are still at the conceptual level. There use case is passing identifiers - you have to know the source. II datatypes are not alwayse supported by other industries. First concrete advice we have to give.

JC: Does that mean any of the rim-derived data structures are not platform-independent because of data-types?

CL: Not cross-industry. Only works if DAM does not include data-types?

JK: Is the question methodological?

CL: Need guidance so they can create generic hand-off to OMG, and fit SAEAF.

RP: How are we going to provide advice for that?

CL: Jane was correct. We should respond to what a DAM is. I volunteered to write the definition of a DAM. Mead is going to write it, and Cecil will help hammer it out. Make explicit definition, to address issues. Must be clearly defined to be used cross-industry.

RP: Where is this stuff placed? Must be posted, and be accepted.

JC: How do we publish it?

RP: Not in just there world.

JC: We now have a Gforge that could be used. Publishing has the need for a shared-artifact repository, including relationships to other artifacts. With ability to pull out custom packages.

RP: in the absence of that, do we have a recommendation?

JC: People need to register the project, post the scope statement in insight, get gforge access, and post it there.

PL: Is that the way it is to be done.

JC: no, it is just an idea.

RP: Need to formalize for Alpha projects.

JK: Not gforge - it is a swamp - we need to consider a formal folder structure.

JC: not posting anonymously.

JC: we dont have enough knowledge, and dont know recommendations.

JK: you need tortise. There is the issue of models, and how to publish. EA? Otherwise it is a governance problem.

RP: Agreed, we have to put a framework for them to publish into. It must be visible.

JC: we need to practice what we preach.

DN:Where is it, and how do we use it? I tried to get the document,and I could not find the latest document.

JC: We have gforge documentation, but it is not well published, or communicated. If part of the SAEAF alpha project includes that, then we should incorporate the intructions.

RP: Who will take point

JC: I will take point. We need a recommended structure.

JK: Another thing to publish, so recommend a folder structure in SVN, forcing people to use the files publication in GFORGE.

JC: Formalized version control.

JK: Different view for outside users than developers. If we develop formal framework, we will have modeling issues. There are solutions we should look at.

RP: Any precident from TSC?

JK: We have R3, which includes EHR functional model, PASS will put in anything, OO will put in detailed dynamic models, CTS2 will put threads of rainbow documents.

JC: we need an action item with a deliverable. I will ask Wilfred Bonney to work with whomever, so we can draw from what he has.

RP:Identify methodology for view and project use.

JC: Thursday Q1 collaboration tools from electronic services. - should align.

RP: We need push model to get it to alpha team. Do we have an education process.

JC: Short gotomeeting walkthru, including MnM in the process.

RP:So you (jane) are going to kick this off.

JC: We have two MnM co-chairs in the room.

RP: Prefer we take it to MnM quickly.

JC: Who can take to MnM on friday? We need concurrence from MnM, and communication to alpha projects.

RP: MnM participants in this room.

DN: Publishing governance of ITS.

 Tony will post list of facilitators 


List of facilitators

  • NCI - Charlie & John
  1. CaEHR - cancer Ambulatory Care EHR
  2. SMS - Specification Management System
  • Infoway - Ron parker
  1. Blueprint 2015
  • Gov. Projects, DOD - Charlie
  1. EHR FM Mapping
  • SD
  1. Oregon Procedure Report Implementation Guide - Cecil
  2. CDA R3 - Patrick
  • Security - AMS
  1. PASS - confirmed project
  • OO - Patrick
  1. OO Dynamic Model
  • ITS - Dale
  1. XML ITS R2 for Data types R2
  2. ITS simplified
  • Vocabulary - Cecil
  1. CTS II - confirmed project

BF

Governance

Agenda for rest of week

  • Finalizing agenda for week
  • Agenda Item 3
  • Other business, and planning for next meeting
  • Adjournment

Approval of minutes

MMS to approve the minutes of the <meeting> as posted to <posting site> by <name/name> Vote:(0-0-0)

Agenda Item 1

example of bullet list(s)

  • level 1
    • level 2
      • level 3
    • level 2
  • level 1

Agenda Item 2

Example of numbered list

  1. Numbered level 1
    1. Numbered level 2
      1. Numbered level 3
      2. Numbered level 3
    2. Numbered level 2
  2. Level 1

Agenda Item 3

Example of grey-boxed note:  The line begins with a space!

Other business, and planning for next meeting

Adjournment

Wiki how-to's

Link examples

Remove the <pre> and </pre> from the examples to instantiate as clickable links

wiki link with alternate name

[[Agenda_Minutes|Back to Agenda-minutes]]

Back to Agenda-minutes

Wiki image file with alternate name

[[image:wikiimage.jpg|Template]]

Example of image

document - must have uploaded it prior to accessing!

[[application/msword:Ex_word_document.doc|word document]]

word document

Note to readers: Permitted file types: png, gif, jpg, jpeg, gif, zip, pdf, jpg, txt, doc.

Fully qualified URL

http://www.hl7.org

http://www.hl7.org

  • or
[[http://www.hl7.org|HL7 Web site]]

[HL7 Web site]

Tables

Tables for HTML programmers

Col1Col 2Col 3Col n
Col1Col 2Col 3Col n

Tables for non-html

Quarter Type Topic Chair Scribe Not available MinutesRcvd
MON Q1 -- Plenary Session -- -- -- N/A

Categories

use

{{InM Open Action Items}}

to create a category

18:14, 29 August 2008 (UTC)