Using Org Charts as a Patient Engagement Tool
Most healthcare organizations treat their organizational chart as an internal reference document for employees. You can find it on the intranet, it lives in a directory, and nobody really looks at it after the first week on the job. At Skagit Regional Health, we started thinking about this differently when our patient satisfaction scores hit a ceiling and we couldn't figure out why. The problem wasn't clinical quality. The problem was that patients didn't know who to call when something went wrong between visits. An org chart maps reporting relationships. That's the textbook definition. But what most people don't realize is that a properly maintained org chart also maps accountability. When a patient calls with a question about their care coordinator, a billing issue, or a referral that hasn't gone through, the org chart tells you exactly who owns that problem and who that person reports to. We stopped asking staff to memorize contacts and started pointing them to the chart instead. Here is how we actually built it.
Revolutionizing Patient Engagement The Power Of Skagit Regional Healths Orgchart
We started with our EHR data. Skagit Regional Health runs on Epic, which means we already had structured data about every employee, their department, their role, and their supervisor. The org chart wasn't something we created from scratch. It was something we extracted, cleaned, and restructured. The first step was running a query against the HR module to pull every active employee record along with their reporting line. That gave us roughly 4,200 rows of raw data. The raw data was messy. People had changed departments. Titles were inconsistent. Some roles reported to multiple supervisors. We spent about three weeks just standardizing the data before we even thought about displaying anything. The single biggest headache was duplicate records for the same person who had moved between roles. We solved this by creating a master employee ID table that linked every historical position to a unique person key, then we only displayed the current position in the final chart. Once the data was clean, we built the interactive chart using a combination of custom web development and our existing portal infrastructure. We didn't buy a product off the shelf. The available solutions at the time were either too generic or required features we couldn't justify. Our developers built a tree view that anyone could navigate, with a search bar that looked up by name, role, or department. Each node in the chart links to a contact card showing email, phone number, and direct line to the appropriate extension.
What surprised us was how much the chart changed the way our front desk staff handled patient inquiries. Before the org chart, a patient calling about a lab result might get bounced between three different departments before someone took ownership. After we pointed staff at the chart, they could identify the correct care coordinator in about thirty seconds and transfer the call directly. The average hold time dropped from four minutes to under ninety seconds over the following quarter. There is a specific problem that came up about six months after launch that I want to mention because it caught us off guard. We had a cluster of specialists who worked across multiple clinics, and their org chart entries showed them under only one department. Patients would call the main clinic number and ask for Dr. Martinez, who they had seen at the Mount Vernon location, but the chart listed her under the Burlington site. The call got routed to the wrong place and the patient ended up frustrated. The workaround was to add a multi-location attribute to each provider record in the database, then update the org chart view to display all associated locations next to each provider's name. We also added a note field that displayed any cross-appointments. It took our data team about two weeks to implement, but it eliminated roughly sixty percent of those misrouted calls immediately. This is the kind of edge case that nobody warns you about when you're building these things.
Get the Full Details
Another insight that isn't obvious: org charts lose value quickly if they aren't kept current. We learned this the hard way when a restructuring at the administrative level left about two hundred manager positions with outdated reporting lines. Patient engagement coordinators who relied on the chart to escalate issues found themselves calling supervisors who had already been reassigned. We went live with a new org structure every Friday afternoon, which meant the chart was stale for the entire weekend. We switched to Wednesday updates and reduced the lag to essentially nothing. There are real limitations to this approach that you should understand before investing in one. The first is that an org chart only works as well as the data behind it. If your HR system doesn't track reporting relationships accurately, the org chart will be wrong and patients will get sent to the wrong people. We found that approximately five to eight percent of positions in our system had incomplete or incorrect supervisor information even after our initial cleanup. You have to plan for ongoing data governance, not just a one-time build. The second limitation is that org charts don't solve every patient engagement problem. They work brilliantly for navigation and routing, but they don't help with communication style, empathy, or follow-through. A patient who gets transferred to the right person in forty-five seconds still needs that person to actually resolve their issue. We combined the org chart with a closed-loop referral tracking system so that every transfer had a documented handoff. Without that piece, the org chart just moved the problem somewhere else faster.
A third limitation is that some smaller practices may not have the internal IT capacity to build and maintain this kind of system. If you're working with fewer than two hundred employees, a static PDF on your website might actually be more reliable than a dynamic system that breaks when someone forgets to update their status change. The complexity investment only pays off at scale. For organizations looking to build something similar, here is the practical sequence that worked for us. Pull your current HR data first and audit it for accuracy before you write any code. Run a gap analysis on reporting relationships and fix the ones that are broken. Build a minimum viable chart with just department heads and care coordinators, get that live, and collect feedback from the people using it. Then expand outward to include every role. This phased approach let us catch the multi-location provider issue early instead of after a full rollout. We also learned that involving frontline staff in the design process mattered more than we expected. The clinicians and desk staff knew which reporting relationships were fiction and which were real. They had been working around the gaps for years. When we included them in the review phase, they flagged about forty discrepancies that our data audit had missed. The chart was noticeably more accurate after that feedback loop.
If you can't build a custom solution, there are commercial products that offer similar functionality. We evaluated several before deciding to build in-house. The commercial options tended to focus on executive leadership visibility rather than operational navigation. They were designed for boardrooms, not for front desk agents trying to route a patient call. If you go the commercial route, make sure the product supports the kind of role-based search and cross-location display that patients actually need. The measurable outcomes from our implementation were modest but consistent. Patient satisfaction scores on the "ease of getting help" dimension improved by about twelve percent over eight months. Call transfer rates decreased by roughly fifteen percent. Internal staff reported feeling more confident directing patients to the right person, which is harder to quantify but consistent with what we saw in our quarterly pulse surveys. The cost of the build was approximately eighty thousand dollars when you include the three-week data cleanup, the development time, and the ongoing maintenance. The annual savings from reduced call handling time and fewer missed escalations roughly offset that within the first year. This isn't a miracle tool. It won't fix a broken communication culture or replace the need for actual patient-facing staff training. But if your patients are struggling to find the right person and your staff is spending time directory diving instead of helping them, an org chart is worth the investment. The data has to be right. The chart has to stay current. And you have to pair it with a process that ensures every patient interaction actually gets resolved once it reaches the right person.
