Start with the workflow, not the encryption label
A visit changes after hours. A supervisor needs to reach the on-call team, clarify a handoff and make sure the next person has the right information. Messaging may be convenient, but convenience alone does not establish an approved channel for electronic protected health information (ePHI).
Encryption protects content within its design boundaries. It does not prevent a message going to the wrong person, establish workforce training or determine what happens to files on a former employee’s device. HHS guidance and HIPAA’s technical safeguards point agencies toward evaluating access, authentication, activity review, integrity and transmission security as part of a broader risk analysis.
The agreement matters as much as the feature list
A Business Associate Agreement (BAA) is required when a vendor is acting as a business associate. HHS explains that a cloud provider maintaining ePHI can be a business associate even when the information is encrypted and the provider lacks the decryption key. The narrow conduit exception should not be assumed for a platform with stored messages, backups or downstream processing.
Agencies should obtain the applicable agreement and confirm covered services, subprocessors and responsibilities before approving a messaging workflow. An agreement alone does not establish compliance: configuration, policies, staff behavior and ongoing risk management also matter.
Evaluate access, audit evidence and record handling
Check the safeguards relevant to the proposed workflow: authorized access, user authentication, audit controls, integrity and transmission security. Review how messages, attachments and recordings reach the designated clinical record and how the organization handles retention and deletion. Marketing labels are not independent evidence that controls work.
For staff accountability, ask who can invite users, change roles and revoke access. Request a demonstration of available audit events and exports. For signing, test signer identity, timestamps, document integrity and export to the designated record. Confirm current plan availability and configuration rather than assuming every advertised module is included.
A fictional after-hours handoff
This example uses no patient data and is not a customer case study, product screenshot or evidence of an implemented integration. An authorized supervisor shares a fictional visit change with the correct restricted staff group. The on-call team clarifies the handoff through an approved conversation, then records material care decisions in the designated clinical record.
During a demonstration, follow that scenario beyond the message: change a team member’s role, revoke access and inspect the available audit evidence. Ask what happens to active sessions and local copies. This turns a feature walkthrough into a useful evaluation of the agency’s operating responsibilities.
Emergency communication still needs an agency-owned plan
A severe weather alert may call for a staff-wide operational broadcast, with patient-specific coordination kept in a restricted approved channel. Evaluate how the organization’s approved channels support that distinction.
Messaging tools do not replace the agency’s emergency preparedness obligations. CMS treats the communication plan as one element for applicable providers; the agency remains responsible for its plan, policies, procedures, training and testing.
Keep AI assistance inside an approved data flow
If a messaging workflow includes AI dictation, transcription or summaries, assess contractual coverage and safeguards for the selected feature and every processor handling ePHI before use. Do not assume the messaging service’s agreement covers a separate AI provider.
Ask where recordings, prompts and outputs are stored, how long they are retained and whether any data can be used to improve models. Keep ePHI out of an AI feature until the organization approves its data flow. Staff should review generated material before using it for care or adding it to the clinical record.
Five questions for a healthcare messaging assessment
The value for an agency is a clearer, more accountable communication process—not a promise of compliance or clinical outcomes. Start with one realistic fictional workflow and agree on responsibilities before going live.
- Which modules and downstream processors does our BAA cover?
- Can we test enrollment, role changes and access revocation with simulated data?
- Which audit events can administrators review or export?
- How are chat, files, signatures and recordings retained, deleted and recovered?
- Which decisions belong in our clinical record, and who reviews AI-generated drafts?
Source basis and limitations
This vendor-neutral article references HHS cloud-computing guidance, the cited 2024 edition of HIPAA technical safeguards and CMS emergency preparedness guidance. Check current requirements and applicability with qualified advisers; the cited regulatory edition is dated, not a claim that rules cannot change. This is education, not a security assessment, product endorsement, compliance certification, or legal or clinical advice.
- HHS: HIPAA and cloud computing
Primary guidance on business associates and cloud services handling ePHI; assess applicability to the proposed workflow.
- 45 CFR § 164.312 — technical safeguards (2024 edition)
Dated official regulatory text covering access, audit controls, integrity, authentication and transmission security; verify current requirements before implementation.
- CMS: core emergency preparedness rule elements
Primary guidance on emergency planning, communication, policies, training and testing for applicable providers.
