DSO

One operating model across your offices.

Bring a dental service organization’s agents, patient records and operating visibility into one platform, with location access and human approval built into the work.

Invite-only · Built around your practice’s permissions

See the workflow
ILLUSTRATIVE WORKSPACE
OttoVeraStellaLuna
Harbor
Pine
Eastlake
LOCAL CONTEXT · DEFINED ACCESS

Meridian Dental Partners

Location review

Prepared by agents. Controlled by your team.

The work behind the work

A dental service organization needs a consistent way of working across locations that have different teams and histories. A policy document can describe the standard, but people still have to apply it to reminders, verification, claims and exceptions.

The central business office needs to see the work without losing the local detail. Regional operators need to know where a process is working and where a new location still needs supervision.

Omnira Dental combines the same agents with an organization, practice and location model. Shared records and roll-up reporting support central visibility. Role-based access, local operating details and action permissions define how the work is carried out.

Practice management across your DSO

01

Put the standard into workflows

Define the reminder timing, booking rules, verification process and approval responsibilities your organization wants to use. Confirm how organization defaults and location adjustments are applied before describing a setting as centrally enforced.

02

Keep billing connected to the source

Vera works eligibility, claims, denials, posting and reconciliation. The central team needs the patient and location context for each exception. Prepared work can then be reviewed by authorized people rather than sent around as disconnected exports.

03

Review performance by location

Owners can inspect production and collections across locations and drill into an office. Otto reports operating measures and agent performance. Combined numbers should lead to a specific workflow question rather than conceal differences between offices.

04

Share payer knowledge

The multi-location design shares payer behavior learning within the organization. A useful correction learned in billing can inform later work. Clinical documentation and the actual payer rules still determine the appropriate claim action.

05

Keep governance explicit

Records carry practice and location context, and access is checked at multiple layers. Actions and access to patient information are logged. Review the BAA, role assignments and data export commitments as part of the organization’s own assessment.

06

Train newly enabled work

New practices and capabilities start supervised for about two weeks. A readiness report shows accuracy by action. The owner chooses what to promote, so a location does not need blanket autonomy to begin using the platform.

A new location enters the operating model

This fictional Meridian example illustrates the intended onboarding process. Migration timing, organization-level controls and rollout terms need a scoped plan.

ILLUSTRATIVE WALKTHROUGH05 / 05
ILLUSTRATIVE WORKSPACE
Otto
Harbor
Pine
Eastlake
LOCAL CONTEXT · DEFINED ACCESS

Roll-up view

Ongoing

Prepared by agents. Controlled by your team.
  1. Andre and the onboarding team identify the records, workflows and reviewers needed for a pilot location.

  2. Hours, providers, rooms, fees and access are reviewed. The organization confirms which defaults and local adjustments are supported.

  3. The location’s enabled capabilities run with human review. Authorized people inspect recommendations and exceptions.

  4. The readiness report informs the owner’s decision. Specific action types can move forward while others remain supervised or off.

  5. The location appears in the permitted reporting picture. Operators follow outstanding issues back to the office and workflow.

Pilot the permissions as well as the work

A rollout should demonstrate what a local front desk user, billing coordinator, provider and owner can each see. Test the access boundaries with the same care as the claim and scheduling workflows.

Local offices also need a clear review path. A person should know which approvals belong to them and which need a central reviewer. Confirm queue filters, regional reporting and permission inheritance as concrete requirements during scoping.

Acquisition migration is a data project as well as a software setup. Review the supported source system, historical records, outstanding balances and any unresolved claims. The two-week training design does not guarantee that every migration can finish within two weeks.

Local context

Different offices. Deliberate boundaries.

Explore an illustrative local configuration. These are fictional offices; the comparison does not expose practice data or promise a particular governance feature.

Fictional offices · illustrative configuration

LOCAL TO HARBOR

8:00 AM opening

Dr. Lena Okafor

Local provider and room rules

SHARED WITHIN THE ORGANIZATION

One patient record

Patient history follows the record. Role and location assignments still govern access.

Prepared first. Permission before action.

Your practice chooses Autonomous, Supervised or Off for each action type. New practices and newly enabled capabilities begin in Supervised mode for about two weeks. Your team approves or rejects recommendations.

A readiness report shows accuracy by action. The owner decides which actions to promote. Some work can remain supervised while other routine actions run autonomously.

The AI interprets and drafts. Tested software performs record changes after permission checks. Every agent action is logged, and supervised work shows what was prepared and why. Clinical decisions and provider signatures stay with clinicians.

The agent prepares the action. An authorized person reviews, edits, approves or rejects it before the record changes.

Interactive explanation · does not change product settings

Organization and location settings

Confirm default inheritance, override rights and authorized reviewers before rollout.

New capabilities

Begin supervised; use readiness evidence to decide each promotion.

Central visibility

Assign access deliberately and inspect the audit trail across the pilot locations.

What we are designing toward

Targets, stated plainly.

These are product design targets, not measured practice results or promised outcomes.

  • Zero AR backlog is the design target.
  • 40–60% fewer claim rejections is the design target.
  • 15+ admin hours back each week is the design target.

Where your team takes over.

  • Organization membership does not create unrestricted cross-location clinical access.
  • No promise of SSO, BI connectors, regional filters or a particular API is made without scope confirmation.
  • A design target is not a portfolio performance guarantee or an acquisition integration deadline.

Set it up around your practice.

01

Scope the pilot

Choose representative locations and define the required billing, scheduling, clinical and access workflows.

02

Review governance

Confirm permission inheritance, the BAA, exports and security-review materials with the onboarding team.

03

Roll out on evidence

Inspect the pilot’s records, approvals and readiness reports before planning the next wave.

Practices own their data and can export it. Review migration scope, enabled features and the BAA with the onboarding team. See security and data access, integrations and current pricing for the wider platform.

The connected team

Follow the handoff.

Before you ask for an invite

The practical questions.

Scope and availability should be confirmed for your practice during onboarding.

Can each location be more conservative?

The specification includes organization defaults with possible location adjustments, but the precise override model needs confirmation. Resolve it before relying on a central-versus-local policy arrangement.

Can a central team handle billing?

The platform supports location-based roles and shared organizational context. Scope the central team’s access and review process, including which queue and filtering features are available.

How is data separated?

Every record carries practice and location context. Isolation is enforced through database constraints, row-level access rules and retrieval filtering, alongside user role and location assignments.

Do new locations get immediate autonomy?

No blanket promotion is required. New practices and newly enabled capabilities begin supervised. The readiness report supports action-by-action decisions by the owner.

Does Omnira support our identity and BI tools?

SSO, user provisioning, BI exports and APIs need confirmation for your organization. Do not infer those integrations from general multi-location support.

How should we discuss commercial scope?

Use the invite process to review locations, migration, governance and rollout requirements. The current public pricing section provides a starting point; these pages do not invent DSO terms.

Industry references.

These references inform the industry context. They do not verify Omnira Dental’s product capabilities or design targets.

  1. Practice modalities among U.S. dentists ADA Health Policy Institute · 2024

    Practice-size and DSO-affiliation data. The linked series includes 2024 data; accessed October 29, 2026.

Omnira Dental · Invite-only

Bring your workflow to the conversation.

Tell us where the work gets stuck. We’ll review your practice’s setup, the enabled features and the approvals your team needs.