Group practice

Several offices. One patient record.

Run a dental group on a shared patient record, with local schedules, role-based location access, and reporting owners can review across offices.

Invite-only · Built around your practice’s permissions

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

Harbor & Pine Dental Group

Shared record · local book

Prepared by agents. Controlled by your team.

The work behind the work

A patient visits one office for an exam and another for treatment. A provider works different days at different locations. The billing team needs to know where the work happened without rebuilding the patient history.

Separate records turn those ordinary situations into copying, checking and phone calls. Owners need combined reporting, but the people at each desk still need to run their own day.

Omnira Dental shares the patient record within an organization while keeping location-specific operating details. Hours, scheduling patterns and provider preferences remain local. Access follows the locations and roles assigned to each person.

Multi-location dental work on one record

01

Keep one patient history

A patient seen at two offices of the same organization remains one patient. Treatment history and communication context follow the shared record. Staff do not need to recreate the conversation because the next visit is at another site.

02

Respect the local book

Each location has local hours, providers and scheduling patterns. Stella applies the appointment constraints for the relevant office. A provider preference at one location does not become a generic assumption for the whole group.

03

Give billing the location context

Vera’s work retains the practice and location associated with the record. Permitted billing staff can work the relevant claims while owners review collections and production at the office level and across locations.

04

Share useful learning

Payer behavior and procedure-duration learning can be shared within the organization. Provider preferences and operational insights stay tied to their local context. Shared learning should help the work without making every office identical.

05

Separate access deliberately

Users can belong to more than one location with a role at each. The platform’s isolation checks operate at the database, access-policy and retrieval levels. A staff assignment, not proximity to a shared patient name, determines access.

06

Review the combined picture

Owners can roll reporting up and drill into a location. Otto supplies the operating picture and Luna routes questions within permissions. A group total can lead to the particular office that needs attention.

A patient changes the place, not the record

In this fictional Harbor & Pine example, Ana Ruiz asks about care closer to work. Confirm cross-office scheduling scope during onboarding.

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

Location reporting

Owner view

Prepared by agents. Controlled by your team.
  1. The dentist’s diagnosed treatment becomes a patient-friendly plan on Ana’s record.

  2. Ana asks about a visit near work. The request stays in the patient thread with the existing plan context.

  3. Staff review the relevant location, provider and appointment rules. Cross-office options depend on the configured and supported workflow.

  4. Verified benefits and the practice estimate remain associated with the record. Location-specific financial arrangements need setup confirmation.

  5. Reporting retains the office where the appointment takes place. Authorized owners can review location and combined performance.

Agree on what is shared

A shared record is useful when everyone understands its boundaries. Decide who works across offices and which jobs remain local. Review a floating provider, a centralized billing user and a front desk user as separate access cases.

The group also needs operating agreement on appointment types and preparation. A procedure duration learned from the organization still has to fit the local provider, room and schedule. The local day should remain understandable to the team delivering it.

During migration, inspect patients who already appear in more than one office’s system. Duplicate handling is a specific question for the onboarding team. Do not assume that sharing a record means historic duplicates can be merged automatically without review.

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

Location roles

Assign each user the offices and roles required for their work.

Shared standards

Review organization defaults and confirm which location overrides are supported.

Schedule changes

Preserve action-level approval when a request crosses locations.

What we are designing toward

Targets, stated plainly.

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

  • 15+ admin hours back each week is the design target.
  • Zero AR backlog is the design target.

Where your team takes over.

  • Sharing a record does not grant unrestricted access to every office’s staff.
  • Cross-office waitlists, duplicate merging and per-location fee schedules need confirmation before being treated as available workflows.
  • Location reporting does not erase the source office attached to the work.

Set it up around your practice.

01

Map your organization

List practices, locations, providers and people working across offices.

02

Review the data

Agree on migration scope and inspect duplicate patients, balances and appointment history with the onboarding team.

03

Pilot the handoffs

Test a local user and a cross-office user during supervised training. Confirm the override model before applying organization defaults widely.

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.

Is a patient one record across offices?

Within an organization, the multi-location model uses a shared patient record. Staff access still depends on the user’s assigned role and location permissions.

Can each office keep its hours?

Yes. Local hours, provider preferences and scheduling patterns are location-specific. The shared record does not require every location to run the same schedule.

Can one billing team work across offices?

Assign the billing team the appropriate roles and location access. Financial records retain their location context, and owner reporting can be viewed by office or rolled up.

Can staff see every other office?

Only if their assigned access allows it. Users may have different roles at different locations. Review those assignments during setup rather than assuming group membership is enough.

Are patient duplicates merged automatically?

Duplicate handling during migration needs confirmation. Review how existing records will be reconciled before import; the shared-record model is not a promise of automatic deduplication.

How is this different from a DSO rollout?

The underlying location model is shared. A DSO may need a larger governance and onboarding plan. The DSO page explains the central review and rollout considerations.

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.