1. 2/11/2014 8:44 AM The CDA Release 3 Specification Stack September 2009 HL7 Services-Aware Enterprise Architecture Framework (SAEAF)

2. Page 2 SAEAF Value Proposition (3): Working Interoperability Interoperability: the deterministic exchange of data/information in a manner that preserves shared meaning Two trading partners interoperate based on a certified level of shared compliance to interoperability specifications/standards Certified level of conformance determine degree of automated interoperability that is possible and/or difficulty of the transformations that are required to enable interoperability Agree on Reference view Agree on Conceptual view Agree on Platform-Independent view Agree on Platform -Specific view A B D C F Component E A -- F: trading partners

3. Page 3 Goal Topic Specification Enterprise / Business Viewpoint Information Viewpoint Computational Viewpoint Engineering Viewpoint Conceptual Business Context, Reference Context Concepts from Domain Analysis (Information) Model Collaboration Analysis, Functional Profile(s), Service Roles and Relationships Existing Platform capabilities, essential requirements regarding compatibility Platform Independent (logical) Business GovernanceProject-oriented Domain Information Model, Constrained Information Model, Localized Information Model, Hierarchical Message Definition Collaboration Types, Interface Specification and Functional Groups, Interaction Types and Collaboration Participations, Contracts Parts Existing Platform models, libraries, intended transparencies of the platform. Platform Specific (implementable) Rules, ProceduresLocalized Information Model, Schema Collaboration scripts, Orchestrations, Realized Interfaces Execution Context (channels, stubs, binders, protocols, and interceptors), Transforms, Deployment Model IP differences appear at the PIM level

4. Page 4 Conceptual Specifications could Include Storyboards Use Cases Use Case Specifications (Sequence Diagrams) Use Case Realizations (Activity Diagrams) Business Operations, including traceability –Focus on Permissions, Obligations, and Restrictions Business Interfaces Concepts from Analysis Model Pointers to Architectural Proof-Of-Concept/Mockup Wire Frame Diagrams A discussion of Dependencies Glossary

5. Page 5 Platform-Independent (Logical) Specifications Provide a technology-independent, common layer of conformance Contain non-ambiguous specifications of static and behavioural semantics Focus on refining the computational and informational viewpoints of the Conceptual Specification. –Information models are transformed from analysis model concepts to a implementation constructs –Computational elements focus on detailed designs of the interfaces involved in the appropriate semantic exchanges –Conformance Statements focus on granularity and composition of the interface specifications workflow components for applications –without applying the details of a particular technology

6. Page 6 Platform-Independent Specification Artifacts Design Guidelines Business Focus Interface Specifications including Operations Implementable Models Choreography and Dynamic Model User Interfaces User Workflows Traceability to other specifications (standardized or local) Transparencies that must be supported by the platform bindings

7. Page 7 Platform Definitions HL7 has created two platform definitions for implementation binding –HL7 V2 –HL7 V3 Other Platform Definition Models include –XML –Java –J2EE –.NET –WSDL + SOAP Platforms can combine with other Platforms –For example, XML is essential to SOAP, and may be combined with Java –caGrid using WSDL + SOAP + an XML flavor

8. Page 8 Multiple Platform-Specific Specifications Platform – Independent Specification Platform – Specific Specification #1 Stack A = Platform – Specific Specification #2 Stack B = Platform – Specific Specification #3 Stack C =

9. Page 9 Platform-Specific Specification Artifacts Platform traceability to defined Transparencies Business Focus and Implemented Policy Impact of the Platform Realizations to Policy Interface Realizations (channels, stubs, bindings, protocols, interceptors, and transformations) User Interfaces Presentation Logic, Session Logic Workflow Realizations of Choreographies, BPL, etc. Operation Signatures Message Schemas

10. Page 10 Testable Conformance in a Specification Stack Abstraction Layers Conceptual Platform Independent Platform Specific Technology Binding conformance Specification Stack Conformance Statements for a given SS are shown in black arrows, Conformance Assertions for a given Technology Binding in red arrows. Conformance Statements

11. Page 11 Conformance, Compliance, Consistency, Traceability Topic Specification Enterprise / Business Viewpoint Information Viewpoint Computational Viewpoint Engineering Viewpoint Conceptual Platform Independent Platform Specific Traceable Consistency Conformance Statements Constrained Conformance Statements Constrained Conformance Statements Compliance Conformant Technology Conformance Assertions source target source target

12. Page 12 Compatibility in a Specification Stack Topic Specification Enterprise / Business Viewpoint Information Viewpoint Computational Viewpoint Engineering Viewpoint Conceptual Platform- Independent Platform- Specific Conformance Statements Constrained Conformance Statements Constrained Conformance Statements Compliance Conformance Technology Conformance Assertions source target source target Compliance Technology Conformance Assertions Conformance Compatibility

13. 2/11/2014 8:44 AM Goal Topic Specification Enterprise / Business Viewpoint Information ViewpointComputational Viewpoint Engineering Viewpoint Conceptual Business Context, Reference Context CDA 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 Platform Independent Business Governance Model Consistency (A) Support Committee Domain Models (B) (A B B A) = (A B) REALM Document Receiver, Document Creator Responsibilities SDA-DMIM CDA-DMIM CDA-RMIM CDA-HD CIM? LIM? Vocabulary Binding to Concept Domains 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 Platform Specific Rules, Procedures Procedures for mapping from B to A Schema Templates Implementation Guides Vocabulary Binding to Value Sets Collaboration scripts, Orchestrations, Realized Interfaces Hunh? Execution Context (channels, stubs, binders, protocols, and interceptors), Transforms (backwards compatibility, human readability), Deployment Model (single schema)