Client: MediCore · Healthcare & Life Sciences · US clinical documentation SaaS (60 staff)

Upgrading a Clinical Documentation Platform

By TechSupport Team. Published November 16, 2026. Updated .

TechSupport Team maintained MediCore’s clinical documentation platform during the migration from .NET Framework 4.8 to .NET 8. In five months, the client’s Defender count moved from 19 critical CVEs to zero for the measured scope. Three third-party library findings were excluded.

Client and engagement facts

Client
MediCore
Industry
Healthcare & Life Sciences
Business context
US clinical documentation SaaS (60 staff)
Delivery model
Software maintenance
Application
Clinical documentation SaaS on legacy framework
Supplied geography
US
Company size in source
60 staff

Application stack and tools

Application stack

  • .NET Framework 4.8 → .NET 8
  • SQL Server
  • Azure

Tools used

  • Microsoft Defender
  • Application Insights
  • SQL Server Query Store

Why Support Was Needed

The client wanted to reduce its vulnerability backlog while keeping clinical review in the release process. The engineers scoped the migration module by module and prepared each release for clinical sign-off.

Technical Work

  • Planned the migration from .NET Framework 4.8 to .NET 8 by module.
  • Added a client clinical sign-off step before each module reached production.
  • Used a composite index to improve the patient-record query.

Representative Incident

One module needed a second clinical review. The client added two weeks for that review, and the module shipped a week later than planned. The full engagement took five months against an initial three-month estimate.

Results and how they were measured

Reported results and their measurement scope
MetricBaselineResultUnitsMeasurement windowSource and scope
Critical CVEs in measured scope1905 monthsClient Defender; Scope: The CVE comparison excludes three findings in a third-party clinical library with no available patch.
Page load4.8 s2.2 ss5 monthsClient App Insights
Slow SQL queries27/day6/day/day5 monthsClient Query Store

Evidence and Limitations

The CVE comparison excludes three findings in a third-party clinical library with no available patch. App Insights and Query Store supplied the performance measures.

Migration Schedule and Clinical Review

The migration took five months against a three-month estimate. One module required a second clinical review.

Scope a Similar Engagement

Identify the framework modules, security backlog and review steps your application upgrade depends on. Request a support plan or explore software maintenance.

Get a technical support plan

Tell us which application needs support, what is reaching your engineers and when you need coverage. TechSupport Team will review the fit and explain the next scoping step.

  • We reply by email.
  • We agree a call about the roles, your stack and the hours.
  • If there is a fit, we propose engineers after an assessment.

A short outline is enough. Add your stack and coverage hours if you know them. Do not include credentials or customer data.

Add coverage and team details

We use these details only to reply to you. Describe the application, stack and hours you need covered. Keep credentials and sensitive technical data out of this form. We save the brief for delivery and use Telegram to notify our team.