Are electronic medical records worth it?

March 23, 2016 0 Comments A+ a-

The use of Electronic Medical Records (EMR) by medical professionals has increased dramatically. According to HealthIT.gov, 2015 statistics show that 56 percent of all U.S. office-based physicians (MD/DO) have demonstrated meaningful use of electronic health records. The downside of these statistics is that when HIPAA was enacted in 1996, privacy was not a major focus and it actually took HHS eight years to publish the initial HIPAA Privacy Rule. It then took the agency several more years to publish initial security rules which directed “covered entities” (e.g., providers, hospitals, health insurers) to perform a risk assessment, understand where their vulnerabilities were, and to adopt reasonable safeguards to fix them.
Unfortunately this timeline has made healthcare records easy pickings for cybercriminals. Since 2010, incidents of medical identity theft have doubled, according to a survey conducted by the privacy-focused Ponemon Institute. A second report by the Identity Theft Resource Center on breaches in the first four months of 2015 showed that one-third of all data breaches by industry occurred in healthcare: 82 instances in total, exposing over 1.7 million records. Modern Healthcare, in fact, estimated that the medical records of almost one in eight Americans have been compromised. The American Action Forum estimates that all the breaches since 2009 have cost the healthcare system $50.6 billion. Data breaches have been so bad that Blue Cross Blue Shield has announced that they will offer their customers identity protection in 2016.
Figure 1- Number of personal data breach incidents by industry over time (http://www.gemalto.com/brochures-site/download-site/Documents/Gemalto_H1_2015_BLI_Report.pdf)
According to a report by the medical research firm Kalorama Information, the problem will worsen over time because the $25B electronic medical record industry is predicted to grow at a 7-8 percent clip in the coming year. Much of the growth is spurred by the 2009 Health Information Technology for Economic and Clinical Health (HITECH) Act, which offered financial incentives for using electronic records until 2015 and penalties for not using EMR thereafter.

Is EMR worth the cost in privacy and peace of mind?


The value of the technology has been heralded as improved diagnosis and treatment through better information access and sharing. Researches, however, have found that the vast majority of providers don’t share electronic patient data outside their own practice. According to a study by the Agency for Healthcare Research and Quality, just 14 percent of providers were sharing data with other providers in 2013 Psychology Today notes that many medical centers’ outpatient

systems cannot “talk” to their inpatient hospital systems; and actually accused “One of the bigger “providers” of electronic health records” of creating data silos that prevent the sharing of their records with outside organizations unless a high fee is paid. This current state of affairs argues for strong action by the government and even stronger action by healthcare organizations.

On the government side, the Obama administration’s proposed fiscal 2017 budget seeks additional funding for the long overdue HIPAA compliance audit program and a variety of other health data privacy and security efforts. In addition to more funding for HIPAA compliance audits, the HHS budget seeks to boost funding for the Office of the National Coordinator for Health IT to advance secure nationwide health information exchange and interoperable healthcare IT, making sure that, for example, electronic health records can easily exchange data. Ultimately, Congress must approve funding.

Can this problem be fixed?


Although the value of EMR is extremely promising, realization of the promise requires a concerted effort by all concerned. From the healthcare organization side, investments in cyber defense and personnel security training is a critical requirement. This action requires a mix of employee education, smart use of technology and physical security for buildings. Actions should include:
  • Protect the network – Health IT departments need to use a variety of tools to keep attackers out and move faster towards the adoption of technologies that limit the damage when attacks do occur.
  • Educate staff members – Employees are often involved in healthcare data breaches so any IT security program should include a big focus on employee education.
  • Encrypt portable devices – Several data breaches have involved the use of portable computing or storage devices that contained protected health information. Healthcare organizations should always encrypt data on any device that might hold patient data, including laptops, smartphones, tablets and portable USB drives.
  • Secure wireless networks – Wireless networks often introduce security vulnerabilities. To protect against attacks, healthcare providers should ensure that their routers and other components are kept up-to-date, network passwords are secure and changed frequently, and unauthorized devices are blocked from accessing the network.
  • Implement physical security controls – Even as electronic health records become more common, organizations still keep a lot of sensitive data on paper. Providers must therefore make sure doors and file cabinets are locked and that cameras and other physical security controls are used.
  • Create and enforce a mobile device policy – A mobile device policy that governs what data can be stored on those assets is imperative. Mobile device management (MDM) software to enforce those policies should also be deployed.
  • Delete unnecessary data – The more data that’s held by an organization, the larger the risk of loss. Organizations should have policies that mandate the deletion of patient and other information that’s no longer needed.
  • Vet the security of cloud-based services – The biggest IT trend over recent years has been the use of cloud computing. The use of cloud-based services increases the importance for organizations to diligently vet the security of these vendors and other involved third parties.
  • Patch electronic medical devices – Keep the software on all medical devices patched and up-to-date to minimize their vulnerabilities.
  • Have a data breach response plan – Despite the precautions, organizations will never be able to prevent every possible IT security incident. That’s why it’s critical to develop a plan of action for when a breach does occur.
According to Bill Odell, VP of Endpoint Device Management marketing for Dell, one approach for dealing with regulatory issues around Personally Identifiable Information (PII) and the Health Insurance Portability and Accountability Act (HIPAA) is through the use of smart patient monitoring devices. Smart devices can give hospital administrators an ability to inventory, locate and manage all of the hospital’s patient care devices from a single console. Operating within such an environment can also provide enhanced protection to patient data as well.
Organizational attitudes towards security must also be both proactive and preventative. This requires the design and implementation of security programs that:
  • Manage and govern user identity, privilege and access
  • Secure networks with deep protection and control
  • Routinely update and manage application updates
  • Manage and secures all endpoints
  • Data protection policies that encrypt both at rest and in motion.
They should also consider adopting the Security Breaches Maturity Model. Developed by Dell, Intel and other industry leaders, this model can be used to rapidly identify and address gaps in technical safeguards needed to address breach risks. Each of us must also take an active interest in the safeguarding of our individual healthcare information. These changes will not only reduce the impact of data breaches, but they will also improve the return on the investments associated with the deployment of this technological advancement.


This post was written as part of the Dell Insight Partners program, which provides news and analysis about the evolving world of tech. Dell sponsored this article, but the opinions are my own and don’t necessarily represent Dell’s positions or strategies.



Cloud Musings
( Thank you. If you enjoyed this article, get free updates by email or RSS - © Copyright Kevin L. Jackson 2015)



Finding a Framework for Hybrid Cloud Risk Management

March 05, 2016 0 Comments A+ a-



 (Sponsored by IBM. Originally published on Point B and Beyond)

Hybrid cloud is rapidly becoming essential to today’s information technology processes. This is why hybrid cloud risk management has become the keystone to many modern corporate strategies. To effectively manage this shift, leading enterprises are reorganizing how the business side of IT is accomplished. When this reality is coupled with the rising cost of poor cybersecurity, decisions often rise to the board level.

Threats that challenge cloud-based information systems can have adverse effects on organizational operations, organizational assets, employees and partners. Malicious entities can exploit both known and unknown vulnerabilities, compromising the confidentiality, integrity or availability of the corporate information being processed, stored or transmitted by those systems. In this environment, risk management must be viewed as a holistic activity that is fully integrated into every aspect of the business.

Establishing Standards for Hybrid Cloud Risk Management

The National Institute of Standards and Technology (NIST) offers a very good model for hybrid cloud risk management that groups activities into three categories based on the level at which they address the risk-related concerns. It divides activities and concerns into:
  • The organization level (tier 1);
  • The mission and business process level (tier 2); and
  • The information system level (tier 3).
Addressing these activities in reverse order, the NIST Risk Management Framework (RMF) provides a disciplined and structured process for integrating tier 3 enterprise information security with risk management activities. Since mission or business processes govern tier 2, those details generally lie outside the scope of general treatment. Tier 1 organizational level aspects are, however, at the heart of the organizational restructuring needed to deal with risk management within today’s hybrid IT environments.





One effective approach for addressing the tier 1 aspects of a cloud ecosystem is through the use of a hybrid IT operating model construct. This distributes tactical and operational risk management activities across a front, middle and back office. Generally referred to as a cloud service brokerage, organizational risk management activities are managed through:
  • A front office that accommodates IT service choice, automated provisioning and quick service delivery;
  • A middle office that holds responsibility for decisions that involve business operations and new IT service brokerage functions; and
  • A back office that integrates orders with service provider fulfillment, thus addressing IT supply chain risk management activities in order to ensure the continuous delivery of solutions from the organization’s cloud ecosystem.

More About Cloud Service Brokerage

The IT service brokerage function addressed here is in no way similar to the real estate or financial service broker function with which many are familiar. Far more than the single transaction service of these other broker types, IT service broker functions sit between the back office (operations) and the front office (user experience).

From that position, it is responsible for new IT business operations skills such as sourcing, procurement, packaging and billing. This continuous and ongoing function defines and executes board guidance with regard to the organization’s technology sourcing strategies. It also supports the creation of solution architectures that maximize the value of the multisourced hybrid IT investments while meeting business needs.

Cyberattacks are a threat to businesses everywhere. Executives, board members and IT professionals must strategically organize to address hybrid cloud risk management. While the RMF and business-specific risk management processes are excellent options for tier 3 and tier 2 issues, a front-middle-back office organizational construct can be used to effectively manage tier 1 and the operational risk of the hybrid IT ecosystem.





Cloud Musings
( Thank you. If you enjoyed this article, get free updates by email or RSS - © Copyright Kevin L. Jackson 2015)