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

Difference between revisions of "20080716 ARB Jump Start"

From HL7Wiki
Jump to navigation Jump to search
Line 19: Line 19:
  
 
== 11-12 – HL7 Enterperise Architecture Framework (HEAF)==
 
== 11-12 – HL7 Enterperise Architecture Framework (HEAF)==
*Who are HL7's  customers?
+
(SOA Development Framework)
**Anyone who benefits from or contributes to our specifications.
+
#Who are HL7's  customers?
**Indirect customers are  
+
*Anyone who benefits from or contributes to our specifications.
***everyone who contributes to healthcare, keeping in mind that the definition of healthcare varies between jurisdictions.
+
*Indirect customers are  
***Those who benefit by our production.
+
**everyone who contributes to healthcare, keeping in mind that the definition of healthcare varies between jurisdictions.
** Direct customers are the people who contribute, either financially or otherwise.
+
**Those who benefit by our production.
*What are HL7's "customers" asking ?
+
* Direct customers are the people who contribute, either financially or otherwise.
**Means to reduce barriers to interoperability
+
#What are HL7's "customers" asking ?
***Technical strategies
+
*Means to reduce barriers to interoperability
****V2 vs V3
+
**Technical strategies
****Messages vs Services
+
***V2 vs V3
***Technical solutions
+
***Messages vs Services vs CDA
*What do "we"(HL7's) think our customers need?
+
**Technical solutions
*What of our customer needs are we willing, able, and prepared to provide
+
***Something that can be implemented DSTU?
*What perparations need to be made to enable us to meed customer needs and expectations as desired.
+
 
 +
#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
 +
#What of our customer needs are we willing, able, and prepared to provide
 +
*We are not ready to provide implementable solutions
 +
*We may partner with others e.g. OMG
 +
*Samples
 +
 
 +
#What perparations need to be made to enable us to meed customer needs and expectations as desired.
 +
 
 +
==We should plan to evangelize to a list of groups, and seek their input.==
 +
**Foundation Steering Division
 +
**Technical Services Division
 +
**Work groups as needed
  
 
== 12-1 – lunch==
 
== 12-1 – lunch==

Revision as of 15:53, 16 July 2008

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-
      Enterprise cloud
      • 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-12 – HL7 Enterperise Architecture Framework (HEAF)

(SOA Development Framework)

  1. Who are HL7's customers?
  • Anyone who benefits from or contributes to our 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.
  1. What are HL7's "customers" asking ?
  • Means to reduce barriers to interoperability
    • Technical strategies
      • V2 vs V3
      • Messages vs Services vs CDA
    • Technical solutions
      • Something that can be implemented DSTU?
  1. 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
  1. What of our customer needs are we willing, able, and prepared to provide
  • We are not ready to provide implementable solutions
  • We may partner with others e.g. OMG
  • Samples
  1. What perparations need to be made to enable us to meed customer needs and expectations as desired.

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

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

12-1 – lunch

1-3 – Service Specifications, Conformance

3-4 – 2bBAM modeling

4-5 – open discussion with Observers

Adjournment

Tony