Healthcare

Healthcare Appointment and Integration Platform

Senior .NET Developer / Integration Developer

Shows the strongest integration-heavy backend story: reliability, supportability, security hygiene, and operational discipline after the first successful API call.

Healthcare Appointment and Integration Platform system visual

Problem and Context

  • Healthcare systems depended on multiple upstream providers with mismatched contracts and variable reliability.
  • Support teams needed diagnostics that preserved privacy while still exposing integration failure context.

Built

  • .NET APIs and middleware that orchestrated hospital appointment and lab-result systems.
  • CRM, payment, video-call, content, and search integrations behind patient-facing surfaces.
  • Rate limiting, background jobs, validation, reCAPTCHA, and diagnostic logging around external calls.

Architecture

  • Layered .NET 7/CQRS APIs for memorial.ro.
  • Tenant-aware hospital middleware unifying Bilmed, Pusula, SAP, IYS, and MobilDev flows.
  • Patient-facing appointment/e-result facade with hardened cookies and strict input hygiene.

Integrations

  • Hospital APIs and systems including Bilmed, Pusula, SAP, IYS, and MobilDev.
  • CRM, payment, video-call, content, and search services behind patient-facing APIs.

Reliability, Security, and Operations

  • Outbound request/response tracing with support-friendly correlation.
  • PII-safe logging through hashing/sanitization and hardened cookie/input handling.

Operations

  • PII-safe logging through hashing and sanitization.
  • Hangfire jobs for indexing and content maintenance.
  • Full outbound call logging for support and forensics.

Technology Stack

ASP.NET CoreCQRS/MediatRSQL ServerHangfireElasticsearch