Government Makes an Appointment for an Open Source Checkup
For anyone interested in politics — and for more than a few interested in technology — the talk of the weekend has been the $787 billion American Recovery and Reinvestment Tax Act of 2009, which cleared Congress late Friday night and is due to be signed into law by President Obama on Tuesday. The bill, which runs to more than 1,000 pages, provides for everything from increased airport security to electric cars for government use, including several billion dollars in appropriations for various technology-related programs. Nestled in with the tax breaks, economic incentives, and direct spending, though, is a brief but exciting provision, setting the stage for Open Source to be the word of the day.
Buried in the depths of the bill — halfway down page 488 in the Library of Congress' Bill Text Div. B — sits Section 4104(b). In a succinct 262 words, Section 4104(b) directs the Secretary of Health and Human Services to study the availability, cost, utility, and interoperability of Open Source health information technology, and to report back his findings no later than October 1, 2010. The HHS Secretary won't be studying Open Source alone, though — in all likelihood, he won't be studying it at all, his staff will — Congress formed a committee of sorts to handle the job, including high-level representatives from the Veterans Health Administration, the Indian Health Service, the Defense Department, the Agency for Healthcare Research and Quality, the Health Resources and Services Administration, and the Federal Communications Commission. The text we reviewed did not set out appropriations for the undertaking, but we suspect it's safe to bet there's a good bit of money in it for someone.
The study places a great deal of emphasis — not surprisingly, considering the cost advantages involved with Open Source — on "smaller health care providers, health care providers located in rural or other medically underserved [sic] areas, and safety net providers that deliver a significant level of health care to uninsured individuals, Medicaid beneficiaries, SCHIP beneficiaries, and other vulnerable individuals." The usual legislative-speak aside, the straightforward and unusually-brief directive seems to indicate that Congress is on the verge of strongly recommending, if not requiring, Open Source health technologies, at least of providers who treat individuals whose care is federally funded. Though it's somewhat par for the course when ordering studies of this sort, the provision specifically directs the Secretary not only to report his findings, but to offer "recommendations for such legislation and administrative action as the Secretary determines appropriate."
If it's going to be done right — and considering the cash being poured into these projects, we certainly hope it is — this undertaking should create at least a few jobs for experienced Open Source-ers. Congress seems to be asking "Is it for real, and does it work?" and who better than the Open Source community to give the answers we've been practicing — in the desert, some might say — for years.
Justin Ryan is a Contributing Editor for Linux Journal.
Trending Topics
| The Linux powered LAN Gaming House | Feb 08, 2012 |
| Creating a vDSO: the Colonel's Other Chicken | Feb 06, 2012 |
| Your CMS Is Not Your Web Site | Feb 01, 2012 |
| Casper, the Friendly (and Persistent) Ghost | Jan 31, 2012 |
| Razor-qt 0.4 - Qt based Desktop Environment | Jan 30, 2012 |
| Using Plop Boot Manager for USB Boot | Jan 25, 2012 |
- The Linux powered LAN Gaming House
- Readers' Choice Awards 2011
- Validate an E-Mail Address with PHP, the Right Way
- Creating a vDSO: the Colonel's Other Chicken
- Boot with GRUB
- Building a Two-Node Linux Cluster with Heartbeat
- Python for Android
- Why Python?
- Your CMS Is Not Your Web Site
- Writing a Simple USB Driver
- Lubuntu on a USB key
7 hours 10 min ago - Because XFCE is neither fish
22 hours 25 min ago - Because XFCE is neither fish
22 hours 26 min ago - KDE Bloat
1 day 5 hours ago - My C-64 Memories
1 day 5 hours ago - Spam
1 day 7 hours ago - Ooops....
1 day 11 hours ago - ----- http://ai.vc/zd
1 day 21 hours ago - ----- http://ai.vc/zd
1 day 21 hours ago - ----- http://ai.vc/zd
1 day 21 hours ago





Comments
Exciting, but what about HIPPA?
I see this as a good thing, but I can't help wondering how the cost of auditing open source software for HIPPA compliance will be paid. Proprietary software vendors can simply amortize the cost over the expected sales. Maybe some kind of co-op between users could finance a team to maintain audit-able releases, so share the cost of audits, but if something went wrong, the liability would fall back on the members of the co-op. I think that the users would not want to assume such risks. As an example, I have friends who used to work for the IT departments of several hospitals near me. Since HIPPA was enacted, those hospitals have outsourced their IT needs in order to limit their risk exposure.