Free 30-minute AI & automation audit with a senior engineer. You keep the notes. Book yours

Use case · Healthcare · United States

Patient self-scheduling and check-in that works with many different EHRs

Self-scheduling, provider search, digital check-in, intake surveys and payments for medical groups, connected to many EHRs through FHIR, HL7 and vendor APIs.

Client details are kept confidential. This use case describes the problem and what we built.

The brief

The client provides patient engagement software to medical groups and health systems in the United States. Its products help patients find and book care, check in before a visit and complete intake forms, while staying in sync with each practice’s EHR.

MultiGenesys engineers worked across the platform: the EHR integration library, scheduling and rules services, the FHIR-based master-data layer and the patient-facing web apps.

The challenge

What needed solving

Every practice runs a different EHR

Medical groups use many different electronic health record systems, each with its own APIs, data formats and scheduling model.

Patients expect to book online

Patients wanted to find a provider, book an appointment, check in and complete forms on their phone, without calling the front desk.

Complex scheduling rules

Which patient can book which slot depends on provider, location, visit type and practice-specific rules that change often.

Patient data in many shapes

Patient, provider and appointment records arrived from each EHR in a different format and needed one consistent model.

The solution

What we built

  1. EHR integration library

    A shared Java library of connectors for major EHR vendors and integration hubs, using FHIR R4 (HAPI FHIR), HL7 v2 and vendor REST APIs, with an EHR validator and a common patient model.

  2. Patient-facing apps

    Angular web apps for self-scheduling, provider search, digital check-in, assessment surveys and tasks, served through a backend-for-frontend layer.

  3. Scheduling and rules

    Appointment, schedule and today's-appointment services with a rule builder that lets practices configure who can book what, and when.

  4. Master data on FHIR

    A master-data service converts platform data to FHIR, stores it in a FHIR server and publishes changes to Kafka on Amazon MSK so other services can react.

  5. Search, events and payments

    OpenSearch-backed provider and appointment search, change-data capture, server-sent events and WebSockets for live updates, and a patient payments module.

  6. Platform engineering

    Java 21 Spring Boot services with shared parent POMs, PostgreSQL and Redis, deployed to AWS through Jenkins with scripted ECS task definitions, plus API, Cypress and performance test suites.

The outcome

What changed

One product, many EHRs

New practices connect through existing EHR adapters rather than a custom build for each one.

Self-service for patients

Patients can find a provider, book, check in and complete intake forms online.

Consistent patient data

A FHIR-based master-data layer gives every service the same view of patients, providers and appointments.

Technology used

  • Java 21
  • Spring Boot
  • HAPI FHIR
  • HL7 v2
  • PostgreSQL
  • Redis
  • Apache Kafka (Amazon MSK)
  • OpenSearch
  • Angular
  • React
  • AWS
  • Jenkins
  • Cypress
  • WireMock

Have a similar problem to solve?

Share a few lines about your project. A senior engineer — not a salesperson — replies within one business day.

Free AI audit Let’s talk