Operations
See how OneSource OS connects records, enrollment, documents, communications, and daily follow-through around the people responsible for the work.
Core records
Practice, provider, location, and payer records give the rest of the work a consistent starting point. When those details are correct and easy to review, enrollment and billing teams spend less time retyping the same information across portals.
Credentialing and enrollment
Credentialing and enrollment are core areas of the platform. A case keeps requirements, documents, dates, and next steps together, so the team can see what has been submitted, what is still pending, and who owns the next step.
Contract context
Contracting belongs alongside enrollment and network participation. Fee schedules, participation terms, and follow-up work should be easy for authorized staff to find with the related credentialing case.
State and plan distinctions
Enrollment requirements vary by state and plan type. OneSource OS keeps each payer path, note, and date attached to the correct practice and provider instead of blending separate records together.
Documents and review
Practice-specific working folders keep documents with the related work. A packet may suggest information for review, but a person remains responsible for confirming changes before they are saved.
Communications
CommCentral keeps messages, follow-up, and related enrollment or claim work together. Important messages remain under human review.
Daily follow-through
Shared work lists can bring claim checks, follow-up, and sign-off into one view so the team can see what needs attention today. OneSource OS supports the work; it is not being presented as a replacement for a complete billing platform or for professional judgment.
Private organization access
Connections to Microsoft services and invited customer access use separate permissions for each organization. Customer sign-in and organization connections remain private.
Guided next actions
Luma can point out what needs attention, explain why, and suggest a next step. Important actions still require a person to review and approve them. The goal is a clearer work queue, not an autopilot that files on your behalf.
OneSource OS workspace · sample information
Operations overview
A sample work queue keeps practice, provider, enrollment, and follow-up context connected.
Sample information is used here; no client records are shown.
Example workflow
Start with the practice, locations, and providers. Names, NPIs, addresses, and tax information need to match the records used for enrollment and billing.
Open a credentialing case with the required documents, dates, and next steps. Authorized staff can see what has been submitted, what is missing, and who is responsible.
Keep each state and payer path separate, with its own notes and dates. This prevents one enrollment record from being mistaken for another.
An uploaded packet can suggest updates beside the current information. A reviewer can accept, correct, or reject each change before it affects enrollment or billing work.
Luma can suggest a follow-up based on a missing document, signature, or payer response. The person using the system sees the reason for the suggestion and approves any important action.
Name the work area you want to understand and whether you are evaluating the service, the platform, or both.
