Practice & provider operations
Unified practice, provider, location, and payer records that give the team one reliable operational view.
OneSource OS
The operating system for RCM teams
One workspace for practices, providers, credentialing, communications, documents, and guided AI assist — so day-to-day work stops living across spreadsheets, inboxes, and disconnected tools.
Idle
What OneSource OS actually is
OneSource OS is a shared operational workspace for RCM organizations. It brings practice and provider records, credentialing and contracting, communications, documents, daily routines, and guided assistance under Luma into one connected view. The software keeps context together while accountable people remain responsible for decisions.
Listen to Luma · starts when you press Play
What OneSource OS is
Hi there — I’m Luma. Here’s what OneSource OS brings together.
Luma narration · transcript included
Idle
Ready. Narration starts only when you press Play.
Transcript
- Hi there — I’m Luma. Here’s what OneSource OS brings together.
- OneSource OS is a shared workspace for RCM organizations, bringing practices, providers, credentialing, communications, documents, and guided assistance together.
- It exists so teams can follow the same story without rebuilding it from inboxes and spreadsheets. It complements the clinical and payment systems your team already uses.
- OneSource RCM remains the human service. OS gives that work a durable home, with me helping your team follow the thread.
- I make recommendations with supporting information. A person reviews and approves important actions.
- If you want OneSource OS updates, join the update list on this site. I’m Luma — built on Azure AI Foundry intelligence, with enterprise-minded safeguards designed into OneSource OS.
Service and software, working together
OneSource RCM is the revenue cycle service: people who own billing, credentialing, denials, and practice-operations follow-through with you. OneSource OS gives that work a durable home, with organization workspaces, clear status, governed outreach, reviewable documents, and evidence-based next steps. The service is available today; product access remains private.
Who these pages are for
Practice owners, office managers, and clinical leaders who feel the daily rebuild across portals and spreadsheets and want to understand the OneSource OS approach. OS complements the clinical, payment, and communication systems teams already use. Recommendations remain under human review. If you need full RCM ownership today, start with services.
Capabilities
Connected capability areas that keep RCM operational work in one place.
Credentialing & contracting
Case workflows, trackers, status visibility, and guided create/update — built for day-to-day credentialing work.
CommCentral
Central communications hub for inbound triage and governed outreach — moving ops off scattered inboxes and ticket tools.
Documents & Working Store
Secure document handling with practice-bound working folders, review, and check-in, built for real clinic workflows.
Daily work & routines
Shared operational lists and practice cadences — claim checks, follow-ups, sign-off — so “what needs attention today” is visible.
Luma
In-product intelligence that guides, drafts, and explains — never silently acts. Luma is the primary assistant; specialists support when useful.
Guidance & support
In-product help (Lifeline) and structured support intake so operators get answers without leaving the workspace.
Tenant control plane & connectors
Connections, consent, organization setup, and customer identity foundations designed to keep each practice workspace separate. Customer access remains private.
Service and software
OneSource RCM delivers the service. OneSource OS connects the operating record.
The platform reduces reconstruction across enrollment, documents, communications, and claims follow-through.
Operational software
Hold the thread across portals, packets, and follow-through.
OneSource OS helps authorized people stop reconstructing the work from inboxes and spreadsheets.
Photo: Unsplash
Feature highlights
Entity workspaces
Workspaces for practices, providers, locations, and payers — durable operational identity instead of reinventing demographics in every portal.
Credentialing cases & trackers
Cases and supporting evidence stay attached to the correct provider, location, payer product, and next action so teams can understand what has happened and what still needs follow-through.
CommCentral & governed outreach
Inbound triage plus practice outreach drafts with practice-aware subjects and signatures. Messages remain drafts until a person approves them.
Document vault & Working Store
Secure document handling with practice-bound working folders, review, and check-in. Packets propose fields beside current values — nothing silent.
Dashboards, Hub & navigation
Overview dashboards with widget customization, quick notes, Hub views, and navigation shaped to the work — so today’s attention list stays visible.
Tools, onboarding & sign-in
NPI lookup, address validation, reference information, team onboarding, and employee sign-in, with invited customer access kept behind the appropriate safeguards.
Hear Luma explain the work
Hear Luma explain a capability
Pick a pillar and hear Luma explain how OneSource OS keeps the work connected. The transcript remains visible throughout.
Listen to Luma · starts when you press Play
Practice & provider operations
Hi there — I’m Luma. Let’s talk about practice and provider operations.
Luma narration · transcript included
Idle
Ready. Narration starts only when you press Play.
Transcript
- Hi there — I’m Luma. Let’s talk about practice and provider operations.
- Unified practice, provider, location, and payer records give the team one reliable operational view.
- OneSource OS is designed to keep those core records coherent over time. When something changes, the change should be visible and reviewable.
- Wrong identity facts become next month’s denials. So I stay careful, cite what I can see, and flag gaps instead of guessing.
- Reliable core records make later enrollment and claims work easier to trace. I’m Luma — built on Azure AI Foundry intelligence, with enterprise-minded safeguards designed into OneSource OS.
A concrete example (no PHI)
A PMHNP joins a group that bills in two states. Today the story may live in CAQH, a spreadsheet, a payer portal note, and a personal inbox. OneSource OS keeps the provider record, state-specific enrollment paths, checklist, and outreach together for authorized users. Luma can summarize what is blocking readiness and identify what still needs confirmation.
Where OS fits
- Works alongside your EHR for clinical charting
- Works with clearinghouse pathways for claim transmission
- Connected operational context with guided assistance
- A workspace for healthcare organizations and their teams
- Operational support around revenue work; payment processing is not part of OneSource OS
- Guided intelligence with people accountable for decisions
- Private access with safeguards matched to each organization
Why this is built for RCM work
Built from real RCM work
OneSource RCM already runs credentialing, enrollment, billing, and denial ownership by hand. OS is tested against that reality, with clear status distinctions that keep teams from treating an early milestone as final.
People stay accountable
Software should reduce reconstruction burden. Recommendations remain starting points for review. Consequential actions, including outbound mail, need human approval.
Luma is guided operational intelligence
Luma explains what happened, cites evidence, and stays calm about uncertainty. Specialists Aster, Vero, and Aven support when useful. Luma explains operational work and does not invent network status.
The problem we refuse to romanticize
Operational work is fragmented across EHRs, clearinghouses, payer portals, CAQH, spreadsheets, forms, email, fax, SMS, document folders, and knowledge that lives in people’s heads. The daily tax is reconstruction: What happened? Which enrollment path? Who owns the next step?
OneSource OS exists to keep that context together so teams spend less time rebuilding yesterday and more time finishing today’s work. Safeguards matter — details live on the Security and control page.
Listen to Luma · starts when you press Play
Why OneSource OS exists
Hi there — I’m Luma. Here’s the problem we refuse to romanticize.
Luma narration · transcript included
Idle
Ready. Narration starts only when you press Play.
Transcript
- Hi there — I’m Luma. Here’s the problem we refuse to romanticize.
- Operational work is spread across EHRs, clearinghouses, payer portals, CAQH, spreadsheets, forms, email, fax, and team knowledge.
- The daily tax is reconstruction: What happened? Which enrollment path? Who owns the next step? What is still blocking billing-ready?
- OneSource OS exists as one workspace for that work — with me to guide, draft, and explain — so teams spend less time rebuilding yesterday and more time finishing today’s work.
- I can help your team spend less time reconstructing that history. I’m Luma — built on Azure AI Foundry intelligence, with enterprise-minded safeguards designed into OneSource OS.
Hear Luma explain the work
Hear how Luma may sound day to day
Hear the daily operating voice through sample alerts with fictional names; every word remains 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
Idle
Ready. Narration starts only when you press Play.
Transcript
- I reviewed yesterday’s new onboarding files and found the following gaps.
- 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.
- For sample practice Northriver Behavioral, the W-9 legal name differs from the group NPI record on file.
- I recommend collecting the corrected packet before the payer checklist is marked ready. Nothing has been sent.
Rules the product is forced to obey
Recommendations stay under human review
Luma drafts and advises. People approve consequential actions — including outbound mail.
Authorization before intelligence
Luma only sees what the operator is allowed to see. If access isn’t allowed, it refuses clearly — it never invents permission.
Built-in privacy protection
An invisible system layer that cannot be prompted away — calm, credible, always present.
No autonomous sending
Outbound mail stays governed. A draft moves forward only after an authorized person reviews and approves it.
Clear status language
If the evidence only supports “submitted,” the team should see that status rather than a stronger claim.
Audit-ready sensitive actions
Sensitive actions are traceable. Support access is explicit, not silent.
Ask about OneSource OS
If your organization wants updates or a private conversation about a relevant workflow, tell us what you are evaluating.
Optional · progress updates
Get OS progress updates
Join the update list for progress notes as OneSource OS matures. The list is how interested organizations can hear about future access and private walkthroughs.
Follow OneSource OS
Request updates or a private conversation about the operational problems the platform addresses.