Who Are We?

1. Who Are We? • An open, international ecosystem containing 70+organizations each working in their own self-interest while collaborating toward a common industry need • Led by internationally-recognized experts in open source, health IT, and platform engineering • A community of software vendors, healthcare provider organizations, governments, standards bodies, academic institutions, and integrators • A technology-neutral open-source collaboration that is based on commercially-friendly licensing • A Non-Profit Trade Association, incorporated within the US as a 501c(6). All Members are equal and OHT does not compete with them.

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 Platforms Knowledge Management Platform Collaboration Platform 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. 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)

6. Shared Tools and Platform: Overview User Interface Platform User Configuration Multi-Platform Support Software Development Platform Application Integration Platform Packaging/ Distribution Platform HIE Connectors Health Data Management Decision support and analytics Security and privacy services Terminology and Mapping Model Driven Health Tools OHT Software Center Version/ConfigManagement Test Harness User License Management Other Conformance Tooling Device Integration Platform TBD TBD

7. 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

9. SUPPLEMENTAL SLIDES • The following may not be necessary • They are being retained until the deck is complete

10. The Definition(s) of Platform… • For a user/consumer: • Concept of what is a platform will vary based upon individual situation • Viability of the OHT platform cannot be predicated on “rip and replace” everything with the OHT offering • Not every component of the platform needs to be of interest/utility for every consumer • The qualities of the OHT Platform(s) include • An integrated set of components forming a “whole” that can accomplish a set of functions or support business and technical needs • Composed of components, they work together and integrate • There is a distinction between the component parts of a platform and the platform itself • Business rules and toolsets • Brought together via an architecture • Governed by an overarching plan • “How much can you change?” “How much do you have control over?”

11. The Definition(s) of Platform… • For a developer/contributor • A framework that facilitates reuse • Define an architectural approach, style, environment , criteria to determine where contributions fit within the platform (and where existing assets exist that can be used/reused) • Support the “minimum set” of features that are needed to be “fit for purpose” for the intended role of the platform • There are components that are “must haves” within a platform. • There are components that may be “nice to have” • There is an expectation that developers/contributors can use all or parts of a platform to achieve their needs; There is further expectation that any additions to a platform will not conflict with/destabilize the existing platform • Dependent on understanding the architectural objectives relating to the boundaries of components and extensibility capabilities • Need to understand the breadth of functionality that is provided and how to access it • Assumptions based upon technology stack, operating system, etc. • The qualities of the OHT Platform(s) include • An integrated set of components forming a “whole” that can accomplish a set of functions or support business and technical needs • Composed of components, they work together and integrate • There is a distinction between the component parts of a platform and the platform itself • Business rules and toolsets • Brought together via an architecture • Governed by an overarching plan • Clearly defined guidelines for interfacing with and/or extending the platform and its components • Quality Assurance toolset/process • “How can you contribute?” “How can you integrate?” • “What can you leverage?”