OneSource OS
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.
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.
Development update ·
Recent development is focused on making everyday administrative work easier to follow. These updates describe work in development, not a public release or a promise that every workflow is available to invited users.
In development
Recent work connects follow-up tasks to the relevant practice and provider, preserves selection and return context, and makes task labels and dates easier to read. Related records still require their own access checks.
In development
A bounded comparison helps reviewers examine selected spreadsheet rows alongside records they are authorized to see. It is preparation for review, not an automatic import, and does not create or change practice records.
In development
Navigation and workspace layouts are being refined across screen sizes so teams can keep the relevant work and context in view. Responsive layout work does not mean a separate mobile app is available.
OneSource RCM services are available today. OneSource OS access remains private. There is no public launch date or self-service product access announced here.
Listen to Luma · starts when you press Play
Hi there, I’m Luma. Here’s what OneSource OS brings together.
Luma narration · transcript included
Ready. Narration starts only when you press Play.
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.
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.
The main parts of administrative work OneSource OS is being developed to connect. Descriptions do not establish availability in a particular workspace.
Keep the right practice, provider, location, and team information together so staff can start with the same facts.
Track applications, payer requirements, supporting documents, status, and follow-up for each enrollment.
Keep incoming and outgoing messages with the correct practice, mailbox, and follow-up task.
Store working documents with the correct practice and review changes before saving them.
Use shared lists for claim checks, follow-up, and approval so the team knows what needs attention today.
Luma explains work, prepares drafts, and suggests next steps. She does not take important actions without a person reviewing them.
Get help and send a support request without leaving the workspace.
Set up team access and check the tools connected to each private workspace.
Service and software
The platform reduces reconstruction across enrollment, documents, communications, and claims follow-through.
Operational software
OneSource OS helps authorized people stop reconstructing the work from inboxes and spreadsheets.
Photo: Unsplash
These highlights describe the product direction and workflows being developed. Availability is not implied; see the current development update above.
Keep important practice, provider, location, and payer details in one place instead of rebuilding them in every portal.
Keep each case and its records with the correct provider, location, payer plan, and next step.
Inbound triage plus practice outreach drafts with practice-aware subjects and signatures. Messages remain drafts until a person approves them.
Review working documents in practice folders. Suggested updates appear beside the current information before anyone saves a change.
Use dashboards, quick notes, and shared views to keep today’s work easy to find.
Use NPI lookup, address checks, payer information, team setup, and secure sign-in. Invited users only see the work allowed for their role.
See which tools and communication services belong to a workspace and whether they are ready to use.
Hear Luma explain the work
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
Hi there, I’m Luma. Let’s talk about practice and provider operations.
Luma narration · transcript included
Ready. Narration starts only when you press Play.
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.
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.
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 is designed to explain what happened, cite evidence, and stay clear about uncertainty. Aster, Vero, and Aven represent planned specialist capabilities, not a claim of active autonomous agents. Luma does not invent network status.
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
Hi there, I’m Luma. Here’s why OneSource OS exists.
Luma narration · transcript included
Ready. Narration starts only when you press Play.
Hear Luma explain the work
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
I reviewed yesterday’s new onboarding files and found the following gaps.
Sample alert · fictional names
Ready. Narration starts only when you press Play.
Luma prepares drafts and suggestions. People approve important actions, including outgoing mail.
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.
Access permissions are checked independently of Luma’s recommendations. AI assistance does not grant access to protected information.
Outgoing mail stays as a draft until an authorized person reviews and approves it.
If the evidence only supports “submitted,” the team should see that status rather than a stronger claim.
Sensitive actions are traceable. Support access is explicit, not silent.
If your organization wants updates or a private conversation about a relevant workflow, tell us what you are evaluating.
OneSource OS interest
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.
