1 / 19

HL7 CTO Focus

HL7 CTO Focus. John Quinn—CTO HL7 Kyoto Meeting May, 2009. HL7 Architecture Project (SAEAF) HL7 Tooling Project HL7 and other SDOs. Architecture Board / SAEAF. HL7 ArB. SAEAF has evolved from an overview of the Services Aware Enterprise Architecture Framework to:

jeff
Télécharger la présentation

HL7 CTO Focus

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. HL7 CTO Focus John Quinn—CTO HL7 Kyoto Meeting May, 2009

  2. HL7 Architecture Project (SAEAF) • HL7 Tooling Project • HL7 and other SDOs

  3. Architecture Board / SAEAF

  4. HL7 ArB • SAEAF has evolved from an overview of the Services Aware Enterprise Architecture Framework to: • Snapshot (High-level Overview) • Introduction • Behavioral Framework • Governance • Enterprise Conformance and Compliance Framework (ECCF)

  5. SAEAF Architecture: “A set of resources, relationships, and processes that collectively define a system and its products-of-value.” • HL7 is concerned with two architectures • #1: The organization of HL7 dedicated to producing specifications that promote interoperability within (between member participants) the “other” architecture, i.e. • #2: The collective “enterprise architecture” that supports healthcare, life sciences, and clinical research

  6. SAEAF… • Is a set ofFrameworks for producing specifications that support aspects of “HL7 architecture #2” • SAEAF is not meant to be a “complete” Enterprise Architecture • SAEAF focuses on the critical interoperability aspects of HL7 specifications in each of the three HL7 Interoperability Paradigms • Has structural, relationship, and process implications for architecture #1 • Defines the artifacts and specification semantics needed to support interoperability in healthcare, life sciences, and clinical research

  7. SAEAF • The 3 component Frameworks of SAEAF: • Behavioral Framework (deck 2) • Specification of integration semantics of IT components • Linkage of integration semantics to real-world behaviors • Governance Framework (deck 3) • Internal HL7 governance • HL7 relationships to other organizations specifying standards • Conformance/Compliance Framework (ECCF) (deck 4) • Layered to enable “degrees” of conformance and compliance • NOTE: there is no formal “Static Framework” listed because of the existing maturity of the HL7 RIM, ADT specification, CDA, etc. which are used to describe static semantics in HL7 specifications

  8. SAEAF • SAEAF… • is now stable/mature enough to begin “pilot” implementations that: • produce SAEAF-compliant message, document, and service specifications • utilize and provide feedback for SAEAF-centric Education • execute under SAEAF-triggered Change Management processes • report to the TSC or its designate • Focus of TSC activities going forward • Education • Change Management • Alpha Projects in all Interoperability Paradigms

  9. SAEAF • Sunday (2009-05-10) Trial Mappings… • SAEAF • Introduction • Behavioral Framework • Information Framework • Enterprise Conformance and Certification Framework • Governance Framework • Implementation Guide • Examples

  10. SAEAF • Sunday (2009-05-10) Trial Mappings… • EA—“Engineering” (primitives) • RIM • Vocabulary • Data Types • Implementation Technology Specifications • CDA

  11. SAEAF • Sunday (2009-05-10) Trial Mappings… • EA—“Manufacturing” (composites) (e.g.,) • CMETS • Other Domain Specific composite artifactsw Today’s View  Beta (Decision)  V1  V2  Alpha 

  12. Tooling

  13. Tooling • A high level plan was produced late last year. • Funds to execute this plan is a significant element of the HL7 Finance Proposal to the US Government and other major HL7 stakeholders. • The plan and its projected benefits for tools to facilitate enhanced product balloting & production, user creation of implementation specification and certification and testing tools have been well received.

  14. Tooling While the specific requirements of SAEAF are still being instantiated, the tooling development project’s requirements will be specified to support and align the HL7 Services Aware Enterprise Architecture Framework.

  15. Production/Publishing

  16. Production/Publishing(w/dependencies)

  17. HL7 & Other SDOs

  18. ISO TC215 • Meeting in Edinburgh end of April • Joint balloting appears to be working • WG6—7 projects in following 3 categories • Identification of Medicinal Products (IDMP) • Medical Product and Device Listing • Individual Case Safety Report (ICSR) • WG6 projects will become JIC Projects • EHR-S joint ballot

  19. SDO Charter Organization (SCO) • HL7 is a charter member of the SCO. • Other members include CDISC ASTM and US only standards organizations NCPDP and X12. • John Quinn is chair-elect (chair in 2011). • Initial discussions are now underway on the applicability of HL7 standards (e.g., RIM) to other US standards groups who have a need to support the interchange of clinical information.

More Related