Aventura, Florida · serving clients across the United States (305) 404-9404Toll-free (800) 767-8566Emergency? Get a call within 1 hour
Healthcare, dental

A nationwide dental group on its own open-source platform, with drivers we wrote for its imaging hardware

A dental organization with a nationwide presence, a leader in its segment, handling patient records and diagnostic images under HIPAA.

Scale
Nationwide practice network, open-source practice management, custom imaging drivers
Engagement
Custom platform, device integration and ongoing development

The challenge

The group's dental-imaging hardware was tied to outdated vendor software that held back every upgrade, and its practice-management system could not be shaped around how its offices actually worked, while all of it had to protect patient health information.

What our team delivered

  • Custom software built on our own build of Open Dental, the open-source practice-management system
  • Custom integrations between the platform and the group's medical devices and imaging hardware
  • Our own drivers for the dental-imaging hardware, reverse-engineered for interoperability, so the devices no longer depended on outdated vendor software
  • A platform the group controls end to end, with no vendor lock-in on its devices or its records
  • HIPAA safeguards designed in: access controls, audit trails, encryption and backups for patient records and images

Result

Imaging devices that work with current systems, a practice platform built around the group's own workflows, and an open-source foundation it owns.

Backup tiers: data lost versus time to recover

Recovery point objective (RPO) is how much recent data a restore loses; recovery time objective (RTO) is how long the restore takes. Faster tiers sit close to the production system and share its fate; slower tiers survive ransomware and site loss. The scale is logarithmic. Illustrative figures.

Backup tiers: data lost versus time to recoverPaired horizontal bars on a logarithmic time scale. Snapshot: RPO 1 hour, RTO 15 minutes. Replica: RPO 1 minute, RTO 5 minutes. Immutable object store: RPO 1 day, RTO 4 hours. Offline copy: RPO 7 days, RTO 1 day.RPO and RTO by backup tier (log scale)RPO: data lostRTO: time to recover1 min10 min1 h6 h1 day7 daysSnapshotsame array, same failure domain1 h15 minReplicasecond site, asynchronous1 min5 minImmutable object storewrite-once, cannot be altered1 d4 hOffline copyair-gapped, no network path7 d1 dKeep one tier of each kind: the fast one restores quickly, the immutable one survives an attacker with admin rights.

ERP development and integration

One database keeps finance, sales, inventory, purchasing and HR in sync, connects to your banks and partners, and grows with custom modules built for how you work.

ERP development and integrationFinance, sales, inventory, purchasing and HR modules share one PostgreSQL database and stay in sync. A secure API connects the ERP to e-commerce, banking and shipping partners, and a new custom module is plugged in without disturbing the rest.YOUR ERPINTEGRATIONSPostgreSQLsource of truthFinanceSalesInventoryPurchasingHRAPIsecureRESTE-commerceBankingShippingCustom modulebuilt for your process

Every sign-in, verified

Staff sign in once, but behind the scenes the device, the identity, a phone approval and your access policy are all checked before any app opens, and strangers are turned away.

Every sign-in, verifiedDiagram of user authentication. A user signs in; the device is checked for MDM and Intune compliance; the identity provider, Active Directory or Entra ID, verifies the account; an MFA push is approved on the user's phone; conditional access evaluates the policy; and access is granted to email, ERP and files. On a second pass, a sign-in from an unknown device in a new location is blocked by the conditional access policy. VERIFIED SIGN-INUserSigns inDevice checkMDM · IntuneIdentityAD · Entra IDMFA pushPhone approvalConditionalaccessPolicy checkEmailERPFilesUnknown deviceNew locationApprove?Blocked

Frequently asked questions

Direct answers to the questions we hear most. Something else on your mind?

Send us a message
Why were custom drivers needed for the imaging hardware?

The group's dental-imaging hardware was tied to outdated vendor software that held back every upgrade. We wrote our own drivers, reverse-engineered for interoperability, so the devices no longer depend on that software. The imaging devices now work with current systems.

What is the practice platform built on?

It is our own build of Open Dental, the open-source practice-management system, with custom integrations to the group's medical devices and imaging hardware. The group controls the platform end to end, with no vendor lock-in on its devices or records.

How is patient data protected?

HIPAA safeguards were designed in: access controls, audit trails, encryption and backups for patient records and images. The case treats these as part of the platform design, not an add-on.

Do you know if your company is safe?

Speak with a security engineer today. The first assessment call is free and confidential.

CallFree assessment