HL7 Interoperability Paradigms Fundamental Methodological ...

608 views

Published on

Published in: Technology, Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
608
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
16
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

HL7 Interoperability Paradigms Fundamental Methodological ...

  1. 1. April 9, 2009 <ul><li>OHT Architecture Project: </li></ul><ul><li>Update and Integration with HL7 SAEAF </li></ul>
  2. 2. OHT Architecture Project Q2 2009 Content <ul><li>Architecture principles </li></ul><ul><li>Tool classification mechanism </li></ul><ul><li>a set of templates, patterns and </li></ul><ul><li>processes that enable </li></ul><ul><li>interoperability of OHT tools. </li></ul><ul><li>Identification of potential barriers </li></ul><ul><li>Recommendation of a governance </li></ul><ul><li>process for the harvesting, </li></ul><ul><li>categorization and custodianship </li></ul><ul><li>of architecture artifacts. </li></ul><ul><li>Executed internal and external </li></ul><ul><li>communication plan </li></ul><ul><li>Architectural Principles Q2/09 </li></ul><ul><li>Tooling Architectural Vision Q3/09 </li></ul><ul><li>Architectural Framework Q3/09 </li></ul><ul><li>Tooling Classification and </li></ul><ul><li>Governance recommendations Q4/09 </li></ul><ul><li>Principles, Architecture Framework </li></ul><ul><li>Specification Stack w examples </li></ul><ul><li>Tool classification </li></ul><ul><li>Recommendations to the Board </li></ul><ul><li>Expectation for detailed Technical </li></ul><ul><li>Architecture Solutions </li></ul><ul><li>Expectation for Architectural </li></ul><ul><li>Framework that allows for a Tooling </li></ul><ul><li>Architecture to emerge through </li></ul><ul><li>Projects </li></ul><ul><li>Desire to reuse tooling components </li></ul><ul><li>Desire to relearn from best practices </li></ul><ul><li>Customer expectations to optimize </li></ul><ul><li>and align Tooling investments </li></ul><ul><li>Funding for Architecture Project </li></ul><ul><li>team members </li></ul><ul><li>Active cooperation from other </li></ul><ul><li>OHT Project Committers </li></ul><ul><li>Successful communication to </li></ul><ul><li>OHT projects Q2/Q3 </li></ul>Added Deleted & Changed Milestones Packaging Editions Dependencies Pressures Statistics Contributing Participants: NCI, Infoway, NHS, NextJ, IHTSDO, NEHTA, HL7
  3. 3. Architecture Project Charter (1) <ul><li>The objective of the OHT Architecture Project is to enable the adoption, development, and deployment of an evolving set of interoperable tools. </li></ul><ul><ul><li>Tools are defined as any software component that is not a clinical end-user application, although such software components may form part of an end user application. Tools are intended to be useful and usable for their intended purpose and to inter operate with each other. </li></ul></ul><ul><ul><ul><li>Definition of “tool” intentionally left somewhat loose as that is not the primary focus of the AP. Rather it is enabling interoperability. </li></ul></ul></ul><ul><li>These tools support the development and deployment of software that enables computable semantic interoperability in the health-care/life sciences/clinical research domains. </li></ul><ul><ul><li>Recognition that CSI can occur in a multitude of ways and complexities </li></ul></ul><ul><ul><ul><li>One-way data export </li></ul></ul></ul><ul><ul><ul><li>Integrated real-time behavior coordination </li></ul></ul></ul>
  4. 4. Architecture Project Charter (2) <ul><li>The OHT Architecture Project operates under the Open Health Tools Development Policy and Process (described at http://www.openhealthtools.org/Documents/Open%20Health%20Tools%20-%20Development%20Process.pdf ) and is chartered by the Board to articulate and adopt a formal architecture framework, architecture principles and best practices that are focused on relevant interoperability and the use of standards. </li></ul><ul><li>As its initial goal, the Architecture Project will develop an architecture framework </li></ul><ul><ul><li>which will enable the evolutionary development of an OHT Platform architecture </li></ul></ul><ul><ul><ul><li>consistent with the various enterprise architectures built and deployed by OHT stakeholders. (i.e. supporting appropriate CSI) </li></ul></ul></ul><ul><li>(Frameworks must be specified top-down. EAS then develops bottom-up.) </li></ul>
  5. 5. Architecture Project Charter (3) <ul><li>Deliverables include: </li></ul><ul><ul><li>a set of architecture principles. </li></ul></ul><ul><ul><ul><li>Focus on CSI rather than “architecture in general” </li></ul></ul></ul><ul><ul><li>a tool classification mechanism that enables stakeholders to contribute and have access to architecture artifacts that underlie the tools </li></ul></ul><ul><ul><li>a Conformance/Compliance Framework adapted to tooling interoperability, including an explicit Specification Stack </li></ul></ul><ul><ul><li>a set of templates, patterns and processes that enable interoperability of OHT tools </li></ul></ul><ul><ul><li>identification of potential barriers to interoperability and recommendations to overcome them </li></ul></ul><ul><ul><li>a recommendation to the board of a governance process to assist in the harvesting, categorization and custodianship of architecture artifacts </li></ul></ul><ul><ul><li>an executed internal and external communication plan </li></ul></ul>
  6. 6. 4Q08 2Q09 1Q09 3Q09 4Q09 First Conceptual Meeting Informal Organizational Meetings – Orlando/Paris OHT Architecture Project Q2 2009 Architecture Principles & Best Practices -harmonized with current projects Draft Framework & Current State Examples Tooling Classification & Governance recommendations
  7. 7. SAEAF Background (1) A “Services-Aware Enterprise Architecture for HL7” <ul><li>April 08: HSSP-sponsored “Services in Healthcare” conference, Chicago, IL (attended by HL7 CTO) </li></ul><ul><li>May 08: HL7 CTO asks the HL7 ArB to “develop a straw-man proposal for services development within the context of an HL7 Enterprise Architecture” </li></ul><ul><ul><li>“ Specify the artifacts and processes necessary to allow HL7 to define specifications for SOA integration.” </li></ul></ul><ul><ul><li>“ Define an HL7 Enterprise Architecture Framework (EAF) which contextualizes HL7 specifications in a SOA environment.” </li></ul></ul><ul><ul><li>Consider services first, but don’t exclude messages or documents as Interoperability Paradigms </li></ul></ul><ul><ul><ul><li>“ HL7 EAF should be services-aware , not service-specific” </li></ul></ul></ul>
  8. 8. SAEAF Background (2) A “Services-Aware Enterprise Architecture for HL7” <ul><li>Summer 08: HL7 Executive Committee agreed to sponsor three face-to-face “ArB EAF Jump-Start” meetings </li></ul><ul><ul><li>Modeled after “Left-Hand Side of the RIM” project (1998) </li></ul></ul><ul><ul><li>Three 3-day F2F meetings in June, July, August, 2008 </li></ul></ul><ul><ul><ul><li>Transparent process </li></ul></ul></ul><ul><ul><ul><ul><li>Open attendance </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Published agendas </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Published artefacts and works-in-progress </li></ul></ul></ul></ul><ul><li>September 08: CTO and TSC requested that initial results of the Jump-Start process be presented at the Vancouver WG meeting via a series of joint-WG meetings and open ArB sessions </li></ul>
  9. 9. SAEAF Background (3) A “Services-Aware Enterprise Architecture for HL7” <ul><li>Jump-Start Deliverables (largely contained in the collection of SAEAF documents) to include (but not be limited to): </li></ul><ul><ul><li>EA framework “informed by” service specification considerations and industry experience ( “services-aware” ) </li></ul></ul><ul><ul><li>Identification and initial specification of required infrastructure currently missing or incomplete in HL7 </li></ul></ul><ul><ul><ul><li>Behavioral Framework (BF) </li></ul></ul></ul><ul><ul><ul><li>Enterprise Conformance & Compliance Framework (ECCF) </li></ul></ul></ul><ul><ul><ul><li>Governance Framework (GF) </li></ul></ul></ul><ul><ul><li>Operational vision for SAEAF deployment </li></ul></ul><ul><ul><ul><li>Integration with existing HL7 and HSSP processes </li></ul></ul></ul><ul><ul><ul><ul><li>complimentary to existing relationships (e.g. OMG) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>extension to message and document Interoperability Paradigms </li></ul></ul></ul></ul>
  10. 10. <ul><li>HL7 ArB </li></ul><ul><ul><li>Yongjian Bao, GE Healthcare </li></ul></ul><ul><ul><li>Jane Curry, Health Information Strategies </li></ul></ul><ul><ul><li>Grahame Grieve, Jiva Medical </li></ul></ul><ul><ul><li>Anthony Julian, Mayo </li></ul></ul><ul><ul><li>John Koisch, NCI </li></ul></ul><ul><ul><li>Cecil Lynch, OntoReason </li></ul></ul><ul><ul><li>Charlie Mead, CTO NCI </li></ul></ul><ul><ul><li>Nancy Orvis, DoD MHS </li></ul></ul><ul><ul><li>Ron Parker, Canada Health Infoway </li></ul></ul><ul><ul><li>John Quinn, Accenture, CTO HL7 </li></ul></ul><ul><ul><li>Abdul Malik Shakir, Shakir Consulting </li></ul></ul><ul><ul><li>Mead Walker, Health Data and Interoperability </li></ul></ul>SAEAF Background (4) Jump-Start Participants <ul><li>Other </li></ul><ul><ul><li>Alex DeJong, Siemens </li></ul></ul><ul><ul><li>Ed Larsen, HITSP </li></ul></ul><ul><ul><li>Galen Mulrooney, JP Systems, VA </li></ul></ul><ul><ul><li>Scott Robertson, Kaiser </li></ul></ul><ul><ul><li>Rich Rogers, IBM </li></ul></ul><ul><ul><li>Ann Wrightson, NHS UK </li></ul></ul><ul><li>Participants brought a wide range of perspectives to the discussion </li></ul>
  11. 11. SAEAF Value Proposition (1): Working Interoperability <ul><li>Interoperability Paradigm (Messages, Documents, Services): specifications which enable two or more (HL7) trading partners to collaborate in the context of a specific business interaction </li></ul><ul><ul><li>No assumptions of size, character, or identity of parties </li></ul></ul><ul><ul><ul><li>Nations, Enterprises, Departments, Individual, Systems, etc. </li></ul></ul></ul><ul><ul><li>No assumptions of exchange details (What, Why, How, etc.) </li></ul></ul>
  12. 12. SAEAF Value Proposition (2): Working Interoperability <ul><li>Working Interoperability: </li></ul><ul><ul><li>The collection of structures, processes, and components </li></ul></ul><ul><ul><ul><li>that support Computable Semantic Interoperability </li></ul></ul></ul><ul><ul><ul><li>in the context of a Conformance/Compliance Framework. </li></ul></ul></ul><ul><ul><ul><li>SAEAF facilitates the explicit and layered expression </li></ul></ul></ul><ul><ul><ul><li>of the set of static, functional, and behavioral semantics that collectively enable Working Interoperability. </li></ul></ul></ul><ul><li>Specifications developed to enable Working Interoperability </li></ul><ul><ul><li>are defined in such a manner so as to ensure that they are </li></ul></ul><ul><ul><ul><li>usable, useful, durable, and that they are </li></ul></ul></ul><ul><ul><ul><li>implementable in a variety of deployment contexts </li></ul></ul></ul><ul><ul><ul><ul><li>in a repeatable, comprehensible manner. </li></ul></ul></ul></ul>
  13. 13. SAEAF Value Proposition (2): Working Interoperability (WI) <ul><li>WI : the deterministic exchange of data/information in a manner that preserves shared meaning </li></ul><ul><li>Two parties interoperate based on a combination of </li></ul><ul><ul><li>certified “ level of conformance ” to formal Conformance Statements (CnS) </li></ul></ul><ul><ul><li>stated “ level of explicit compliance ” to integrated specifications or standards expressed via Compliance Statements (CmS) </li></ul></ul><ul><ul><li>“ levels” help quantify degree-of-difficult in achieving WI </li></ul></ul>Agree on “Reference” view Agree on “Conceptual” view Agree on “ Platform-Independent” view Agree on “ Platform -Specific” view A B D C F Component Component E
  14. 14. RM-ODP (1) ISO Standard (RM – ODP, ISO/IEC IS 10746 | ITU-T X.900 ) Why? True? Where? How? What? An instance of a SAEAF Specification Stack is made up of Conformance Statements which are asserted as valid by a technology binding and verified by Certification . ECCF cells contain artifacts -- developed de novo or drawn from pre-existing specifications -- that are (often) generated via Constraint Patterns. They are sorted by RM-ODP Viewpoints.
  15. 15. RM-ODP (2) ISO Standard (RM – ODP, ISO/IEC IS 10746 | ITU-T X.900 ) <ul><li>Non-hierarchical and Non-orthogonal </li></ul><ul><ul><li>Each Viewpoint can (and most often will) contain a hierarchy of “layered” information </li></ul></ul><ul><ul><li>Distinguish Conformance vs Compliance Statements </li></ul></ul><ul><ul><ul><li>CnS validated/certified via technology implementation </li></ul></ul></ul><ul><ul><ul><li>CmS (often implicitly) validated (i.e. transformation is correct) </li></ul></ul></ul><ul><ul><ul><li>Both may generate hierarchical “layers” in a SS instance </li></ul></ul></ul>An instance of a SAEAF Specification Stack is made up of Conformance Statements which are asserted as valid by a technology binding and verified by Certification . ECCF cells contain artifacts -- developed de novo or drawn from pre-existing specifications -- that are (often) generated via Constraint Patterns. They are sorted by RM-ODP Viewpoints. Information Business / Enterprise Computational Engineering Technology
  16. 16. The SAEAF ECCF Context (1) <ul><li>Group A develops Specification X </li></ul><ul><li>Group A publishes Specification X </li></ul><ul><ul><li>Developers want to implement Specification X </li></ul></ul><ul><li>Group B develops Specification Y </li></ul><ul><li>Group A wants to say “Specification X uses Specification Y” </li></ul><ul><li>ECCF Context  Certify that </li></ul><ul><ul><li>Specification X is “correctly implemented” </li></ul></ul><ul><ul><li>Specification Y is “correctly referenced” </li></ul></ul>
  17. 17. The SAEAF ECCF Context (2) <ul><li>Problem: </li></ul><ul><ul><li>What does “correctly implemented” mean? </li></ul></ul><ul><ul><li>What does “correctly referenced” mean? </li></ul></ul><ul><ul><li>How can we define these concepts explicitly ? </li></ul></ul><ul><ul><ul><li>Support repeatable/reproducible certification of “correctness” </li></ul></ul></ul><ul><ul><ul><ul><li>Computational </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Human-assisted </li></ul></ul></ul></ul><ul><li>If explicit definitions and processes are not established -- e.g. via the ECCF -- implicit assumptions will be inconsistently made explicit as they are realized in technology components, and are usually only apparent at run-time </li></ul>
  18. 18. The SAEAF ECCF Context (3) <ul><li>Answers based on three inter-related but separate concepts </li></ul><ul><ul><li>Conformance </li></ul></ul><ul><ul><li>Compliance </li></ul></ul><ul><ul><li>Consistency </li></ul></ul><ul><li>Each defines “one or more relationships between components/artifacts in an instance of the Specification Stack” </li></ul><ul><ul><li>“ transformations” </li></ul></ul><ul><ul><ul><li>Constraint (most common) </li></ul></ul></ul><ul><ul><ul><li>Extension (must be well-defined to sustain WI) </li></ul></ul></ul><ul><ul><ul><li>Other </li></ul></ul></ul><ul><ul><li>“ dependencies” (use of one Specification by another) </li></ul></ul>
  19. 19. The SAEAF ECCF Context (4) <ul><li>Conformance </li></ul><ul><ul><li>Conformance Statements certified/validated by Technology realization/binding </li></ul></ul><ul><li>Compliance </li></ul><ul><ul><li>Compliance Statements implicitly validate that Source artifact is correctly transformed </li></ul></ul><ul><ul><ul><li>between Specification Stack levels-of-abstraction </li></ul></ul></ul><ul><ul><ul><ul><li>Conceptual-layer Information Model (DAM) is transformed to PIM Class Model </li></ul></ul></ul></ul><ul><ul><ul><li>transformation of a single, cell-specific artifact </li></ul></ul></ul><ul><ul><ul><ul><li>Generalized Constraint Pattern </li></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>Restriction of possible value sets on an attribute </li></ul></ul></ul></ul></ul>
  20. 20. The SAEAF ECCF Context (5) <ul><li>Consistency </li></ul><ul><ul><li>Does involve the logical notions of “if I have A, I need to have B” </li></ul></ul><ul><ul><ul><li>Activity Diagram in Computational VP which exposes a data gram must consistently use the semantics of a </li></ul></ul></ul><ul><ul><ul><li>Class Diagram in Information VP in which the specific semantics of the data gram are represented </li></ul></ul></ul><ul><ul><li>Does not involve “transformations” between specification artifacts </li></ul></ul><ul><ul><ul><li>Transformations are about Compliance </li></ul></ul></ul><ul><ul><ul><ul><li>not Conformance </li></ul></ul></ul></ul><ul><ul><ul><ul><li>not Consistency </li></ul></ul></ul></ul>
  21. 21. ECCF Terms of Art <ul><li>Specification Stack </li></ul><ul><li>Conformance Statement (and associated Assertion) </li></ul><ul><li>Conformance Certification (validation of Assertions) </li></ul><ul><li>Compliance Statement (and associated Transformation) </li></ul><ul><li>Compliance Certification (usually implicit) </li></ul><ul><li>Consistency (logical coupling of SS artifacts for single topic) </li></ul><ul><li>Traceability (vertical per-column navigation of SS instance) </li></ul><ul><li>Jurisdiction (see Governance presentation) </li></ul><ul><li>Provenance (see Governance presentation) </li></ul>
  22. 22. The ECCF Specification Stack (1) <ul><li>The ECCF Specification Stack </li></ul><ul><ul><li>Classifies artifacts by RM-ODP Viewpoints </li></ul></ul><ul><ul><li>Specification levels  engineering level-of-abstractions </li></ul></ul><ul><ul><ul><li>Conceptual Level – Concept (Requirements/Analysis) Model </li></ul></ul></ul><ul><ul><ul><li>Platform-Independent – Logical Model </li></ul></ul></ul><ul><ul><ul><li>Platform-Specific – Implementable Model </li></ul></ul></ul><ul><ul><ul><ul><li>not an implementation per se </li></ul></ul></ul></ul>An instance of a SAEAF Specification Stack is made up of Conformance Statements which are asserted as valid by a technology binding and verified by Certification . ECCF cells contain artifacts -- developed de novo or drawn from pre-existing specifications -- that are (often) generated via Constraint Patterns. They are sorted by RM-ODP Viewpoints.
  23. 23. ECCF Specification Stack (2) <ul><li>A given instance of the ECCF Specification Stack is scoped to a given “topic” </li></ul><ul><ul><li>A coherent (consistent) collection of artifacts which define a “standard” for achieving Working Interoperability </li></ul></ul><ul><li>Enterprise Architecture Specification: “a layered set of ECCF Specification Stacks, each focused on a separate topic.” </li></ul><ul><ul><li>Multiple dependencies between stack instances including </li></ul></ul><ul><ul><ul><li>Reuse </li></ul></ul></ul><ul><ul><ul><li>Constraint </li></ul></ul></ul>An instance of a SAEAF Specification Stack is made up of Conformance Statements which are asserted as valid by a technology binding and verified by Certification . ECCF cells contain artifacts -- developed de novo or drawn from pre-existing specifications -- that are (often) generated via Constraint Patterns. They are sorted by RM-ODP Viewpoints.
  24. 24. The ECCF Specification Stack (3) (Exemplar artifact types that capture WI Semantics) Technology VP tests Conformance Statements collected in cells Topic Specification Enterprise / Business Viewpoint Information Viewpoint Computational Viewpoint Engineering Viewpoint Conceptual Business Context, Reference Context Domain Analysis (Information) Model Collaboration Analysis, Functional Profile(s), Service Roles and Relationships Existing Platform capabilities Platform- Independent Business Governance Project-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, etc. Platform- Specific Rules, Procedures Localized Information Model,Transforms, Schema Collaboration scripts, Orchestrations, Realized Interfaces Execution Context, Platform Bindings, Deployment Model
  25. 25. The ECCF Specification Stack (4): Conformance, Compliance, Consistency, Traceability Traceable Consistency Conformance Statements Constrained Conformance Statements Constrained Conformance Statements Compliance Compliance Conformance Conformance Assertions source target source target Topic Specification Enterprise / Business Viewpoint Information Viewpoint Computational Viewpoint Engineering Viewpoint Conceptual Platform Independent Platform Specific Technology
  26. 26. Reference Specifications/Materials (1) (Exemplar Artifacts) <ul><li>A given Reference artifact may be used, applied, referenced, transformed or otherwise leveraged by any cell of the Specification Stack (within the same VP) </li></ul><ul><ul><li>Reference Specifications do not reside in a “layer” of the Specification Stack per se </li></ul></ul><ul><ul><ul><li>“ Surround” or “provides input to” instances of the SS </li></ul></ul></ul><ul><ul><li>Other SDOs or “organizations with significant operational jurisdiction” (e.g. govt programs) may also produce (and require) Reference Specifications/Materials </li></ul></ul>Reference Specification Enterprise / Business Viewpoint Information Viewpoint Computational Viewpoint Engineering Viewpoint HL7 Reference EHR-FM, Clinical Statement Pattern RIM, CDA EHR-FM, Behavioral Framework Platform Architectures, RIMBAA
  27. 27. Reference Specifications/Materials (2) Abstraction Layers Viewpoint Technology Specification Stack E /B Info Comp Eng Conceptual Platform Independent Platform Specific HL7 Reference OHT Reference
  28. 28. Reference Specifications/Materials (3) Technology Conformance Reference specifications/standards -- each specified with its own Specification Stack -- can be “plugged in” in any SS cell. Compliance of these standards is often not validated until Conformance is formally tested. Conformance Statement Compliance Conformance Statement Conformance Statement Compliance compliance SDO2 Reference compliance SDO1 Reference Specification Stack
  29. 29. The ECCF Specification Stack (5): Mature Topic Viewpoint Technology Specification Stack E /B Info Comp Eng Abstraction Layers Concptual Platform Independent Platform Specific X X X X X X X X X X X X X denotes artifacts that HL7 or another SDO (or relevant jurisdiction) has defined O denotes things that an implementer must define (none shown … thus mature) Note that implementers will always have to define some things (e.g. local governance) when adopting a standard, preferably documented in a compliant specification Mature specifications are (in part) mature because they are comprehensively and relevantly compliant to other standards
  30. 30. ECCF Specification Stack (6): Mature Topic Technology conformance Because of the topic’s maturity, realizing the CnSs referenced by the Red arrows in Technology results in realizing the CnSs referenced by the black arrows Conformance Statements Conformance Statements Conformance Statements Conformance Statements Abstraction Layers Conceptual Platform Independent Platform Specific Specification Stack
  31. 31. The ECCF Specification Stack (7): Mature Topic Technology conformance Green arrows represent (implied) Compliance to other standards (asserted in isolation) Black arrows represent Conformance Statements made at multiple levels of abstraction (L  R flow indicates movement through Conceptual, PIM, and PSM) Red arrows represent validation of Conformance Statements Consistency and Traceability not explicitly shown Compliance and Traceability between the levels of the Specification Stack is documented via the Provenance . Natural alignments are identified (e.g. EHRs-FM and Computational components via use of SDO3) Conformance Statements Conformance Statements Conformance assertions Conformance Statements compliance SDO2 Reference compliance SDO3 Reference 3 rows: Con, PIM, PSM 4 columns: RM-ODP VPs Specification Stack
  32. 32. The ECCF and Governance <ul><li>The ECCF can only be effective when associated with a well-defined Governance Framework (GF) </li></ul><ul><ul><li>SAEF Education Series Part 4 </li></ul></ul><ul><li>In the context of multiple SDOs or other jurisdictional organizations developing Specifications/Standards that are shared across multiple Specification Stacks, effective Governance is a Critical Success Factor. </li></ul>
  33. 33. Conclusions (1): The Value of an ECCF <ul><li>The enemy of WI is implicit Conformance Statements (CnS) </li></ul><ul><ul><li>A specification that does not explicitly document all the viewpoints at the various levels of abstraction forces implementers to make assumptions about the missing CnSs </li></ul></ul><ul><ul><ul><li>Missing CnSs will be explicitly realized in an implementation but may not be documented in any specification </li></ul></ul></ul><ul><ul><ul><li>Loss of traceability </li></ul></ul></ul><ul><li>The greater the distance on the Stairway to Heaven, the more difficult the transforms required to achieve WI </li></ul><ul><ul><li>In some cases, CSI adapters MAY NOT be able to be built </li></ul></ul><ul><ul><ul><li>For example, you cannot act on data that was never collected, or was collected with incompatible meaning </li></ul></ul></ul>
  34. 34. Conclusions (2): The Value of an ECCF <ul><li>ECCF provides a structured way to </li></ul><ul><ul><li>Certify Conformance: implementation testability to stated Conformance Statements </li></ul></ul><ul><ul><li>Certify Compliance: explicit transformation/utilization of Specification/Standard artifacts </li></ul></ul><ul><li>An organization adopting an ECCF can build explicit Specifications/Standards that are compliant to other Specifications/Standards </li></ul><ul><ul><li>Each Specification/Standard encapsulates important business rules </li></ul></ul><ul><ul><ul><li>Now able to be considered enterprise architectural requirements </li></ul></ul></ul>
  35. 35. Conclusions (3): Certifications and Life Cycle <ul><li>In the interoperability world, certification of Conformance occurs at a different point in the lifecycle than the certification of Compliance or Consistency </li></ul><ul><ul><li>Conformance certified at technology binding time </li></ul></ul><ul><ul><li>Compliance certified at ballot or specification creation </li></ul></ul><ul><ul><li>Consistency empirically certified through lifecycle </li></ul></ul><ul><li>Traceability makes the “most sense” when it can be validated “from the top to the bottom of the Specification Stack” </li></ul>
  36. 36. Conclusions (4): The Value of an ECCF <ul><li>Precise specifications also enable stakeholders to quantitatively assess systems or components to determine whether they are explicitly conformant with the identified standards and therefore compliant to the other interoperability standards referenced in a given Specification Stack. </li></ul>
  37. 37. Conclusions (5): A Final Metaphor <ul><li>The ECCF as a framework defines a set of “standards of measurement” from which an EAS can be developed </li></ul><ul><ul><li>Similar to plumb line, level, ruler, measurement systems in the “hard” building traces </li></ul></ul><ul><li>The results of applying the ECCF (and its associations with Governance and the Behavior Framework) in an enterprise context results in a set of inter-related Specification Stacks </li></ul><ul><ul><li>i.e. an Enterprise Architecture Specification (EAS) </li></ul></ul>“ You can’t build a skyscraper by nailing together 1000 dog houses.” (Grady Booch) “ You can’t build a skyscraper with just a hammer and a saw.” (John Koisch)
  38. 38. Q & A
  39. 39. Definitions: Provenance and Jurisdiction <ul><li>Jurisdiction: The boundary and scope of authority of a person or group. May be bound by a geographical boundary and/or a specific domain of influence. </li></ul><ul><ul><li>The artifacts which populate a Specification Stack by definition fall under an implicit or explicit Jurisdiction </li></ul></ul><ul><ul><li>SDOs are one example of a Jurisdiction </li></ul></ul><ul><ul><ul><li>Government authorities </li></ul></ul></ul><ul><ul><ul><li>Enterprises </li></ul></ul></ul><ul><ul><ul><li>Collaborating participants within the scope of working interoperability </li></ul></ul></ul><ul><ul><li>See SAEAF Education Series Part 4 (Governance) </li></ul></ul>
  40. 40. Definitions: Provenance <ul><li>Provenance: Documentation that identifies the traceability of the history of each artifact in a specification from it’s origination as requirements documentation through to implemented technical components - may be included within the specification or by reference to an external artifact </li></ul><ul><ul><li>Also includes other standards and reference artifacts that are used / referenced by an artifact (compliance) </li></ul></ul><ul><ul><ul><li>Demonstrates accountability </li></ul></ul></ul><ul><ul><li>Traceability is an “instance-level” concept </li></ul></ul><ul><ul><li>Provenance is a “collection-level” concept </li></ul></ul><ul><ul><ul><li>See SAEAF Education Series Part 4 (Governance) </li></ul></ul></ul>
  41. 41. Definitions (0): HL7 use of Conformance vs Compliance <ul><li>Terms often used interchangeable and ambiguously </li></ul><ul><ul><li>HL7 V2.x (x < 5): </li></ul></ul><ul><ul><ul><li>“ compliance”  using MSH as the first segment </li></ul></ul></ul><ul><ul><li>HL7 V2.y (y > 4), V3: </li></ul></ul><ul><ul><ul><li>“ conformance”  “testable” as to ability to fulfill to stated specification </li></ul></ul></ul><ul><li>SAEAF utilizes both terms </li></ul><ul><ul><li>Conformance of a technology binding to a given Conformance Statement (CnS) is claimed via Conformance Assertion (CnA) </li></ul></ul><ul><ul><li>Compliance of an artifact transformation defined by a Constraint Pattern (for example) … but wait, there’s more… </li></ul></ul>
  42. 42. Definitions (1): Conformance (http://www.nehta.gov.au/dmdocuments/IF_2%200.pdf) <ul><li>Boolean value signifying the ability of a given implementation to satisfy a specific Conformance Statement (CnS) </li></ul><ul><ul><ul><li>For a given CnS, an implementation is conformant IF it satisfies (“validates”) the specified CnS </li></ul></ul></ul><ul><ul><ul><ul><li>Conformance is granular </li></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>Asserted and certified for a single Conformance Statement </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><li>Ideally certification is accomplished via automation </li></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>Certain CnSs may require human interaction for certification </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><li>Conformance is focused on implementation </li></ul></ul></ul></ul><ul><ul><ul><ul><ul><li> “ stronger” than Compliance </li></ul></ul></ul></ul></ul><ul><li>Conformance does not a priori depend on the existence of a “standard” (in the formal sense of the term) </li></ul><ul><ul><li>Specification containing CnSs is all that is required </li></ul></ul>
  43. 43. Definitions (2): Conformance Statement vs Assertions <ul><li>A Conformance Statement (CnS) is testable and verifiable statement about a system capability </li></ul><ul><ul><li>A system asserts conformance to a given CnS via a Conformance Assertion (CnA) </li></ul></ul><ul><ul><li>Assertion of specific capability can be verified as True or False at specific test points in an implementation, referred to in RM-ODP as “conformance points” </li></ul></ul><ul><ul><ul><li>Overall process is Conformance Certification </li></ul></ul></ul><ul><ul><ul><li>Usually done by 3 rd -party to avoid conflict-of-interest </li></ul></ul></ul><ul><li>E.G. “Operation X <MUST, MAY,…> bind to the RIM attribute Observation.value with a value set specified in LOINC as ….” </li></ul>
  44. 44. Definitions (3): Compliance (http://www.nehta.gov.au/dmdocuments/IF_2%200.pdf) <ul><li>Given an existing Source artifact , a Target artifact is said to be compliant IF it has been derived using known, agreed-upon derivation methods. More specifically… </li></ul><ul><ul><li>The statement “HL7 XML is compliant with W3C XML” means that “All valid HL7 XML message instances are also conformant to W3C XML.” </li></ul></ul><ul><ul><li>“ The Target artifact is compliant with the Source artifact IF all conformant implementations of the Target are also conformant with the Source.” (from RM-ODP standard) </li></ul></ul><ul><ul><ul><li>Extensions may introduce new CnSs and affect Conformance </li></ul></ul></ul><ul><ul><li>e.g. Web Services security specifications must be compliant with Web Service messaging (SOAP) if a security application is to support communication using SOAP </li></ul></ul>
  45. 45. Definitions (4): Compliance (cont) <ul><li>Navigation between levels of the SS is via transformations and therefore about Compliance . </li></ul><ul><li>One type of transformation involves CnSs made at one level to those made at another level. </li></ul><ul><ul><li>The results of these valid transformations will be traceability of a given CnS </li></ul></ul><ul><ul><ul><li>the traceable path may be a one-to-many-to-many path as the successively more concrete levels (rows) of the SS are vertically traversed </li></ul></ul></ul><ul><li>In the end, however, overall Conformance (and not Compliance) will be asserted by a technology binding and certified/validated as True or False. </li></ul>
  46. 46. Definitions (5): Consistency <ul><li>Addresses Specification Stack integrity and logical consistency </li></ul><ul><ul><li>Coherence of artifacts across Viewpoints </li></ul></ul><ul><ul><ul><li>E.G. An Activity Diagram in the Business VP of the Conceptual layer of the SS utilizes a datagram passed between 2 activities </li></ul></ul></ul><ul><ul><ul><li> The Information VP of the Conceptual layer must contain a class diagram which explicitly defines the static semantics of the datagram </li></ul></ul></ul><ul><ul><ul><li> The Computational VP of the Platform-Independent layer should contain a direct (or traceable) realization of the business behavior depicted in the Activity Diagram which utilizes the static components defined by the Information VP </li></ul></ul></ul><ul><ul><li>Not as formally defined as Conformance or Compliance </li></ul></ul><ul><ul><ul><li>Critically important for communication among multiple enterprise stakeholders </li></ul></ul></ul><ul><ul><li>Cannot (at present) be validated automatically </li></ul></ul>
  47. 47. Definitions (6): Certification <ul><li>A description of a specific process </li></ul><ul><ul><li>Conformance Certification (implementation) </li></ul></ul><ul><ul><ul><li>the common use of the term -- validation of Conformance Assertions </li></ul></ul></ul><ul><ul><li>Compliance Certification (artifact transformation) </li></ul></ul><ul><ul><ul><li>usually verified during Conformance Certification </li></ul></ul></ul><ul><ul><li>Consistency Certification (artifact coherence) </li></ul></ul><ul><ul><ul><li>usually verified during Conformance Certification </li></ul></ul></ul><ul><li>The process itself </li></ul><ul><ul><li>“ The system is going through Conformance Certification” </li></ul></ul><ul><ul><ul><li>Commonly only applied to Conformance Certification </li></ul></ul></ul>
  48. 48. RM-DOP, ECCF and Conformance and Compliance (1) <ul><li>Conformance Statement </li></ul><ul><ul><li>Organized within four RM-ODP “Viewpoint Specifications” </li></ul></ul><ul><ul><ul><li>Business, Information, Computation, Engineering </li></ul></ul></ul><ul><li>Viewpoint Specifications </li></ul><ul><ul><li>Collected per topic </li></ul></ul><ul><ul><li>Grouped by levels of abstraction </li></ul></ul><ul><ul><ul><li>Conceptual (Requirements/Analysis) </li></ul></ul></ul><ul><ul><ul><li>Platform-Independent (Logical) </li></ul></ul></ul><ul><ul><ul><li>Platform-Specific (Implement able ) </li></ul></ul></ul><ul><ul><ul><ul><li>Not an implementation per se </li></ul></ul></ul></ul>
  49. 49. RM-ODP, ECCF and Conformance vs Compliance (2) <ul><li>Technology: the 5 th Viewpoint </li></ul><ul><ul><li>A specific technology binding that asserts -- via Conformance Assertions -- conformance to one or more Conformance Statements (CnSs) gathered from the other Viewpoints </li></ul></ul><ul><ul><ul><li>Compliance (redux): RM-ODP uses the term compliance to indicate that the same software component can conform to more than one standard </li></ul></ul></ul><ul><ul><ul><ul><li>Standard A is compliant with Standard B if </li></ul></ul></ul></ul><ul><ul><ul><ul><li>all conformant implementations of Standard A are </li></ul></ul></ul></ul><ul><ul><ul><ul><li>also conformant to Standard B </li></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>HL7 XML is compliant with W3C XML if all valid HL7 XML message instances are also conformant to W3C XML. </li></ul></ul></ul></ul></ul>
  50. 50. RM-ODP, ECCF and Conformance vs Compliance (3) <ul><li>Conformance </li></ul><ul><ul><li>A Conformance Assertion made by a technology binding claiming fulfilment of a specific Conformance Statement (CnS) must be certified (“validated”) as True or False </li></ul></ul><ul><li>Compliance </li></ul><ul><ul><li>Compliance is not about technology binding </li></ul></ul><ul><ul><li>Compliance is about transformations between artifacts </li></ul></ul><ul><ul><ul><ul><li>Transformations often implement constraint patterns </li></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>ECCF row  row, i.e. Levels-of-Abstraction in MDA </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>ECCF intracellular, i.e. adoption of a specification for use by another </li></ul></ul></ul></ul></ul><ul><li>Consistency and Traceability (defined later) are also important </li></ul><ul><li>Collectively, these terms navigate instances of the ECCF Specification Stack </li></ul>
  51. 51. RM-ODP, ECCF and Conformance vs Compliance (4): The Meaning of “Certification” <ul><li>Conformance </li></ul><ul><ul><li>the “traditional” dimension-of-application of the term </li></ul></ul><ul><ul><li>Certification body is (usually) done by an independent from organization claiming Conformance </li></ul></ul><ul><ul><ul><li>Claims made via one or more Conformance Assertions) to one or more Conformance Statements (collected in instances of Specification Stacks) </li></ul></ul></ul><ul><ul><ul><li>Certification verifies CnAs as True </li></ul></ul></ul><ul><li>Conformance Certification is a statement to verify Trust </li></ul>
  52. 52. RM-ODP, ECCF and Conformance vs Compliance (5): The Meaning of “Certification” <ul><li>Compliance Certification </li></ul><ul><ul><li>Not formally done </li></ul></ul><ul><ul><ul><li>“ compliance certification” is not an “operational reality” in most cases </li></ul></ul></ul><ul><ul><ul><li>e.g. of “formal” compliance certification: “HL7 XML ITS is compliance with W3C XML specification” </li></ul></ul></ul><ul><ul><li>Transformations are often not formally defined </li></ul></ul><ul><ul><li>Validity of a given transformation may not be known </li></ul></ul><ul><ul><ul><li>verifiable until Conformance Certification, balloting, or other “formal” testing/validation/certification processes </li></ul></ul></ul><ul><ul><li>Compliance navigates an ECCF SS either “vertically” or “horizontally” </li></ul></ul><ul><ul><ul><li>Vertically (row-to-row downward: decreasing LoA </li></ul></ul></ul><ul><ul><ul><li>Horizontally (intracellular):  constraints/localizations </li></ul></ul></ul>
  53. 53. RM-ODP, ECCF and Conformance vs Compliance (6): Summary <ul><li>By formalizing the notions of Conformance, Compliance, and Certification, the ECCF provides </li></ul><ul><ul><li>a multi-dimensional framework and vocabulary to… </li></ul></ul><ul><ul><ul><li>document explicit assumptions and three levels of abstraction </li></ul></ul></ul><ul><ul><ul><li>integrate specifications or standards developed outside of the SS per se </li></ul></ul></ul><ul><ul><ul><ul><li>and to utilize these external standards in any cell of an ECCF SS </li></ul></ul></ul></ul><ul><ul><li>a model for enabling formal compliance certification in special cases where it may be warranted prior to technology binding and conformance certification </li></ul></ul>

×