How does Lumin Connect avoid double-handling for care professionals?

One of the biggest practical concerns care providers raise about adopting a new platform is double-handling: needing staff to type information into Lumin and then also into the provider's existing care management software. Lumin's answer to this is Lumin Connect, an integration layer that lets the two systems share data so staff only enter information once.

What double-handling looks like (and why it's a problem)

Without integration:

• A care coordinator enters a new participant's details in the care management software
• The same details are then entered again in Lumin's Community Management Portal
• An appointment is scheduled in the care management software
• The reminder is then created again in Lumin so the participant sees it on their CareHub
• An alert from Lumin (missed medication reminder, emergency) needs to be manually logged in the care management software for clinical compliance For a care provider managing 50, 200, or 2,000 participants, this duplicated work is significant — and it's where errors creep in.

What Lumin Connect does

Lumin Connect is the integration platform that links Lumin to other systems the provider already uses. The most common integrations for care professionals are with care management software:

• AlayaCare
• AutumnCare
• iCareHealth
• Others, depending on the provider's stack Lumin Connect handles:
• Participant data sync — adding, updating, removing participants in both systems
• Appointment and reminder sync — appointments scheduled in care management flow as reminders to the participant's CareHub
• Alert and event flow — events on the Lumin platform (alerts, check-ins, communications) flow into the care management system's record
• Authentication — staff use their existing care management login (SSO) for Lumin too, no separate password

How it works in practice

A typical flow with Lumin Connect:

1. Care coordinator schedules a home visit in their care management software. The appointment automatically appears as a reminder on the participant's CareHub.
2. The participant taps "Got it" on the reminder. The acknowledgement flows back to the care management software.
3. On the day of the visit, the care worker arrives. If they want to check in remotely beforehand, they can call the participant from the Community Management Portal — but the appointment, the participant's details, the visit notes all live in their normal care management interface.
4. After the visit, the care worker logs the visit in care management. Lumin reflects the activity without anyone needing to log it twice. The result: staff work in their familiar care management software, and Lumin is the participant-facing surface.

What's required for Lumin Connect to work

• The provider's care management software supports integration. Lumin Connect has pre-built connectors for the most common platforms. For less common ones, custom integration is possible but scoped as a project.
• The provider's IT (or care management vendor) is willing to enable the integration. This is usually straightforward but does involve a conversation with the care management vendor.
• A small initial setup project, typically 2–8 weeks depending on complexity, during which Lumin Connect is configured, mappings are agreed, and the data flow is tested in a controlled cohort.

What's not in scope

• Clinical records. Lumin Connect syncs operational data (participants, appointments, reminders, alerts) but doesn't move clinical assessments, care plans, or detailed notes. Those stay in the care management system, where they belong.
• Billing. Lumin's billing for the platform is separate from care management's billing for services. They don't need to talk to each other.
• Real-time everything. Most sync is near-real-time (within seconds), but some events are batched. Lumin Connect's specific sync behaviour is configured during setup based on what the provider needs.

Getting Lumin Connect set up

Contact Lumin Support. Typical conversation:

1. What care management system you use — Lumin checks for an existing connector
2. What sync behaviour you'd like — full sync, partial, one-way, two-way
3. Pilot cohort — usually 10–30 participants to test the integration before broader rollout
4. Production rollout — once piloted The integration is included in Enterprise village/care provider plans and available as a module on other tiers.