onc si frwk_spec factory_2010
TRANSCRIPT
THE ONC STANDARDS AND INTEROPERABILITY FRAMEWORK
An Introduction to S&I Framework and NIEM
Outline
» The ONC S&I Framework (what is it, why is it, how does it work)
• Activities and Processes
• National Information Exchange Model
• Information Exchange Package Documentation
» Model-Centric Specifications (using models to do what???)
• The Approach – Model Centric Specification
• SSA Example
» Next Steps (discussion)
ONC Standards and Interoperability Framework
3
Tools and Services(Use Case Development, Harmonization Tools, Vocabulary Browser, Value Set Repository, Testing Scripts, etc)
Tools and Services(Use Case Development, Harmonization Tools, Vocabulary Browser, Value Set Repository, Testing Scripts, etc)
Use Case Developmentand Functional Requirements
Use Case Developmentand Functional Requirements
Standards Development
Standards Development
Certificationand TestingCertificationand Testing
Harmonization ofCore Concepts
Harmonization ofCore Concepts
Implementation Specifications
Implementation Specifications
Pilot Demonstration Projects
Pilot Demonstration Projects
Reference Implementation
Reference Implementation
Why do we need an interoperability framework?
Why do we need an interoperability framework?
» Move toward more “computational” implementation specifications (IS)• Scalable processes• Ability to develop tools to increase the efficiency of IS development and
maintenance• The importance of developing IS that are explicit and subject to less
interpretation» Link use cases and standards from inception to certification
• Keep the certification processes tightly linked to the standards and IS processes
• Support tool development for certification testing• Develop the testing for compliance at the same time as developing the
standards» Integrate multiple SDOs with different expertise across the process
• Transport packages• Vocabulary• Value sets• Security
» Provide repeatable mechanisms for harmonization and integration of existing standards across SDOs04/18/23
S&I ConOps Organizing Principles
• Not a “waterfall” Process: Developing and harmonizing standards and service specifications across diverse communities necessitates concurrent, agile activities, not waterfall processes
• Need for Structured Coordination: To manage coordination of the concurrent activities within the framework , we need well defined:
• Artifacts• Roles• Decisions (Control Points)
• Artifacts: To support the requirement of computable and traceable resultant artifacts, the S&I framework needs ensure the content and structure of the artifacts within the process are well defined and provide continuity within the activities and the tools.
• Roles: Clear “ownership” of significant artifacts and activities must be assigned to ensure coordination, lack of duplication and discontinuity throughout the process. An example of this is the Use Case Stewart, but there are additional roles throughout the process.
• Control Points: At points in an iterative and incremental process, prioritization, validation or approval of artifacts is required to ensure quality and alignment with goals. These points, and the approval entities need to be well defined for the framework to operate smoothly.
S&I Activities Use Cases and Harmonization
» Engages a wide community in defining use cases to be driven through the process
» Focus on solving a real problem• Determines scope• Able to “test” if the use case solves the
problem• Prevents “analysis paralysis” • Does not model in the abstract• Open, transparent process
» Output Business Scenarios should describe• Services• Standards• Business rules, trust, policies
» Output can be captured as • Use Cases and Activity Diagrams• Collaborations• BPMN• Etc…
» Use-case driven (bottom up) with top down coordination
» Multiple use cases might have overlapping standards, services or policies
• E-prescribing and adverse event reporting• Clinical care summary and quality reporting• Laboratory data exchange and clinical
decision support» Need to have a strong harmonization framework
that spans different standards organizations
7
Use Case Developmentand Functional Requirements
Harmonization ofCore Concepts
S&I ActivitiesStandards Development andImplementation Specs
» As part of the use case development and harmonization process gaps in standards may arise
» Gaps may exist in
• Data package
• Value Sets
• Services
» Work with SDOs (NLM, HL7, IHE etc) to fill in gaps
» Allows the standards work to proceed in parallel with development of the implementation specifications
» Using a model-centric approach to provide sufficient details to support implementation
» Implementation Specification is an explicit description of the
• Standards
• Services
• Policies
» Specifications are packaged together to support use cases and business scenarios
» Create guidelines for development of reference implementation
8
Standards Development
Implementation Specifications
S&I ActivitiesReference Implementation and Pilots
» Executable implementations of specifications
» Can be used by others to help guide their own implementation or find problems with specifications
» Encourages feedback to ONC
» Reference implementations in use by stakeholders
» Confirms use case is being supported
» ONC helps provide coordination of pilot demonstrations
9
Pilot Demonstration Projects
Reference Implementation
S&I ActivitiesCertification and Testing and Tools and Services
» Provides mechanisms and infrastructure for testing specification implementations
» Includes conformance testing for individual specifications as well as interoperability testing for business scenarios
» Tools and Tests can be used as part of ONC Certification
» Tools and Repositories used to support the other S&I activities
» Example• IEPD and model repositories• Vocabulary sets• Modeling tools and guidelines• Collaboration tools
» Will leverage existing tools and repositories whenever possible
» Many of the repositories and collaboration tools to be publically available
10
Tools and Services(Use Case Development, Harmonization Tools, Vocabulary
Browser, Value Set Repository, Testing Scripts, etc)Certificationand Testing
S&I Governance (Artifacts, Roles and Controls)
04/18/23
Core artifacts are versioned and controlled
Core artifacts are versioned and controlled
Artifacts are “packaged”
and released
Artifacts are “packaged”
and released
Each artifacts has a
responsible role
Each artifacts has a
responsible role
Artifacts and releases have prioritization and approval
points, or “controls”
Artifacts and releases have prioritization and approval
points, or “controls”
National Information Exchange Model Overview
» The National Information Exchange Model (NIEM) is a Federal, State, Local and Tribal interagency initiative providing a foundation for seamless information exchange.
» NIEM is a framework to:
• Bring stakeholders and Communities of Interest together to identify information sharing requirements in day-to-day operational and emergency situations;
• Develop standards, a common lexicon and an on-line repository of information exchange package documents to support information sharing;
• Provide technical tools to support development, discovery, dissemination and re-use of exchange documents
• Provide training, technical assistance and implementation support services for enterprise-wide information exchange.
» ONC Office of Standards and Interoperability plans build a Health Information Exchange Model (NIEM Health) that is harmonized with NIEM
» NIEM Health to leverage NIEM conventions and NIEM components where possible
From NIEM website http://www.niem.gov/index.php
What is an IEPD?
» An Information Exchange Package Documentation (IEPD) is a collection of artifacts that describe the construction and content of an information exchange
• Developed to provide the business, functional, and technical details of the information exchange through predefined artifacts
• Created with a core set of artifacts in a prescribed format and organizational structure to allow for consistency
• Designed to be shared and reused in the development of new information exchanges through publication in IEPD repositories
• IEPDs contain design specifications for an information exchange but may not include supplementary information such as implementation decisions.
04/18/23
NIEM Process
From NIEM website http://www.niem.gov/index.php
IEPD: Information Exchange Package Documentation
The IEPD Artifacts
IEPDs contain both required and
recommended artifacts
Required : Bold
Recommended : Italic
Note: Best practices for most
organizations include many of the
optional artifacts listed here
Scenario Planning
Analyze Requirements
Map & Model
Build & Validate
Assemble & Document
Publish & Implement
No required artifacts. Publish the IEPD to a repository and implement the exchange
S&I NIEM Harmonization Strategy
» ONC’s Office of Interoperability and Standards is building a Health Information Exchange Model (NIEM Health) that is harmonized with NIEM
» Health and Human Services petal to serve as bridge between NIEM and NIEM Health
16
Human Services
CapabilityElaboration
Capability Formulation
Construction Release & Publication
Use Case Development
Spec Development
Harmonization
Reference Impl
Cert &Testing
S&I Development Phases
S&I Governance
Health Community
Participants
Scenario PlanningScenario Planning Analyze Requirements
Analyze Requirements Map & ModelMap & Model Build &
ValidateBuild & Validate
Assemble & Document
Assemble & Document
Pub. & Impl.
Pub. & Impl.NIEM Lifecycle
S&I NIEM Process Harmonized
Addressing Challenges for the Health Information Exchange Model
Challenge ApproachExistence of disparate health information exchange standards and specifications and implementation approaches
Map exchange requirements to existing standards & specifications and address any gaps, duplications, or overlaps
Harmonization and management of several well-established, large vocabularies for semantic interoperability
Leverage existing vocabulary repositories (e.g. PHIN VADS), coordinate with Unified Medical Language System (UMLS), and collaborate with standards development organizations
Usability of existing HIT exchange protocols and specifications
Use NIEM processes and adapt supporting tools to create computable, useable implementation specifications
NIEM only addresses data content, but transaction behavior and security provisions are necessary for health information exchange
Adapt structure and content of S&I IEPD to incorporate transport and security aspects of exchange
Compatibility of S&I IEPDs with existing NIEM infrastructure and tools, as well as existing health information exchange protocols
Develop and adapt NIEM and health information technology tools and framework to support NHIN goals
Model Centric Specifications
19
Model Centric Specification Development
» The S&I Framework uses models to capture the information required to specify exchanges between parties on the NHIN. This supports the 2 primary goals of the S&I Framework
• To aid in the creation of specifications that are less ambiguous than specs traditionally done using word processing tools.
• To support the creation of specifications by other groups» Models refers largely to the visual representation of exchange syntax, semantics,
dependencies and rules. » By using models the S&I Framework intends to:
• Establish a repeatable pattern for evolution and traceability from requirements to implementation of specifications
• Provides for the implementation of specifications using multiple possible technologies
• Support the composability and reuse among specifications• Support the creation of specifications by groups outside ONC by providing
guidelines, patterns, repositories and tools
Developing the Model Centric Approach
» Identify Specific Requirements
» Define a Solution Strawman
» Use an existing NHIN business scenario as a proof of concept
Requirements for a Model Centric Approach
» The modeling approach used by the S&I Framework must• Provide traceability from Use Case and Requirements
through to one or more implementations• Provide semantic and syntactic modeling constructs to
support defining the information and behavior that are part of exchanges
• Support the need to harmonize with existing standards defined at different levels of abstraction
• Be adoptable by different organizations• Be able to integrate into NIEM process
Solution Strawman
» Three main components
• Adopt the OMG Model Driven Architecture (MDA) based modeling concepts
• Select a set of tools/technologies/practices that are easily adoptable
• Utilize the model-centric paths through the NIEM processes and related artifacts
S&I Model Centric Proof of Concept
Used SSA Disability Determination business scenario as a starting point
»Goals
•Refine NIEM process to develop S&I implementation specifications based on the SSA Disability Determination business scenario
•Develop IEPD artifacts using NIEM process
–Computable UML model for content and transactions based on MDA
–IEPD for content and transactions
•Identify tools/technologies/practices needed for S&I Framework process and gaps in existing tools
24
Model-Centric Solution - MDA
» Base S&I Framework modeling on the 3 OMG/MDA model abstractions.
• Computational Independent Model (CIM)• Platform Independent Model (PIM)• Platform Specific Model (PSM)
» Define a mechanism to show traceability from Use Cases and Functional Requirements through to technical bindings defined in a PSM.
» Define a flexible modeling foundation by which different types of specifications can be defined.
» Provides ability for multiple technology bindings for the same set of logical specifications (multiple PSMs)
Model-Centric Solution – Tools/Technologies/Practices
» Use the OMG Unified Modeling Language v2.x• Is an industry standard general modeling language• Provides mechanisms for customization of modeling constructs via profiles.
» Utilize OMG XML Model Interchange (XMI) format• Provides flexibility for non-graphical manipulations of models (ex searching,
transforming, reporting, …)• Vendor neutral standard allowing use of multiple UML modeling tools • Allows for sharing of models and offers path to integration with NIEM tooling
» Adopt/Adapt an existing UML profile/framework/modeling standard for defining specifications of exchange behaviors.
• Examined HL7 SOA-Aware Interoperability Framework (SAIF) and OMG Service Oriented Architecture Modeling Language (SoaML).
• SoaML or some variation with some influences from SAIF appears to be the best fit.
Specification ModelsNIEM Processes and ArtifactsS&I Activities
Harmonization ofCore Concepts
Harmonization ofCore Concepts
Implementation Specifications
Implementation Specifications
Reference Implementation
and Pilots
Reference Implementation
and Pilots
Business Processes, Use
Cases
Business Rules, Business
Requirements
Exchange Content Model, Mapping
Document
Exchange Schema,
Subset/Constraint Schema,
Main Document, IEPD Catalog,
IEPD Metadata, Sample XML
Vision Document, Process Model
Use Case Model, Interaction Model,
Domain Model
Behavior ModelDomain Model
Web Services Schema and WSDL
Use Case Development
and Functional Requirements
Use Case Development
and Functional Requirements
Certification and Testing
Certification and Testing
CIM
PIM
PSM
Scenario Planning
Analyze Requirements
Map and Model
Publish and Implement
Build and Validate
Assemble and Document
Model Centric Solution - NIEM
Proposed Structure for S&I IEPD
04/18/23
Notes»3 Levels of Modeling Abstractions
» Computational Independent Model (CIM)» Platform Independent Model (PIM)» Platform Specific Model (PSM)
»Overall IEPD package contains artifacts from each specification level (CIM, PIM, PSM) each covering behaviors, rules, and content»The S&I IEPD is intended to provide a complete set of specification information for any implementers starting from any abstraction level
Sample Model – CIM Business Scenario
Sample Model – PIM Realization
Sample Model – PIM Service Architecture
Sample Model – PIM Domain Model
Sample Model – PSM WSDL Interface
Where are We Now
» SSA Prototype effort confirms the concepts of using models to define NHIN specifications
» Open Questions• Finding the right Too-Much vs. Too-Little modeling
balance (can model-centric be agile?)• Best way to model existing vocabularies and code sets.• How much harmonization with NIEM models is possible• How existing interoperability efforts (e.g. PHIN, caBIG)
relate to NHIN – NIEM Health• How Public Health Information Exchanges will be
managed, modeled, and enabled
What’s Next
» Create a NIEM Health standards harmonization process and governance framework» Establish roadmap for existing NHIN standards, MU harmonization, and non-MU health information exchange specifications» Establishes a repeatable, iterative process for developing widely reusable, computable implementation specifications» Establishing the tooling and repositories needed» Establishing the practices and guidelines for modeling» Enables semantic traceability so that useable code can be traced back to original requirements and definitions» Promotes transparency and collaboration from broad range of health stakeholders
ScenarioPlanning
Use Case Development
and Functional Requirements
Use Case Development
and Functional Requirements
Standards Development
Standards Development
Certificationand TestingCertificationand Testing
Harmonization ofCore Concepts
(NIEM framework)
Harmonization ofCore Concepts
(NIEM framework)
Implementation Specifications
Implementation Specifications
Pilot Demonstration
Projects
Pilot Demonstration
Projects
Reference Implementation
Reference Implementation
NIEM IEPD Lifecycle
Questions