1 HL7 SAIF Enterprise Conformance and Compliance Framework (ECCF) Overview Baris E. Suzek Bob Freimuth VCDE Monthly Meeting December, 2010

Acknowledgements Baris Suzek Bob Freimuth Raghu Chintalapati Kunal Modi Jeff McLean Brian Davis Mike Keller Avinash Shanbhag Sherri De Coronado Charlie Mead caBIG VCDE/Architecture participants 2

Outline Introduction What is Working Interoperability/SAIF/ECCF? Current Status What is available for SAIF/ECCF implementation? Near Future What will be available for SAIF/ECCF implementation?

Working Interoperability (WI) The collection of structures, processes, and components that support Computable Semantic Interoperability (CSI) between two parties who are interacting to achieve one or more business goals. Interoperability: ability of 2 or more systems or components to exchange information (syntax, structure) and to predictably use the information (semantic, meaning) that has been exchanged From HL7 SAIF Book

Service Aware Interoperability Framework (SAIF) The core value proposition is working interoperability Provides sub-frameworks (grammars for describing different aspects): Information Framework (IF): Static semantics; Information models, Data type bindings (ISO 21090) etc. Behavioural Framework (BF): Dynamic semantics; Operations, interactions, and collaborations Enterprise Conformance and Compliance Framework (ECCF): Structured specifications and validation Governance Framework (GF): Entities overseeing the development and implementation of specifications for services

Enterprise Conformance and Compliance Framework (ECCF) Provides structured service specification stack: Viewpoints from Reference Model of Open Distributed Processing (RM-ODP) Abstraction layers from Object Management Group MDA Enables explicit specification of the interoperability-critical aspects of a system Not all systems will be required to use the ECCF framework Allows different implementations to conform to the same specification stack Enables conformance certification and compliance validation: Test implementation against stated conformance statements using conformance assertions

ECCF Specification Stack Figure showing relationship of 1) conformance statements/profiles, 2) compliance, 3) localization, and 4) conformance assertions Compliance: Artifacts derived from other artifacts by traversal of successive levels of abstraction Localization: Custom modifications or other alterations Conformance Statements/Profiles: Explicit testable representations of explicit assumptions. Conformance Assertions: Assertions against a conformance statement that can be verified as True or False.

Current Status What is available for ECCF implementation?

SAIF/ECCF Implementation Guide Figure showing the location of the ECCF implementation guide within the SAIF IG, at 9

SAIF/ECCF Implementation Guide (cont’d) the SAIF IG references artifacts, examples, best practices, policies, standards, and templates 10 ArtifactsExamples Best practices, policies, standards, templates

NCI Enterprise Service Specification Templates Table of contents at

NCI Enterprise Services Inventory Blueprint (Example Specifications) Figure showing the specifications that are available at

Business Architecture and Domain Analysis Models Domain Analysis Model (DAM) Life Sciences DAM Biomedical Research Integrated Domain Group (BRIDG) Business Architecture Model (BAM) Life Sciences BAM Biomedical Research BAM

ECCF Specification Review Criteria Developed by Enterprise Service Specifications Team (ESST) Used by Composite Architecture Teams (CAT) Figure shows examples of criteria used for specification review

Near Future What will be available for ECCF implementation?

SAIF IG 2.0 Figure showing the 3 other frameworks in the SAIF IG: governance, information, and behavioral. 16 New GF, IG, BF implementation guides for frameworks Revision of SAIF IG

SAIF/ECCF Training 2.0 First release due Mid-February, 2010 Draft Organization: Segment 1: Introduction and Overview Segment 2: Specifying Data Services Segment 3: Specifying Analytical Services Segment 4: How the ECCF Affects Old and New Processes Segment 5: Next Steps 17

Semantic Infrastructure and caGrid 2.0 Support for easing development and consumption of ECCF artifacts e.g. ECCF Registry Better interoperability as proposed by HL7 SAIF 18

caBIG Clinical Informatics Suite Potential tooling Best practices Reference implementations 19

20 Questions