We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byAriana Graves
Modified over 2 years ago
2/11/2014 8:51 AM The CDA Release 3 Specification Stack September 2009 HL7 Services-Aware Enterprise Architecture Framework (SAEAF)
Page 2 CDA R3 Requirements Topic Specification Business Viewpoint Information ViewpointComputational Viewpoint Engineering Viewpoint Conceptual Business Context, Reference Context CDA 6 (10.a) Support for A&F (5) Support for Public Health (6) Concepts from Domain Analysis (Information) Model SDA DAM (w/ CDA Refinement) Collaboration Analysis, Functional Profile(s), Service Roles and Relationships Existing Platform capabilities, essential requirements regarding compatibility (3, 6.a) R2 Compatibility (10.b) DAM Compatibility (1) Platform Independent Business Governance (1) Model Consistency (2) Committee Domain Models REALM Document Creator/Receiver Responsibilities (6.b) SDA-DMIM (2) CDA-DMIM CDA-RMIM CDA-HD Vocabulary Binding to Concept Domains Existing Extensions (6.c) Collaboration Types, Interface Specification and Functional Groups, Interaction Types and Collaboration Participations, Contracts Parts Steward/Custodian, Legal Authenticator, Subject/Patient Existing Platform models, libraries, intended transparencies of the platform. CCD Templates, DCMS, et cetera C-MET Use (9) Platform Specific Rules, Procedures Model mapping procedures Validation of Extensions (7) Schema Templates Implementation Guides Vocabulary Binding to Value Sets Collaboration scripts, Orchestrations, Realized Interfaces ? Execution Context, Transforms (backwards compatibility, human readability), Deployment Model (single schema) (3,4)
Page 3 Business Viewpoint Conceptual – Business Context, Reference Context –6 Principles of CDA (10.a) –Support for A&F (5) –Support for Public Health (5.c) Platform Independent – Business Governance –Model Consistency (2) –Support Committee Domain Models (1) –Model Mapping Procedures –REALM –Document Receiver, Document Creator Responsibilities (6.b) Platform Specific – Rules, Procedures –Validation of Extensions (7)
Page 4 Information Viewpoint Conceptual – Domain Analysis Model –SDA DAM (w/ CDA Refinement) Platform Independent – Information Models, Hierarchical Message Definition –SDA DMIM, CDA DMIM –Vocabulary Binding to Concept Domains –Existing Extensions Platform Specific – LIM, Schemas –Schema, Templates –Implementation Guides –Vocabulary Binding to Value Sets
Page 5 Computational Viewpoint Conceptual – Collaboration Analysis, Functional Profile(s), Service Roles and Relationships Platform Independent – Collaboration Types, Interface Specification and Functional Groups, Interaction Types and Collaboration Participations, Contracts Parts –Steward/Custodian –Legal Authenticator –Subject/Patient Platform Specific – Collaboration Scripts, Orchestrations, Realized Interfaces –?
Page 6 Engineering Viewpoint Conceptual – Existing Platform capabilities, essential requirements regarding compatibility –(3, 6.a) –R2 Compatibility (10.b) –DAM Compatibility (1) Platform Independent – Existing Platform models, libraries, intended transparencies of the platform. –CCD Templates, DCMS, et cetera –C-MET Use (9) Platform Specific – Execution Context, Transforms, Deployment Model –Backwards Compatibility –Human readability –single schema (3,4)
2/11/2014 8:44 AM The CDA Release 3 Specification Stack September 2009 HL7 Services-Aware Enterprise Architecture Framework (SAEAF)
One-standard-per-year Leveraging rigorous process to accelerate standard approval 1.
SAIF and Sound: Fast Track to Standard Development Leveraging rigorous process to accelerate standard development and approval through predictable and.
Page 1 PASS as a SAEAF Alpha Project Preliminary discussion and exploration Thursday, April 23 rd, 2009.
1 Clinical Interoperability Council January 21, 2010 Phoenix, Arizona Dianne M. Reeves National Cancer Institute Overview: NCI caDSR and Semantic Services.
1 September 2013 An Architecture for CDS and Quality Measurement September 2013.
2/5/2014 4:51 PM SAEAF Education Series Session 1: Introduction and Overview September 2009 HL7 Services-Aware Enterprise Architecture Framework (SAEAF)
Slide 0 EHR SD RM - EHR Way Forward … Future State Reference Architecture HSSP Practitioners Guide Volume II Immunization and Adverse Event Reporting Prototype.
Mapping of DICOM SR Basic Diagnostic Imaging Report to HL7 CDA R2 Diagnostic Imaging Report Helmut König, Siemens Medical Solutions DICOM WG20 / HL7 II.
Standards & Interoperability Kickoff HHS – ONC September 20, 2010 Office of Standards and Interoperability 1.
HDF: HL7 Methodology Ioana Singureanu M&M co-chair, HDF Editor Eversolve, LLC.
Slide 0 EHR SD RM - EHR Way Forward … Future State Reference Architecture HL7 EHR SD RM Project EHR System Design Reference Model Constructing a Future.
MITA with HL7 Information Out of Cycle HL7 WGM, May, 2009, St. Paul, MN Health Level 7.
Copyright © 2006 Data Access Technologies, Inc. Open Source eGovernment Reference Architecture Approach to Semantic Interoperability Cory Casanave, President.
Depicting EHRs Immunization capability HL7 WGM – September 11, 2006 Immunization Storyboard project update.
Query Health Pilots Sub-Work Group December 8, 2011.
16 August Trends in Practical Deployment of HL7 Standards: supporting regional electronic healthcare records Mark Shafarman Past Chair HL7 with additional.
Introduction to the Clinical Document Architecture Gay Giannone MSN, RN June 10, For the HL7 Child Health Work Group.
1 Service Oriented Architecture Reference Model An informal SOA Ontology.
Copyright © 2008 Model Driven Solutions. Standards for Service Architectures SOA for e-Government Conference Cory Casanave cory-c (at) modeldriven.com.
Practical ebXML Registry uses for interoperable eBusiness Open Forum 2003 on Metadata Registries 8:40am to 10am January 22, 2003.
The European Organisation for the Safety of Air Navigation AIRM Review Forum AIRM Status Report.
Designing High Performance XDS Registries/Repositories IHE Interoperability Showcase – HIMSS 2006 Joe Gallant Product Manager.
Invitation to Join Open Health Tools Draft by Skip McGaughey
1/23/2014 9:52 AM SOA4HL7: Defining Services based on HL7 Messaging Artifacts Alan Honey, Kaiser Permanente Enterprise Architect (Based on material initially.
All rights reserved, Copyright © INTAP Overview: Guide for applying RM- ODP with UML Profile for EDOC From Enterprise Model to Computational Model.
WGM-May © Health Level Seven ®, Inc. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven, Inc.
1 Service Oriented Architectures (SOA): What Users Need to Know. OGF 19: January 31, 2007 Charlotte, NC John Salasin, Ph.D, Visiting Researcher National.
© 2006 The MITRE Corporation. All rights reserved For Internal MITRE Use Information Architecture as a Decision-Support Tool Dr. M. A. Malloy
MITA Business Processes, Technical Functions & Services Monday Quarter 2 Presentation May 18, 2009.
© 2016 SlidePlayer.com Inc. All rights reserved.