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 4 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)
Integrating the Healthcare Enterprise IHE Overview Keith W. Boone Interoperability Architect, GE Healthcare Co-chair, IHE Patient Care Coordination PC.
Page 1 PASS as a SAEAF Alpha Project Preliminary discussion and exploration Thursday, April 23 rd, 2009.
September, 2005What IHE Delivers 1 CDA-based content integration profiles Philippe Lagouarde, Cegedim Co-chair Vendor, IHE-France.
Helmut König, Siemens Medical Solutions
Service Oriented Architecture Reference Model
HL7 V2 Implementation Guide Authoring Tool Proposal
Depicting EHRs Immunization capability HL7 WGM – September 11, 2006 Immunization Storyboard project update.
HL7 Quality Reporting Document Architecture DSTU
2/11/2014 8:44 AM The CDA Release 3 Specification Stack September 2009 HL7 Services-Aware Enterprise Architecture Framework (SAEAF)
SAIF and Sound: Fast Track to Standard Development Leveraging rigorous process to accelerate standard development and approval through predictable and.
1 September 2013 An Architecture for CDS and Quality Measurement September 2013.
HDF: HL7 Methodology Ioana Singureanu M&M co-chair, HDF Editor Eversolve, LLC.
WGM-May © Health Level Seven ®, Inc. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven, Inc.
One-standard-per-year Leveraging rigorous process to accelerate standard approval 1.
Clinical Decision Support TC Order Set Proposal September 14, 2005.
1 Clinical Interoperability Council January 21, 2010 Phoenix, Arizona Dianne M. Reeves National Cancer Institute Overview: NCI caDSR and Semantic Services.
1 Service Oriented Architectures (SOA): What Users Need to Know. OGF 19: January 31, 2007 Charlotte, NC John Salasin, Ph.D, Visiting Researcher National.
Copyright © 2006 Data Access Technologies, Inc. Open Source eGovernment Reference Architecture Approach to Semantic Interoperability Cory Casanave, President.
SOA Modelling By Rajat Goyal.
The European Organisation for the Safety of Air Navigation AIRM Review Forum AIRM Status Report.
© 2018 SlidePlayer.com Inc. All rights reserved.