All agency case studies

    Community clinic · Illustrative workflow study

    Accountable messaging as a clinic team grows

    A growing clinic separates scheduling updates from clinical conversations and makes workforce access review a routine task.

    Hypothetical example—not a customer testimonial. No measured results or agency endorsement are claimed. Images are illustrative. This is an evaluation aid, not legal advice or a compliance certification.

    Illustrative clinic administrator and nurse reviewing a tablet

    The coordination challenge

    Front-desk staff, nurses, providers and administrators have different responsibilities. Shared accounts and broad group chats blur who can see patient details, while new hires and departing staff make permissions harder to manage. Patient reminders also need their own risk assessment.

    A proposed agency workflow

    1. Separate communication purposes

      Map scheduling, clinical handoffs, administrative announcements and patient replies separately. Determine which staff need access for each purpose and follow applicable disclosure rules.

    2. Make account changes deliberate

      Use individual identities, approved authentication and documented permission changes. Review new hires, role changes and departures with a named administrator; avoid shared credentials.

    3. Rehearse an incident review

      Using synthetic data, test a wrong-recipient report, preserve the available evidence and follow the privacy officer’s investigation procedure. Confirm what the vendor actually records and exports.

    Evidence to validate before PHI

    • A role-by-role permissions demonstration
    • Sample administrative and access audit records
    • The applicable BAA and service-specific data flows
    • Patient communication preferences and device policies

    What the agency could measure

    Proposed evaluation measures—not observed improvements.

    • Accounts reviewed at each workforce change
    • Permission exceptions identified and resolved
    • Time to revoke access for departing staff
    • Staff completion of the approved messaging training

    Plan considerations: Enterprise

    Enterprise includes 35 users, 90-day message retention, E-Learning and Sentinel email protection in the published comparison. Check usage-based charges and the agency’s records requirements. A higher tier does not itself establish HIPAA compliance.

    Message retention is a plan feature, not a universal legal retention requirement. Confirm clinical-record duties, exports and the executed agreement before deployment.

    The takeaway

    Growth needs repeatable access decisions—not just a larger group chat. Assign an owner to permissions, training and incident review.