Keeping Your IIS Site Online

If you are hosting a site with Microsoft Internet Information Services (IIS) 7.0, you should be aware of a potential bug that could take your site offline.

IIS may not always get along with your antivirus updates. DHIT recently encountered an issue in which a McAfee antivirus update causes a key DLL to stop loading and IIS Application Pool to stop, which consequently disables website hosting. When attempting to load an IIS-administered site, you will see a  503 error (Service Unavailable):

Error caused by IIS issue

The particular issue may arise if a component of your antivirus software is removed or expired. For example, your McAfee Host Intrusion Prevention client could be inadvertently updated without all necessary components, uninstalled or otherwise corrupted.

The fix for this issue is quick (and relatively painless), involving a few edits to the applicationHost configuration file.

There are other, related IIS issues detailed in Microsoft support documentation here.

While the fix for this bug straightforward, catching these issues in a timely manner may not be. DHIT uses Microsoft Internet Information Services in a variety of implementations for our applications and has experience ensuring hosting stability.

We recommend not only staying current on Windows and antivirus software updates, but also maintaining a level of support to ensure that potential issues are monitored and remedied quickly to minimize downtime and vulnerability.

DHIT offers tiers of support to accommodate not only ongoing software customization but server continuity. Please contact us with any questions about this issue and keep your health data environment running smoothly.  

Unclogging Data in Health IT

There has been much controversy in the Health IT world over the issue of “data blocking” – to what extent it truly exists and, if so, what to do about it.

It’s worth noting first that the magnitude of this problem may be exaggerated. As recently reported by ONC, an analysis of a nationwide survey of hospitals showed some heartening results:

(N)ear universal adoption of EHRs by hospitals and significant increases in hospitals’ electronically exchanging health information with outside providers compared to past years.In addition, there are a number of technologies available – including DIRECT protocol – that are widely available, easy to implement, but simply underused.

However, even if the extent to which systems are actively obstructing the flow is overblown, there is much work to be done. In testimony before the Senate’s HELP Committee on the subject of health IT “data blocking,” Dr. David C Kendrick – who leads MyHealth Access Network (a non‐profit health information exchange organization in Oklahoma) – provided some helpful guideposts.

Dr. Kendrick first gave a succinct and workable definition of interoperability, in which patients “have their complete, longitudinal medical record available wherever and whenever decisions are made about their health.”

Dr. David C. Kendrick offers testimony before
Senate HELP Committee on Thursday, July 23, 2015.

Kendrick went on to list drivers of data obstruction culled from his experience. Some specific examples include:

• Excessive interface and maintenance costs 
• “Hotel California” problem: vendors do not offer data portability as intended by ONC, so customers “can check out other EHR products any time they like, but their data can never leave” 
• "Garbage in Garbage Out”: Poor data quality and standardization
• EHR-centered development that extends interoperability only to EHR+its partners
• Vendors achieving certification with one feature set, but features are not fully delivered post-certification

In one of the most striking moments in the testimony, Kendrick declared that MyHealth has “never seen a completely correct Patient Care Summary despite processing millions of them.” 

Where data blocking persists, incentives are lacking for collaboration. In Kendrick’s experience, provider-based blocking was a challenge early in the existence of MyHealth, but the problem has “quickly receded as value‐based payment models take hold.” “Data blocking,” on the whole, may simply be a more loaded term for the obstacles that exist in pursuit of the Holy Grail of interoperability.

It’s not easy developing a universal secondary language for health care. But it is up to health IT developers not to settle for “just good enough to pass." As an industry, we now know the ideal to which we are striving and the major barriers.

And while software developers are not policymakers, we can offer our own set of incentives for interoperability through ease of use, affordability and functionality that goes beyond mere compliance.  A good place to start is putting data-sharing front-and-center in our applications.