20090922 arb Atlanta wgm

Minutes Template

Architecture and Review Board Meeting Minutes

September 22, 2009

Back to Agenda-minutes

Name	Present	With	Affiliation	E-mail address
Curry, Jane	Yes	ArB	Health Information Strategies	janecurry@healthinfostrategies.com
Grieve, Grahame	?	ArB	Kestral Computing	grahame@kestral.com.au
Julian, Tony	?	ArB	Mayo Clinic	ajulian@mayo.edu
Koisch, John	?	ArB	NCI	koisch_john@bah.com
Loyd, Patrick	?	ARB	Gordon point Informatics LTD.	patrick.loyd@gpinformatics.com
Lynch, Cecil	?	ArB	ontoreason LLC	clynch@ontoreason.com
Mead, Charlie	?	ArB	Booz Allen Hamilton	charlie.mead@booz.com
Nelson, Dale	?	Arb	II4SM	dale@zed-logic.com
Ocasio, Wendell	?	ArB	Agilex Technologies	wendell.ocasio@agilex.com
Parker, Ron	?	ArB	CA Infoway	rparker@eastlink.ca
Quinn, John	?	ArB	Health Level Seven, Inc.	jquinn@HL7.org
Shakir, Abdul-Malik	?	ArB	Shakir Consulting	ShakirConsulting@cs.com
Bear, Yogi(template)	?	Guest	US Dept. Interior, Park Service	yogi@jellystonepark.gov

Call to order

The meeting was called to order at by chair <name> with <name> as scribe.

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

Discussion

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 

JC: ArB asking MnM to identify the artifacts to be included int the Grid. First order of business is to produce documentation: What artifacts do we produce, and where do we put them.

RP: MnM is not ready for this.

JC: Today MnM would point to HDF as methodolgy.

JK: Does MnM define folders?

JC: we hand it off to MnM; we do it and force MnM to use it, or we work together.

RP: MnM has their way now.

JK: Part of rollout is impacts to publishing.

RP: My proposal - learning process. Once it is sorted out . .

1. Framework introduces new artifacts.
2. We declare them.
3. we sit with MnM and ask what would fit without any problem.
4. What is white space, where are the gaps, and are they relevant.
5. Post as part of methodology.
6. MnM assert discovery process
7. facilatators push to projects.

PL: we have generated artifacts and interactive. We have tooling needs, the first versions will be manually produced.

RP: I know MnM will get very interested. For Alpha we will need slack.

JC: We can say that.

RP: we need to do CF further.

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

Behavioral Framework (formerly known as Dynamic Model)

JC: I need to show governance framework thursday.

JK: Further modeling efforts. BF separates accountability - who does what when. Services, V3 messages, documents define this using different foundations.

• Services formalise accountability for accountability around the roles.
• V3 message specs formalice accountability to sender/receiver
• SDA accountability is deferred to the receiver
• business process - can be formalized behind interfaces, cn be evaluated more precisely.

GG: The ADA detila minimal accountability.

PL: They are not orthogonal. V3 messages is a transport mechanism as well as the transport. Documents dont describe transport.

RP: I dont disagree.

JK: formalize accountability in a contract.

GG: Services and messages bind at a different time, CDA defers to the user.

JK: what we are trying to do with BF is to give artifacts that they already understand. We want to make sure as we transform between messages/documents/services we do it right.

 All should read the education documents posted at:

JK: Contracts maek specific rules agout content, platforms, and localizations that may or may not be part of a given statndard. e.g. contracts may contain quality of service agreements.

JK: V3 O&O separated responsibility into three parties. (Projected POLB_IN111100).

JC: tooling is waiting for the BF.

JK: The dynamic model has never been formally approved.

JK: We are not only changing models, messages, documents - the needs of our customers have changed. We need drive by interoperability. You cannot rely on business model.

GG: It is still valid.

JK: Now we have a world where the customers are enterprises, having infrastructure, need structures to apply to their business model. We have presumed for months that our concepts are valid. When you separate accountability conceptually, and it is still valid a lot of the time. But there are a lot of organizations that have formalized infrastructure and processes.

JC: you cannot pull in design conceptions in the model level.

RP: From a national project this is a big deal.

GG: We are talking about a maturity model for the industry.

JK: I am not sure that if you apply to existing, it will not be mature.

JK: V3 has captured the semantics of the vertical model of interactions better than other industries. We re-organized it based on feedback. What were were trying to understand it HL7 Roles. (required for RM-ODP - which shoves them onto roles). We can build solutions out of conceptual, platform independent, or platform independent. The solutin package contains the contract template, with a rich behavioral model. We can ballot role: V3 ballots receiving roles + event driven packages. We can ballot behaviors. Now we must ballot dependencies.

JC: we already said we had to do it.

JK: Dont know how to get around it. half of drive-by interoperability needs services.

JC: business now understand that the rules are now important.

RP: Where have you said that?

JK: I said it public to combined educational session. Don Mon was there, ed, Austin was there. This is a formalization of all the change we have discussed.

RP: What do we have?

JK: Q3 we have a project with OO to provide dynamic model we need.

GG: Express appreciation for John's work.

JK: Wednesday Q3: Hans J. Buitendijk: "The agenda is focusing on Composite Order to understand how to apply the Behavioral Model work in progress, as well as get better insight how to ensure that content that is to be conveyed through various mechanisms (using Composite Order and CDA R3 as an example) is to be modeled/documented. The following will be used to test it: a Lab Order and Medication Order with a Lab Test for context as part of a Composite Order, while that same lab test is also used as context in a CDA R3 document that also may document the existence of the medication order that was communicated through the Composite Order.

In today's world and understanding, the way to apply the SAEAF behavorial model to the payload is not clear, and ensuring the core payload is consistent regardless of exchange mechanism is not clear. Hopefully Wednesday Q3 and Q4 will provide substantial progress in these two areas to enable OO to complete Composite Order (and subsequently Clinical Event Reporting), while it can help other work groups as well as the ARB and MnM promote consistency in approach across work groups.

"

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!

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]]

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

Col1	Col 2	Col 3	Col n
Col1	Col 2	Col 3	Col 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)