Healthcare-oriented Modeling Environment ( HoME ) Managed jointly by: Veterans Health Administration (VHA) IBM modeling-mdt.projects.openhealthtools.org

9 December 2008HoME: Modeling Tools for Healthcare2 Healthcare-oriented Modeling Environment (HoME) Open source modeling environment for creation and implementation of healthcare standards  Full open source stack, or components for commercial modeling tools Model-driven development throughout lifecycle  Based on industry standard modeling languages Planned scope to include:  Information models  UML with stereotype extensions and validation rules  SOA: service identification, analysis, design, and realization  OMG SoaML: modeling SOA in UML  Generation of XSD, WSDL, and other implementations  Automated publication of SDO specifications and implementation guides using the OASIS DITA standard

9 December 2008HoME: Modeling Tools for Healthcare3 The Problem: Healthcare Standards Interoperability Lack interoperability and shared artifacts between related healthcare standards and standards organizations  Including HL7, X12, NCPDP, and HITSP  Incompatible models, methods, and XML structures  Lack a shared extensible services architecture  Differentiate messaging and services architectures Difficult adoption of (non-)harmonized standards by  VA Healthcare Information Model (VHIM)  Federal Healthcare Information Model (proposed)  Health Architecture Interagency Group (HAIG)  Many other healthcare provider organizations

9 December 2008HoME: Modeling Tools for Healthcare4 Solution Enabled by HoME Project Three essential features to a successful solution 1.Models based on industry standard languages Includes a modeling style guide to enable SDO shared artifacts Support creation of harmonized reference information model Enable reusable and extensible SOA specifications 2.Methods based on cross-industry best practices Services method based on OMG SoaML and IBM’s Service- Oriented Modeling and Architecture (SOMA) Unify information modeling methods from healthcare SDOs 3.Software Tools that enable creation, use, and reuse of models and methods

9 December 2008HoME: Modeling Tools for Healthcare5 Based on Industry Standards for MDA Open Health Tools OMG Specifications Model Development Tools (MDT) UML2 + UML2 Tools OCLODMBPMN2 EMF + Validation + Compare + Search Model-to-Model SBVR GMFModel-to-Text ODM (OWL, RDF, CL) SBVROCLUML UML Models & SOAOntology Design MOF Transformation and Mapping Eclipse Modeling Project IMMBPMN2 XSD

9 December 2008HoME: Modeling Tools for Healthcare6 Information Models (HL7 Extensions) UML profiles for extended healthcare SDO metadata Modeling tool UI enhancements for clinical analysts Terminology constraints on attribute values Modeling extensions work in open source or commercial UML tools Import information models from HL7 MIF format Validate UML model as HL7 RIM restriction Transform UML model for XSD design and generate schemas

9 December 2008HoME: Modeling Tools for Healthcare7 IBM’s SOMA Life-cycle Flow © Copyright 2008 by IBM,

9 December 2008HoME: Modeling Tools for Healthcare8 OMG SOA Modeling Language (SoaML) Example UML model from the SoaML specification. The Services Architecture defines a collaboration of roles and participants. OMG SoaML Specification draft,

9 December 2008HoME: Modeling Tools for Healthcare9 SoaML Example Details Drill into the Purchasing Service contract composed of two more detailed service contracts. Specify the service interfaces and operations required by the Ordering Service.

9 December 2008HoME: Modeling Tools for Healthcare10 Looking for: Early Adopters HL7 information models in UML SOA design with SoaML  Architecture, collaboration contracts, interfaces, choreography XML Schema generation

9 December 2008HoME: Modeling Tools for Healthcare11 Looking for: OHT Project Collaborators Use and extend HoME Modeling CDA templates in UML Model transformations  UML to UML  UML to OWL Healthcare terminologies as UML model constraints  Semantic annotations and integration SOA service identification, specification, realization, implementation, and deployment MDA generation  XSD, WSDL, Java EMF bindings and APIs

9 December 2008HoME: Modeling Tools for Healthcare12 OHT Architectural Questions General components developed as part of OHT  SoaML profile, WSDL generation, model publishing  Synergy with non-healthcare developers  Our greatest challenge is developer resources (broaden appeal) Components with product dependencies  Rational Software Modeler (RSM) UI integration  Extension points and/or adapters  Deployment in COTS tools and infrastructure Reuse and sharing of OHT components across projects  Eclipse plug-ins and features  Need coordinated release planning and update site

9 December 2008HoME: Modeling Tools for Healthcare13 OHT Modeling Project Plan Continue development and first release of OHT UML modeling tools for HL7 committees Develop and deliver documentation and tutorials Outreach to other healthcare SDOs: use and extend HoME Outreach to implementers of standards (including VA) Define and start a new project task for terminology modeling support in UML Research task: DITA for Technical Standards (publishing)  Participate in new OASIS subcommittee  Prototype DITA publication from UML models Detailed project plan and ‘Open Issues’ work items available at: