20080716 ARB Jump Start

Minutes: Work in progress

Back to minutes page Agenda_Minutes

The meeting was called to order at 8:30am by John Koisch with Tony Julian as the scribe.

• • Attendees: Mead Walker, John Koisch, Tony Julian, Abdul-Malik Shakir, Jane Curry
  • Visitors: Ed Larsen

8-10 - Conformance and Compliance, Conformance Models

• Discussion was held concerning the caBIG ENterprise Integration Conformance and Compliance_016 document.
• An enterprise can be depicted as a cloud, with exposed and unexposed services.
• Multiple enterprises may overlap, with the exposed services being the intersection points.
  • Enterprise diagram-
    
    • WE know how to do this with the Internet/Intranet, and the boundaries.
    • WE do NOT know how to do this via systems or services.

10-11 – Review of 2bBAM Modeling

• Discussion was held concerning the role of the ARB in this endeavor. There is an understanding that this is the right group since the expertise is at the table.

11-1 – HL7 Enterperise Architecture Framework (HEAF)

(SOA Development Framework) Who are HL7's customers?

• Anyone who benefits from or contributes to our interoperability specifications.
• Indirect customers are
  • everyone who contributes to healthcare, keeping in mind that the definition of healthcare varies between jurisdictions.
  • Those who benefit by our production.
• Direct customers are the people who contribute, either financially or otherwise.

What are HL7's "customers" asking ?

• How to "govern" the specifications
  • How do I promote reuse
• Means to reduce barriers to interoperability
  • Technical strategies
    • V2 vs V3
    • Messages vs Services vs CDA
  • Technical solutions
    • Something that can be implemented DSTU?
    • Sample content
• Stability in the work products

What do "we"(HL7's) think our customers need?

• Computable semantec interoperability(CSI)
  • We have not connected the dots between the benefits and work to get there.
  • We can achieve incremental benefit by reducing barriers to CSI
  • CSI is a goal that can be achieved
  • CSI is 'plug and play'
• Guidance
  • Can I translate V2 to V3?
  • Implementation guides
• Standards
• Help
  • Are you ready?
  • Do you need an interface engine?
  • Education
• Solutions that they can implement directly
• Criteria for conformance
• Coherent
• Reuse
• Flexibilty and stability

What of our customer needs are we willing, able, and prepared to provide(today)

• We are not ready to provide implementable solutions
• We may partner with others e.g. OMG

What preparations need to be made to enable us to meet customer needs and expectations as desired.(Future)

• 2bBAM
• articulation of a service specification
  • Content
  • format
  • processes
  • Actions/tools
• conformance criteria /processes at the various levels
  • How do we express adherence
  • How do we assert adherence
  • How do we demonstrate adherence
• Dynamic model
  • Orchestration or choreography
  • Leverage to business needs
  • Interactions/conversations
  • Application roles
    • Specialized for specific use cases?
  • Receiver responsibilities (Contract?)
  • Pre-conditions?

We should plan to evangelize to a list of groups, and seek their input.

• • Foundation Steering Division
  • Technical Services Division
  • Work groups as needed

2- 3 – Service Specifications, Conformance

• Ed Larsen presented his suggestion to HITSP that HITSP adope a Services Based ENterprise Architectue to augment or replace its existing framework.
• HITSP does not develop standards
• Policy makers and industry create a use/modification request
• Interpoerability Specification
  • Transaction package - set of transactions
  • Transaction components or standards
  • Component translates to payload
• all derived from base standards.
• Some have come into the Framework sideways, picking and choosing
• Need to move framework into architecture
• Need to define how far down the stack the conformance testing goes
• HL7, CEN, and Eclipse are developing Services based architectures
• Ed walked us through the IS01 HITSP spec (laboratory to EHR).

Adjournment

Tony