20120726 arb minutes
Jump to navigation Jump to search
ARB - Meeting (Date in Title)
- Call to order
- Roll Call
- Approval of Agenda
- Approval of Minutes
- Report from Architecture Project
- Review of Architecture Implications of Strategic Initiatives
- Other business and planning
|HL7 ArB Work Group Meeting Minutes
Time: 4:00pm U.S. Eastern
|Facilitator||Parker, Ron||Note taker(s)||Julian, Tony|
|.||Constable, Lorraine||Constable Consulting Inc.|
|X||Curry, Jane||Health Information Strategies|
|.||Dagnall, Bo||HP Enterprise Services|
|.||Grieve, Grahame||Health Intersections Pty Ltd|
|X||Hufnagel, Steve||U.S. Department of Defense, Military Health System|
|X||Julian, Tony||Mayo Clinic|
|.||Loyd, Patrick||ICode Solutions|
|.||Mead, Charlie||National Cancer Institute|
|.||Ocasio, Wendell||Agilex Technologies|
|X||Parker, Ron||CA Infoway|
|.||Quinn, John||Health Level Seven, Inc.|
|Quorum Requirements Met: Yes|
- Minute Approval
- MOTION to approve minutes(Andy/Zoran)
- VOTE (7-0-0)
- Architecture Implications of Strategic Initiatives(SI) - Jane Curry
- Dont speak to Awareness of customer base.
- Jane: Strategic Initiatives:
- We dont have measurable goals, so these are really goals instead of initiatives
- Most of part 1 are Board Level
- "Adoption" section does not have metrics
- 2.1.5 defines the beginning of a market segmentation analysis
- 2.2 is where the Business Architecture begins.
- Includes business, Board, and TSC requirements.
- 2.2.4 End to end V3/CDA template and implementation guide infrastructure has been developed
- Defines work, but requires work before TSC can implement
- 2.2.5 defines a task, but does not define measurability.
- 2.2.6 Vocab is working on aligning vocabulary across v2/v3/CDA.
- 2.3.1 Industry responsiveness has been demonstrated through the timely development and maintenance of key standards
- 2.3.2 HL7 Standards implementation has gotten easier
- 2.3.3 HL7 Education Plan has been developed
- 2.3.4 Tooling strategy has been developed - has been trialed by tooling. Grahame will come back to Board at the summer retreat with recommendation.
- 2.3.5 Product strategy has been developed - Not the same thing as product lines.
- Cecil: Issue is that there is a two-fold problem:
- Messaging and the Message Organizing and sending within a known enterprise
- Messaging in a Health Information Exchange is a larger problem. Developers are comfortable with the message space, but not what happens when the message leaves your boundaries.
- People dont know the implications of the OIDS in the exchange. - People are lost.
- Ron: Not enough guidance to use the standards.
- Cecil: Why are not all of the IT oids in the OID registry? There is an infrastructure/tooling issue.
- Jane: I realized working with the open health tools that HL7 exists in an ecosystem. The implementers are not all on the same page. We are not serving the OHT initiatives. IHE implementations: From an implementors perspective we are doing a disservice to our customers by not understanding the requirements.
- Jane: No one defined what "Easier to adopt" means. Would be better if we knew what it is. Our Business Architecture should not be anonymous to the GOM - needs to pay attention to IHE - Need to be more collaborative, make our work more accessible.
- There are Non-TSC governance issues galore.
- Ron: This is our opportunity to make comments about the SI to help the TSC meet them. We need to define assumption, abscences, and opportunities for actions by the TSC.
- Ron: The idea of broader engagement is interesting. Not sure how the TSC or Board would action them.
- Ron: This is good - we need to reframe for the TSC.
- Cecil: This is the same effort we had around SNOMED with TERMINFO. We need a similuar thing to make US MU usable.
- Jane: IHE is only one of other kinds of implementation strategies.
- Ron: How do we action what you have done?
- Jane: I defined the impact of the SI on the Business Architecture. We need to provide pushback to the TSC. There is no indication of how these are being actioned. Is there a delegation plan?
- Ron: TSC needs to map the SI to projects. We need to provide guidance to the TSC to go back to the Board where necessary. We should look at these,and assert where risks might be.
- Ron: Tony will put on agenda for next week.
- Risk assessment goes back to the TSC
- Business architecture is
- SAIF glossary is Zoran.
- Ron will provide feedback to Austin and John - they may want revisions.
- Ron: Semantic web leave for the WGM - a Lloyd and Charlie thing.
- Ron: SAIF model IG will not get to until WGM. Ron will do templating of the Architecture at the WGM.
- Adjournment at 4:50 PM Eastern.