ServiceNow Healthcare Norfolk, Virginia

Sentara Healthcare

IT Operations Automation

Sentara needed one integrated technology ecosystem for its One Sentara transformation, but fragmented support and manual outage handling consumed help-desk time and made it harder to scale consistent employee services across hospitals, health plans, and future expansion markets.

1.5K Items in service catalog
100% Of annual resource planning conducted in ServiceNow
100-plus resource groups
30K employees, 2.7K beds across 12 hospitals

Reported impact

Business outcome

Sentara now runs 100% of annual resource planning in ServiceNow, supports staff through a 1,500-item service catalog, automates outage notifications so agents stay available for higher-priority clinician issues, and uses the same platform foundation to support One Sentara and expansion into Florida.

  • Customer Experience
  • Productivity Improvement
  • Scalability

Solution

Sentara expanded its long-running ServiceNow estate into the operational backbone for the One Sentara program, using IT Service Management, IT Operations Management, Strategic Portfolio Management, and Virtual Agent to unify employee support and IT planning. IT Service Management provides the 1,500-item service catalog, incident workflows, outage records, and self-service foundation used by staff across hospitals and health-plan operations. Strategic Portfolio Management now holds the full annual resource-planning process, breaking work down across more than 100 resource groups so executives can make resourcing decisions from one dataset. Virtual Agent and portal self-service reduce dependence on manual channels, while the wider platform automates outage reporting and ticket creation through a telephony integration. The result is one ServiceNow environment that handles frontline support, operational automation, and portfolio visibility as Sentara expands into Florida and beyond.

Data flow

Service requests, outage records, catalog interactions, and portfolio data are captured in ServiceNow. Virtual Agent and the self-service portal handle routine needs first, the help-desk telephony integration plays outage messages and creates incident tickets for callers, and Strategic Portfolio Management rolls resource and project demand up into executive planning views.

Solution architecture

4 components · 2 layers
  1. Serving
    • Virtual Agent Adds self-service interactions that reduce pressure on live support channels.
  2. Orchestration
    • IT Service Management Provides the service catalog, incident workflows, and request management used across Sentara's operations.
    • IT Operations Management Supports operational issue handling and outage visibility inside the ServiceNow platform.
    • Strategic Portfolio Management Captures annual resource-planning data and converts it into executive planning views.

Architecture clues

  • Outage records are surfaced to callers through a telephony integration that can automatically create a unique incident ticket for each caller.
  • Resource-planning data is broken down by people and projects across more than 100 resource groups.
  • The platform is intended to stitch together hospital operations, health-plan operations, and the Florida expansion under One Sentara.

Evidence from the source

"On one occasion alone, around 80 callers-all wishing to report the same problem at the same time-instead received an automated message and then a follow-up email when the issue had been resolved."
"Sentara and partner, 3CLogic, built an integration in ServiceNow that automatically plays a recorded message about current outages to the caller."
"Sentara's entire annual resource planning process is being conducted in ServiceNow SPM."
"Sentara's platform includes numerous built-in self-service features, including a 1,500-item service catalog and Virtual Agent."
"ServiceNow is the strategic platform that drives all IT activity at Sentara-and it's the platform that will stitch everything together as we become One Sentara and extend our service into Florida and beyond."
Transparency Evidence & methodology 85/100 reference value · 79% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value85/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact15/25
    1 metric describe measurable impact.
  • Deployment scale5/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence79%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance0/10
    The publication date has no documented provenance.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. ServiceNow

    Sentara Healthcare customer story

    First-party
    https://www.servicenow.com/customers/sentara-healthcare.html
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes

Date evidence

  • First archived Jul 3, 2024 · Internet Archive · Independent First Wayback Machine capture; confirms the page existed by this date, not when it was published.
    Open date source
  • Sitemap last modified Jul 30, 2026 · ServiceNow · Publisher metadata Publisher-reported modification timestamp; not a publication date.
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.