Skip to main content

What Does Data Archiving Bring To Healthcare Intelligence?

Healthcare organizations house enormous amounts of data – amounts that have been multiplied many times over since the widespread adoption of electronic health records (EHR) systems over the last decade. What few of these groups know how to reckon with, though, is how to best manage data that’s no longer in use – particularly data from systems the organization has since retired. What’s the best way to handle this information?

When data is no longer in active use, the best thing that healthcare systems can do it archive it. Archiving data is different from backing it up for continuity purposes. While systems may find ways to use this data again later on, data archiving is premised on the idea that the system the data is connected to no longer exists. This can apply to any of the major data management systems used in healthcare, from EHRs to medical imaging platforms and opioid use monitoring platforms. As such systems are decommissioned, the data should be archived.

Why Keep Your Data?

If you’re no longer using a given platform and you aren’t simply migrating the data to a new system, why should your organization keep it? There are several advantages to maintaining archived data.

First, and perhaps most importantly, your system may need to maintain legacy data for compliance reasons. Hospitals and other providers are generally required to respond to certain types of records requests, so even if your organization has changed systems, you’ll need to have that data archived in a vendor-neutral way. Vendor-neutral archiving offers limited, HIPAA compliant accessibility via centralized storage and a consolidated search system. And if compliance is your only goal, you don’t need a particularly advanced storage system to meet these goals.

Other Reasons To Archive Data

While compliance is one of the most important reasons to archive legacy healthcare data after a platform transition, it’s not the only one. Many healthcare organizations also retain data for future research into care improvements or related projects, in which case it’s critical to ensure that when you decommission a data system, you also export and appropriately store any associated metadata.

Many healthcare organizations also choose to archive data for financial reasons and security reasons, which often go hand in hand. Consider, for example, an old piece of software used to manage healthcare data. Over time, as the system is replaced by more modern platforms, the company announces they will no longer be updating it. That’s a problem since old software quickly becomes a security risk. While your organization could pay to manage this outdated solution, that’s going to be more expensive than simply archiving the data and eliminating the old platform – indeed, research shows that 85% of organizations that have archived data from legacy IT data have seen financial benefits. Particularly in the era of software as a service, it doesn’t make sense to keep paying the subscription fees for software that is no longer providing a service, but is actually a liability.

A Matter Of Priorities

Archiving may not always be the right choice for an organization, and when to archive data is a decision that needs to be made on a case-by-case basis, and is often a matter of organizational culture. Large, urban hospital systems are far more likely to focus on liability and risk management in their archival process; the sheer volume of data on hand can represent a cybersecurity risk for these systems. Smaller, rural systems with a stable patient base, as well as research organizations, are more likely to focus their archival processes on retention and accessibility – relative to volume, these groups are more likely to go back to reference their decommissioned system data.

Big Data, Big Costs

Healthcare data archiving is positioned to become a critical issue in over the next several years as organizations migrate between systems and data volume continues to grow. Simply put, keeping old systems HIPAA compliant is going to become increasingly untenable, financially and technically. Add to that the concerning fact that cyberattacks on healthcare systems have been on the rise and healthcare organizations will find themselves faced with enormous fines for data breaches, above and beyond those costs incurred by their primary systems. In 2019 alone, data breaches cost healthcare organizations over $4 billion.

Are there solutions besides data archiving that can provide healthcare organizations with the security and access they need while remaining compliant? It’s a pressing concern, and one with no real answers, though some have proposed a more holistic approach to cybersecurity and others have suggested that more of these groups need to employ a Chief Information Security Officer (CISO).

Unfortunately, solving problems associated with active data is ultimately a different task than managing security and access to data from decommissioned data, and they won’t be solved more efficiently by addressing them together. Though both elements need to be safeguarded, for now, data archiving remains the most reliable and affordable solution for older data.

Now it’s time for more organizations to tackle data archiving as a central pillar of their security plans.

The post What Does Data Archiving Bring To Healthcare Intelligence? appeared first on SmartData Collective.



from SmartData Collective https://ift.tt/3oAn3C8
via IFTTT

Comments

Popular posts from this blog

Zooming in on maps with sf and ggplot2

(This article was first published on r-bloggers – WZB Data Science Blog , and kindly contributed to R-bloggers) When working with geo-spatial data in R, I usually use the sf package for manipulating spatial data as Simple Features objects and ggplot2 with geom_sf for visualizing these data. One thing that comes up regularly is “zooming in” on a certain region of interest, i.e. displaying a certain map detail. There are several ways to do so. Three common options are: selecting only certain areas of interest from the spatial dataset (e.g. only certain countries / continent(s) / etc.) cropping the geometries in the spatial dataset using sf_crop() restricting the display window via coord_sf() I will show the advantages and disadvantages of these options and especially focus on how to zoom in on a certain point of interest at a specific “zoom level”. We will see how to calculate the coordinates of the display window or “bounding box” around this zoom point. Loading t...

Controlling legend appearance in ggplot2 with override.aes

[This article was first published on Very statisticious on Very statisticious , and kindly contributed to R-bloggers ]. (You can report issue about the content on this page here ) Want to share your content on R-bloggers? click here if you have a blog, or here if you don't. In ggplot2 , aesthetics and their scale_*() functions change both the plot appearance and the plot legend appearance simultaneously. The override.aes argument in guide_legend() allows the user to change only the legend appearance without affecting the rest of the plot. This is useful for making the legend more readable or for creating certain types of combined legends. In this post I’ll first introduce override.aes with a basic example and then go through three additional plotting scenarios to how other instances where override.aes comes in handy. Table of Contents R packages Introducing override.aes Adding a guides() layer Using the guide argument in scale_*() Changing multiple aesthetic par...