This wiki has undergone a migration to Confluence found Here
Difference between revisions of "20080716 ARB Jump Start"
Jump to navigation
Jump to search
Line 20: | Line 20: | ||
== 11-12 – HL7 Enterperise Architecture Framework (HEAF)== | == 11-12 – HL7 Enterperise Architecture Framework (HEAF)== | ||
(SOA Development Framework) | (SOA Development Framework) | ||
− | + | '''Who are HL7's customers?''' | |
+ | *Anyone who benefits from or contributes to our specifications. | ||
*Indirect customers are | *Indirect customers are | ||
**everyone who contributes to healthcare, keeping in mind that the definition of healthcare varies between jurisdictions. | **everyone who contributes to healthcare, keeping in mind that the definition of healthcare varies between jurisdictions. | ||
**Those who benefit by our production. | **Those who benefit by our production. | ||
* Direct customers are the people who contribute, either financially or otherwise. | * Direct customers are the people who contribute, either financially or otherwise. | ||
− | + | '''What are HL7's "customers" asking ?''' | |
*Means to reduce barriers to interoperability | *Means to reduce barriers to interoperability | ||
**Technical strategies | **Technical strategies | ||
Line 33: | Line 34: | ||
***Something that can be implemented DSTU? | ***Something that can be implemented DSTU? | ||
***Sample content | ***Sample content | ||
− | + | '''What do "we"(HL7's) think our customers need?''' | |
*Computable semantec interoperability(CSI) | *Computable semantec interoperability(CSI) | ||
**We have not connected the dots between the benefits and work to get there. | **We have not connected the dots between the benefits and work to get there. | ||
Line 52: | Line 53: | ||
*Reuse | *Reuse | ||
*Flexibilty and stability | *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 are not ready to provide implementable solutions | ||
*We may partner with others e.g. OMG | *We may partner with others e.g. OMG | ||
Line 63: | Line 64: | ||
**format | **format | ||
**processes | **processes | ||
− | **tools | + | **Acts/tools |
*conformance criteria /processes at the various levels | *conformance criteria /processes at the various levels | ||
**How do we express adherence | **How do we express adherence | ||
+ | **How do we assert adherence | ||
**How do we demonstrate adherence | **How do we demonstrate adherence | ||
*Dynamic model | *Dynamic model |
Revision as of 16:21, 16 July 2008
Contents
- 1 Minutes: Work in progress
- 1.1 8-10 - Conformance and Compliance, Conformance Models
- 1.2 10-11 – Review of 2bBAM Modeling
- 1.3 11-12 – HL7 Enterperise Architecture Framework (HEAF)
- 1.4 We should plan to evangelize to a list of groups, and seek their input.
- 1.5 12-1 – lunch
- 1.6 1-3 – Service Specifications, Conformance
- 1.7 3-4 – 2bBAM modeling
- 1.8 4-5 – open discussion with Observers
- 1.9 Adjournment
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.
- Enterprise diagram-
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) 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.
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?
- Sample content
- Technical strategies
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
- Acts/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
We should plan to evangelize to a list of groups, and seek their input.
- Foundation Steering Division
- Technical Services Division
- Work groups as needed