Difference between revisions of "20100121 arb minutes"
m (→Thursday Q3) |
m (→Thursday Q3) |
||
Line 110: | Line 110: | ||
*SAEAF and RIMBA Defered to a telcon | *SAEAF and RIMBA Defered to a telcon | ||
*Results of meeting w/Electronic services( Ron Parker) | *Results of meeting w/Electronic services( Ron Parker) | ||
+ | |||
Ron Parker: SAEAF deserves its own page, not public. There will be a public page which will refer people to ArB. It will be pointed to from other wiki pages. | Ron Parker: SAEAF deserves its own page, not public. There will be a public page which will refer people to ArB. It will be pointed to from other wiki pages. | ||
+ | |||
Jane Curry: Instead of pointing to gforge, there is now under the ArB front page. Tony will harmonize. | Jane Curry: Instead of pointing to gforge, there is now under the ArB front page. Tony will harmonize. | ||
+ | |||
Ron Parker: Met with Conformance and answered their questions. | Ron Parker: Met with Conformance and answered their questions. | ||
+ | |||
Ron Parker: Met with Electronic services: We will provide the the HTML to be presented to the public, Electronic Services will apply stylesheets. | Ron Parker: Met with Electronic services: We will provide the the HTML to be presented to the public, Electronic Services will apply stylesheets. | ||
+ | |||
Ron Parker: Timelines: PIC has peer review document, Ron talked with Helen about tweaking. | Ron Parker: Timelines: PIC has peer review document, Ron talked with Helen about tweaking. | ||
+ | |||
Jane Curry: DId we articulate that the next iteration is due 3week before next WGM. | Jane Curry: DId we articulate that the next iteration is due 3week before next WGM. | ||
+ | |||
Ron Parker: For next call will provide project plan for our cycles. We have more budget for Karen's work - two working groups meeting for here time. We need persistant tools to manage versions/content. | Ron Parker: For next call will provide project plan for our cycles. We have more budget for Karen's work - two working groups meeting for here time. We need persistant tools to manage versions/content. | ||
+ | |||
Jane Curry: We committed to find out from NCI because they are selecting tools presently. | Jane Curry: We committed to find out from NCI because they are selecting tools presently. | ||
*Revisit Governance Scope | *Revisit Governance Scope | ||
+ | |||
Ron Parker: Talked to Charlie about expectations - 10-11 pages - trying to scope down governance to match current release of ECCF and BF. | Ron Parker: Talked to Charlie about expectations - 10-11 pages - trying to scope down governance to match current release of ECCF and BF. | ||
+ | |||
Jane Curry: My pushback: There is a significant scoping excercise within the governance of the ECCF. Your interoperability community is usually a multiple-community effort. Some are constrained at the ECCF. They need to be in more than one stack. | Jane Curry: My pushback: There is a significant scoping excercise within the governance of the ECCF. Your interoperability community is usually a multiple-community effort. Some are constrained at the ECCF. They need to be in more than one stack. | ||
+ | |||
Ron Parker: I want that in. It is difficult to discuss scoping without the language. Charlie said ECCF and BF gave us a grammer. | Ron Parker: I want that in. It is difficult to discuss scoping without the language. Charlie said ECCF and BF gave us a grammer. | ||
+ | |||
Jane Curry: I dont have to do specification? | Jane Curry: I dont have to do specification? | ||
+ | |||
Ron Parker: No | Ron Parker: No | ||
+ | |||
Jane Curry: In the implementation HL7 will have to address coherence across domain. | Jane Curry: In the implementation HL7 will have to address coherence across domain. | ||
+ | |||
Ron Parker: What is needed to support current level of participation? What would the alphas need to know? | Ron Parker: What is needed to support current level of participation? What would the alphas need to know? | ||
+ | |||
Ann Wrightson: I am concerned that people tend to assume that when you do this you are introducing across organization. We need to make concious effort that it be larger than a single interop community. | Ann Wrightson: I am concerned that people tend to assume that when you do this you are introducing across organization. We need to make concious effort that it be larger than a single interop community. | ||
+ | |||
Jane Curry: Interoperability community needs to assess where focus is required, as well as the spec stack scope. When you start drawing pictures, on what subject, it depends on the share purpose at the subject level. They may make different choices for another subject. | Jane Curry: Interoperability community needs to assess where focus is required, as well as the spec stack scope. When you start drawing pictures, on what subject, it depends on the share purpose at the subject level. They may make different choices for another subject. | ||
Line 157: | Line 174: | ||
Ron Parker: Opportunities to extend. | Ron Parker: Opportunities to extend. | ||
*Information Framework Sketch | *Information Framework Sketch | ||
+ | AW: Sketched | ||
*Items brought up this meeting | *Items brought up this meeting | ||
*Adjournment | *Adjournment |
Revision as of 21:32, 21 January 2010
Minutes Template
Contents
Architecture and Review Board Meeting Minutes
<date>
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
Agenda approval
MMS to approve the agend below <name/name> Vote:(0-0-0)
- Call to order
- Approval of agenda
- Approval of minutes
- Communication action items
- Agenda Item 2
- 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 2
- level 1
Agenda Item 2
Example of numbered list
- Numbered level 1
- Numbered level 2
- Numbered level 3
- Numbered level 3
- Numbered level 2
- Numbered level 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]]
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]]
Note to readers: Permitted file types: png, gif, jpg, jpeg, gif, zip, pdf, jpg, txt, doc.
Fully qualified URL
http://www.hl7.org
- or
[[http://www.hl7.org|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)
Thursday Q3
- Call to order
- Approval of Agenda for Quarter/Day
- SAEAF and RIMBA Defered to a telcon
- Results of meeting w/Electronic services( Ron Parker)
Ron Parker: SAEAF deserves its own page, not public. There will be a public page which will refer people to ArB. It will be pointed to from other wiki pages.
Jane Curry: Instead of pointing to gforge, there is now under the ArB front page. Tony will harmonize.
Ron Parker: Met with Conformance and answered their questions.
Ron Parker: Met with Electronic services: We will provide the the HTML to be presented to the public, Electronic Services will apply stylesheets.
Ron Parker: Timelines: PIC has peer review document, Ron talked with Helen about tweaking.
Jane Curry: DId we articulate that the next iteration is due 3week before next WGM.
Ron Parker: For next call will provide project plan for our cycles. We have more budget for Karen's work - two working groups meeting for here time. We need persistant tools to manage versions/content.
Jane Curry: We committed to find out from NCI because they are selecting tools presently.
- Revisit Governance Scope
Ron Parker: Talked to Charlie about expectations - 10-11 pages - trying to scope down governance to match current release of ECCF and BF.
Jane Curry: My pushback: There is a significant scoping excercise within the governance of the ECCF. Your interoperability community is usually a multiple-community effort. Some are constrained at the ECCF. They need to be in more than one stack.
Ron Parker: I want that in. It is difficult to discuss scoping without the language. Charlie said ECCF and BF gave us a grammer.
Jane Curry: I dont have to do specification?
Ron Parker: No
Jane Curry: In the implementation HL7 will have to address coherence across domain.
Ron Parker: What is needed to support current level of participation? What would the alphas need to know?
Ann Wrightson: I am concerned that people tend to assume that when you do this you are introducing across organization. We need to make concious effort that it be larger than a single interop community.
Jane Curry: Interoperability community needs to assess where focus is required, as well as the spec stack scope. When you start drawing pictures, on what subject, it depends on the share purpose at the subject level. They may make different choices for another subject.
Ann Wrightson We discussed in ITS this morning. Some people can do this, but we need to provide a method for doing it.
Jane Curry: I disagree with your disagreement. At what point are you drawing what from where? It is not top-down driven.
Ann Wrightson I am concerned about the triangle. People only populating the implementable.
Andy Bond: Not only tech stack is computable: It should be a logical transformation. Governance can cover policy and regulation. This will control layer appropriate for community. They can get interoperability at the conceptual level.
Ann Wrightson SOme of the interoperability has not been document.
Andy Bond: It consists of some things that dont work.
Ron Parker: It is fuzzy thinking. The governance Jane needs to express is to governance in terms of ECCF - identifying shared purpose and shared governance. What is formal expression and grammer thereto. How do you govern WG's is a separate conversation.
Jane Curry: Explain "What is needed to support current level of interest and participating.
Ron Parker: Focus on the participatants. Identify formalisms or artifacts (existing or new) required for this expression. People are struggling on what the tangable things look like.
Jane Curry: I got out of tuesday a big change is the idea of authoritative requirements - who is providing, and what is their authority? From headspace? Never Declared? VS requirements stated/external with know ownership.
Ron Parker: Anything else.
Jane Curry: Interconnecting systems have to have relationships to an organization. The problem is when you cross boundaries?
Jane Curry: there are two levels - i will try not to do six.
Ron Parker: Opportunities to extend.
- Information Framework Sketch
AW: Sketched
- Items brought up this meeting
- Adjournment
Thursday Q4
- Call to order
- Approval of Agenda for Quarter
- Schedule for SAEAF document Publishing
- Alpha Facilitation
- Peer Review
- Other business and planning
- Telcon Schedule
- Next WGM meeting schedule (day/quarter)
- Adjournment