GooScript · Agency guide

    HIPAA-compliant messaging guide

    A practical framework for home health, hospice and clinic teams: evaluate the safeguards, define the workflow and prepare your people before sharing patient information.

    Educational guidance—not legal advice, certification or a guarantee of compliance.

    Illustrative agency care team reviewing a handoff on a tablet
    Illustrative agency scene; no patient information is shown.

    Compliance is a workflow, not an app label

    The HIPAA Security Rule requires administrative, physical and technical safeguards for electronic protected health information (ePHI). For messaging, assess access control, authentication, audit controls, integrity and transmission security in the actual workflow. [2]

    HHS describes encryption as an addressable implementation specification under the currently effective rule: assess whether it is reasonable and appropriate, implement it when it is, and document any justified alternative or rationale. “Addressable” is not permission to ignore it. End-to-end encryption alone does not establish a compliant service or agency. HHS encryption guidance

    Where a vendor creates, receives, maintains or transmits PHI on your agency’s behalf as a business associate, a written BAA is generally required. Confirm the exact service, storage, integrations and subcontractors it covers. A BAA sets duties; it is not a certification. HHS business associate guidance

    Ask for evidence, not just feature names

    Use these questions in a demonstration with synthetic data. They are evaluation criteria, not a claim that every listed detail is legally mandated or included in every GooScript plan.

    Identity & access
    Can every action be associated with an individual account, and can your agency grant and revoke appropriate access?

    Evidence to request: An account, permissions and offboarding demonstration.

    Encryption & devices
    How are transmission, storage, backups, linked devices and notification previews protected?

    Evidence to request: Service-specific security documentation and a lost-device drill.

    Audit controls
    Which activities are actually recorded, who can examine them and how are records protected?

    Evidence to request: Sample records, review permissions and export behavior.

    Records & retention
    Where do clinical decisions belong, and how do messages and attachments follow your retention policy?

    Evidence to request: A clinical-record workflow, retention settings and termination terms.

    Incidents & continuity
    How do staff report a wrong recipient or lost phone, and what happens when messaging is unavailable?

    Evidence to request: A tested incident-reporting path and urgent backup channel.

    BAA & data flows
    Where a business associate relationship exists, does the executed agreement cover the exact service and its subcontractors?

    Evidence to request: The applicable BAA, data-flow review and integration scope.

    Separate care-team messaging from patient texting

    Staff handoffs & on-call requests

    Verify the authorized recipient and current care-team membership. Protect previews and device access, agree on escalation expectations, and record clinical decisions in the required health record. A read receipt is neither clinical acceptance nor an emergency response guarantee.

    Explore agency workflows

    Patient reminders & replies

    A reminder can still reveal a care relationship. Confirm the phone number and communication preferences, assess the content and delivery path, explain relevant risks, and define what happens when a patient replies with clinical information. Patient preference does not remove all safeguard obligations.

    Read the messaging FAQ

    HIPAA does not approve or ban all apps by name. Ordinary SMS and consumer chat may leave gaps in accounts, backups, offboarding, audit evidence and applicable agreements; encryption claims alone do not settle those questions. HHS guidance on ePHI over open networks

    An agency rollout checklist

    1. Map the communication

      List handoffs, on-call requests, scheduling, attachments and patient replies. Identify ePHI, recipients, devices, backups and the clinical record for each workflow.

    2. Document the risk assessment

      Have the privacy or security officer evaluate the risks and appropriate safeguards. A vendor’s encryption claim or a signed BAA is not a replacement for this analysis.

    3. Review the service and agreement

      Confirm permissions, records, retention, notifications and subcontractors. Execute the applicable BAA before a business associate handles PHI; check any AI or external integration separately.

    4. Pilot with synthetic data

      Rehearse a handoff, a wrong-recipient report, an access revocation and a lost-device incident. Do not use real patient information to test an unapproved workflow.

    5. Train and assign ownership

      Name the account administrator and incident contact. Define permitted channels, recipient checks, clinical documentation and an urgent telephone escalation path.

    6. Review after rollout

      Examine access changes, available audit evidence and reported exceptions. Reassess the workflow when the service, devices, integrations or staffing changes.

    Sources & service review

    For GooScript, review the published BAA and safeguards and data handling, then request service-specific evidence. Your agency’s applicable agreements and source policies remain authoritative. Consult your privacy or security officer and legal adviser.

    Continue your agency evaluation

    Book an agency demo