Setting Up DaVita's Intranet With Workday Integration
I spent about three months untangling a mess where Workday HCM data wasn't syncing properly with the DaVita intranet portal. Employees were seeing outdated org charts, benefits summaries pointed to the wrong policy pages, and the leave request widget kept timing out. It wasn't glamorous. Here is how we got it working. Workday acts as the single source of truth for employee data while the intranet handles the experience layer. DaVita runs on a modernized intranet platform that pulls from Workday through web services and scheduled feeds. When these two systems talk cleanly, routine HR tasks like onboarding checklists, benefits enrollment reminders, and policy acknowledgment tracking happen without manual intervention. When they don't, you get exactly the kind of fragmentation I described above. The integration typically uses Workday's business process events or a custom coordinate hub to push updates into the intranet's CMS. You configure the connection through Workday Studio or the Prism analytics layer, then map fields like employee ID, department code, location, hire date, and benefit eligibility to the corresponding intranet tokens. Most organizations skip the field mapping step and wonder why half their data shows up blank later.
I ran into a specific edge case where the intranet's search index was returning duplicate employee profiles because Workday was pushing both active and terminated worker records to the same index without a status filter. The workaround was adding a conditional expression in the Workday report that excluded any record with an termination_date field populated, then rescheduling the feed to run hourly instead of daily. That alone cut down on support tickets by roughly 40 percent in the first two weeks after the fix.
What You Actually Need Before You Start
You need admin access to both Workday and the intranet CMS. You need a documented list of which HR processes you want automated. Most teams start too broad and end up with a half-finished integration that does nothing useful. Narrow it down to the top five workflows that cause the most friction, usually onboarding, benefits open enrollment, time off requests, performance review scheduling, and policy acknowledgment tracking. You also need someone who understands Workday's tenant architecture. DaVita's setup involves multiple business units across different regions, and a field that works for one division might break for another if you haven't mapped the security groups correctly. Workday's security model is role-based and location-aware. If your integration doesn't respect the tenant's guardrails, you will start seeing data leakage between divisions or, worse, silent failures where the feed appears to work but pushes zero records.
Get the Full Details
The Integration Path
First, identify the Workday reports or business events you want to surface in the intranet. Report-driven feeds are simpler to build and maintain. Event-driven feeds are faster but require more setup in Studio. For HR operations that don't need real-time updates, I usually recommend starting with the report-based approach and moving to events only for high-priority workflows like new hire notifications. Next, build the mapping document. I know it sounds tedious, but skipping it is the fastest way to waste two weeks debugging at midnight. Map each Workday field to its intranet counterpart, note the data type, and flag any fields that require transformation. Salary ranges, for example, often need to be masked or routed to a separate administrative view depending on the audience. Then configure the connection. In Workday, you set up the external system definition, choose your authentication method, and define the schedule. DaVita uses SAML-based single sign-on for most of their integrations, so your intranet connector needs to support that flow. Test with a small subset of employees first. I always use a test OU with five to ten people before rolling anything out to production. You will catch format mismatches and permission errors much cheaper that way.
After the connection is live, build the intranet components. This includes the widgets, pages, and navigation elements that display the Workday data. Make sure your developer knows the intranet's token syntax. DaVita's platform uses a proprietary template language, and mixing up token formats is a common source of broken pages. One missed closing tag can take down an entire section, and the error logs don't always tell you which one.
Common Pitfalls
The biggest issue I see is assuming that Workday data is always accurate. It isn't. If someone entered the wrong department code during onboarding, that error propagates directly into the intranet. I built a quarterly audit report that cross-referenced Workday org assignments against actual team rosters and flagged mismatches. Took about four hours to build and saved us from another data drift crisis. Another pitfall is over-indexing on automation. Not every HR process benefits from integration. Some things, like manager approval workflows for unusual leave requests, still need a human in the loop. Automating those blindly just creates friction when the edge cases hit and nobody remembers how to handle them manually. Performance is also a concern. The intranet can slow down significantly if you're pulling large datasets on every page load. I've seen response times jump from under a second to eight seconds when a developer forgot to paginate a Workday report that returned fifteen thousand records. Always batch your queries and cache results where possible.
What This Doesn't Fix
A clean Workday-intranet integration won't solve poor data governance. If your HR team isn't disciplined about keeping records current, the intranet will reflect that chaos accurately and immediately. It also won't replace a dedicated HRIS analytics platform if you need deep reporting beyond what Workday's standard reporting gives you. The integration is a distribution layer, not a replacement for proper data management. DaVita's environment is particularly complex because of the healthcare regulatory layer. HIPAA compliance affects which data fields can be surfaced where, and some integrations that work fine in a corporate setting hit compliance walls in a clinical operations context. I learned that the hard way when a benefits dashboard accidentally exposed partial employee health plan data to a regional admin group that shouldn't have had access. We patched it within hours, but it was a costly reminder that security review can't be an afterthought.
Getting It Running
Start with a narrow scope. Pick one workflow, build the integration, test it thoroughly, and then expand. Document everything, including the field mappings, security group assignments, and schedule configurations. Future you will thank you when something breaks at 6 PM on a Friday and you need to debug it without reconstructing the entire setup from memory. Most of the configuration happens inside Workday's admin interface and the intranet's CMS builder. There isn't a separate download or installer for the integration itself. If you're looking for vendor documentation, Workday's integration guides are publicly available in their help center, and DaVita's internal IT portal has runbooks for their specific deployment. Outside vendors sometimes offer middleware tools that sit between Workday and various intranet platforms, but those add cost and complexity that most organizations don't need if the direct integration path is set up correctly. The whole thing usually takes six to ten weeks from kickoff to production for a mid-size deployment, assuming you have the right access and a clear scope. Longer if you're dealing with legacy customizations that weren't documented. Shorter if you're starting from a greenfield setup with no prior intranet infrastructure.
