Existing practice systems
Keep the system of record.
Connect the operating context.
Strictly sits above the practice systems already in place. Context enters through the approved connection path, becomes usable across one orchestration layer, and continues into named standards and endpoints.
Context bridge
Select either edge to trace the shared connection layer.
Existing practice systems
Ingress
Via SIKKA or direct API
Connection + orchestration layer
Normalized operational context
Patient context
Appointment context
Claim context
Payment context
Standards + endpoints
Open Dental
A named practice system enters the shared connection path while the PMS remains the system of record.
The bridge has four distinct jobs.
Separating the system of record, connection path, shared context, and interoperability surface makes the architecture understandable without overstating implementation details.
Connection path
Context enters via SIKKA or direct API.
The wording stays intentionally high-level: the approved source establishes the connection path, not an endpoint catalog or public API specification.
Strictly context layer
Normalize the context around the work.
Patient context
Appointment context
Claim context
Payment context
Standards + endpoints
Continue into the approved interoperability surface.
FHIRR5
A canonical, standards-aligned data model for shared operational context.
ERA / 835
Approved claims and remittance context inside the broader operating flow.
Integrated Terminals
The named payment infrastructure endpoint in the approved interoperability surface.
Connection matters when the next work stays connected.
Patient, appointment, claim, and payment context can continue from the connection layer into scheduling, claims, payments, and revenue follow-up.
Patient context
Appointment context
Claim context
Payment context
Once the context is connected, Revenue Cycle shows how aging work moves toward action, review, and resolution.
Follow the revenue pathKeep the system of record. Upgrade the work around it.
See your own schedule, claims and balances running inside Strictly in a 20-minute walkthrough.