OneSource RCM

Luma

Hi there, I’m Luma.

I keep the story of the work together, explain what needs attention, and prepare the next step for your team to review. I’m Luma, built on Azure AI Foundry intelligence, with enterprise-minded safeguards designed into OneSource OS.

This is a public introduction with sample narrations, not access to the private OneSource OS application. Specialist capabilities are planned; examples do not establish active features or product availability. Every narration has a visible transcript.

Listen to Luma · starts when you press Play

Meet Luma

Hi there, I’m Luma.

Narration controls · transcript included

Ready. Narration starts only when you press Play.

Transcript

  1. Hi there, I’m Luma.
  2. This is a public introduction to an experience in development. OneSource OS access remains private, and this narration does not confirm feature availability.
  3. I keep the story of the work together, explain what needs attention, and prepare the next step for your team to review.
  4. Credentialing, enrollment, documents, messages, and claim follow-up often get split across EHRs, payer portals, CAQH, email, and spreadsheets. People spend too much time finding out what already happened.
  5. OneSource OS gives that work a shared home. If you choose narration, my voice is paired with the transcript you see here.
  6. I bring in focused help when it is useful. I show supporting information, and your team remains responsible for important decisions.
  7. I can’t wait to show you how I can help your team finish work faster and with fewer surprises. I’m Luma, built on Azure AI Foundry intelligence, with enterprise-minded safeguards designed into OneSource OS.

OneSource OS workspace · sample information

Communications workspace

Prepare the next follow-up with context attached

See how Luma can summarize an enrollment thread and prepare a draft for review.

Sample information is used here; no client records are shown.

What I speak for

I explain work in OneSource OS, show where information came from, and bring in focused help when it is useful. I am not a clinician, attorney, payer, or compliance officer. When proof is missing, I say what still needs to be confirmed. I only use information the user is allowed to see.

  • Clear explanations of operational work
  • Plain-language summaries of enrollment progress and missing evidence
  • Coordination of specialists under Luma
  • Voice narration paired with a visible transcript
  • Recommendations with supporting information for human review

What I am for

  • Explain what happened in an operational thread
  • Keep useful context together for the people doing the work
  • Surface next actions with supporting information
  • Draft outreach and summaries for human review
  • Coordinate specialists under one consistent experience
  • Stay usable by voice when you choose it
  • Say clearly when evidence or confirmation is still missing

How Luma stays in bounds

  • Guided explanations for website and OS workflows
  • Drafts and recommendations that remain under human review
  • Human-approved communication workflows
  • Access-aware assistance
  • No clinical, legal, or payer decision authority
  • No payment processing or movement of funds
  • No unchecked web research or unsupported private sources

How I show up

Think of an experienced healthcare operations director sitting beside you. I stay calm, direct, patient, and clear about what is known. I use short sentences and show supporting information. If proof is missing, I say so instead of guessing.

Built on Foundry, designed for real clinics

I’m Luma, built on Azure AI Foundry intelligence, with enterprise-minded safeguards designed into OneSource OS.

How I sound in short lines

  • I found three applications waiting on provider signatures.
  • This payer response applies to the Washington enrollment, not the Idaho enrollment.
  • The payer acknowledged the application. I can show you the response and the next follow-up date.
  • The draft is ready for your review. Nothing has been sent.
  • The checklist still needs the W-9 and the collaborating-physician letter before this path can move.
  • I can outline the follow-up. I will not submit it without your approval.

I avoid exaggerated confirmations, invented effective dates, and language that makes a recommendation sound like an approved action.

Sample moments

Illustrative examples of the experience being developed, not evidence of active workflows or available specialist agents.

  • Luma summarizes what is blocking a credentialing case and what to do next.
  • A patient-insurance outreach draft is prepared for your review before it can be queued.
  • Ask where something lives and Luma points you to the right workspace.
  • Vero helps check verification information without taking decision authority.
  • When access is not allowed, Luma protects the information and explains the limit.

Meet Luma’s specialist capabilities

Specialists under Luma

I remain the main personality. Aster, Vero, and Aven describe planned areas of specialist assistance within the same experience. They are not being presented as active autonomous agents. Access checks remain separate from AI recommendations.

Planned · Guided workflows and education

Aster

Guided workflows, onboarding, and education so operators know what to do next without leaving the workspace.

Planned · Verification and audit support

Vero

Verification, audit, and compliance clarity that helps teams check supporting information without inventing authority.

Planned · Workflow and task coordination

Aven

Workflow and task coordination that surfaces stalled work and next actions for review.

Design principle · Access before assistance

Security & Privacy Guard

Access permissions are checked independently of Luma’s recommendations. AI assistance does not grant access to protected information. This is a system safeguard, not a separate personality or a certification claim.

Listen to Luma · starts when you press Play

My specialist team

Hi there. I’m Luma. Let me introduce the specialist capabilities being planned.

Narration controls · transcript included

Ready. Narration starts only when you press Play.

Transcript

  1. Hi there. I’m Luma. Let me introduce the specialist capabilities being planned.
  2. I remain the main personality. These are planned areas of focused help, not a claim that autonomous specialist agents are active or generally available.
  3. Aster is planned for guided workflows, onboarding, and education. Vero is planned for verification and audit clarity. Aven is planned for workflow and task coordination. Each recommendation remains a starting point for human review.
  4. Access permissions are checked independently of my recommendations. AI assistance does not grant access to protected information.
  5. These helpers are part of Luma, not separate products. I explain what each one does and when a person needs to step in.
  6. I can’t wait to show you how this team can help operators move faster without losing control. I’m Luma, built on Azure AI Foundry intelligence, with enterprise-minded safeguards designed into OneSource OS.

Hear Luma explain the work

How I may sound day to day

Hear sample operational alerts using fictional names, with every word available in the transcript.

Listen to Luma · starts when you press Play

Sample alert · onboarding gaps

I reviewed yesterday’s new onboarding files and found the following gaps.

Sample alert · fictional names

Ready. Narration starts only when you press Play.

Transcript

  1. I reviewed yesterday’s new onboarding files and found the following gaps.
  2. For sample provider Jordan Hale, the collaborating-physician letter is still missing, and the state license upload is an older PDF that expires before the requested effective date.
  3. For sample practice Northriver Behavioral, the W-9 legal name differs from the group NPI record on file.
  4. I recommend collecting the corrected packet before the payer checklist is marked ready. Nothing has been sent.

OneSource OS interest

Tell us what you want to follow.

OneSource OS is being shaped around the operational work OneSource handles every day. Share what caught your attention and whether you want occasional updates, a private discussion, or a future-fit conversation.

This form does not create an OS account or promise access, timing, features, or pricing. Do not include PHI or patient-specific details.

What are you interested in?

Select all that apply.