The savvy tech strategy behind Obamacare

The ONC's Doug Fridsma explains why the health IT for EHRs and Obamacare should be like the Internet, and not like ERP or traditional IT systems

The U.S. health care industry is undergoing several massive transformations, and the Office of the National Coordinator (ONC) for Health Information Technology in the Health and Human Services Dept. is spearheading the technical requirements and interpreting the legislative mandates into the specific policy requirements.

Doug Fridsma, chief scientist, HHS ONC
Doug Fridsma

Its efforts started during the George W. Bush administration, which mandated in 2004 the use of interoperable electronic health records (EHR) systems by 2014 in what is known as the HITECH Act, and its efforts have become even more important due to the 2010 Patient Protection and Affordable Care Act (ACA), aka Obamacare, that changes the rules to ease citizens' access to medical care and to further require electronic systems use by providers and patients alike, so the use of such systems matters more in achieving the ACA's cost and eficiacy goals.

[ Also on InfoWorld: Consumerization comes to electronic health records. • The rough road to reliable data exchange among EHRsPatient engagement will be tough task for health techThe iPad revolution is coming to a hospital near youiPads have won the hospitals, but Android may win the patients. | Subscribe to InfoWorld's Consumerization of IT newsletter today. ]

Doug Fridsma, an M.D., is chief science officer and director of the ONC's Office of Science and Technology, and thus helps lead the federal efforts to make the HITECH requirements happen at a technical and medical level. Fridsma spent an hour with me discussing the issues that many health care IT and medical providers have raised as the deadlines get closer. The interview took place as the feds prepare to roll out the national signup registry this fall for individuals long denied health care to get it, though funds starvation by Republican congressmen has slowed the technical deployment and caused some rollout delays.

My key takeaway was not to think of the health IT efforts as the equivalent of ERP -- as I had been doing -- but as like the Internet. An ERP system prescribes process and procedure, whereas the Internet provides a framework for multiple kinds of uses and values. The feds want the latter, even if in the short term a single set of rules implemented via technology might have more appeal to health care providers that want a simple answer as to what they need to do. That's not an obvious approach in traditional IT thinking -- nor the approach used in many other countries -- but it makes a lot of sense given the constant change in technology.

The following is the edited transcript of our interview. Here are the key sections:

1 2 3 4 5 6 7 8 9 10 Page 1
Page 1 of 10
How to choose a low-code development platform