Skip to main content

Curve PMS Integration: What to Expect & Current Limitations

Written by Alyssa Elso

When integrating Practice by Numbers (PbN) with Curve PMS, you’ll have full access to the core functionality needed to run and grow your practice—while a few areas are still evolving as Curve continues to expand their API.

The most important takeaway: Everything you rely on day-to-day in PbN - KPIs, Revenue IQ, Huddle, Tasks, patient tracking, and reporting is fully functional and accurate.

The items outlined below represent areas where Curve does not currently expose certain data. These are limitations in data depth, not visibility, and they do not impact your ability to use PbN effectively.


What Works Today (At a Glance)

PbN + Curve fully supports:

  • Patient syncing

  • Appointments and scheduling visibility

  • Ledger and financial data (for reporting and KPIs)

  • Patient notes

  • Core reporting and analytics (Practice IQ, Revenue IQ)

Bottom line: You have complete visibility into practice performance and where to take action.


Current Limitations (and What They Mean for You)

Insurance Deductibles Not Available via API

Curve does not currently provide deductible data through its API.

What this means:

  • Deductibles will still be managed and viewed in Curve.

  • This does not impact financial reporting or KPIs in PbN.


Payment Method Details Not Included

Payment types (card, check, cash, etc.) are not included in ledger data.

What this means:

  • Total revenue and collections are still fully accurate in PbN.

  • You may reference Curve if you need payment-type breakdowns.

This is a granularity limitation, not a reporting limitation.


Scheduling Blocks & Provider Availability

Curve does not expose:

  • Scheduling blocks

  • Custom provider schedules

  • Availability overrides

What this means:

  • PbN reflects actual appointments and patient flow, which drive performance.

  • Some schedule nuances (like blocked time) may still be managed in Curve.

PbN tracks what actually happens on the schedule—the part that impacts KPIs.


Limited Incremental Sync Support

Incremental syncing is currently supported for:

  • Patients

  • Appointments

  • Ledger entries

Other data requires full syncs.

What this means:

  • Core reporting data remains up to date and reliable.

  • Some background processes may take slightly longer, but do not affect usability.

  • Curve does not provide real-time data through its API, while the Curve UI displays real-time values. Because of this, there may still be minor differences between the numbers shown in PbN (based on the last API sync) and the numbers in the Curve UI report.


Documents & Recall Types Not Available

Curve does not currently provide access to:

  • Documents

  • Recall types

What this means:

  • Recall tracking in PbN still works using visit history and procedures.

  • Documents remain accessible in Curve.

This is a labeling limitation—not a visibility issue.


Clinical Data (Perio, Conditions)

Curve does not expose:

  • Periodontal (perio) data

  • Dental conditions (organization or patient-level)

What this means:

  • Deep clinical charting details are not available in PbN.

  • Hygiene production, SRP trends, and revenue insights remain fully visible and accurate.

You still have the signal—just not all the clinical depth yet.


New Patient Classification Differences

Curve API does not currently provide a patient-created date. Because of this, PbN determines new patients based on the earliest of the available appointment date or the transaction date.

In addition, PbN only includes patients who have at least one of the following fields available:

  • Next regular appointment

  • Next preventive appointment

  • First visit date

What this means:

  • New patient counts in PbN may differ from Curve’s “New Patients This Month” report.

  • Some patients may appear as new in PbN based on their earliest recorded activity, even if they have a prior history in Curve.

  • Patients shown as new in Curve may be excluded from PbN if they lack the required activity fields.

This is a data availability limitation, not a reporting issue.

PbN uses the most reliable data provided by Curve to classify patients, ensuring consistency across KPIs and reporting, while slight variations may occur compared to Curve’s native reports.


Provider Mapping & Fee Schedule Relationships

Curve does not currently provide a relationship between:

  • Providers

  • Fee schedules

  • Insurance fee mappings

Because this relationship is not exposed through Curve’s API, PbN cannot calculate certain UCR-based insurance metrics within the Insurance Detail chart.

What this impacts:

The following columns within the Insurance Detail chart will remain blank:

  • UCR Prod

  • Prod % of UCR

  • Coll % of UCR

Location: Practice IQ → Dashboard → Scorecards → Insurance Write-Offs → Insurance Detail

Other columns within the chart, such as Insurance Name and Prod / Patient, will continue to populate normally.

What this means:

This limitation is isolated to UCR-based calculations that depend on provider-to-fee schedule relationships.

All other insurance reporting, production reporting, collections reporting, and KPI visibility continue to function normally within PbN.


Big Picture

Curve is a newer integration, and these limitations are expected at this stage.

What matters most:

  • Your KPIs and reporting are complete and accurate

  • Your team can fully use PbN to track performance and take action

  • Any gaps are primarily around deeper clinical detail or system-specific workflows

As Curve expands their API, additional data and functionality will continue to be added.

Did this answer your question?