Richmond and Central Virginia · nationwide service
Medical billing services for Richmond practices
Richmond practices need a clean distinction between Virginia PRSS enrollment, individual MCO participation, rendering-provider setup, and the EHR records used to submit claims. OneSource RCM connects enrollment, configuration, claim follow-up, and aging work instead of treating each as a separate ticket.
Photo: Unsplash
Richmond practice context
What changes the work in Richmond
OneSource serves Richmond practices remotely from Baltimore County, Maryland, connecting local payer and enrollment requirements to the revenue workflow.
The enrollment layer
Virginia uses PRSS for enrollment and revalidation. Fee-for-service enrollment does not replace separate MCO contracting or credentialing.
The product layer
A payer name is not enough. Richmond practices need the exact product, network, service location, rendering-provider relationship, and effective date reflected in the billing workflow.
The transaction layer
Clearinghouse acceptance, payer receipt, adjudication, remittance, and payment are different checkpoints. The useful question is where the transaction stopped and who owns the next action.
The practice layer
Identify the PRSS status, managed-care plans, provider types, and first claims affected.
Richmond payer path
Connect the approval record to the first payable claim.
The review follows the provider, entity, location, product, and transaction evidence that applies in Virginia. It does not rely on a single portal label or a generic national checklist.
Virginia Medicaid / PRSS enrollment guidance
Virginia payer evidence that affects Richmond practices
Virginia uses PRSS for enrollment and revalidation. Fee-for-service enrollment does not replace separate MCO contracting or credentialing. Verify the current payer instructions for the provider type and product before acting.
Enrollment classification
Separate fee-for-service, MCO-only, and combined participation requirements before starting.
Location and specialty
Match provider type, specialty, service locations, licenses, and certifications to the submitted record.
MCO evidence
Track each managed-care contract and effective date separately from PRSS approval.
Practice patterns we can evaluate in Richmond
These are operating situations, not claims that OneSource already represents a particular practice or payer relationship in the city.
Enrollment and growth
Behavioral-health groups navigating PRSS plus several managed-care plans
Payer mix and operations
Primary-care and outpatient groups adding rendering providers or service locations
Revenue cleanup
Virginia practices with approvals that have not translated into clean adjudication
Conversion without a canned intake
The first review should narrow the problem.
A useful inquiry identifies the entity, provider type, service locations, payer products, EHR, clearinghouse, and the first transaction that did not behave as expected. Do not include patient-specific information in the website form.
- Enrollment or network-participation evidence
- Configuration, claim, authorization, or remittance symptom
- The operational owner and deadline, if one exists
Current-source boundary
Payer rules change. The work starts by reopening the source.
The public payer context on this page is a planning aid. The payer or government program's current documentation and the practice's executed agreements control eligibility, enrollment, participation, billing, and payment.
Richmond practice review
Start with the workflow that is costing attention or cash.
Identify the PRSS status, managed-care plans, provider types, and first claims affected.
Review the revenue path for your Richmond practice
Identify the PRSS status, managed-care plans, provider types, and first claims affected.