Implementation services · EHR managed support
Stoltenberg Consulting
Stoltenberg Consulting is a healthcare IT firm known for EHR managed support, FlexSourcing help desk, and related go-live and optimization staffing across major EHRs. It is stronger as ongoing support than as a greenfield build-only SI story.
Strong fit
- Hospitals that need flexible Tier 1+ EHR help desk and partial IT outsourcing
- Organizations stabilizing after go-live more than running a greenfield build
- CIOs who want support metrics tied to ticket resolution
Weak fit
- Buyers hiring for a full Epic build program with module design ownership
- Groups that will not share ticket and EHR access with an outside support partner
- Tiny practices that only need vendor help desk for one cloud EHR
Bottom line
Stoltenberg Consulting earns a Recommend for health systems shopping EHR managed support and flexible sourcing. It is a weaker fit for a classic greenfield build SI. Outcomes center on first-call resolution, clinician ticket friction, and the ability to ramp support without a rigid multi-year lock-in story. Product is the FlexSourcing / help-desk model across major EHRs. Implementation is an operations handoff as much as a project plan. Pricing is managed-services oriented. Score sits slightly below Tegria and Nordic on our board because the firm is a weaker fit for greenfield build RFPs.
Score breakdown
Weights: Outcomes 35% · Product 30% · Implementation 20% · Pricing clarity 15%.
Stoltenberg focuses on EHR and hospital IT support: Tier 1+ help desk, flexible sourcing, legacy support, and go-live command-center style staffing across Epic, Oracle Health, MEDITECH, and other platforms.
That is a different hiring reason than a Nordic-style Epic build. Compare it when your pain is ongoing clinician tickets and partial outsourcing, not module design from scratch.
Score reflects solid managed-support outcomes with ordinary SI pricing opacity and a narrower fit for greenfield implementation RFPs.
Competitor landscape
| Vendor | Overall | Speed to go-live |
|---|---|---|
| Stoltenberg Consulting | 7.2 | 7.0 |
| Tegria | 7.6 | 7.7 |
| Nordic | 7.4 | 7.1 |
| MedSys Group | 7.3 | 7.0 |
Pricing
| Item | Detail |
|---|---|
| Model | Managed IT / FlexSourcing contracts sized to ticket volume, applications supported, and coverage hours. |
| What usually drives cost | Applications in scope, service levels, and how much you ramp for go-lives or migrations. |
| What to ask in diligence | Monthly cost at your ticket volume, SLAs, and what changes when you add a major EHR event. |
| Published pricing | Public list price: not published. Expect a managed-services quote. |
Prerequisites for purchase
| Need | Why it matters |
|---|---|
| What you need to get Stoltenberg Consulting to function | |
| Ticket and EHR access paths for support staff | Support fails without tools and credentials. |
| Service-level targets clinicians will accept | Vague promises of better support cannot be staffed. |
| Internal IT owner for escalations beyond Tier 1 | Everything cannot stay at the help desk. |
| Application inventory in scope | Unbounded app lists destroy SLAs. |
| Willingness to retire parallel shadow support channels | Parallel support channels hide how much ticket volume you actually have. |
| What will maximize your value | |
| Publish first-call resolution and reopen rates | Managed support is a metrics business. |
| Use FlexSourcing to ramp for known events | Go-lives need planned capacity. |
| Coach end users on portal and self-service paths | Ticket volume is partly behavior. |
| Align support hours to clinical peaks | Daytime-only coverage fails nights. |
| Review knowledge articles monthly | Stale scripts create repeat tickets. |
| Deal-breakers | |
| You need a full greenfield Epic build partner, not managed support. | |
| You will not grant required EHR access. | |
| No internal Tier 2/3 owners exist for escalations. | |
| Leadership expects unlimited apps at commodity seat prices. | |
| You only need vendor SaaS chat support for one clinic product. | |
Value creation time frame
| # | Stage | Typical range |
|---|---|---|
| 1 | Contract signed → kickoff | 2-6 weeks (access, runbooks, SLA baselining) |
| 2 | Kickoff → first live workflow | 4-10 weeks to steady ticket handling on priority apps |
| 3 | First live workflow → steady value | 2-4 months of tuning before SLAs stabilize |
Methodology
| Weight | Factor | What it measures |
|---|---|---|
| 35% | Customer outcomes | Whether buyers get measurable operational or clinical-workflow results after go-live |
| 30% | Product | Capability depth, reliability, and fit for the job the category actually buys |
| 20% | Implementation | How hard it is to stand up, integrate, train, and stabilize |
| 15% | Pricing clarity | Whether a buyer can model total cost without a mystery quote |
| Label | Meaning |
|---|---|
| Highly recommend | Strong outcomes and product with manageable caveats |
| Recommend | Solid fit for the right buyer; know the tradeoffs |
| Conditional | Only with a specific use case or heavy caveats |
| Not recommended | Avoid for most buyers in this category |
Read our full methodology for how we weight scores and assign recommend labels.