GooScript · Agency questions

    HIPAA secure messaging FAQ for agencies

    Answers about BAAs, encryption, audit logs, and everyday care-team messaging, grounded in HHS guidance and GooScript’s published policies.

    Educational information, not legal advice, a certification, or a guarantee of compliance. Your privacy or security officer and legal adviser should assess your agency’s specific workflow. Source policies and your applicable agreements remain authoritative.

    Business Associate Agreements

    When does an agency need a BAA with a messaging vendor?

    Where a vendor creates, receives, maintains, or transmits PHI on behalf of your agency as a business associate, a written business associate agreement is generally required before that activity begins. Confirm which service, storage, integrations, and subcontractors it covers. Not every recipient is a business associate: for example, HIPAA excludes provider-to-provider disclosures for treatment from the business associate requirements.

    HHS: Business associate questions

    Does signing a BAA make our agency HIPAA compliant?

    No. A BAA sets contractual duties; it is not a certification or a substitute for risk analysis, appropriate safeguards, staff training, and compliant use. The agency still needs to manage its workforce, permissions, devices, and communication policies.

    HHS: Security Rule summary

    Where can we review GooScript’s BAA?

    GooScript’s published BAA describes permitted PHI uses, safeguards, subcontractor obligations, incident reporting, and return or destruction of data. Review the agreement that applies to your organization before sending patient information. Reading a public FAQ or BAA is not evidence that your organization has executed an agreement.

    Review GooScript’s Business Associate Agreement

    Encryption & data protection

    Does HIPAA require encryption or end-to-end encryption?

    Under the currently effective Security Rule described by HHS, encryption is an addressable implementation specification—not something to ignore. Assess whether it is reasonable and appropriate, implement it when it is, and document any justified alternative or rationale where the standard can otherwise be met. “End-to-end encrypted” alone is not a universal HIPAA compliance test. Evaluate transmission, storage, backups, notifications, and key management.

    HHS: Encryption requirements

    Is an encrypted consumer messaging app enough for patient information?

    No. Encryption alone does not establish an appropriate healthcare workflow. Evaluate individual accounts, authorized recipients, access revocation, audit controls, personal backups, device exposure, and applicable service agreements. Even a cloud provider that stores only encrypted ePHI and cannot decrypt it can be a business associate. Do not assume an app’s encryption claim replaces a BAA or other safeguards.

    HHS: Encrypted cloud storage and business associates

    What does GooScript’s published policy say about encryption?

    GooScript’s BAA calls for encryption of ePHI in transit and at rest, access controls, authentication, audit logging, and monitoring. These are published contractual obligations, not an independent security audit. Ask for service-specific evidence and confirm the configuration and data flow for your intended use, including AI assistance, before introducing PHI.

    Review GooScript safeguards & data handling

    Audit logs & accountability

    What does HIPAA require for audit controls?

    The Security Rule requires mechanisms to record and examine activity in systems containing or using ePHI. For messaging, evaluate how activity is associated with individual users, how records are protected, and how your agency reviews them. A message’s read receipt alone is not a complete audit-control program.

    HHS: Security Rule summary

    Which audit-log details should we request from a vendor?

    Request sample records and a demonstration using synthetic patient data. Ask which sign-in, access, message, attachment, permission-change, and administrative events are actually recorded; which users can review them; and how timestamps, integrity, exports, and incident investigations work. This is an evaluation checklist, not a claim that HIPAA mandates every listed field or that GooScript records them all.

    Read the agency vendor-evaluation checklist

    How long should we keep messages and audit logs?

    Set a documented retention policy for the types of records involved, applicable laws, clinical-record responsibilities, contracts, and investigation needs. Do not assume a documentation-retention requirement is a universal deadline for every chat or log. Confirm the purchased service’s retention and export behavior, legal-hold process, and data return or deletion at termination.

    Review data-handling and retention responsibilities

    Messaging rules for care teams

    Does HIPAA ban SMS, WhatsApp, Viber, Telegram, or Signal by name?

    HIPAA does not approve or ban every app by name. The question is whether your agency’s actual use protects ePHI and satisfies applicable obligations. Consumer accounts may leave gaps in organizational control, backups, offboarding, audit evidence, or BAA coverage. HHS allows adequately protected ePHI over open networks; that is not blanket permission to send clinical details through any app.

    HHS: Sending ePHI over open networks

    Can staff message patient information during handoffs?

    Use your agency’s approved channel and verify each recipient’s authorization and role in the care workflow. Limit group membership appropriately, protect notification previews, and record clinically relevant decisions in the required clinical record. An encrypted chat does not automatically become the official health record. Follow your organization’s disclosure, access, and escalation policies.

    Read the HIPAA-compliant texting guide

    Can we send patients reminders or replies by text?

    Assess the message content and delivery path rather than assuming reminders are never PHI. Confirm the phone number and communication preferences, explain relevant privacy risks, and document your agency’s safeguards and limits. A patient preference does not remove all security responsibilities, and a reminder does not authorize an unrestricted clinical conversation over ordinary SMS.

    HHS: Sending ePHI over open networks

    Can caregivers use personal phones, and what happens if one is lost?

    Personal phones are not automatically prohibited, but the agency must evaluate access, authentication, notifications, local storage, backups, and shared-device risks. Define lost-device reporting and access-revocation procedures before deployment. On loss or a wrong-recipient message, contact your agency’s privacy or security officer promptly, preserve relevant evidence, and follow the incident-response process; notification duties depend on the incident and applicable rules and agreements.

    HHS: Security Rule summary

    Review your agency’s messaging workflow

    Bring a handoff or on-call scenario to a GooScript demonstration using synthetic data. Review the applicable BAA and safeguards before introducing patient information.

    Agency guides, plans & case studies