What kind of projects do you specialize in?

I design distributed platforms, secure integrations, and AI-enabled systems. Healthcare is my primary specialization — patient onboarding, provider operations, referral management, and care-delivery workflows — with enterprise architecture experience beyond it.

How do you approach AI systems that handle sensitive data?

I design controlled inference boundaries: sensitive data is redacted (using tools like Presidio) before any external model call, inference is decoupled from the interactive request path, and every step is auditable.

Can you help modernize legacy health platforms?

Yes. I lead modernization engagements that incrementally migrate fragile monoliths to highly scalable, decoupled microservices using patterns like Strangler Fig and Event Sourcing.

Abhijeet Srivastava

AI & Platform Architect

Specializing in healthcare platforms and care-delivery workflows.

I design distributed platforms, secure integrations, and AI-enabled systems, with a primary focus on healthcare.

My work connects backend architecture with the realities of patient onboarding, provider operations, referral management, and care delivery—from defining system boundaries to making workflows reliable in production.

Technical depth across industries. Applied experience in healthcare.

Explore My Work → Discuss an Architecture Challenge →

Scroll to explore

10+Years in Architecture & Backend Systems

4Enterprise-Scale Architectures Delivered

3Industries: Healthcare, Reinsurance, Government

Architecture delivered for

Curio Digital Therapeutics•Reinsurance Group of America•SmartData Inc•India GST Portal

Selected work

AI Inference Behind a Privacy Boundary

Architected a clinical AI pipeline where PHI is redacted before any external model call, with inference decoupled from the request path.

Read the case study →

Monolith Decomposition on Live Clinical Traffic

Led a Strangler Fig migration of a live clinical platform to microservices, with CDC keeping data consistent through the transition.

Read the case study →

Enterprise Portal Modernization

Directed a backend redesign and federated-authentication modernization for a high-volume reinsurance portal, across distributed teams.

Read the case study →

All case studies →

Technical foundations. Healthcare applications.

My technical foundation is broadly applicable. Healthcare is where I apply it most often, working across sensitive information, connected systems, and care-delivery workflows.

Distributed systems

Designing service boundaries, event flows, and recovery paths across connected systems.

In healthcare Coordinating patient, provider, scheduling, and notification workflows.

Related case study →

Data modeling

Creating clear domain models, relationships, and lifecycle rules.

In healthcare Representing organizations, providers, patients, referrals, and appointments without losing their operational meaning.

Security architecture

Defining identity, authorization, tenant boundaries, and auditability.

In healthcare Designing appropriate access to patient information across organizations and roles.

Related case study →

Cloud infrastructure

Designing deployment, scaling, environment separation, and recovery.

In healthcare Supporting reliable operation of care-delivery platforms and their integrations.

Related case study →

Integration architecture

Connecting systems through explicit API contracts, events, and webhooks.

In healthcare Supporting partner integrations and coordinated healthcare workflows.

Related case study →

AI evaluation

Evaluating task completion, failure handling, escalation, and operational cost.

In healthcare Testing AI-assisted navigation and workflow support beyond whether a conversation sounds natural.

Related note →

Production reliability

Making failures observable, recoverable, and safe to investigate.

In healthcare Detecting interrupted workflows, preventing duplicate actions, and verifying releases.

How I work

Understand the workflow

Identify the people, decisions, handoffs, exceptions, and desired outcome.

Define the system

Establish domain models, service boundaries, access rules, and integration contracts.

Make trade-offs explicit

Evaluate complexity, reliability, security, delivery effort, and operational cost.

Validate in practice

Use testing, observability, controlled rollout, and production feedback.

Engineering depth, grounded in healthcare workflows

I'm a hands-on architect working across distributed systems, cloud infrastructure, secure integrations, and AI-enabled platforms — most often at the point where software design meets real operational complexity.

More about how I work →

Architecture Notes

Healthcare AIBeyond the Black Box: Architecting Human-in-the-Loop AI for Clinical Decision Support AI RegulationIs Your Clinical AI Feature a Medical Device? The FDA CDS Exemption, Explained for Architects AI RegulationShipping Model Updates Under FDA Rules: What a PCCP Demands of Your Architecture

All notes & articles →

Working on a platform where the workflows have to hold up?

Healthcare platform, production AI, secure integrations, or a legacy system that needs to become dependable — I can help design the blueprint and carry it into production.

Discuss an Architecture Challenge →