Presentation is loading. Please wait.

Presentation is loading. Please wait.

OHT ARCHITECTURE COUNCIL UPDATE Presentation to September 2011 OHT Board of Stewards Meeting Ken Rubin, HP Craig Miller, Vangent.

Published byWendy Annice Rich Modified over 8 years ago

Similar presentations

Presentation on theme: "OHT ARCHITECTURE COUNCIL UPDATE Presentation to September 2011 OHT Board of Stewards Meeting Ken Rubin, HP Craig Miller, Vangent."— 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.OHT Vision Principles - The community is based upon openness, transparency, meritocracy, and contributions. See the OHT Principles. OHT Principles Process - OHT is leveraging proven open-source community governance and processes to achieve rapid outcomes OHT Process.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 OHT PlatformsOHT Architecture

3 OHT Process OHT Purpose OHT Principles OHT Environments OHT “At a Glance” Discover Enable organizations to communicate and coordinate Contribute and discover assets of value Share objectives, lessons-learned, best-practices Find opportunities to share or avoid costs Collaborate Pool ideas within an established, multidisciplinary, diverse community Share common infrastructure and mitigate risks Provide next generation of collaborative tooling Experiment Incubate ideas and evaluate new technologies Provide software, tools, exemplary applications Provide test and simulation environments Reduce costs via sharing technology and expanding markets Deploy Provide a consumer repository and software store Track, manage, distribute info and software assets Empowering users to configure systems to meet their needs Expand market share through platform ubiquity Provide technology training and support Knowledge Management Environment Collaboration Environment Virtualized Testing & Integration Environment OHT Software Center

4 OHT Community Toolset DiscoverCollaborateExperimentDeploy 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 -- CollabNet community -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 1. Introduce and discuss OHT Platforms 2. Within each platform, discuss the different components 3. Discuss potential tooling for architecture modeling 4. Define/refine next steps for the OHT Architecture Council

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

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 Software SDK Content SDK Integration SDK Representative OHT Projects: IHTSDO SNOMED CT Workbench Model-Driven Health Tools Clinical Modeling Project (Steve Huff)

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 HIE Connectors Health Data Management Decision support and analytics Security and privacy services Identity Management Shared Standards Representative OHT Projects: Tolven OpenMRS HIEOS NexJ AIP OpenCDS OpenPASS VUHI OpenEMPI

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. User Interface Platform TBD Representative OHT Projects: 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. Device Platform InvasiveNon-Invasive Shared Infrastructure Representative OHT Projects: Continua Stepstone

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 OHT Software Center Version/Config Management License Management Conformance Tooling Asset Repository Artifact Publishing Representative OHT Projects: HEART Watson

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

Download ppt "OHT ARCHITECTURE COUNCIL UPDATE Presentation to September 2011 OHT Board of Stewards Meeting Ken Rubin, HP Craig Miller, Vangent."

Similar presentations

Connected Health Framework

Connected Health Framework
Www.mchc.org | Implications for Health Information Exchange – MetroChicago January 2011.

| Implications for Health Information Exchange – MetroChicago January 2011.
ELTSS Alignment to Nationwide Interoperability Roadmap DRAFT: For Stakeholder Consideration in response to public comment.

ELTSS Alignment to Nationwide Interoperability Roadmap DRAFT: For Stakeholder Consideration in response to public comment.
Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213-3890 Sponsored by the U.S. Department of Defense © 1998 by Carnegie Mellon.

Software Engineering Institute Carnegie Mellon University Pittsburgh, PA Sponsored by the U.S. Department of Defense © 1998 by Carnegie Mellon.
6th MSDI Working Group Meeting

6th MSDI Working Group Meeting
© 2006 IBM Corporation IBM Software Group Relevance of Service Orientated Architecture to an Academic Infrastructure Gareth Greenwood, e-learning Evangelist,

© 2006 IBM Corporation IBM Software Group Relevance of Service Orientated Architecture to an Academic Infrastructure Gareth Greenwood, e-learning Evangelist,
Thee-Framework for Education & Research The e-Framework for Education & Research an Overview TEN Competence, Jan 2007 Bill Olivier,

Thee-Framework for Education & Research The e-Framework for Education & Research an Overview TEN Competence, Jan 2007 Bill Olivier,
Vision of how informatics enables a transformed health system Joyce Sensmeier MS, RN-BC, CPHIMS, FHIMSS, FAAN Vice President, Informatics, HIMSS President,

Vision of how informatics enables a transformed health system Joyce Sensmeier MS, RN-BC, CPHIMS, FHIMSS, FAAN Vice President, Informatics, HIMSS President,
1 Copyright 2008 NexJ Systems Inc. Confidential and Proprietary - Not for Distribution. Open Source Strategy NexJ Systems Inc.

1 Copyright 2008 NexJ Systems Inc. Confidential and Proprietary - Not for Distribution. Open Source Strategy NexJ Systems Inc.
A Robust Health Data Infrastructure P. Jon White, MD Director, Health IT Agency for Healthcare Research and Quality 2014-06-10.

A Robust Health Data Infrastructure P. Jon White, MD Director, Health IT Agency for Healthcare Research and Quality
HSSP-OHT “Toolkit” Project. Today’s Call Quick review of the project’s intent Status of activities to date Discussion of the two use cases Inventory of.

HSSP-OHT “Toolkit” Project. Today’s Call Quick review of the project’s intent Status of activities to date Discussion of the two use cases Inventory of.
Who Are We? An open, international ecosystem containing 70+ organizations each working in their own self-interest while collaborating toward a common industry.

Who Are We? An open, international ecosystem containing 70+ organizations each working in their own self-interest while collaborating toward a common industry.
Who Are We? An open, international ecosystem containing 70+ organizations each working in their own self-interest while collaborating toward a common industry.

Who Are We? An open, international ecosystem containing 70+ organizations each working in their own self-interest while collaborating toward a common industry.
Pennsylvania GTO 3-Year Strategic Plan NSGIC Annual Conference 2005 Rochester, NY Jim Knudson Stacey White

Pennsylvania GTO 3-Year Strategic Plan NSGIC Annual Conference 2005 Rochester, NY Jim Knudson Stacey White
Engineering, Operations & Technology | Information TechnologyAPEX | 1 Copyright © 2009 Boeing. All rights reserved. Architecture Concept UG D- DOC UG D-

Engineering, Operations & Technology | Information TechnologyAPEX | 1 Copyright © 2009 Boeing. All rights reserved. Architecture Concept UG D- DOC UG D-
Project Highlights. New Process Project Report videos available at

Project Highlights. New Process Project Report videos available at
11 Title. Who is Open Health Tools? A Non-Profit Trade Association, incorporated within the US as a 501c(6). All Members are equal and OHT does not compete.

11 Title. Who is Open Health Tools? A Non-Profit Trade Association, incorporated within the US as a 501c(6). All Members are equal and OHT does not compete.
Improving the world's health and well-being by unleashing health IT innovation State Initiatives Alesha Adamson VP Strategic Relations & Initiatives Open.

Improving the world's health and well-being by unleashing health IT innovation State Initiatives Alesha Adamson VP Strategic Relations & Initiatives Open.
Presentation to the OHT Board Request to approve the HEART Project as a charter project Presented By Skip McGaughey Robert Kolodner.

Presentation to the OHT Board Request to approve the HEART Project as a charter project Presented By Skip McGaughey Robert Kolodner.
Summary Report Project Name: Platform Implementation Project (PIP) Brief Project Description: –PIP will deliver a reference implementation of OHT assets.

Summary Report Project Name: Platform Implementation Project (PIP) Brief Project Description: –PIP will deliver a reference implementation of OHT assets.

Similar presentations

Ads by Google