The situation
Important systems worked, but ownership and support had become fragmented.
IdahoTMS relied on a mix of cloud accounts, clinic computers, scanners, shared files, networking, and vendor-managed services. Administrative access and technical knowledge were spread across different people and providers, making routine support slower and increasing the risk that one unavailable account or individual could interrupt operations.
Primary risk
Critical accounts, devices, and recovery information were not consistently under documented clinic control.
ClinicsIT approach
Recover ownership first, stabilize daily operations, then document and prioritize longer-term improvements.
Business result
A clearer, more supportable environment with less dependence on undocumented knowledge or a single provider.
Project scope
A practical recovery project across identity, workstations, scanning, and support.
Microsoft 365 administration
Recovered administrative control, reviewed tenant ownership, and established a clinic-controlled path for ongoing management and recovery.
Google Workspace and domain ownership
Clarified the relationship between the domain, DNS, reseller-managed Google Workspace, Shared Drives, and administrative recovery.
Workstation standardization
Rebuilt and standardized approved clinic computers with consistent naming, support accounts, software, access, and reporting.
Secure remote support
Established dependable attended and unattended support paths so troubleshooting could begin without waiting for improvised access.
Scanning and shared-file workflow
Stabilized document intake from the Brother multifunction printer into a clinic-controlled Shared Drive workflow.
Security and continuity planning
Identified risks involving PHI access, local administrator use, Wi-Fi, backups, NAS storage, account recovery, and remaining unmanaged devices.
Why ownership came before upgrades
Replacing hardware would not have solved missing administrator access, unclear billing control, undocumented recovery methods, or dependence on former providers. ClinicsIT first worked to establish who controlled each system and how the clinic could recover it. That foundation made every later technical decision safer.
How the recovery unfolded
Three connected workstreams turned scattered access into a supportable clinic environment.
Workstream 1Account and administrative recovery
The first priority was determining who controlled the systems that controlled everything else.
- Recovered Microsoft 365 administrative control and documented the tenant, roles, recovery path, and ownership responsibilities.
- Clarified how Squarespace, DNS, the clinic domain, and reseller-managed Google Workspace were connected.
- Established clinic-controlled administrative and recovery paths so future access would not depend on one employee, consultant, or personal device.
- Documented vendor relationships, billing dependencies, support cases, and the next decisions ownership needed to make.
Workstream 2Workstation and support standardization
Once administrative control was clearer, the clinic computers could be brought into a repeatable support model.
- Rebuilt and standardized approved workstations with consistent naming, support accounts, remote access, and core applications.
- Created separate routine-support and break-glass recovery accounts instead of relying on shared or informal local administrator access.
- Verified remote desktop readiness and unattended support so ClinicsIT could respond without recreating access during every incident.
- Produced machine-level reports and ongoing documentation so onboarding, replacement, and troubleshooting could follow the same process.
Workstream 3Scanning, security, and continuity
The project also exposed workflow and security concerns that were easy to miss while the clinic was focused on keeping daily operations moving.
- Stabilized scanning from the Brother multifunction printer into the clinic Shared Drive and documented fallback options.
- Identified that scanned documents were too broadly accessible and recommended restricted intake, storage, and user-access workflows.
- Documented concerns involving Wi-Fi design, backups, NAS storage, identity enforcement, remaining unmanaged computers, and local administrator privileges.
- Separated immediate operational fixes from longer-term infrastructure projects so the clinic could improve security without disrupting care delivery.
Work completed
From emergency cleanup to repeatable clinic IT operations.
- Recovered and documented access to key Microsoft 365, Google Workspace, domain, DNS, and administrative systems.
- Created clinic-controlled routine-support and break-glass recovery accounts on approved workstations.
- Standardized workstation naming, remote access, administrative readiness, Google Drive access, and technical reporting.
- Reduced routine dependence on unmanaged local administrator accounts.
- Stabilized scanner intake into the clinic Shared Drive and documented fallback options.
- Identified excessive access to scanned documents and recommended restricted intake and storage workflows.
- Produced ongoing technical documentation covering ownership, security concerns, vendor relationships, infrastructure, and next actions.
- Created a roadmap for remaining workstations, networking, Wi-Fi, backup, NAS storage, identity enforcement, and remote support.
Outcomes
What changed for the clinic.
Clearer ownership
Administrative systems and recovery paths are better aligned with the clinic rather than an individual employee or outside provider.
Faster support
Approved remote-support and workstation-access methods reduce time lost establishing basic access during an incident.
More consistent computers
Standard naming, support accounts, software, and documentation make clinic workstations easier to maintain and replace.
Safer document handling
The clinic has a clearer understanding of scanning, Shared Drive access, PHI exposure, and options for a restricted intake workflow.
Documented continuity
Important knowledge is moving out of personal memory and into clinic-owned technical documentation.
Prioritized next steps
The clinic can address networking, backup, storage, security, and remaining devices in a planned order instead of reacting blindly.
“ClinicsIT helped us regain control of our digital infrastructure, stabilize critical workstations, establish secure remote support, and create clear documentation. We now have a much more organized and dependable IT foundation.”
Mark — IdahoTMS & Behavioral Health
This case study describes technology administration and operational improvements only. It does not include patient information or clinical records.
Related guidance
Practical resources used in this kind of clinic recovery.
Does your clinic need the same kind of technology cleanup?
ClinicsIT can inventory ownership, stabilize support access, standardize workstations, document the environment, and build a practical recovery roadmap.
Schedule a Free Clinic IT Review 