Records and team access
Organization, practice, and provider records
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.
Operations
The work behind the platform, in plain language.
See how OneSource OS connects records, enrollment, documents, communications, and daily follow-through around the people responsible for the work.
Operational domains
Credentialing cases
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.
Contract context
Contracting
Keep contracts, fee schedules, participation terms, and follow-up with the related credentialing case.
Payer references and evidence
Payer enrollment distinctions
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.
Documents and review
Documents & Working Store
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.
Connected communications
CommCentral
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.
Daily follow-through
Claims operations & daily routines
Shared lists bring claim checks, follow-up, and approval into one view. OneSource OS supports the team’s work. It does not replace a complete billing platform or professional judgment.
Private access and availability
Team access and connected tools
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.
Guided next actions
Clear next steps
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
Keep the next action beside the record that explains it
A sample work queue keeps practice, provider, enrollment, and follow-up context connected.
Sample information is used here; no client records are shown.
OneSource OSSample workspace
Operations overviewKeep the next action beside the record that explains it
Sample dataJordan Hale, PMHNPEffective date evidence
Needs reviewNorthstar · Main officeERA enrollment
Payer response dueWeekly claim reviewThree related denials
Owner assignedExample workflow
Follow an enrollment journey
Provider and practice record
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.
Credentialing case opens
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.
State-specific payer path
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.
Working Store review
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.
Next action with evidence
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.
Important boundaries
- Payment processing and autopay
- Patient portal
- A public mobile app
- Unrestricted automated claim submission, rebilling, or voiding
- A promise that EHR revenue alone gives a complete cash picture
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.