3 responses

  1. Joyce Moulton
    January 3, 2017

    You are quite correct in all of that. I laughed (sadly) with the mention of jello. I have 5 sets of records for one hospital procedure and they were produced intentionally to add and remove data as simple as “inpatient record”, “ambulatory record”, and “bedded outpatient”. They couldn’t remove the imbedded default classification which was wrong. How bad is it that a hospital was performing operations and yet did not know – the EMR defaulted to Inpatient for lack of admission orders! Would anyone ever go there again when something so basic had not been determined? I had not thought of it as jello but my term is “amoeba”. Definitely gelatin like in nature – a shape shifter. All patients should have the information. It is not unlike our rights to see our credit reports. The system must be totally transparent for us to challenge the content and the addition of affective bias put in health records – similar to the game of gossip when we were kids. Patients need empowerment. My days of blind trust are over – it is now trust but verify. Patients deserve better and best.


  2. karl walter keirstead
    January 3, 2017

    Why, oh why, does ONC not first address the problem before trying over and over again to evolve a “solution”?

    The issue of “interoperability” has been addressed across many sectors of the economy and basically, it goes like this.


    A generic data exchanger accommodates automated data sharing on a need-to-know basis, across any number of data publishers and subscribers, each reading and writing data using their own native data element naming conventions.

    Given buildup of a respectable set of data transport formats, organizations do not need to write parsers and formatters to post/retrieve data from data exchange engines.

    Just as internet download sites can be mirrored to increase capacity, the same approach applies to data sharing via data exchangers.

    Civerex offered a couple of years ago to donate its Data Exchanger to ONC for use across the healthcare industry. We never heard back.

    Of course, for interoperability to work, software vendors have to first make it possible for their systems to export data and to import data.

    Data blocking for ‘customer retention’ just keeps the healthcare industry a couple of decades behind.


  3. meltoots
    January 4, 2017

    ONC is rudderless and lost at sea. They work in buzzwords and not in the real world.
    Their EHR policies have set back usability, interop, safety, security, and burden at least 10 years. We need new blood.


Leave a Reply




Back to top
mobile desktop