1 / 7

HL7 Artifacts within SAIF ECCF

HL7 Artifacts within SAIF ECCF. HL7 Service-Aware Interoperability Framework ( SAIF ) Stephen.Hufnagel.ctr@tma.osd.mil. 27 April 2011. Implement & Test. Initiation. SAIF ECCF - Services Aware Interoperability Architecture - Enterprise Compliance and Conformance Framework.

alexa
Download Presentation

HL7 Artifacts within SAIF ECCF

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 Artifacts within SAIF ECCF HL7 Service-Aware Interoperability Framework (SAIF) Stephen.Hufnagel.ctr@tma.osd.mil 27 April 2011

  2. Implement & Test Initiation SAIF ECCF - Services Aware Interoperability Architecture - Enterprise Compliance and Conformance Framework EHR-S FM & EHR-S CI-IM EHR System Function Model & EHR System Computationally-Independent Information-Model V&V Checkpoint Peer Review “Ballot” Analysis V&V Checkpoint V&V Checkpoint HL7 Development Framework (HDF) DSTU - Draft Standard for Trial Use “Prototype” • Specifications for • Business Objects • Components • Capabilities • Applications • Systems DAMDomain Analysis Models CDAClinical Document Architecture CMETCommon Model Element Types D-MIM Domain Message Information Model Design • Interoperability Specifications for • Messages and/or • Documents and/or • Services V&V Checkpoint Draft Working Document; Not for Public Distribution V&V is Verification and Validation

  3. ECCF SAIF ECCF Viewpoints CIM PSM CIM is Computationally Independent Model PIM is Platform Independent Model PSM is Platform Specific Model PIM Draft Working Document; Not for Public Distribution

  4. Topic Maps among viewpoints and their architectural artifacts can define Traceability RACI Charts for each viewpoint can define stakeholder roles and responsibilities “Who does What When” “Who needs What When” Potential Architectural Artifacts

  5. The ECCF is not a comprehensive enterprise-architecture[1]; rather, we use it to specify information exchange interoperability and conformance statements for documents, messages and services. RACI Charts for each viewpoint can define stakeholder roles and responsibilities “Who does What When” “Who needs What When” Topic Maps among viewpoints and their architectural artifacts can define Traceability Bold Blue Indicates Reusable HL7 Models

  6. Bold Blue Indicates Reusable HL7 Models

  7. Business Viewpoints Conceptual Independent Model Platform Independent Model Platform Specific Model Information Viewpoints Conceptual Independent Model Platform Independent Model Platform Specific Model CUIs CUIs Engineering/Technical Viewpoints Conceptual Independent Model Platform Independent Model Platform Specific Model Behavioral Viewpoints Conceptual Independent Model Platform Independent Model Platform Specific Model HL7 EHR-S FM CUIs CUIs CUIs CUIs Investment Portfolio Line Items Planning Budget for New, Improved, Sustained or Sunset Capabilities Product Line Inventory Inventory of Systems and their Capabilities and Functions Key to Traceability Traceability is achieved by using Concept Unique numeric Identifiers (CUIs) from the HL7 EHR System Functional Model (EHR-S FM) as attributes to all SAIF artifacts. This is analogous to a library system, which uses Dewey decimal numbers as book identifiers.

More Related