Healthcare IT Systems Delivery

Healthcare IT Systems Delivery

This case grounds the portfolio in real operational systems: support work, workflow improvement, and delivery coordination inside a healthcare setting.

2018 — 2023

A real-world healthcare IT delivery case covering system operations, infrastructure coordination, internal tooling, and clinical system rollout in a live environment.

Overview

From 2018 to 2023, my healthcare IT work covered clinical systems, networks, endpoints, reporting support, asset visibility, cybersecurity compliance, and business-side rollout coordination across a community health service center and satellite sites.

Problem

Healthcare IT problems are rarely only technical. A spreadsheet used for address tracking, unclear responsibility during rollout, or a poorly timed migration can affect clinical operations quickly, so changes needed to be stable and easy for different teams to adopt.

Role

IT systems operator and business-side delivery contributor. I supported daily operations, built small internal tooling, prepared reports, and coordinated with users and vendors during system change.

Context and constraints

Clinical operations had low tolerance for downtime or confusing process changes.
Stakeholders included IT staff, clinical and operational users, managers, and vendors.
Solutions had to fit existing Windows, IIS, SQL Server, and Excel-heavy workflows.

What I built

A C#/ASP.NET IP address management tool backed by SQL Server and IIS to replace spreadsheet tracking.
Support routines for clinical systems, endpoints, networks, and reporting requests across multiple sites.
Business-side rollout support for the child healthcare system migration from C/S to B/S architecture.

Technical approach

Used C#, ASP.NET, SQL Server, IIS, SQL, and Excel because they matched the support environment.
Prioritized maintainability, visibility, and handover clarity over new architecture.
Used pilots, feedback collection, and staged rollout support to reduce operational disruption.

Outcomes

Improved IP management for around 900 records and 500+ assets, reducing lookup and allocation time from 5–6 minutes to under 1 minute; also supported a clinical migration that reduced typical waiting times from about 40 minutes to 20–30 minutes.
Helped the system migration move through pilots, feedback, vendor coordination, and go-live support.
Built practical experience with reliability, constraints, and cross-functional delivery in a healthcare environment.

Reflection

This experience still shapes my engineering judgment: a system has to be understandable, recoverable, and workable for the people who operate it after launch.