1 / 15

OHT Architecture Council update

OHT Architecture Council update. Presentation to September 2011 OHT Board of Stewards Meeting Ken Rubin, HP Craig Miller, Vangent. OHT “Underpinnings”.

haamid
Download Presentation

OHT Architecture Council update

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OHT Architecture Council update Presentation to September 2011 OHT Board of Stewards Meeting Ken Rubin, HP Craig Miller, Vangent

  2. OHT “Underpinnings” • Purpose – To transform the world’s health and well being through a diverse, collaborative and productive HIT ecosystem. See the OHT Vision. • Principles - The community is based upon openness, transparency, meritocracy, and contributions. See the OHT Principles. • Process - OHT is leveraging proven open-source community governance and processes to achieve rapid outcomes OHT Process. • Platforms – The core products of the community (tools, exemplary applications, etc.), building the technical foundation for OHT collaboration and Innovation. See OHT Platforms and OHT Architecture

  3. OHT “At a Glance” OHT Purpose OHT Principles OHT Process OHT Environments Knowledge Management Environment Collaboration Environment VirtualizedTesting & Integration Environment OHT Software Center

  4. OHT Community Toolset Discover Collaborate Experiment Deploy People • - Member Directory • - Open Source Educational Materials • - Skill Inventory • - Early Adopters • - Requirements Council • Architecture Council • Health Council • - Communities of Practice • Academic innovation and courseware • - Incubators • - Healthcare workforce education • - Training • - Integration labs Process • Project updates on YouTube • Quarterly project updates (BOCA) • - Intellectual property certification • Academic Challenge • Charter Projects • Forge Projects • OHT Governance • Professional Software Development Process • - Approach to assist/assure quarterly incremental delivery (BOCA/Arrow) • Adopt the principles and processes of open source to build reusable assets to help deploy • - Integrate knowledge based engineering into the deployment cycle Tools • Roadmap Documents • BOCA Charts • Community Forum • - inventory of other tools and projects • - CollabNetcommunity • Asset Repository / Knowledge Mgmt • - Community Forum • - OHT Architecture • Professional development, build, debug , integration and testing environment • - Standard configuration and version management • OSS License Management Engine • Software Distribution Platform Normal Text - Available capability Italics - Coming soon

  5. Guiding principles on COTS use within the OHT community…. • The OHT community recognizes that off-the-shelf software may be useful for OHT as an organization. As part of sustaining the OHT community itself, COTS may be used so long as: • OHT Intellectual Property can be migrated from any COTS program used • No COTS program becomes so integral to OHT that it cannot be replaced • Work products of the OHT Charter Projects are not inherently dependent on any specific COTS offering

  6. Using OHT Products… • OHT’s objective is to provide a set of complementary platforms that support an Open Health Ecosystem • Use of OHT platforms or components does not require adoption of the entirety of the platform(s) [e.g., “rip and replace” is not an expectation] • Planned duplicative functionality may be offered within OHT to address real-world technical considerations (e.g., OS, hardware, software stack)

  7. Technical Meeting Recap • Introduce and discuss OHT Platforms • Within each platform, discuss the different components • Discuss potential tooling for architecture modeling • Define/refine next steps for the OHT Architecture Council

  8. OHT Platforms User Interface Platform TBD TBD Packaging & Distribution Platform OHT Software Center Development Platform Runtime Platform Version/ConfigManagement HIE Connectors Health Data Management Decision support and analytics Security and privacy services Identity Management Software SDK Shared Standards License Management Conformance Tooling Content SDK User Artifact Publishing Integration SDK Asset Repository Device Platform Legend To be developed Invasive Non-Invasive Shared Infrastructure Components Exist

  9. Development Platform Provides tools for software and content developers to create health solutions. These can include tools to generate code and interfaces, as well as health data components such as vocabularies or data models. Development Platform • Representative OHT Projects: • IHTSDO SNOMED CT Workbench • Model-Driven Health Tools • Clinical Modeling Project (Steve Huff) Software SDK Content SDK Integration SDK

  10. Runtime Platform Standards-based services and components that facilitate the management, exchange and analysis of health data, including enabling services for managing patient identities, security and privacy. Runtime Platform • Representative OHT Projects: • Tolven • OpenMRS • HIEOS • NexJ AIP • OpenCDS • OpenPASS • VUHI • OpenEMPI HIE Connectors Health Data Management Decision support and analytics Security and privacy services Identity Management Shared Standards

  11. User Interface Platform Tools and specifications that enable the creation of a user-controllable interface to personal health information that is portable across desktop and mobile devices. • Representative OHT Projects: • TBD User Interface Platform TBD TBD

  12. Device Platform Projects that provide tools and services to help create and manage software for medical devices, including the exchange of data with health records. • Representative OHT Projects: • Continua • Stepstone Device Platform Invasive Non-Invasive Shared Infrastructure

  13. Packaging and Distribution Platform Applications and services that enable OHT solutions to be discovered, downloaded and evaluated. These solutions can include software, interfaces, licenses and conformance tests, among others. Packaging & Distribution Platform • Representative OHT Projects: • HEART • Watson OHT Software Center Version/ConfigManagement License Management Conformance Tooling Artifact Publishing Asset Repository

  14. Architecture Modeling Will focus on developing a to-be enterprise architecture that articulates the relationship between architectural platforms and components to: • Business capabilities map • Suites of interoperable products developed using the OHT architecture • OHT projects • Standards

  15. Next Steps Complete survey of architecturally significant projects Focus on supporting critical OHT initiatives: • GA Tech • Rockefeller HEART • PIP Identify leads for each platform

More Related