1 / 10

OSEHRA Open Adoption Model

OSEHRA Open Adoption Model. Promoting an OSS VistA Healthcare Platform. Prepared for OSEHRA AWG by Edward Ost 9/23/2014. OSEHRA Conference – Stephen Warren. “Proprietary Innovation versus OSS Innovation” “More than just taking out but putting in”

allegra-nichols
Download Presentation

OSEHRA Open Adoption Model

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. OSEHRA Open Adoption Model Promoting an OSS VistA Healthcare Platform Prepared for OSEHRA AWG by Edward Ost 9/23/2014

  2. OSEHRA Conference – Stephen Warren • “Proprietary Innovation versus OSS Innovation” • “More than just taking out but putting in” • “VA has a preference for working with open source software solutions and open source communities” • “When that new contract [T4] is in place, it will have an OSS requirement on it.”

  3. Moving from OSS License to OSS Culture • OSS license does not necessarily imply community driven • How to promote and accelerate community driven ingest of code by the VA? • Evolve from VA centric publishing to community driven development

  4. Cathedral and Bazaar

  5. Principles • What is the scope of OSEHRA stakeholders? • VA infrastructure • Broader healthcare network(s) supporting veterans • What is the scope of OSEHRA? • Platform • Product • Community-driven versus a community of consumers? • Self-governed • Dependent on government

  6. Community-Driven • What structures encourage a culture of community? • What structures are necessary to provide a path to active community participation in creating code? • What structures enable collaboration between community members?

  7. VistA Stewardship • What role(s) should the VA have wrtVistA • Consumer • Contributor • Publisher • Steward • Does the VA 800 lb gorilla skew the balance of the OSEHRA community? • Where should the center-of-gravity of the community be, VA or OSEHRA? • Should there be a change in scope or charter of OSEHRA wrt VA and VistA stewardship?

  8. What can we learn from other OSS Communities? • Apache • OpenStack • Linux

  9. Open Adoption Model • Open Reference Architecture • OSS Reference Implementation • API Management • How can we apply this in a community-driven way to OSEHRA and VistA in a manner in which establishes an open market rather than a closed Cathedral.

  10. Community Technical Enablers • Standards based • Service oriented • Test Driven contracts • Devops infrastructure-as-code • Decentralized SCM (Github) These enablers allows the community to collaborate technically to drive innovation from the bottom-up rather than the top-down Provides a more scalable crowd-sourcing innovation model

More Related