Patients may request confidential communications through an unsecured channel, but choice comes with risk. Learn how informed consent, HIPAA privacy rights, and stronger safeguards for electronic health information shape a provider’s response—especially when convenience and security pull in different directions.

Multiple Choice

Regarding requests to send records via unsecured transmission, which statement aligns with the described standard?

Patients have a right to confidential communications and may request to receive or transmit PHI through alternative, including unsecured, means. The provider should accommodate reasonable requests when the patient understands the risks of unencrypted transmission and provides any necessary consent. However, this approach conflicts with higher standards for safeguarding electronic PHI, since the Security Rule emphasizes protecting data during transmission. So the client may request unsecured transmission, but doing so goes against the stronger security expectations, and compliance depends on the patient’s informed consent rather than an automatic approval.

Unsecured Record Transmission in TeleMental Health: Respecting Choice While Protecting Privacy

Telehealth can make care more accessible, but it also changes how health information moves. A record that once traveled in a sealed envelope may now pass through email, a patient portal, or another digital channel. That convenience comes with a question for providers: what happens when a client asks for records to be sent through a method that isn’t encrypted?

The answer isn’t simply “yes” or “no.” Clients have privacy rights, and they may ask to receive or transmit protected health information (PHI) through alternative means, including an unsecured channel. At the same time, telehealth professionals have a duty to protect sensitive data. The challenge is to respect a client’s informed choice without treating security as an afterthought.

The client’s right to request another channel

Under HIPAA, people may ask a covered provider to communicate with them through alternative means or at an alternative location. For example, a client might ask a clinic to send information to a personal email address rather than leave a voicemail at home. They might also request a particular way to receive records.

Providers generally must accommodate reasonable requests for confidential communications. A client does not have to disclose why they’re making the request. The reason may be personal, practical, or tied to safety: perhaps a shared mailbox isn’t private, or a client has limited access to a secure portal. What matters is that the request is reasonable and can be handled without undue burden.

This right does not mean every requested method is equally safe. Sending PHI through an unencrypted email account, for instance, may expose it to risks that don’t arise in a secure portal. The message could be misdirected, accessed through a compromised account, or stored in a way the provider can’t control. A client can still ask for that channel, but the provider should make sure the risks are understood before proceeding.

A choice can be allowed and still carry risk

It helps to separate two ideas that can sound contradictory: a client may request an unsecured method, and the provider should still favor strong safeguards.

HIPAA does not ban every form of unsecured electronic communication in every circumstance. The Security Rule calls for reasonable and appropriate protections for electronic PHI, including safeguards for information sent over networks. Encryption is an important tool, but HIPAA’s technical safeguard rules are flexible rather than a blanket instruction that every transmission must use encryption in every case.

That flexibility is not a green light to ignore security. Providers need to assess risks and use safeguards that fit their setting. In teleMental Health, that may include secure portals, encrypted email, access controls, device protections, and clear procedures for handling records. These steps reduce exposure before a client ever asks for a different method.

When a client specifically requests an unsecured channel, the provider should explain the practical risks in plain language. “This email isn’t encrypted” is more useful when paired with what that means: someone with access to the account or the transmission path may be able to view the information. The explanation should be calm and specific, not alarming. The goal is informed choice, not pressure.

If the client understands the risks and still wants that method, the provider may be able to honor the request, subject to applicable law, organizational policy, and the circumstances of the disclosure. The request should not be treated as automatic approval of any transmission under any conditions. Identity, destination, and the amount of information being sent still matter.

What informed consent should look like

Consent is more than a quick “sure” at the end of a conversation. A good process gives the client enough information to make a real decision and creates a clear record of that decision.

A provider might confirm:

  • Which channel the client wants to use.

  • The address, number, or account where the information will go.

  • That the channel may not be encrypted or fully secure.

  • What type of information will be sent.

  • Whether the client still wants to proceed after hearing about the risks.

The wording should be easy to understand. Technical terms can be useful in policy documents, but they aren’t always helpful in a conversation with a client. A simple explanation is often better: “This message may be visible to someone who can access your email account, and we can’t control every system it passes through.”

Documentation matters, too. A brief note that records the client’s request, the explanation provided, and the client’s decision can help show that the provider handled the matter thoughtfully. It also gives the care team a reliable reference if the client later asks why a record was sent in a particular way.

Reasonable safeguards still apply

A client’s choice of an unsecured method does not erase a provider’s responsibilities. The provider should still take reasonable steps to reduce avoidable risks. For example, they can double-check the destination address, send only the information needed for the request, and avoid including unnecessary sensitive details in a message’s subject line.

The same care applies to devices and staff workflows. A secure portal won’t help much if staff leave records open on a shared computer or send them to an address copied incorrectly. Small checks can prevent large headaches. It’s a bit like confirming a mailing address before sending an important document—ordinary, perhaps, but essential.

Providers should also consider whether a different option would meet the client’s needs with less risk. Perhaps the client can download the record from a portal, receive it by postal mail, or use another confidential communication method. These alternatives should be offered, not used to dismiss a reasonable request. The client’s preferences deserve genuine consideration.

Telehealth adds a few extra wrinkles

In teleMental Health, privacy concerns reach beyond the record itself. A client may join a session from a shared home, use a family device, or rely on an email account that another person can access. Their request for a particular communication channel may reflect a real need for confidentiality, even if the channel seems less secure from the provider’s point of view.

That’s why a blanket response can miss the point. Automatically refusing every request for unsecured transmission may disregard the client’s right to request confidential communications. Automatically agreeing to every request, on the other hand, overlooks the provider’s duty to use reasonable safeguards. A thoughtful response sits between those extremes: listen, explain, confirm the client’s choice, and follow applicable policy.

Providers should also distinguish a client’s request from routine office convenience. Sending records through an unsecured channel because it is faster is not the same as doing so because the client asked for it after hearing the risks. The reason for the choice, the information involved, and the safeguards used all shape the decision.

A balanced approach protects trust

Privacy and access aren’t opposing goals. A client may need a particular communication method to receive care information safely in their own circumstances, while the provider must keep data protection at the center of telehealth services. Respecting one doesn’t require abandoning the other.

A sound response to an unsecured-transmission request starts with the client’s rights, then adds clear information about risk and sensible safeguards. The provider should avoid promising that an unsecured channel is fully safe, but also avoid claiming that HIPAA prohibits it in every situation. Where the client understands the limits and the request can reasonably be accommodated, the provider can make a careful, documented decision.

In teleMental Health, trust is built through these small moments. A clear explanation, a respectful conversation, and a careful check of the destination can turn a risky request into an informed one. The technology may change, but the core task remains familiar: protect confidentiality while treating the client as an active partner in decisions about their information.