Operations
See how OneSource OS connects records, enrollment, documents, communications, and daily follow-through around the people responsible for the work.
In development · Records and team access
Practice, provider, and location records give the team one place to start. Invited users are connected to the correct organization and only see the work they are allowed to use.
In development · Credentialing cases
Track each credentialing case with its requirements, documents, dates, proof, and next steps. The team can see what happened without treating every stage as the same status.
In development · Contract context
Keep contracts, fee schedules, participation terms, and follow-up with the related credentialing case.
In development · Payer references and evidence
Enrollment rules vary by state, payer, plan, provider, location, and billing setup. OneSource OS keeps general payer guidance separate from proof about a specific application.
In development · Documents and review
Working folders keep documents with the correct practice and task. The system may suggest an update, but a person must review it before it is saved.
In development · Connected communications
CommCentral keeps incoming and outgoing messages with the correct practice and mailbox. It also keeps the message history and follow-up easy to find. Access depends on the user’s role and permission.
In development · Daily follow-through
Daily Tasks development connects follow-up to the relevant practice and provider, with clearer labels, dates, and return context. Seeing a task does not grant access to a related record. Broader claim checks and approval routines remain development work, not a replacement for a complete billing platform or professional judgment.
In development · Private access and availability
Invited users, team roles, and connected tools are managed for each organization. Staff can check whether a tool is ready before they depend on it. Customer access remains private.
In development · Guided next actions
Luma can point out what needs attention, explain why, and suggest a next step. A person must review and approve important actions. Luma does not file or send work on her own.
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 organization, practice, locations, and providers that actually apply. Names, NPIs, addresses, and tax information need to match the records used for enrollment and billing; a provider record is attached only when the customer workflow requires one.
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, payer, product, provider, and location path separate, with its own references, evidence, notes, and dates. This prevents general payer guidance or 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.
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.
