Luma Health (coming)

Luma Health patient-messaging integration status + what to expect when it lands.

Updated 2026-04-24 · Edit this page on GitHub

title: "Luma Health (coming)" description: "Luma Health patient-messaging integration status + what to expect when it lands." order: 2 category: "integrations" updated_at: "2026-04-24"

Luma Health integration is on the v1 roadmap but not shipped. This page exists so you can confirm "coming" vs "already shipped" at a glance.

Status

Pending. Blocked on Luma sandbox access; ETA follows Luma's standard partner onboarding cadence.

We post milestone updates to status.ralthealth.com when:

  • Luma grants us sandbox credentials
  • The Rounds ↔ Luma integration enters beta on one tenant
  • General availability ships

What it will do

Bi-directional sync between Luma Health and Rounds:

  • Appointments from Luma → Rounds — Luma-scheduled appointments appear on the Rounds Patient Flow board automatically
  • Flow-state transitions in Rounds → Luma — marking a patient as "checked_in" in Rounds updates Luma's patient-status view
  • Messages from Luma → Rounds notes — SMS / email replies from patients surface as anonymized notes on the appointment
  • No PHI in Rounds — patient identification stays in Luma; Rounds sees only the anonymous P-XXXX code mapped to Luma's patient_id

Workarounds until it ships

Most practices using both tools today:

  • Keep Luma as the source of truth for scheduling
  • Manually create appointments in Rounds at day-start using the front desk's daily schedule printout
  • Use Rounds' Microsoft 365 calendar integration for automatic appointment sync if your Luma push-to-calendar is enabled

If you hit a problem

  • You're evaluating Rounds specifically because of the Luma integration: email support@ralthealth.com — we'll flag you for early-access when sandbox opens
  • You need real-time bi-directional sync now: our short answer is "not in v1"; the long answer involves the workarounds above
  • Other: support@ralthealth.com