Oracle's 539 in Kansas City: The VA EHR Cohort LinkedIn Lost
Oracle's WARN window closes June 15, 2026, releasing 539 Cerner veterans in Kansas City. Here's how to source them before federal contractors do.
Oracle's WARN-mandated termination window for the Cerner-rooted Oracle Health cohort closes June 15, 2026. The Kansas City filing names 539 positions with effective dates of May 26 and June 1, and reporting puts total Oracle Health cuts at 8,000 to 10,000 roles. If you recruit healthcare IT and you searched LinkedIn last week for "Cerner consultant," you already missed most of these people.
What actually happened in Kansas City
Oracle filed WARN paperwork covering nearly 550 positions at 8779 Hillcrest Road, with Healthcare IT News pinning the final count at 539. The campus is not closing. There are no bumping rights. The layoffs are permanent, and Oracle folded WARN's 60 days of notice pay into existing severance rather than stacking it, so signing the release waives WARN claims. Strauss Borrelli PLLC opened investigations into potential WARN Act violations in Kansas City and Washington State in April 2026, then closed them without public resolution. New Jersey workers alleged separate violations under that state's 90-day WARN law.
The Revenue and Health Sciences unit, which houses the former Cerner business, lost roughly 30% of its headcount. SaaS and Virtual Operations Services took similar cuts. SVP of Product Management for Clinical and Healthcare AI Suhas Uliyar and EVP of Health Sanga Viswanathan are both gone. Five executives sent in specifically to fix the Cerner integration are gone. Oracle Health has lost 57 acute care clients in three years.
This is the cohort. And it lands on the open market at the exact moment the VA EHR Modernization (EHRM) program restarts.
The VA timing is the whole story
The VA paused most Oracle-Cerner deployments in April 2023 over patient safety and usability problems at Mann-Grandstaff VA Medical Center in Spokane, the original 2020 go-live. The system is currently live at only six of VA's 170 medical centers, including the joint VA/DOD rollout at Captain James A. Lovell Federal Health Care Center in North Chicago.
In 2026, the program restarts at 13 facilities. The first wave is four Michigan sites in mid-2026: VA Battle Creek, VA Detroit, VA Ann Arbor, and VA Saginaw. Nine more follow through end of 2026 across Ohio, Kentucky, Indiana, and Alaska. VA Secretary Doug Collins has asked Congress for an additional $840 million in FY27, taking EHRM to $4.2 billion, partly because the legacy VistA system costs $700 million a year just to keep alive. Lifecycle cost estimates for the program now range from $37 billion to $50 billion.
A March GAO report found only 13% of VA staff using the new system believed it made VA as efficient as possible. 58% believed it increased patient safety risks. That is the operational context the Michigan team is about to walk into, and the people who survived the Mann-Grandstaff cutover are the only ones who know which scheduling and pharmacy bugs they are about to re-encounter.
Federal contractors know this. Leidos, Booz Allen, SAIC, Accenture Federal, and VetsEZ are the obvious downstream destinations, not provider health systems. VetsEZ is already posting VistA DevOps SME roles tied to VA work. ALKU and Tech Mahindra show up in professional-network data as the consultancies already absorbing Cerner Millennium talent off Oracle's rolls.
Why LinkedIn search fails on this cohort
Here is the trap. Post-acquisition, profiles for this group increasingly read "Oracle Health" rather than "Cerner." But the skills worth hiring were built under the Cerner taxonomy: Millennium, CCL, PowerChart, FirstNet, PathNet, Rhapsody. If you search "Oracle Health engineer," you will miss the VA-EHRM veterans because their tenure predates the rebrand. If you search "Cerner consultant," you miss everyone who already updated their headline.
The strings that actually surface the talent are system-level, not title-level:
- Cerner CCL (Cerner Command Language) and Discern reports
- Cerner Millennium architecture and Cerner data model
- Cerner OpenEngine, HL7 message structure, Corepoint, Cloverleaf
- Rhapsody, Cerner FSI
- Cerner Millennium PathNet (LIS)
- Mann-Grandstaff, Lovell FHCC (the named go-live sites)
Active US job postings from federal contractors recruit against exactly these strings. Cerner-interface-engineer median pay sits at $96,107 per year as of April 2026, which tells you both how undervalued the cohort is relative to general SWE comp and why the federal-contractor absorption will happen fast.
Boolean on LinkedIn handles maybe two of these terms before the operator hits the result-set ceiling and starts dropping qualified matches silently. The cohort lives across three identity layers (current Oracle Health title, prior Cerner title, and a federal-contractor sub-contracting history) that no single LinkedIn query reaches. This is the exact problem we built Refolk for: you describe the person in plain English ("former Cerner Millennium engineers in Kansas City who worked Mann-Grandstaff or Lovell, now or recently at Oracle Health") and get a ranked shortlist across GitHub, LinkedIn, and the open web. The system-keyword signal in resumes, conference talks, and federal-contract press releases is where this cohort actually lives.
The "Cerner" string is dying on LinkedIn. The skills it represents just got 539 new free agents in Kansas City. </pull> Wait, that should be a fenced block:
pull The Cerner string is dying on LinkedIn. The skills it represents just got 539 new free agents in Kansas City.
## The five execs are a sourcing map, not a sob story
When five executives sent specifically to fix the Cerner integration all leave inside one cut, their direct reports become the highest-leverage hires for any vendor pitching VA work. Those people know which Mann-Grandstaff defects shipped to Lovell, which were patched, and which are about to surface at Ann Arbor. That tacit knowledge does not show up in a job title. It shows up in commit history on internal tooling, in HIMSS slide decks from 2021 and 2022, in named contributions to Cerner Open Developer Experience repos, and in mentions on VA OIG response threads.
Uliyar and Viswanathan are the public-facing names. Their teams are the trade.
The 60-day silent window
Here is the part most layoff trackers get wrong. The Oracle Health cohort is not on the open market in the way the WARN filing suggests. Severance pay only releases if engineers sign Oracle's release. Many are quietly weighing the tradeoff between signing now and pursuing claims tied to the WARN-stacking question Strauss Borrelli flagged before closing its investigations. During that window, displaced engineers are not updating LinkedIn. They are not posting "open to work." They are talking to former managers and federal-contractor recruiters privately.
For HL7 healthcare IT recruiters, that means three things:
- Direct outreach beats waiting. If you wait for the cohort to surface on LinkedIn, ALKU and Tech Mahindra will have already absorbed the top quartile.
- First-message specificity wins. "Saw your Cerner Millennium work" gets ignored. "Saw you were on the PathNet thread for Mann-Grandstaff in 2021" gets a reply.
- The federal-contractor angle is the actual pitch. Provider health systems offer 5-10% premiums. Leidos and SAIC offer cleared roles with VA-direct exposure. The cohort will follow the work.
This is also why generic ATS searches fail. Most ATSs index resume titles, not the system-level keywords inside the experience bullets. A Cerner Clinical Report Systems Advisor resume will say "CCL," "Discern," "RevElate," and "PowerChart" in the body, but the title field says "Senior Federal Testing Consultant" or "Cerner Millennium PathNet Independent Consultant." Refolk indexes the full surface area, which is why "Cerner CCL plus VA plus Kansas City metro" actually returns the cohort instead of a wall of irrelevant Oracle DBAs.
What to do this week
If you have a VA-adjacent req open (or a provider req where Cerner Millennium experience would be decisive), the next three weeks are the window.
Map the four named anchor sites
Mann-Grandstaff (Spokane), Lovell FHCC (North Chicago), and the Michigan four (Battle Creek, Detroit, Ann Arbor, Saginaw) are the keyword anchors that disambiguate this cohort from generic healthcare IT. Anyone with two or more named sites on their experience is high signal. Anyone with VistA-to-Cerner conversion experience plus a named site is the top 5%.
Skip the title field. Search the systems.
Build queries on PathNet, CCL, Discern, Rhapsody, OpenEngine, FSI, and Cerner Millennium. Filter for Kansas City metro (Overland Park, Lawrence, Shawnee, Olathe) and the Spokane / North Chicago corridors. The Refolk index already weights system-level Cerner keywords toward this cohort because we built the entity graph around the acquisition timeline, which means a plain-English query like "Cerner Millennium engineers who left Oracle Health in 2026" pulls profiles regardless of whether their current headline says Oracle, Oracle Health, or Cerner.
Move before the federal contractors do
VetsEZ, Leidos, Booz Allen, SAIC, and Accenture Federal are all aware of this cohort and have headcount tied to the 13-site 2026 rollout schedule. Their cycle time from interview to offer is fast on cleared work. If you are a provider health system or a non-federal vendor, you are in the second window, not the first.
Treat VistA experience as a six-month asset
Anyone who survived the 2020 Mann-Grandstaff cutover knows VA's legacy VistA quirks that the Michigan team will re-encounter starting mid-2026. That knowledge dilutes once the Michigan go-lives complete and the next generation of implementers builds direct experience. If you are hiring for VA EHR Cerner talent, the candidates with deep VistA-to-Cerner conversion history are the rarest, and they will not be rare in twelve months.
The bottom line
The Oracle Health layoffs 2026 story is not "8,000 to 10,000 people are looking for work." It is "539 specific Kansas City Cerner veterans, plus an unknown number of Mann-Grandstaff and Lovell alumni, are about to choose between federal contractors, regional health systems, and consulting absorbers, and the choice happens in a 60-day window where LinkedIn doesn't see them."
Search the systems, not the title. Name the sites in your outreach. Move before VetsEZ does.
FAQ
Why doesn't LinkedIn return this cohort for "Cerner consultant" searches?
Two reasons. First, Oracle rebranded most internal titles to "Oracle Health" post-acquisition, so current headlines often omit "Cerner" entirely. Second, the cohort's real skill signal lives in system-level keywords (CCL, PathNet, Rhapsody, OpenEngine, Mann-Grandstaff) that sit in the body of the profile, not the title field LinkedIn search ranks against. Boolean queries also hit operator ceilings before they can combine three identity layers (current Oracle title, prior Cerner title, federal-contractor adjacency).
When exactly does the Oracle Health Kansas City WARN window close?
Effective termination dates in the Kansas City WARN filing are May 26 and June 1, 2026, with the broader severance and release deadline extending through approximately June 15. The 8779 Hillcrest Road campus is not closing, and the cuts are permanent with no bumping rights. Strauss Borrelli PLLC opened and closed investigations into possible WARN Act violations without public resolution.
Which federal contractors are the most active absorbers right now?
Based on current job postings and professional-network signal, VetsEZ (VistA DevOps SMEs), Leidos, Booz Allen, SAIC, and Accenture Federal are the obvious destinations for the VA EHRM-adjacent talent. ALKU and Tech Mahindra are absorbing the broader Cerner Millennium consulting pool. Provider health systems are the second wave, generally arriving 30-60 days after the federal contractors lock in their cleared hires.
What's the single most valuable subsegment of this cohort?
Engineers who worked the 2020 Mann-Grandstaff cutover and have hands-on VistA-to-Cerner conversion experience, particularly anyone who also touched the Lovell FHCC joint VA/DOD deployment. That experience directly maps to the Michigan four (Battle Creek, Detroit, Ann Arbor, Saginaw) going live in mid-2026, and the knowledge has roughly a six-month shelf life before the next generation of implementers catches up.