IAM Implementation Mistakes in Healthcare
Being in the IT industry, we cannot hope that the attacks will stop and they won’t stop. However, the pattern adopted by criminals points to a lack of checks and laziness in blocking or addressing the loopholes in the IT systems. In such a scenario, all healthcare providers can do is implement the right technology and avoid costly mistakes due to a compromised IT system. The sensitivity of the information in the Healthcare IT security space cannot be undermined, because it can potentially result in sensitive information being stolen such as SSNs, Birthdates or any PII-related information. This can dent the reputation, lead to loss of customers, monetary loss in the form of regulatory penalization, and cost involved in putting the right technology in place to rectify the system.
I am assuming you must have heard the statement, “Prevention is better than cure”. It rightly fits into this scenario. One such solution that can be implemented to introduce preventive control is implementing IAM. However, there are some mistakes that are made widely while implementing IAM technology or executing IAM tasks. Hence, I am writing this article to expose these IAM mistakes to some extent. For being experts in the field of IAM, and having taken up a lot of healthcare-related projects at Avancer.
Listed below are classic IAM implementation mistakes in Healthcare that our experts have come across:
Setting up a system for the sake of compliance:
Many healthcare organizations look at regulatory compliance as a liability. However, they fail to look at it as an opportunity to create agile IT systems by setting the right networks and placing application integrators that seamlessly interact with the IAM system that also works in ensuring compliance. HIPAA, HITECH, management of Electronic Health Records (EHRs) have been enforced through a range of regulations. They act as high-level guidelines rather than prescriptive recommendations, but many organizations treat them as comprehensive security rulebooks. IAM experts discourage this kind of approach as it leaves healthcare providers compliant with regulations, but not in the spirit of regulation.
Missing out on minimizing information duplicity:
Clinical errors emerging from duplicate or incomplete patient records can compromise patient safety. IAM systems need to integrate and communicate with data silos created not just within a healthcare establishment but also between various stakeholders. Moving into an electronic environment points to the need for an accurate system of patient identification. In addition, integrating APIs into the system becomes important in bringing together silos of information related to patient records, and then further strategizing this information through correct access.
Overreliance on internal expertise:
IAM is a niche technology and an important cyber security element. It is not possible to find the right set of talent. Without sufficient investments in advanced tools and human capital, a firm’s internal cybersecurity staff and systems will always be deficient in skills and capabilities. As healthcare service providers cannot afford to fumble on IT Security, therefore getting IAM consultants on board can help. Such association helps in knowledge exchange and learning avenues for the in-house IT team, bringing them in contact with IAM mentors. This is a win-win situation for both — the IT employees to gain greater knowledge of the system and for the organization to have a better IT security shield.
Missing out on educating and mentoring employees:
While an employee might mistakenly leave a loop open for cybercriminals, employers must take this threat as an opportunity to create a digitally healthy workforce. Just being aware of risks faced by a user (read employee) in IT/Cyberspace can potentially shut down a threat funnel. In addition to establishing security checks such as access governance, user identity verification and activity auditing, training employees on recommended IT practices is becoming more critical to ensuring IT Security.
Under-investment in technology:
CIOs and IT Security professionals struggle with justifying the cost of making an IAM investment. It is however not the possibility of attack, but the impact of an attack that should drive investment into IAM infrastructure. Even after having an IAM system in place, manual management of various applications acts as a deterrent to the spirit of placing an IAM system. Application Integrators must be utilized to strengthen interaction amongst IAM Systems and various applications.
Taking note of the above-mentioned mistakes and making rectifications on the same can help in achieving robust IAM Systems that interact effortlessly with the IT System.
