How Do I Comply with HIPAA when Emailing PHI?

How Do I Comply with HIPAA when Emailing PHI?

By Elizabeth McElhiney, MHA, CHPS, CPHIMS, CRIS
Director of Compliance and Government Affairs
Verisma
July 12, 2024

Combine the words HIPAA, protected health information (PHI) and email, and you’ve just found a topic that’ll leave many healthcare professionals uneasy. Nevertheless, email is frequently used for sharing PHI with patients and their caregivers. All healthcare organizations should develop policies and procedures to comply with HIPAA while delivering PHI via email.

It’s not as simple as citing a policy forbids emailing PHI. One of the key initiatives of the Office of Civil Rights (OCR) is to increase access for patients to their health information, including unencrypted email. So, while it may seem counterintuitive to email patients medical records and health information, providers and healthcare organizations may need to do exactly that to meet a patient’s requested format.

Why use email to send PHI?

As our world becomes more reliant on technology to communicate and manage our daily lives, the healthcare industry has seen their own technological revolution with electronic health records (EHR), e-prescribing, patient portals, wearable tech, and many other advancements. With email a main means of communication, it’s only natural patients would like to communicate in a way they’re familiar with.

Many healthcare organizations have their own email systems needed to function for business. But when it comes to communicating with patients, practices are often confused over what they can, and cannot, do. The U.S. Department of Health and Human Services (HHS) provides guidance on emails used in healthcare. They note the HIPAA Privacy and Security Rules don’t prohibit the use of email but do require proper policies and procedures to protect PHI. Guidance on a patient’s right to access their PHI underscored the ability for patients to request this information via email. And they consider email to be readily producible by nearly all covered entities, with exceptions if a file is too large to transmit via email.

While practices should defer to utilizing secure, encrypted email while transmitting PHI, the guidance from the OCR indicates if a patient wants their PHI to be delivered via unencrypted email, covered entities and business associates must comply.

How can I send an unencrypted email with PHI? Isn’t that against HIPAA?

Sending PHI via unencrypted email doesn’t violate HIPAA, but covered entities and business associates must take reasonable steps to ensure patients understand and acknowledge the risk of unsecured email transmission. The OCR provided this guidance because they want patients to easily receive their PHI in accordance with their right to access PHI.

In an interview with Report on Patient Privacy, Deven McGraw, Deputy Director of the HHS OCR, said, “We are trying to make it as easy as possible [for people] to exercise their HIPAA rights in a way that works best for them. But it is not meant to be a sort of blanket, ‘Get Out of Jail Free’ card on security.”

Meaning, if a patient requests their records be delivered via unencrypted email, the covered entity or business associate must comply with the request after assurance from the patient they understand the risk of unsecured email. Denying a patient their access request be sent via unsecured email could mean an OCR complaint.

But isn’t email a breach waiting to happen?

Email can be difficult to protect at rest and in transit. It’s important healthcare organizations follow industry best practices for utilizing email, which typically include dual authentication and encryption, to prevent a PHI breach.

Unsecure email is much more difficult to protect. If a patient acknowledges, verbally or in writing, the risks of their PHI being sent via unsecure or unencrypted means, the patient accepts the risk of potential disclosures occurring in transit, or upon arrival, to the intended email address.

Considerations for delivering PHI via email

With email a frequent transmission method for PHI, healthcare practices need to consider the risks and best practices for utilizing email in their own organization.

Some initial suggestions for appropriately transmitting email include:

  • Servers containing email should be encrypted.
  • When communicating PHI externally, utilize encrypted email technology.
  • Ensure all staff are trained on email best practices.
  • Develop a policy and procedure for working with patients when the PHI file size is too large to be delivered via email.
  • Develop a policy and procedure to alert patients to the risks of delivering PHI via unencrypted or unsecure email.
  • Create your duty to warn statement and receive written or verbal confirmation.
  • If the email address is received verbally, confirm the address using the NATO Phonetic Alphabet.

Rely on a partner to navigate the changing regulatory landscape

With the rapid evolution of technology, it can be difficult to keep up with the regulatory landscape of what is, and isn’t, allowed – all while trying to avoid an unauthorized disclosure (UAD). Luckily, covered entities can work with business associate partners like Verisma to handle PHI disclosures – transferring the work burden and duty to warn.

And, while many patients can access data via portals, Verisma Request App® (VRA) opens up secure electronic delivery to third-party requestors, such as commercial health plans and attorneys – offering the same record-ordering convenience enjoyed by patients – and avoids the risks associated with email all together.

Does emailing PHI (encrypted or unencrypted) seem like more work than it’s worth? Our healthcare data experts are extensively trained in PHI delivery best practices including utilizing encrypted and unencrypted email, as well as responding to complicated right to access requests. We’ll take on these tricky situations for you. Find out how we relieve the burden of PHI email exchange by requesting a demo today.

Verisma Compliance Resources

Get the latest updates written and curated by HIM compliance experts and subscribe to our weekly newsletter.
Best Practices for Managing Mental/Behavioral Health Records/Psychotherapy Notes

Best Practices for Managing Mental/Behavioral Health Records/Psychotherapy Notes

By Elizabeth McElhiney, MHA, CHPS, CPHIMS, CRIS
Director of Compliance and Government Affairs
Verisma
June 20, 2024

Under Health Insurance Portability and Accountability Act (HIPAA) Privacy Law, there’s a distinction between mental health records, part of a patient’s overall medical record, and psychotherapy notes, which are provided special consideration to be separate pieces of information. Healthcare professionals shouldn’t consider extra privacy protections afforded to psychotherapy notes as applicable to general mental health records, or the overall care and treatment of a patient could be impacted. We discuss how clients wish to label mental/behavioral records within their patients’ medical records. As with any HIPAA regulations, circumstances occur in which state laws supersede regulations set by federal law, so it is imperative health organizations understand their state laws. Our documentation and process adjusts to state when extra patient authorization is required for such information to be released. This information isn’t meant to be legal counsel, rather it’s a general guide to understanding the intricacies of HIPAA regulation.

Mental Health Records vs. Psychotherapy Notes

The U.S. Department of Health and Human Services (HHS) distinguishes between mental (which includes behavioral) health records compared with psychotherapy notes. HHS states, “Psychotherapy notes are treated differently from other mental health information both because they contain particularly sensitive information and because they are the personal notes of the therapist that typically are not required or useful for treatment, payment or health care operations purposes other than by the mental health professional who created the notes.”

HHS uses the HIPAA Privacy Rule to define psychotherapy notes “as notes recorded by a healthcare provider who is a mental health professional documenting or analyzing the contents of a conversation during a private counseling session or a group, joint or family counseling session and that are separate from the rest of the patient’s medical record.”

Mental health records, on the other hand, are considered to fall within general protected health information (PHI) and be part of the general health record. HHS outlines psychotherapy notes aren’t inclusive of medical prescriptions, session start and stop times, frequency of treatment, clinical tests, summaries of diagnosis, symptoms, prognosis, etc. These pieces of information are considered mental health records, thus part of the patient’s general medical record. It’s important to always consider individual states may have their own definition of mental or behavioral health. In these cases, you’ll want to know and understand any differences between state and federal definitions so you can determine if you need to apply additional privacy protections. As patients move between different healthcare providers, its critical health information be appropriately documented and shared for proper continuity of care of the patient. Diagnosis and medication information is imperative for any healthcare provider to properly and confidently provide care to a patient. Because mental health records and psychotherapy notes differ, HHS outlines they’ve different protections under the Privacy Rule: “Generally, the Privacy Rule applies uniformly to all PHI, without regard to the type of information. One exception to this general rule is for psychotherapy notes, which receive special protections.” Records related to mental health don’t receive these extra protections because they’re considered part of the general record. This distinction means thought and care should be put into how this information is stored and possibly shared, as most are not privy to the sensitive information contained in psychotherapy notes.

As organizations continue to implement protocols for managing medical records, they must consider how mental health records and psychotherapy notes differ in content and storage. Best practices state mental health records be stored within the patient’s general medical chart, while psychotherapy notes should be stored separately from the patient’s general medical record. If an organization wishes to store the psychotherapy notes within their electronic health record (EHR) system, special naming and filing standards should be documented and communicated. Staff members should be trained on the differences between psychotherapy notes and mental health records. Mental health records should be coded as such and included in the patient’s general electronic record. The psychotherapy notes should then receive an individualized designation which communicates the relevant patient while not being added to that patient’s general medical record.

Professional Discretion and Extenuating Circumstances

The term “professional discretion” is used throughout medical records regulatory law, pertaining to the rules surrounding psychotherapy notes. Healthcare providers maintain professional discretion on when and what information should, or shouldn’t, be released. Circumstances pertaining to family access to psychotherapy notes, law enforcement inquiries, and third-party requestors are especially dependent on this caveat to determine compliance.

The importance of professional discretion serves to indicate how critical it is organizations maintain a well-articulated system for the storage of psychotherapy notes. An example of professional discretion playing a part in the release of psychotherapy notes would be if a provider felt there was an imminent threat of a patient causing harm to themselves or others. A provider must use their professional discretion to determine if the situation meets the requirements for disclosure of psychotherapy notes to law enforcement for the purpose of prevention.

Patient Access to Psychotherapy Notes

As dictated by the HIPAA “Right to Access” provision, a patient must be allowed to gain access to their current medical records as defined by an organization’s “designated record set” in a timely manner, without undue burden. If the maintenance and contents of mental health professional’s notes fall within the definition of psychotherapy notes as defined in the Privacy Rule, they aren’t to be considered part of an organization’s designated record set, or the patient’s medical record. Since psychotherapy notes fall under this Privacy Rule exception, covered entities aren’t obligated to release a patient’s psychotherapy notes pertaining to their treatment. It’s of great importance the psychotherapy notes are maintained separately, or clearly noted as separate, from the patient’s medical record. If this step isn’t taken, the Privacy Rule exception doesn’t apply and a records custodian must include the notes when releasing information.

Third-party Requestors

If a third-party requestor is seeking to obtain medical records from the healthcare organization, the records custodian should follow normal protocol seeking required authorization. If psychotherapy notes relating to the requested records are also present at the organization, it must seek separate patient authorization – which states psychotherapy notes may be included – before releasing the notes to the third-party requestor. This is of paramount importance as inappropriate release of psychotherapy notes is noncompliant and may have undesirable effects for the related patient.

Verisma Compliance Resources

Get the latest updates written and curated by HIM compliance experts and subscribe to our weekly newsletter.
Interoperability Challenges in the Pursuit of Patient Access

Interoperability Challenges in the Pursuit of Patient Access

By Elizabeth McElhiney, MHA, CHPS, CPHIMS, CRIS Director of Compliance and Government Affairs
Verisma
May 17, 2024

I recently had the honor to moderate a panel with really engaging, super bright, and deeply invested panelists who are looking at patient access from three perspectives:

  • Health Information Management (HIM)
  • Patient
  • Patient Advocate

Key Challenges

We discussed how many places HIM professionals need to go to assemble a patient’s complete medical record within one organization. Chances are high that it’s not one electronic medical record (EMR). Often, hospital records and outpatient clinical records are in multiple systems. There’s also paper, microfiche, independent labs, imaging, and coordination with different providers and pharmacies to tackle. From a patient and patient advocate perspective, navigating the U.S. healthcare system to access protected health information (PHI) is also far from easy. In some states, consumers need more than one consent to release information. There are numerous usernames and passwords to remember when trying to access portals. These pose challenges even before acknowledging language and literacy barriers. Anna McCollister, member of the Sequoia Project’s Board of Directors and advisory committee member for the Health IT Advisory Committee (HITAC) at the Office of the National Coordinator for Health Information Technology (ONC), perfectly illustrates the complexity of living with complex, chronic disease. She’s asking health technology companies to think beyond what they’re in charge of. For consumers to feel less of a burden, health tech needs to understand their focus area is part of a much larger picture. Anna’s requesting a seamless platform, so consumers can see all their data in one place – saving valuable time and effort. This tool is even more important for patients who aren’t feeling 100 percent, and don’t have excess energy to give.

Managing PHI

Vong Miphouvieng, Vice President of HIM and Clinical Documentation Integrity at a large health system in Texas, agrees EMRs have made it somewhat easier to access data, but not everyone wants to use a patient portal. They partnered with Verisma to simplify access, creating a consumer-focused health system. With interoperability, patient information can now be obtained from one location. No matter where consumers receive care, there’s one phone number, one website, one email, one place they get all their health information. The provider also extended call-center hours, making it easier to access information in myriad ways via portal, snail mail, or walk-in – providing various methods to fit consumer needs.

Veronica Richardson, Vice President of Integrity at Preferred Family Healthcare (PFH), details challenges their transient clients have with mobility. Some don’t have smartphones to request information, and staff can’t always contact them either. They’ve also centralized the release of information (ROI) process so there’s one Dropbox. No matter where patients receive care, they can request records from PFH.

Government’s Role

Data rights need to be more visible when consumers are trying to access information in their provider’s office or in a patient portal. Required alerts describing patient rights, what’s available to be accessed in a portal, and who to contact if consumers can’t access data in a timely manner, need to be front-and-center – along with government contact information to report violations.

Bottom Line

We’ve been talking about interoperability for years, but there’s more work to be done to achieve seamless information sharing between healthcare providers and from one EMR to the next. The process to download, print, mail, and PDF data for integration into the receiving provider’s EMR is still daunting. Consumers are rightfully demanding faster turnaround times, and interoperability is the key for better patient access. The good news? We all know what’s needed. Together, we can define the remaining barriers, outline what’s keeping us from knocking them down, and define how we can work with the healthcare ecosystem and policy makers to get us to true interoperability.

Verisma Compliance Resources

Get the latest updates written and curated by HIM compliance experts and subscribe to our weekly newsletter.
Can TEFCA Get Us to True Interoperability?

Can TEFCA Get Us to True Interoperability?

By Connie Renda, MA, RHIA, CHDA
Vice President of Industry Advocacy and Business Development

Verisma

April 18, 2024

By January 2026, all certified electronic health record (EHR) users must comply and exchange information per the Trusted Exchange Framework Common Agreement (TEFCA). My colleague, Roberta Baranda, past president of the California Health Information Association (CHIA) and health information management (HIM) director at Valley Children’s Hospital spoke about TEFCA several years ago. I looked it up and thought, another government regulation to enforce what we’ve all been needing, wanting and working towards for many years, interoperability. If all of us are on the same page about interoperability, why is it so difficult to achieve?

An unprecedented amount of data is being collected across a diversity of sectors, which, if harnessed, could transform public health decision-making. Yet significant challenges stand in the way of such a vision, including the need to establish standards of data sharing and interoperability, the need for innovation in both methodological approaches and workforce models, and the need for data stewardship and governance models to ensure the protection and integrity of the public health data system. (Martin, et. al., 2022)

Why’s the Government Weighing in on Interoperability? Better Patient Outcomes

All healthcare professionals agree there’s a need for a viable, reliable method, and framework for health information to be exchanged. Most everything we do in health information ultimately results in trusted info being exchanged. When we analyze charts, the purpose is to ensure completeness of the record so the recipient will have the patient’s full story. When we code a record, the data are captured for research recipients and the payers to receive information pertaining to cost of care. Document imaging specialists ensure paper records are incorporated into the electronic version of the chart to provide continuity of care. Of course, clinicians feverishly document care of the patient knowing information will result in better outcomes or prevention of further illness.

Federal efforts may address some impediments to electronic health information exchange. Specifically, the Trusted Exchange Framework and Common Agreement being implemented by the Office of the National Coordinator for Health Information Technology (ONC)—which aims to describe a common set of nonbinding principles to help facilitate exchange among health information networks—may mitigate costs providers face by providing a simpler approach to connecting with other providers. However, stakeholders noted that participation in this effort is voluntary and does not address issues like information technology staffing shortages and gaps in broadband access that pose particular challenges to electronic exchange for small and rural providers. (Gordon, 2023)

Health Information Access Challenges

The government mandate speaks to the importance of access to health information. The vision of our national organization, American Health Information Management Association (AHIMA) is “A world where trusted information transforms health and healthcare by connecting people, systems, and ideas.” Can TEFCA be the conduit for us to get there? The National Institutes of Health (NIH) addresses implications and solutions for interoperability challenges, including a copious amount of health data with outdated workforce models, and numerous resource constraints.

Data science and technology companies continue to be on the cutting edge of information exchange. As such, the data science and technology sector has the expertise to help mitigate and solve challenges within legacy data systems… departments working within a resource-constrained environment and a workforce whose expertise is focused on health, rather than technology. In addition, to increase accuracy and efficiency, there is a need to develop processes for timely data sharing that require minimal human effort. (Martin et. al, 2022)

TEFCA Guidance Resources: ONC and AHIMA

During the February Verisma Academy webinar, Elisabeth Myers, Deputy Director, Office of Policy, ONC, presented an on-demand course with solid, actionable information that’s really worth checking out: Exploring HTI-1, TEFCA and AI in Healthcare – Where Are We in 2024?

Separately, AHIMA provided a two-page guideline on what TEFCA means for provider organizations, underlining the idea that when orgs exchange information through Qualified Health Information Networks (QHINs), “there’s increased focus on how to expand use cases and make a broader impact.” In terms of adaptability, “TEFCA will be able to grow and adapt as needed to ensure it serves user needs,” including “a three-year roadmap for the TEFCA to begin utilizing the Fast Healthcare Interoperability Resource (FHIR).”

Will TEFCA Help Solve Interoperability Challenges?

At the very least, TEFCA has us discussing this important topic and moving in a unified direction as an industry. Providers who struggle with resources to stay on top of what these regulations mean, or how to operationalize them, can lean on external partners who’ve expertise in this space – ultimately benefiting everyone.

I’m proud to work for a company fostering interoperability with technology-rich tools mitigating human error. We help provider partners manage the deluge of incoming records, care coordination processes, and sharing information — with privacy and security at the forefront. We’re also passionate about becoming your trusted partner.

References:

www.ahima.org; What Does the TEFCA Mean for Your Organization?
https://ahima.org/media/zw3hx0c3/tefca_summary_fin.pdf

Martin LT, Nelson C, Yeung D, Acosta JD, Qureshi N, Blagg T, Chandra A (2022) The issues of interoperability and data connectedness for public health. Big Data 10:S1, 19–24, DOI: 10.1089/big.2022.0207.

Gordon, L. (2023) Electronic Health Information Exchange: Use Has Increased, but Is Lower for Small and Rural Providers. GAO-23-105540; Published: Apr 21, 2023.
https://www.gao.gov/products/gao-23-105540.

Verisma Compliance Resources

Get the latest updates written and curated by HIM compliance experts and subscribe to our weekly newsletter.
Key Differences Among Healthcare Data Archiving Solutions

Key Differences Among Healthcare Data Archiving Solutions

By Olah, a Verisma Company

March 12, 2024

Here’s the good news: When it comes to data archiving solutions, you’ve got options. The bad news: You’ve got options.

It’s nice to have choices when deciding on your ideal partner, but that also means you’ll need to thoroughly research each solution to find the best fit. On the surface, all may look equally viable in terms of archiving records effectively. However, every healthcare organization embarking on the journey of application retirement for the first time has different needs and priorities. The same is true for organizations that need to replace their current data archiving solution or vendor. The top three reasons for making the switch, according to a recent KLAS report, are missing data, missed timelines, and lack of integration with the electronic medical record (EMR).

All of this means you have your homework cut out for you, including understanding what common myths about archiving records are untrue, to ensure you make the best purchase decision possible. The wrong choice can be costly in terms of lost productivity, compliance risk, patient safety, and more.

Structured Data Archiving Options: Understanding the Differences

Generally speaking, healthcare data archiving solutions differ significantly when it comes to the following categories:

  • Methodology for archiving records
  • Speed and efficiency
  • Cost structure
  • Compliance and security
  • Customization
  • Integration capabilities
  • User experience

In OIah’s experience, most healthcare organizations consider “compliance and security” to be the most important distinguishing factor, with speed and efficiency a close second. The same KLAS report found that price, sales experience, and functionality drive purchasing decisions for all providers, whether they’re replacing a data archiving solution or choosing one for the first time. You already know the top priorities at your own facility. Thoroughly vetting each structured data archiving option is paramount because it prevents you from wasting time, money, and resources on a solution that doesn’t ultimately deliver the return on investment you seek.

With that said, healthcare organizations focusing on application retirement typically want to make the process as expeditious as possible. They need to move legacy data quickly and efficiently to contain costs, mitigate risk, and promote business continuity. That’s why proactive planning is so critical.

Questions to Consider When Weighing Application Retirement Solutions

Preparing questions in advance helps you make the most of your conversations with vendors and understand the intricacies of the differences between data archiving solutions designed specifically for healthcare settings. We’ve done some of that work for you. Use the list of 12 questions below as a starting point and add additional queries you feel are relevant to your organization’s unique needs and priorities.

1. What methodology do you use for archiving records?

While some data archiving solutions use extract, transform, and load (ETL) to migrate a portion of legacy data into new systems, others use a quick and simple “lift and shift” methodology to maintain all data from legacy systems. This is an important distinction you’ll want to clarify.

2. How do you store archived records?

Some offerings from vendors store archived records in silos. Users must click into multiple silos to access records for a single patient. Others store archived records in one patient-centric location that includes all archived data for each individual patient. This means multiple clicks aren’t necessary, making the user experience much more positive. Again, an important question to ask.

3. What is the speed and efficiency of the data archiving solution?

ETL solutions can be slower because they involve data conversion and validation. Non-ETL solutions rapidly archive large volumes of legacy data, making them much faster. This is an important consideration in terms of user productivity and patient safety.

4. What is your cost structure for archiving records?

It’s best to start exploring financial considerations upfront. Some vendors may have hidden costs associated with the number of patient records archived or the size of the legacy system. Others offer a more straightforward pricing model so you know how much the entire application retirement project will cost.

5. How do you ensure compliance and security?

Some vendors stay abreast of new and emerging regulatory requirements while others lag behind. A preferred vendor, for example, is likely aware of the potential for a machine-readable-code requirement for PHI (personal health information) holding systems, which would increase interoperability by ensuring that data’s produced in a more easily-read format. Also ask the vendor to articulate specifically what it does to promote HIPAA compliance and cybersecurity, or you may be placing patient privacy and data security at serious risk.

6. How well does the data archiving solution integrate with existing systems?

Some data archiving solutions integrate seamlessly with existing systems, while others may require additional effort for which your organization may not have available time and resources. For example, at a minimum, you’ll probably want the legacy data deeply integrated with your upcoming EMR and admission, discharge, transfer feed so users can see that data as easily as possible. Be sure to inquire whether the vendor supports the FHIR communication standard, a next-generation interoperability standard designed to enable the efficient exchange of clinical and administrative health data.

7. Can we customize the solution?

Some data archiving solutions may offer more options for customization or be nimbler than others when it comes to implementing enhancements. If this is important to your organization, be sure to ask for examples.

8. How easy will it be to access, use, and even purge archived data now and in the future?

Focus on data representation and manipulation capabilities your users need. For example, do they need to search and filter data based on multiple criteria? Do they commonly ask for the ability to save filters for repeated use? Does the system automatically identify data records to purge based on a variety of factors? Can you implement exceptions? Is there a detailed audit log of all activities?

9. What level of support do you provide?

Services are equally as important as software to the success of your data archiving project. Be sure to inquire about ongoing support for data retrieval, staff education, data lifecycle management, performance monitoring and optimization, disaster recovery planning, and scalability. Also inquire about updates such as system upgrades and potential data security improvements.

10. How do you ensure data integrity?

How likely is it that legacy data will be corrupted or lost during the application retirement process? This is an important consideration from a legal perspective, as organizations could be held liable if important legacy patient data is missing.

11. What user training do you provide?

Ideally, the healthcare data archiving solution requires minimal user training. If training is necessary, how does the vendor provide ongoing assistance so everyone can leverage the system effectively and efficiently?

12. What future costs can we anticipate?

With some healthcare data archiving vendors, the introductory price you receive isn’t the one you have in the long term. Ensure prospective vendors document their current and future rates in writing.

Choosing the Right Vendor for Archiving Records

Narrowing the options for healthcare data archiving solutions may seem daunting, but it becomes more manageable when you ask pointed questions about what the vendor does—and does not—do. Throughout this process, the answers will become crystal-clear and you’ll know exactly what you need.

See Olah™, Verisma’s simple, fast, and complete solution to archiving, in action today.

Verisma Compliance Resources

Get the latest updates written and curated by HIM compliance experts and subscribe to our weekly newsletter.

Questions to Ask Vendors When Archiving Your Healthcare Data Storage

Questions to Ask Vendors When Archiving Your Healthcare Data Storage

By Olah, a Verisma Company

March 7, 2024

When it comes to choosing a clinical data management vendor, making an informed decision is paramount. The most effective way to ensure that you find the right fit for your organization? Ask questions. Lots of questions. Failing to gather important information means your data archiving needs may not ultimately be met. Healthcare data storage is nuanced, and doing your homework ensures maximum return on investment (ROI) from any solution in which you invest.

Here are 14 must-ask questions during meetings with potential data archiving partners:

 

1. What is the total cost of ownership of the data archiving solution?

While data archiving can save you money, it’s critical to look at the long-term financial picture. This includes understanding the initial costs of data migration and ongoing costs related to future migrations, user training, and more.

 

Why this is important:

The “sticker price” isn’t always meaningful in the context of the big picture. For example, do data usage patterns indicate you may need additional healthcare data storage in the future? If so, how might costs increase? How long do you need to store the data, and what are the short- and long-term costs associated with that timeframe? What about training new staff? Will this result in a significant loss of productivity? The goal is to promote positive financial results and reduce costs.

 

2. Are there any hidden fees or additional costs of which the healthcare organization should be aware?

Be sure to investigate items that may be added after you initially sign with a vendor or vague line items buried in a contract. For example, do fees increase commensurate with the number of patient records archived or the size of the legacy system?

 

Why this is important:

Hidden fees can easily escalate costs and detract from the overall anticipated ROI. This is the opposite of what should happen.

 

3. How easily does the data archiving solution integrate with existing systems?

Consider clinical data systems (e.g., the electronic health record) and non-clinical data systems (e.g., the enterprise resource planning system). Can users easily access information with as few clicks as possible?

 

Why this is important:

Data integration is an important aspect of ease of use and overall user satisfaction. It will alleviate provider and staff burden during ongoing healthcare staffing shortages and improve the speed of care and patient experience.

 

4. What kinds of data can the solution archive, and are there limitations?

For example, can the solution handle images as well as other file types? Can it integrate data from any legacy application or only certain ones?

 

Why this is important:

Limitations could stand in the way of current and future strategic goals. They could also affect ROI.

 

5. How does the data archiving solution ensure compliance with HIPAA?

Clinical data management vendors can employ their own full-time privacy and security officer and/or have a compliance officer to ensure all regulatory requirements are met. Inquire about any staff who may be safeguarding your data and consider the following questions: Does the solution integrate into your enterprise audit and compliance software? Does it provide healthcare organizations with print-ready reports that demonstrate compliance, including audit logs? If so, how does the solution track data at each stage of user access?

 

Why this is important:

One of many reasons to implement a healthcare data storage solution is to reduce cybersecurity risks—not introduce new ones. Asking this question gives you a sense of whether and how the vendor prioritizes security compliance.

 

6. What security measures are in place to protect the data?

For example, what are the vendor’s encryption methods, and when is data encrypted? Is 256-bit encryption used? Does the solution permit role-based access with break-glass access protocols? What about specific healthcare data storage requirements? Is electronic protected health information and personally identifiable information stored within a Tier III (or higher) SOC 2-certified data center?

 

Why this is important:

Again, it’s about reassurance that the healthcare data storage vendor has taken all possible steps to protect your data.

 

7. Does the vendor carry sufficient cybersecurity insurance?

If so, what’s included? Every company needs to be prepared in the event of a data breach, and asking these questions can ascertain that your data archiving vendor can cover your organization and itself.

 

Why this is important:

This question demonstrates the vendor’s level of accountability and commitment to its customers’ best interests.

 

8. How easily can users access and retrieve data from the data archiving solution?

Do users have immediate access to historical records? Can they see a singular view of patients across archives?

 

Why this is important:

A poor user experience breeds frustration. If users can’t find what they need in a timely manner, this could also affect compliance with information blocking requirements in the 21st Century Cures Act.

 

9. Is the data archiving solution web-based? Or does it require an onsite server?

 

Why this is important:

Web-based solutions provide secure access from anywhere, thus improving the user experience and efficiency while simultaneously reducing the risk of data breaches.

 

10. What type of support and training is provided during and after implementation?

How easy is it for users to learn the solution? Can they learn it in minutes, or will it take hours or even days?

 

Why this is important:

Time is money. Training should be clear and concise, and the solution should be highly intuitive so users can access information when, where, and how they need it.

 

11. How long does it typically take to fully implement the data archiving solution?

The answer to this usually depends on the specific approach the clinical data management vendor takes. Solutions using an extract, transform, and load (ETL) approach can be slower because they involve data conversion and validation. Non-ETL solutions rapidly archive large volumes of legacy data, making them much faster.

 

Why this is important:

Today’s healthcare organizations don’t have time to waste. Timely access to information is paramount.

 

12. How does the clinical data management vendor maintain data integrity during migration?

For example, what data validation standards does the vendor use to ensure data retention requirements are met? Does it use a combination of automated and manual validation processes?

 

Why this is important:

If a vendor can’t articulate this clearly, it could mean their validation standards are lackluster. This poses a direct threat to information that providers use to make critical decisions. Poor data validation can create many problems and challenges related to patient safety, care quality, and more.

 

13. Are there case studies that demonstrate the successful implementation of the data archiving solution?

 

Why this is important:

Case studies—and any specific returns on investment and metrics cited therein—can be helpful in terms of comparing options and customer experiences.

 

14. Can the healthcare organization request references?

Case studies may or may not be blinded. Either way, it’s a good idea to speak with individuals who have first-hand experience with the solution. Ideally, it would be individuals working in a similar-size organization and/or with the same or similar legacy systems.

 

Why this is important:

You’ll learn things the vendor might not tell you (both good and bad). In addition, even if an organization goes on the record for a case study, it may still be worthwhile to contact them directly to get a sense of how their experience evolved over time since the case study was published.

 

A Solution to Accelerate Your Data Archiving

Taking the time to thoroughly vet clinical data management vendors helps healthcare organizations find the right solution that fits their needs. Learn more about Olah™, Verisma’s simple, fast, and complete solution to data archiving.

Verisma Compliance Resources

Get the latest updates written and curated by HIM compliance experts and subscribe to our weekly newsletter.