Healthcare – The chickens finally have come home to roost

Make your day by clicking on the link here below and then read this blog post.

If you feel healthcare in the USA is “too expensive” write to Rep. Michael Burgess (R-Texas), a physician who leads the House Energy and Commerce trade subcommittee and is drawing up a bill to enforce data sharing, and tell him he can have interoperability simply by taking some of the members of the “Electronic Health Records Association” to court.

My comments at “story” were:


Who buys EMR software that is incapable of exporting its data? Who subscribes to a cloud EMR service that has no option for exporting the data?

And if you must acquire/subscribe to a system that charges ‘extra’ to unlock data export, why are doctors suffering sticker shock?

Is it because they bought a “car” without checking to see whether a motor/transmission was included and if not, how much extra?

Seems to me HIPPA says healthcare service providers are custodians of patient data. How can you be a custodian when you don’t have custody?

Thank goodness, at least one person has it right i.e. “Interoperability is what makes an EHR useful,” said Rep. Michael Burgess (R-Texas) – no surprise to see that Rep Burgess is an MD, not an IT person going into the marketplace to find software that “meets the needs” of clinical staff who have never been consulted re their needs.

And, if you are reading this and think that “interoperability” is “difficult” – think again.

My group builds software for healthcare, law enforcement, manufacturing, b2b.

Aside from healthcare, none of these other sectors could function without seamless interconnectivity. For this reason we built a Data Exchanger that lets any system talk to any other system.

For healthcare, we even built an e-hub that allowed 100+ clinics, all using different EMRs, to exchange data. It ran in pilot mode for about 12 months, consolidating more than 120,000,000 data elements without any significant hiccup.

Each time we found a new set of trading partners who could not use one of our “standard” data transport formats, we wrote a parser/formatter.

We found over time that the number of new formats slowed, but, we had, by that time, grown weary of writing parsers/formatters, so we developed a “sniffer” that could scan an incoming document, figure out pretty much on its own what was new/different and greatly reduce the amount of custom programming needed.

None of this was “rocket science”.

It may be time for a class action suit against the big “x”  EMR vendors. No need to include Civerex in this pack, our EMRs have included import/export facilities since 1995.

My take . . . .. I think many of the players in this game deserve each other.

Do we really need an act of congress to provide relief for victims of self-imposed stupidity?

As my grandmother used to say ” Well,  . . ..  I never”



Management consultant and process control engineer (MSc EE) with a focus on bridging the gap between operations and strategy in the areas of critical infrastructure protection, major crimes case management, healthcare services delivery, and b2b/b2c/b2d transactions. (C) 2010-2019 Karl Walter Keirstead, P. Eng. All rights reserved. The opinions expressed here are those of the author, and are not connected with Jay-Kell Technologies Inc, Civerex Systems Inc. (Canada), Civerex Systems Inc. (USA) or CvX Productions.
This entry was posted in FIXING HEALTHCARE, Interoperability and tagged . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s