tag:blogger.com,1999:blog-1138176541520410652.post5922704783316661593..comments2023-09-05T08:39:39.149-07:00Comments on Dynamic Health IT - Quality Measure and Interoperability Solutions : Unclogging Data in Health ITJeff Robbinshttp://www.blogger.com/profile/05743306808974585977noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-1138176541520410652.post-8908885015980538502015-10-17T10:42:54.221-07:002015-10-17T10:42:54.221-07:00One thing I'd like to add RE data/information ...One thing I'd like to add RE data/information blocking based on decades of HCIT systems integration experience is that there is both a "macro" problem with all EHR vendors (which as the blog post suggests "may be exaggerated") in the sense that few if any support or encourage their clients to (as one major EHR vendor once put it) "take a can opener to their database", and a "micro" problem with some individual EHR vendors, who I have seen behave in ways that I almost can't believe that their healthcare provider clients would put up with, like preventing clients from making ad hoc queries of their own data and then charging outrageous fees to extract data for them. <br /><br />So while it's arguably impractical to treat individual instances of the problem, and even recognizing that not all EHR vendors are evil, I think that treating the general problem by putting significant data blocking penalties in place could help to reduce the tendency of even a handful of EHR vendors to behave badly, even if only by giving hospital IT staff some leverage when trying to implement an interface or do some integration work. Thomas Lukasikhttps://www.linkedin.com/in/exnihilumnoreply@blogger.com