Modern Healthcare Platform

Modern Healthcare Platform

Incode Group delivers a production-ready, self-hosted healthcare solution built on Medplum (open-source healthcare developer platform) plus Foo Medical (ready-to-fork medical practice sample webapp). We customize backend + frontend, integrate with third-party healthcare systems, and deploy to your infrastructure so you ship faster without rebuilding an EHR from scratch.
Summarize with:

Overview

Medplum is an open-source, API-first platform for building compliant healthcare apps, including: identity/auth (OAuth/OpenID/SMART-on-FHIR), a FHIR-based clinical data repository, SDKs, an admin/developer web app, server-side automation (“Bots”), and a React UI component library.

Medplum is an open-source, API-first platform for building compliant healthcare apps, including: identity/auth (OAuth/OpenID/SMART-on-FHIR), a FHIR-based clinical data repository, SDKs, an admin/developer web app, server-side automation (“Bots”), and a React UI component library.

Foo Medical is an open-source “medical practice sample app” built on Medplum. It includes patient registration/authentication, health records (labs, meds, vaccines, vitals), patient-provider messaging, care plans, and scheduling, fully represented in FHIR. It’s explicitly designed to be cloned/forked and customized for your business needs.

Problem

Healthcare teams need to ship compliant software fast, but building a custom EHR/clinical backend from scratch is slow and expensive. Interoperability (FHIR/SMART/HL7), secure access control, workflow automation, and integrations (labs, prescribing, billing, documents) quickly become a major engineering lift.

Solution

Incode Group delivers a self-hosted solution built on Medplum plus the Foo Medical starter app so you start with production-grade building blocks (FHIR datastore, auth, admin tooling, automation, UI components) and a working clinical webapp baseline. We customize both backend and frontend, implement workflows and integrations, and deploy everything on your infrastructure accelerating time-to-market while keeping you in control of the codebase.

Features

FHIR-Native Clinical Data Platform
Built on a standards-based FHIR data model to store and manage patients, encounters, observations, medications, labs, and care plans. This ensures consistent, interoperable clinical data across the entire platform.
Secure Identity and Access Management
Supports OAuth/OpenID authentication with role-based access control for patients, clinicians, and administrators. Access policies can be tailored to meet organizational and regulatory requirements.
Ready-to-Use Clinical Workflows
Includes patient registration, health records, care plans, patient-provider messaging, and appointment scheduling. These workflows provide a proven functional baseline for healthcare applications.
Enterprise Master Patient Index (EMPI)
Provides the foundation for building a robust Enterprise Master Patient Index to manage patient identity across fragmented systems. Supports patient record matching, human-in-the-loop review, and controlled merging based on configurable rules.

Benefits

Faster Time-to-Market
Accelerates healthcare product delivery by leveraging a production-ready, standards-based platform instead of building core systems from scratch. Teams can focus on business differentiation rather than foundational infrastructure. This significantly shortens development cycles and reduces time-to-launch risk.
Unified and Accurate Patient Identity
Unifies patient records from multiple, fragmented systems into a single, trusted patient profile. This reduces duplicate records, mismatched identities, and inconsistencies across clinical and administrative systems. As a result, organizations gain higher data integrity and more reliable patient information at scale.
Interoperability by Design
Built on FHIR standards to ensure seamless data exchange across internal systems and external partners. This reduces integration complexity and improves compatibility with existing healthcare ecosystems. The platform remains future-proof as interoperability requirements evolve.

Architecture

Medplum is a FHIR R4–native healthcare platform built around a Node.js API server and a React-based Admin UI, backed by PostgreSQL and Redis. It supports real-time features (chat), integrations (AWS), and healthcare interoperability standards (FHIR, HL7v2)

‍

Overall architecture

‍

Components

  • Medplum Server (API + backend services) — Node.js + TypeScript
  • Medplum App (Admin UI) — React + TypeScript
  • PostgreSQL 16 — primary storage for FHIR resources (JSONB-heavy)
  • Redis 7 — caching, sessions, background jobs/queues

Key capabilities

  • FHIR REST API + GraphQL
  • Bulk FHIR export ($export)
  • FHIR Subscriptions
  • Real-time chat via WebSockets
  • Multi-tenant isolation by Project

Authentication and authorization are implemented using OAuth 2.0, OpenID Connect, and SMART-on-FHIR standards. The system uses JWT tokens for session management, bcryptjs for password hashing, and Passport.js strategies for flexible identity provider integrations. Security best practices are enforced through Helmet headers, CORS configuration, rate limiting, and full audit logging via the FHIR AuditEvent resource.

‍

Frontend overview

‍

The Medplum Admin App is built with React 19 and TypeScript, bundled using Vite 7 and managed with React Router 7. The UI layer leverages Mantine 8 for component styling and layout, Tabler icons for visual consistency, and Monaco Editor for embedded code editing. The application integrates tightly with the Medplum SDK, including @medplum/core for API communication, @medplum/react for over 60 prebuilt healthcare-focused components, and @medplum/fhirtypes for strong TypeScript typing across FHIR models. Testing is handled using Jest and React Testing Library.

The FooMedical patient portal follows a similar frontend architecture, using React 19, TypeScript, and Vite. It extends the Medplum SDK to provide patient-facing functionality including appointment booking, doctor chat, medical history access, prescription management, and health dashboards. Visualization capabilities are supported via Chart.js and react-chartjs-2, while the Mantine component library ensures consistent UI/UX across administrative and patient experiences.

The ecosystem is supported by a structured package architecture including @medplum/server for backend logic, @medplum/app for the Admin UI, @medplum/core and @medplum/fhirtypes for FHIR communication and typing, @medplum/react and @medplum/react-hooks for reusable frontend logic, @medplum/mock for testing environments, @medplum/cli for operational tooling, and @medplum/hl7 for HL7v2 protocol support.

Video

Questions & Answers

Is the platform compliant with healthcare regulations?

The foundation is built on industry standards and secure identity management principles. Role-based access control, auditability, and infrastructure-level security can be configured to align with regional regulatory requirements. Final compliance depends on implementation and deployment policies, which we support during delivery.

Who is this platform designed for?

The platform is suitable for digital health startups, healthcare providers, telemedicine platforms, and enterprises modernizing legacy systems. It is especially valuable for organizations that require interoperability, flexibility, and infrastructure ownership.

Is This the Right Solution for You?

Leave your email below
and we will contact you soon to discuss further details.

Customer Ratings & Reviews

4.5
Based on
1
reviews
Write a review
5 stars
1
4 stars
0
3 stars
0
2 stars
0
1 star
0
Rate your experience
0.0
The score may evaluate scalability, security, integrity, performance, maintainability, or even your general impression.
By submitting this form, you acknowledge that you agree with Incode Group Privacy Policy
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
4.5
February 10, 2026
Exactly what we needed instead of a rigid EHR. FHIR-native backend, clean UI, and smooth deployment on our own servers.
Author:
Mark R.

Other related solutions