Healthcare

Healthcare Appointment & Integration Platform

Senior .NET Developer / Integration Developer

This project is a good example of the type of backend work I do best: integration-heavy systems where reliability matters after the first successful API call.

Overview

This project was part of a healthcare digital platform with public web/mobile surfaces, middleware APIs, appointment workflows, e-result access, CRM integration, payment flows, video visits, search, OTP login, consent handling, and operational logging.

My role focused on backend and integration delivery. I worked on .NET APIs and middleware that connected hospital systems and supporting services behind cleaner, more consistent contracts.

What The Platform Needed

The platform had to support patient-facing and operational workflows across multiple systems:

The main engineering challenge was not only calling external APIs. The harder part was making the integrations predictable, traceable, and supportable when different systems had different identifiers, payload shapes, authentication rules, and failure modes.

  • Appointment and doctor/unit/hospital data flows
  • Patient login and OTP-based access
  • Lab/radiology/e-result access
  • CRM form submissions and follow-up workflows
  • Payment and video-visit integrations
  • Search indexing for public healthcare content
  • Consent and communication-permission handling
  • Reliable logging for support and troubleshooting

My Backend Work

I helped build and maintain backend surfaces using .NET, ASP.NET Core, SQL Server, EF Core, CQRS/MediatR, background jobs, HTTP integrations, validation, rate limiting, and structured logging.

Key work included:

  • Building backend APIs and middleware surfaces for healthcare workflows
  • Integrating hospital appointment and e-result APIs
  • Connecting CRM, payment, video-call, SMS/OTP, and search systems
  • Mapping IDs across hospital, web, mobile, and middleware systems
  • Persisting request/response logs for troubleshooting and auditability
  • Adding validation, throttling, and safer handling around patient-facing flows
  • Supporting background jobs for indexing and operational processing
  • Keeping sensitive data handling practical with PII-safe logging patterns

Technical Highlights

  • Backend stack: .NET, ASP.NET Core, SQL Server, EF Core, MediatR/CQRS
  • Integrations: hospital APIs, CRM, payment provider, video-call provider, SMS/OTP, Elasticsearch/search
  • Reliability: background jobs, cached mappings, request/response diagnostics, retry-aware integration thinking
  • Security: JWT/OTP flows, rate limiting, consent/version handling, input validation, safer logging
  • Operations: support-friendly diagnostics and traceable external calls

Why This Project Is Relevant

This project is a good example of the type of backend work I do best: integration-heavy systems where reliability matters after the first successful API call.

It is relevant for clients who need:

For calendar, scheduling, or Microsoft Graph-style work, the same core patterns apply: keep internal records mapped to external IDs, make create/update/delete behavior idempotent, log failures clearly, handle retries carefully, and give admins enough visibility to support the workflow in production.

  • Appointment or scheduling systems
  • Healthcare or regulated workflows
  • Backend API development
  • External API integrations
  • SQL Server/.NET production systems
  • Admin-managed operational workflows
  • Background processing and sync-style architecture
  • Better logging and support visibility around integrations

Project Images

More Relevant Projects