Rebuilding A Practice’s Digital Systems, Workflows, And Automation

The Problem With Shared Documents Nobody Owns

In most practices the intake form, the policy, and the consent template all sit in a shared folder, and anyone who opens one can change it. Nobody does it on purpose. Someone fills out a form inside the master file, saves, and the blank form is gone. Version history gets deleted while cleaning it up. Six months later nobody is sure which document is current, and two versions of the same policy are in use.

We sorted the practice’s policies, forms, and staff resources into five areas the team already thinks in: Operations, Clinical, Medication Management, Human Resources, and Billing. The staff hub gives them one route to the current document, sitting alongside the tools they use all day.

SharePoint Access That Matches The Job

Staff got read access to approved documents. The people who actually own a document got a custom Master Maintainer Update Only permission that lets them update an existing master and review version history, but not add files, delete files, or delete versions. Practice leadership and the Microsoft 365 administrators kept administrative control, and restricted material kept its own separate access.

The August 24 verification found 97 controlled masters live, each still holding its own unique permissions, with the custom permission applied across 90 master file assignments on two SharePoint sites. Seventy-one shortcut paths were reconciled against the live structure so no link quietly points at the wrong copy.

Using A Form Without Destroying The Master

1. Open The Approved Master

   Staff find the current document through the staff hub or the document library.

2. Make A Working Copy

   Download or Save a Copy before typing anything into it.

3. Leave The Original Alone

   The completed copy goes where that work belongs. The master stays ready for the next person.

A Controlled Update Process

Maintainers got a written process too: confirm the approved change, update the existing master in place, reopen it, check Version History, and confirm the staff links still land on the same document. Uploading a new file with the same name is how a practice ends up with two masters and no way to tell them apart.

Work Across The Practice’s Systems

Document control was one piece of a wider engagement. Microsoft Forms and Lists carried intake tracking, Outlook and Teams delivered staff notifications, Power Automate moved the approved updates, and Tebra reports fed a custom Spravato scheduling workspace. Each one was built around who is responsible for the step, not around the software.

The EHR review covered staff workflow, practice requirements, vendor demonstrations, migration, support, reporting, and what a replacement would actually have to do before it was worth moving.