20080717 ARB Jump Start

From HL7Wiki
Jump to navigation Jump to search

Architecture Board

Minutes of the 20080717 July out-of-cycle Day 3


Call to order

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

Attendance

NameRoleAffiliationemail
Curry, Jane ArB Health Information Strategiesjanecurry@healthinfostrategies.com
Julian, Tony ArB Mayo Clinicajulian@mayo.edu
Koisch, John ArB Bozkoisch_john@bah.com
Larsen, Ed guest HITSPerlarsen@erlinc.com
Shakir, Abdul-Malik ArB Shakir ConsultingShakirConsulting@cs.com
Walker, MeadArBMead Walker Consultingdmead@comcast.net

8-9 -- open discussion with Observers

  • Discussed having a taxonomy of services
    • Need to empower the committees to name/scope services in a consistent manner so as to encourage CSI.
    • Message type is payload, Interaction includes the behavior(trigger event) and receiver responsibilities.
    • Services will have to have a richer specification.
    • There is a collaboration with other Standards Development Organizations(SDOS), but it is coming slowly
    • HITSP is forcing the attention to conformance.

September Table of Contents

Services Aware Enterprise Architecture Framework

  1. 2bBAM
    1. Drivers(Goals, customer needs, Performance measurements) Tony
    2. Organization (participants and roles) Tony
    3. Organization Structures Tony
    4. Organization Processes Tony
    5. Artifacts Jane
      1. Taxonomy and roadmap of the standards
    6. Levels of Interoperability Service Contract Specifications(ISCS) (formerly known as trading partner agreements(TPA))
    7. Stack of specifications that support ISCS's John (from EA Framework below?)
    8. Structure of HL7 delivers support for customers to craft ISCS
  2. Interoperability Service Specification
    1. Interoperability service contract specifications John (Conformance and Compliance document from NCI as content)
      1. Service enabled Dynamic Framework Mead
      2. Static Model
    2. Meta-Model
    3. Taxonomy of Services
  3. Conformance
    1. Conformance Criteria (assertions)
    2. Conformance adherence (Realization)
    3. Conformance Validation (Inspection/testing)
  4. Artifacts for SOA

Enterprise Architecture Framework

AMS: belongs in Stack of Specifications that support ISCS above

JK: I am not sure it belongs there

  1. Interoperability service contract specifications
  2. Levels of Interoperability Service Contract Specifications(ISCS) (formerly known as trading partner agreements(TPA))
  3. Stack of specifications that support ISCS's
    1. Reference
      1. Reference Information Model (Rim)
      2. Abstract data types (adt)
      3. HL7 Development framework
        1. Message Development framework
        2. Services Development framework
        3. Structured Document Development framework
        4. Electronic Health Record Functional Model
          1. Profile
      4. cpp (Email to Grahame)
      5. Guidance for using vocabulary in information structures(terminfo)
      6. Structured Vocabulary (sv)
      7. dmel
      8. IV (email to Grahame )
      9. Service Specification Methodology
    2. Blueprint
      1. Domain analysis Model(DAM)
      2. Domain Message Information Model(DMIM)
      3. Service Functional Model SFM
      4. Electronic Health Record Functional Model (EHR-FM)
    3. Platform Independent Model
      1. Refined Message Information models(RMIM)
      2. Templates
      3. CDA lgs
      4. IHE Profiles(parts)
      5. Dynamic Models (Instance)
      6. Logical Service Model
    4. Platform specific model
      1. Implementable/Implementation Technology Specification (ITS)
      2. Serialization models
      3. Web Services Description Language (WSDL) Fragments
      4. Vertical Bar (AKA Version 2) (VBAR)
    5. Platform Instance
      1. Full WSDLs
      2. Simple Object Access Protocol (SOAP)
      3. JAVA POJO/EJB
      4. Lower Level Protocol (LLP)
  4. Structure of HL7 delivers support for customers to craft ISCS
  5. Taxonomy and roadmap of the standards
  6. Ballot Quality

9-10 -- Project and Product Database

10-11 -- wrap up, task assignment, and project plan for intervening 4 weeks until third meeting

Lunch (Optional)

Afternoon working session

Work continued on the 2bBam. People volunteered to fill out portions of the content as documented in the table of contents.

The meeting was adjourned at 3:00pm U.S. EST.

Tony 18:52, 17 July 2008 (UTC)