When integrating Practice by Numbers (PbN) with Curve PMS, it’s important to understand that certain data and workflows are limited by Curve’s current API capabilities. While the integration supports core functionality such as patient syncing, appointments, and notes, some data points are inaccessible, and certain actions cannot be performed directly in PbN.
The sections below outline these limitations so your team knows what to expect and where workflows may need to remain within Curve.
🔹 Missing Deductibles in Insurance Plan API
The Curve API does not include deductible information in the insurance plan response.
Although previously referenced in documentation, this field is not supported.
There is currently no mechanism to retrieve deductible data programmatically.
Impact:
Deductible information must be reviewed directly in Curve.
Any need for this functionality would require a feature request.
🔹 Missing Payment Type in Ledger Entries
The Curve API does not provide payment method details (e.g., card, check, cash) in ledger entries.
There is currently no field available to identify how a payment was made.
Support for this feature is expected in a future release.
Impact:
Payment methods cannot be identified within PbN.
Manual verification in Curve may be required.
🔹 No API for Scheduling Block Retrieval
There is no API endpoint available to retrieve scheduling block data.
Scheduling blocks are not distinguished from regular appointments in the API.
Workaround:
Appointments can be filtered by time (e.g., hourly) to help infer blocked time.
This approach does not guarantee accuracy.
🔹 Limited Support for Incremental Data Retrieval
Incremental sync using the changedSince parameter is only supported for:
Patients
Appointments
Ledger Entries
Other endpoints do not support incremental updates.
Impact:
Full data syncs are required for unsupported endpoints.
This may increase processing time and API usage.
🔹 No API for Documents and Recall Types
The Curve API does not provide access to:
Documents
Recall Types
Impact:
These data types cannot be synced into PbN.
They must be accessed directly within Curve.
🔹 No API for Dental Conditions and Patient Dental Conditions
The Curve API does not expose:
Dental conditions (organization-level)
Patient-specific dental conditions
Impact:
Clinical condition data cannot be accessed or synced into PbN.
This limits integration of condition-related reporting or workflows.
🔹 No API for Provider Custom Schedule and Availability
Provider-specific schedules and availability overrides are not available via the API.
This includes:
Custom provider schedules
Time-based availability overrides
Impact:
PbN cannot fully replicate provider availability logic from Curve.
Scheduling views may differ slightly between systems.
🔹 No API Support for Patient Perio Data
The Curve API does not provide access to periodontal (perio) data.
Impact:
Perio charting and related clinical data cannot be synced or analyzed in PbN.
This information must be accessed directly within Curve.
🔹 Writeback Support in Curve PMS Integration
Writeback functionality from PbN to Curve is limited to a small set of supported actions.
Supported Writeback Areas
New patient creation
New appointment creation
Patient notes
Unsupported Writeback (Read-Only in PbN)
The following actions must be completed directly in Curve:
Patient updates
Appointment updates
Payments and refunds
Form submissions
Documents
Impact:
PbN should be treated as read-only for most data outside of supported actions.
Updates must be completed in Curve for unsupported areas.