Five systems that were never built to talk, made to report and provision as one

Identity lifecycle automation driven from ADP Workforce Now, plus direct database work against Dentrix Enterprise, for a dental service organization whose data sits across five disconnected systems.

Five systems each hold a piece of a dental group’s data and none of them was built to talk to the others. That is the starting condition here, at a dental service organization whose data sits across five disconnected systems: Dentrix Enterprise alongside Dolphin, Denticon, Peerlogic and ADP Workforce Now. Two problems follow from it, and both are the work: getting information out of a system whose schema the vendor doesn’t publish, and getting access into all five when someone is hired, changes role, or leaves.

Access driven by the HR event, across all five

A TA LifeCycle Manager deployment watches ADP Workforce Now and provisions or removes access across Dentrix Enterprise, Dolphin, Denticon, Peerlogic and the Microsoft estate as an employee is hired, changes role, or leaves. It runs as its own fully isolated deployment for this client. See employee identity lifecycle for what the service covers.

Reporting from a schema the vendor doesn’t document

Dentrix Enterprise’s own schema isn’t documented anywhere the vendor publishes, so reporting and integration work reads its database directly rather than waiting on an API the product doesn’t offer. Document Center attachments, which are otherwise locked inside Dentrix Enterprise, are made reachable from the rest of the estate under controlled access. Routine database maintenance runs the same way, directly against the system, because there is no application-level control for it. Read the Dentrix Enterprise work in full.

Denticon, one system among the five

Denticon sits in this estate too, and it has no write API of its own, so the same read-and-verify pattern described on Denticon applies here.

If Dentrix Enterprise or ADP is the system you’re stuck on

Tell us what you’re trying to get out of Dentrix Enterprise’s database, or which downstream system still gets updated by hand after an ADP event. Contact us, or book a call and bring the specifics.