Skip to main content

Open Source Could Have Saved Ontario Hundreds of Millions | Slashdot


The McMaster University researchers claim their system could be rolled out for two percent of the billion-dollars-plus already spent on the project. The report itself (PDF) also makes note of the excessive consultation spending: "By 2008, the Ministry’s eHealth Program Branch had fewer than 30 full-time employees but was engaging more than 300 consultants, a number of whom held senior management positions."









Hopefully more and more of these studies will be done on big projects and over time people will learn to at least strongly consider open source options. Especially when taxpayer money is involved it seems flat-out wrong to not investigate the potential savings offered by open source.

Comments

Anonymous said…
Agreed with you here Matt. The issue with our government is that there is no balance in oversight. If you watch any of the RFP lists, most government contracts are sole source. There are few opportunities for consultants to recommend good solutions that are cost effective. If government modeled it's IT initiatives after non-profits I am certain there would be far less money spent!
Matthew Woodward said…
Sad that government itself isn't seen as a non-profit. ;-) Hopefully with the attempt to push for preferring open source solutions in government (which is happening at municipal and federal levels) this will change over time.Ultimately in any project the best solution needs to be selected, but "best" should incorporate all aspects of the project, a huge one of which is cost. If the end result is as good or better with open source solutions and the cost is substantially lower, there's no logical reason to spend a ton more money to wind up with the same end result.This will take time since throwing money at the problem is the way things have been done for so long, but it's nice to see it starting to change at least.

Popular posts from this blog

Installing and Configuring NextPVR as a Replacement for Windows Media Center

If you follow me on Google+ you'll know I had a recent rant about Windows Media Center, which after running fine for about a year suddenly decided as of January 29 it was done downloading the program guide and by extension was therefore done recording any TV shows.

I'll spare you more ranting and simply say that none of the suggestions I got (which I appreciate!) worked, and rather than spending more time figuring out why, I decided to try something different.

NextPVR is an awesome free (as in beer, not as in freedom unfortunately ...) PVR application for Windows that with a little bit of tweaking handily replaced Windows Media Center. It can even download guide data, which is apparently something WMC no longer feels like doing.

Background I wound up going down this road in a rather circuitous way. My initial goal for the weekend project was to get Raspbmc running on one of my Raspberry Pis. The latest version of XBMC has PVR functionality so I was anxious to try that out as a …

Setting Up Django On a Raspberry Pi

This past weekend I finally got a chance to set up one of my two Raspberry Pis to use as a Django server so I thought I'd share the steps I went through both to save someone else attempting to do this some time as well as get any feedback in case there are different/better ways to do any of this.

I'm running this from my house (URL forthcoming once I get the real Django app finalized and put on the Raspberry Pi) using dyndns.org. I don't cover that aspect of things in this post but I'm happy to write that up as well if people are interested.

General Comments and Assumptions

Using latest Raspbian “wheezy” distro as of 1/19/2013 (http://www.raspberrypi.org/downloads)We’lll be using Nginx (http://nginx.org) as the web server/proxy and Gunicorn (http://gunicorn.org) as the WSGI serverI used http://www.apreche.net/complete-single-server-django-stack-tutorial/ heavily as I was creating this, so many thanks to the author of that tutorial. If you’re looking for more details on …

The Definitive Guide to CouchDB Authentication and Security

With a bold title like that I suppose I should clarify a bit. I finally got frustrated enough with all the disparate and seemingly incomplete information on this topic to want to gather everything I know about this topic into a single place, both so I have it for my own reference but also in the hopes that it will help others.Since CouchDB is just an HTTP resource and can be secured at that level along the same lines as you'd secure any HTTP resource, I should also point out that I will not be covering things like putting a proxy in front of CouchDB, using SSL with CouchDB, or anything along those lines. This post is strictly limited to how authentication and security work within CouchDB itself.CouchDB security is powerful and granular but frankly it's also a bit quirky and counterintuitive. What I'm outlining here is my understanding of all of this after taking several runs at it, reading everything I could find on the Internet (yes, the whole Internet!), and a great deal…