- Why don’t we just take someone else’s eHealth system that works and run it here?
- If finance, supply chains, and practically every other industry can move data around easily, why can’t healthcare do it?
Why do our provinces feel compelled to do everything on their own? Is it a sense of provincial pride? “We Albertans know better than Manitobans how to run a healthcare system.” The Bureaucratic Mandate? “My province needs its own independent Standards, Architecture, Privacy and Security healthcare offices”. Asserting sovereignty can feel politically rewarding, but it introduces two unnecessary costs to expanding a successful eHealth solution from one Province into another:
- Re-certifying for Privacy and Security.
- Re-tooling for interoperability.
Canada Health Infoway (CHI) has been eager to take on this role and will certify that a healthcare system meets national interoperability, privacy, and security standards. As a vendor, I welcome the opportunity to certify my system once with a national agency and be done with it. However, before I sign up for this, I first need to be damn sure this certification will be honoured by most of the provinces. It’s currently not mandated by any.
Without the explicit agreement of the provinces to relinquish this responsibility to CHI, CHI’s certification is meaningless. There are two things CHI could do to fix this:
- Co-operation. Persuade provinces to relinquish responsibility for this certification work to Canada Health Infoway. Vendors want it (see the published ITAC Health position). Citizens want it (because they want eHealth systems sooner, at a lower cost.) All that remains is persuading provincial governments to do the right thing.
- Incentive. Secure billions of dollars of funding from the Federal Government and provide it to organizations only if they purchase certified systems. This is the approach the U.S. took with its Centers for Medicare & Medicaid Services Meaningful Use Incentive program.