SaMoLo in Government Open Source Projects. Lessons from the CONNECT project. A Nation ’ s Call to Action.
SaMoLo in Government Open Source Projects
Lessons from the CONNECT project
“We’ll be on our way to computerizing all of America’s medical records, which won’t just eliminate inefficiencies, save billions of dollars and create tens of thousands of jobs – but will save lives by reducing deadly medical errors.”
– President Barack Obama, February 4, 2009
CONNECT is a software solution that supports health information exchange.
CONNECT uses Nationwide Health Information Network standards and governance to ensure HIEs interoperate with other current and future exchanges.
CONNECT can be used to:
FHA ensures Federal participation in ONC-led initiatives
CONNECT was “released as open source code” to keep costs low and to promote widespread adoption to encourage health information exchange.
FHA enabled cross-agency collaboration, aggregate + coordinated benefits
Use of open source tools accelerated development
Open source community contributed to development
CONNECT is in the midst of transitioning to a fully open-source community-driven project.
Project Uses Open Source Components
Source Code “Published”
Government-Sponsored Open Source Project
Open Source License
Source Code Hosted/Available
Open Source Project that Originated in the Government
Technique used in Agile software projects to guide project or sprint retrospective
- Coding standards!!
- Flexible infrastructure
- Structured, defined, and understood internal and external communication plans
- Definition of roles and governance
Sustained investment in community
- Dedicated technical resources to outreach and nurturing of the community (tricky labor category?)
Acknowledgment that you – your office, your program, and your contract support – are going to REALLY expose yourselves – process, quality, risks, issues, results
Long-term planning – discuss the exit strategy early. And know that it will change.
Caveat: These did not occur with FHA/CONNECT, but in general are behaviors that need to be set aside when you’re running an open source project
Tolerance of dissention/posturing among collaborating contractor teams – the only focus should be support the mission, on the project faces risk
June 28, 2012 (11am)
Webinar on GitHub
July 2, 2012 (1pm)
Next sprint planning meeting
August 1, 2012CONNECT Release 3.3.1