TL;DR
- A family medicine practice with three locations had three separate IT vendors, none of whom coordinated — patient portal failures at location three had gone unresolved for months
- Email deliverability was at 71% inbox rate; SPF was only configured for location one's sending infrastructure
- We audited all three locations, fixed the patient portal DNS misconfiguration, corrected email authentication across all sending sources, and consolidated IT under a single managed services provider
- Patient portal issues resolved in 47 days; email inbox rate improved to 96.3%; practice administrator reclaimed 6–8 hours/month previously spent on unproductive vendor coordination
Three Vendors, Three Locations, Nobody Talking to Each Other
A family medicine practice had grown from one location to three over five years. Each location had been set up somewhat independently, and the technical environment reflected that.
The owner put it directly: "We have three vendors, none of them know what the other is doing, and every time something breaks I spend a week emailing people who blame each other."
What they were dealing with:
- Three separate IT vendors — one per location, none of whom communicated with each other
- Patient communication emails going to spam at an unacceptable rate
- The patient portal working correctly at locations one and two, and intermittently failing at location three for reasons nobody had been able to diagnose
- HIPAA compliance review coming up with no documentation of their systems or access controls
- The practice administrator spending an estimated 6–8 hours per month on IT coordination that produced no resolution
The email deliverability problem was affecting patient care: appointment reminders, test result notifications, and portal access emails were failing to reach patients, generating callbacks and no-shows that could have been avoided.
Two-Week Audit Across All Three Locations
We started with a two-week technical audit covering all three locations: network configuration, email setup, DNS records, patient portal configuration, access credentials, software inventory, and vendor contracts.
Email deliverability: The SPF record was configured for location one's sending infrastructure only. Locations two and three were sending from IPs not covered by the record — every email sent from those locations was unverifiable, and receiving mail servers were filtering accordingly. We added all three sending sources to the SPF record, implemented DKIM signing at the domain level, and set DMARC to monitoring mode to track authentication failures across the full sending environment.
Patient portal failure at location three: A DNS entry had been misconfigured during the initial location three setup and never corrected. The portal subdomain was resolving to the wrong IP intermittently — a TTL misconfiguration interacting with a CDN caching rule created a failure that appeared under load but not in simple tests, which is why two vendors had been unable to reproduce it consistently.
Vendor consolidation: Negotiated termination of the three-vendor arrangement and consolidated IT support under a single managed services provider with visibility across all three locations. Single point of contact, cross-location documentation, consistent SLA.
Documentation: Produced a full systems inventory, network diagram, access credential register, and vendor contact sheet for each location. Provided to the practice for the upcoming HIPAA compliance review.
18-month technology roadmap: Delivered a written roadmap covering HIPAA documentation requirements, planned EHR integration, anticipated staff growth and licensing needs, and a recommended upgrade cycle for aging workstations at location two.
Patient Portal Fixed in 47 Days, Email Deliverability Recovered
Results measured from engagement start:
- Patient portal issues at location three resolved in 47 days — root cause was a DNS misconfiguration that had been in place since setup
- Email inbox rate improved from 71% to 96.3% within two billing cycles of correcting the SPF/DKIM configuration
- 6–8 hours per month reclaimed by the practice administrator, previously spent on unproductive multi-vendor coordination
- HIPAA compliance review passed with no findings related to IT documentation — the first time the practice had been able to say that
- Single IT contact across all three locations with documented, consistent response procedures
The practice now has a technology environment that reflects how they actually operate — as one organization across three locations — rather than three independent setups that happened to share a name.
Frequently Asked Questions
What does a fractional technical advisor do differently than an IT vendor? A standard IT vendor responds to tickets and keeps systems running. A fractional technical advisor identifies root causes, coordinates across vendors, and owns the technology strategy — the "why are we doing this and what should we do next" questions that don't belong in a support ticket. In this case, the distinction was that we audited the full environment across all three locations and made vendor-level decisions, rather than being one more vendor responding to individual incidents.
How does SPF misconfiguration affect patient communication emails? SPF (Sender Policy Framework) is an email authentication standard that tells receiving mail servers which IP addresses are authorized to send email from your domain. When locations two and three were sending from IPs not listed in the SPF record, those emails looked to Gmail, Outlook, and other providers exactly like spoofed or phishing messages. They were filtered to spam without the recipient knowing they existed. For a medical practice sending appointment reminders and test result notifications, that's a direct patient care issue.
How long does it take to fix email deliverability for a multi-location practice? DNS changes like SPF and DKIM propagate within 24–48 hours. Deliverability improvement with major email providers (Gmail, Outlook) follows the sending reputation, which improves over 2–4 weeks of clean authenticated sending. In this case, the inbox rate moved from 71% to 96.3% within two billing cycles — roughly 60 days from the DNS correction.
What is HIPAA compliance documentation and why does a website and email setup need to address it? HHS HIPAA requirements include technical safeguards for electronic protected health information (ePHI), which includes patient communications sent by email and data handled by the patient portal. The audit documentation we produced — systems inventory, access controls, vendor register — gives the compliance reviewer evidence that access to patient data is controlled, monitored, and recoverable. Without that documentation, the review has nothing to evaluate.
When should a medical practice consider a fractional technical advisor instead of just IT support? When the problems are at the coordination or decision level, not the ticket level. Signs: multiple vendors blaming each other for a problem nobody owns, recurring issues that keep getting "fixed" without root cause analysis, no single person who can answer what systems exist and who has access, or growth (new locations, new integrations) that IT support isn't equipped to plan for.