Practice and provider records
Keep the right practice, provider, location, and team information together so staff can start with the same facts.
OneSource OS
One place for the work behind revenue cycle management
OneSource OS brings practice records, credentialing, payer information, messages, documents, and follow-up into one private workspace. Your team can see what happened, what is missing, and what comes next.
Idle
What OneSource OS actually is
OneSource OS is a shared workspace for RCM teams. It keeps practice and provider records with credentialing, payer information, messages, documents, and daily follow-up. People still review the facts and make the 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 service team that handles billing, credentialing, denials, and practice operations with you. OneSource OS gives that work one organized home. It keeps status, messages, documents, and next steps easy to review. OneSource RCM services are available today. Access to OneSource OS is still private.
Who these pages are for
These pages are for practice owners, office managers, and clinical leaders who are tired of piecing work together across portals, inboxes, and spreadsheets. OneSource OS works beside the clinical, payment, and phone systems your team already uses. People review every important recommendation. If you need RCM help now, start with our services.
Capabilities
The main parts of RCM work that OneSource OS brings together.
Credentialing & contracting
Track applications, payer requirements, supporting documents, status, and follow-up for each enrollment.
CommCentral
Keep incoming and outgoing messages with the correct practice, mailbox, and follow-up task.
Documents and working folders
Store working documents with the correct practice and review changes before saving them.
Daily work & routines
Use shared lists for claim checks, follow-up, and approval so the team knows what needs attention today.
Luma
Luma explains work, prepares drafts, and suggests next steps. She does not take important actions without a person reviewing them.
Guidance & support
Get help and send a support request without leaving the workspace.
Team access and connections
Set up team access and check the tools connected to each private workspace.
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
Practice and provider workspaces
Keep important practice, provider, location, and payer details in one place instead of rebuilding them in every portal.
Credentialing cases & trackers
Keep each case and its records with the correct provider, location, payer plan, and next step.
CommCentral and approved 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
Review working documents in practice folders. Suggested updates appear beside the current information before anyone saves a change.
Dashboards, Hub & navigation
Use dashboards, quick notes, and shared views to keep today’s work easy to find.
Tools, onboarding & sign-in
Use NPI lookup, address checks, payer information, team setup, and secure sign-in. Invited users only see the work allowed for their role.
Connected tools and availability
See which tools and communication services belong to a workspace and whether they are ready to use.
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.
- Practice, provider, location, and payer records give the team one reliable place to start.
- OneSource OS keeps those records together over time. When something changes, the team can see and review the change.
- 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.
An example using fictional information
A psychiatric nurse practitioner joins a group that bills in two states. The work may be split across CAQH, a spreadsheet, payer portals, and several inboxes. OneSource OS keeps the provider record, state payer information, enrollment cases, documents, and approved messages together. Luma can explain what needs attention without treating an early step as final approval.
Where OS fits
- Works alongside your EHR for clinical charting
- Works with clearinghouse pathways for claim transmission
- Connected records with guided help
- 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 the time spent rebuilding old work. Recommendations are a starting point for review. A person must approve important actions, including outgoing mail.
Luma helps explain the work
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.
Why teams need a clearer system
RCM work is spread across EHRs, clearinghouses, payer portals, CAQH, spreadsheets, forms, email, fax, text messages, and shared folders. Staff waste time finding out what happened, which enrollment path applies, and 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 why OneSource OS exists.
Luma narration · transcript included
Idle
Ready. Narration starts only when you press Play.
Transcript
- Hi there, I’m Luma. Here’s why OneSource OS exists.
- Operational work is spread across EHRs, clearinghouses, payer portals, CAQH, spreadsheets, forms, email, fax, and team knowledge.
- Teams lose time answering basic questions. What happened? Which enrollment path applies? Who owns the next step? What still needs to be done before billing can begin?
- 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 built into the product
Recommendations stay under human review
Luma prepares drafts and suggestions. People approve important actions, including outgoing mail.
Check access first
The system checks the user, organization, role, and permission before showing protected information. If access cannot be confirmed, the system does not show the information.
Built-in privacy protection
An invisible system layer that cannot be prompted away, calm, credible, always present.
No autonomous sending
Outgoing mail stays as a draft until 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.
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.