60 likes | 181 Vues
This document outlines the HL7 Services-Aware Enterprise Architecture Framework (SAEAF) and its CDA R3 requirements from a business viewpoint, emphasizing conceptual models, governance, and model consistency. It covers principles supporting access and functionality, public health, document responsibilities, and domain analysis. The content addresses both platform-independent and specific aspects, including validation, extensions, and collaboration frameworks. It also highlights the importance of compatibility with existing platforms, ensuring seamless integration in health information systems.
E N D
The CDA Release 3 Specification StackSeptember 2009 HL7 Services-Aware Enterprise Architecture Framework (SAEAF)
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)
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
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 • ?
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)