Skip to main content
Industry
Adult Home Care · US Healthcare SaaS
Client
US Healthcare Operator (Under NDA)
Status
Production-Ready Development
Team
Cross-Functional Engineering Team
Technologies
Node.js, TypeScript, React, Flutter, PostgreSQL, AWS, OAuth2/JWT, AES-256, AI/OCR

The Problem We Set Out to Solve

A US healthcare operator approached us to build the next generation of adult home care agency management software — a multi-tenant SaaS that home care agencies could subscribe to instead of running fragmented legacy tools. The problem in adult home care is structural: agencies juggle paper intake forms, separate scheduling tools, third-party EVV apps, manual billing pipelines, and unconnected payroll exports. Compliance breaks down at every handoff. Caregivers can’t verify visits without 4-step workarounds. Billing claims get rejected for missing EVV data. Audit prep takes weeks.

The client needed a unified platform where one agency subscription replaces five disconnected tools — with HIPAA-grade security, federally-mandated EVV compliance, EDI 837/835 billing, and a mobile caregiver app that survives an audit. Built once, sold many times to home care agencies across multiple US states. And critically, they needed AI engineered into the platform from day one — not as a marketing layer over a legacy product, but as a real capability set covering document intelligence, voice-to-text caregiver workflows, predictive scheduling, and risk-pattern detection. The goal: ship a platform that’s structurally ahead of the legacy home-care SaaS competition on launch day.

Project Scope

We are architecting and building a complete 3-module SaaS ecosystem covering the full lifecycle of an adult home care agency.

  • Module 1 — Super Admin Platform: Global governance layer. Multi-tenant provisioning, subscription & billing engine, plan/add-on enforcement, global EVV/AI/payer rule configuration, platform-wide RBAC, audit logging. Zero PHI by design.
  • Module 2 — Agency Dashboard (Web): Tenant-level operational system. Client intake, clinical assessments, scheduling, EVV oversight, service authorization tracking, billing, payroll, compliance reporting, AI document automation. 7+ distinct user roles with RBAC.
  • Module 3 — Caregiver Mobile App (EVV): Field-grade Flutter application. GPS-verified clock-in/out, biometric authentication (Face ID/Touch ID), face-match anti-fraud verification, ADL task documentation, AI voice-to-text visit notes, offline read-only mode for limited connectivity.
  • Multi-Tenant Architecture: Single database instance with strict schema-per-agency isolation. Tenant-aware routing, query scoping at the data layer, zero cross-tenant access enforced at application + database layers.
  • Compliance & Security: AES-256 at rest, TLS 1.2+ in transit, mandatory MFA for platform admins, immutable per-tenant audit logs, encrypted system logs. HIPAA-aligned, 21st Century Cures Act EVV-compliant, CMS Medicaid/Medicare-ready, EDI 837/835 claims integration.
  • AI Automation Layer: OCR/NLP document extraction, voice-to-text caregiver note transcription, grammar cleanup and summarization, risk-flag detection, predictive scheduling, anomaly detection.
Healthcare SaaS Architecture

Our Engineering Approach

1.

Compliance-First Architecture

HIPAA, 21st Century Cures Act EVV, and CMS Medicaid/Medicare requirements drove the data model, the deployment topology, and the audit-log design from week one — not bolted on post-build.

2.

Schema-Per-Tenant Isolation

Each agency tenant gets a dedicated database schema within a single database instance. Tenant-aware routing and query scoping enforce zero cross-tenant data access at both application and database layers.

3.

Zero-PHI Governance Plane

The Super Admin platform handles tenant provisioning, subscriptions, and platform configuration — but never accesses, processes, or stores Protected Health Information. PHI stays exclusively inside tenant schemas, by architecture not by policy.

4.

Caregiver Field Security

Biometric login (Face ID/Touch ID), face-detection at clock-in/out for anti-fraud, GPS-verified visit location, device fingerprinting, and JWT-based session security on a Flutter app engineered for unreliable field network conditions.

5.

Integration-Ready Billing

EDI 837 (claims) and EDI 835 (remittance) integrations designed in from the data model, not retrofitted. Payer-specific billing rule engine. Payroll export pipelines for OT, holiday, and weekend rule handling.

AI · DIFFERENTIATION

AI Embedded Across the Stack — Not Bolted On

Legacy home-care SaaS competitors typically retrofit AI as a marketing layer over a 10-year-old product. We’re engineering AI into this platform from the data model up — six concrete capabilities that reduce caregiver documentation burden, surface clinical risk earlier, automate the highest-error data-entry steps, and remove operational friction across the agency.

01

Document Intelligence (OCR + NLP)

Extracts structured data from insurance cards, prior authorizations, medical intake forms, and uploaded clinical documents automatically. Eliminates one of the highest-error data-capture points in the agency workflow and reduces intake time from hours to minutes.

02

Voice-to-Text Caregiver Notes

Caregivers dictate visit notes in the mobile app; AI transcribes in real time, applies grammar cleanup, and structures the output for the clinical record. Designed so caregivers can document while still in the client’s home — not three hours later from memory.

03

Clinical Risk-Flag Detection

AI analyses visit notes, ADL completion patterns, and visit-frequency signals to flag clinical risk indicators — fall-risk changes, medication non-adherence patterns, hospitalization likelihood — and routes them to RN supervisors before they become incidents.

04

Predictive Scheduling

AI suggests optimal caregiver-client matches based on geographic proximity, skill match, language preferences, historical care quality, and availability — instead of coordinators solving the matching problem manually on a spreadsheet for every shift.

05

EVV Anomaly & Fraud Detection

EVV streams are continuously analysed for anomalies: clock-in patterns that don’t match GPS data, unusual visit-duration spikes, suspiciously identical visit notes across clients — surfacing potential fraud or data quality issues before payer audits do.

06

Note Summarisation & Quality Scoring

Long-form caregiver notes are summarised for RN review; documentation quality is scored against compliance standards; flagged notes are routed for caregiver coaching. Improves the audit-readiness of the clinical record over time without manual chart review.

Design Challenges We’re Solving

Multi-Tenant PHI Isolation

Schema-per-agency partitioning enforced at the database layer with middleware validation that runs before any business logic executes — making cross-tenant data exposure architecturally impossible, not just policy-prevented.

EVV Anti-Fraud Verification

Combined GPS, biometric, and face-detection verification at each caregiver clock-in/out. Designed to satisfy state-level EVV adopter/aggregator requirements while remaining usable in the field.

Field-Grade Offline Mode

Caregivers visit clients in homes with unreliable cellular coverage. Mobile app caches visit schedules and client details for offline read-only access, with EVV actions queued until reconnection. Sandboxed local storage, encrypted at rest.

Platform Scope & Design Targets

The platform is in production-ready development. The numbers below describe architectural ambition and engineering scope — not historical production metrics.

3 Modules

3 Integrated Modules

Super Admin governance layer, multi-tenant Agency Dashboard, and Caregiver Mobile App — built to work as one product, sold as one subscription.

Compliance

6+ Compliance Frameworks

HIPAA Privacy & Security Rules, 21st Century Cures Act EVV, CMS Medicaid/Medicare, EDI 837/835, NIST Cybersecurity Framework, HL7, plus state-specific home care regulations.

User Roles

8 Distinct User Roles

Platform Owner, Super Admin (Operations / Billing / Compliance), Support Admin, Agency Admin, Coordinator, RN/Clinical Supervisor, Billing Specialist, Payroll Specialist, Caregiver — each with granular RBAC.

Mobile EVV

Multi-Factor EVV

GPS + biometric + face detection at each clock-in/out, capturing caregiver identity, client identity, location, timestamps, services delivered, and ADL completion for full EVV mandate compliance.

Engagement Status

This platform is in production-ready development for a US healthcare operator under NDA. Architecture, compliance design, and module scope reflect engineering decisions made and code shipped to staging. Live production metrics will be added once the platform launches.

Why This Case Study Matters

If you’re evaluating engineering partners for a regulated healthcare SaaS, three things matter more than any vendor’s sales pitch:

  • Have they actually built for HIPAA-grade compliance before? Our 5+ year Litigation Management System for Nepal’s central bank (read NRB case study) was built to the same architectural bar: maker-checker workflows, immutable audit logs, role-based partitioning, deployment isolation, bilingual support. Healthcare regulatory architecture isn’t conceptually different from central-bank regulatory architecture — we’ve been shipping it for 15 years.
  • Can they actually do multi-tenant SaaS at scale? Our DiNePa Digital Negotiation Platform (read DiNePa case study) has been live for 5+ years at 99.4% uptime for European enterprise procurement with strict tenant isolation. The schema-per-tenant pattern we’re using on this healthcare platform is the same pattern that hasn’t had a cross-tenant incident in 5 years of EU production.
  • Are they engineering it right now — or just pitching from a deck? Healthcare SaaS expertise can’t be faked. We’re writing the code, making the schema decisions, designing the EVV anti-fraud flow, and integrating EDI 837/835 right now. If you want to review specific architecture decisions before our first call, we can walk through them on a screenshare.
Discuss Your Healthcare SaaS Project
Healthcare SaaS Engineering
E Multitech Solution Healthcare HIPAA practice

Ship a healthcare SaaS that survives the HIPAA auditor on the day it goes live.

3
Integrated modules
Super Admin · Agency · Caregiver
HIPAA
Architected · BAA-ready
SOC 2–aligned controls
6
Embedded AI capabilities
across the stack
EVV
21st Century Cures Act
EDI 837/835 ready

Tell us your clinical workflow. We’ll tell you the HIPAA architecture we’d use on day one.

Direct line, founder-to-founder +977 9851038796 Roshan Subedi, Founder & MD · 48-hour reply, engineer-only