01 · Data
Confirm the inputs and the intended work
The technical dataset, scope, software environment, implant system, production pathway, and responsibilities are reviewed before work proceeds.
How we work
PlanSurg does not force every client into the same model. We shape the engagement around your existing capabilities, responsibilities, software, partners, and goals.
A clear public workflow
The detailed operating controls are adapted during onboarding, but every case-level engagement follows the same visible principle: technical work moves forward only when the right information, review, and approval are in place.
01 · Data
The technical dataset, scope, software environment, implant system, production pathway, and responsibilities are reviewed before work proceeds.
02 · Plan
Planning, segmentation, model preparation, guide design, or workflow support is performed within the defined scope and client environment.
03 · Approval
The appropriately licensed provider reviews and approves the clinical plan and any design intended for clinical use. Silence is never treated as approval.
04 · Release
Approved deliverables are released to the laboratory, clinic, printing center, or qualified manufacturer responsible for the next step.
Patient information and case exchange
Case files are exchanged only through a secure channel agreed during onboarding. Access, sharing, retention and responsibilities are defined before patient information is received.
The transfer method can be adapted to the laboratory's established workflow when the selected service, plan and configuration support the applicable privacy and security requirements.
Do not send patient information through this website or ordinary email. We confirm the authorized case channel before any patient files are exchanged.
Two engagement paths
The client-facing structure changes, but the need for defined responsibilities, controlled review, and traceable deliverables does not.
Direct support
PlanSurg can support an established workflow or help define a new one around the organization's team, software, partners, production resources, and operating goals.
White-label support
PlanSurg can provide agreed planning, design, documentation, or capacity support while the laboratory retains its client relationship and established communication pathway.
Support shaped to the organization
Dental laboratories
Support overflow, add planning or design capacity, or collaborate with your existing technical team while your laboratory keeps the client relationship.
Clinics with a workflow
Add planning, design, training, and workflow support without replacing the systems or partners you already use. Your provider retains clinical authority.
Clinics building a workflow
Decide what belongs inside the practice, what can be supported externally, how the team should be prepared, and how technical work connects with review and production.
Hospitals & institutions
Support workflow assessment, production-pathway planning, responsibility mapping, documentation, quality structure, planning and design, staff training, and technology readiness.
Printing & manufacturing pathways
Planning and design support, workflow review, technical documentation, and production coordination can be provided within clearly defined responsibilities.
PlanSurg does not manufacture implants or custom plates.
Education & technology
Support professional education, team training, workflow implementation, and surgical subject-matter discussions for organizations working with digital surgical technologies.
What remains consistent
The client defines the organization, objectives, available systems, responsible participants, and intended production pathway. PlanSurg defines and performs the technical scope it accepts, documents identified inconsistencies, and prepares the agreed deliverables for review.
The responsible licensed provider retains diagnosis, indication, treatment objectives, implant selection, final implant positioning, consent, clinical decisions, surgery, and clinical outcomes. Manufacturing remains with the party contractually responsible for production.
The detailed operating process is established during onboarding after the scope, participants, systems, security needs, and responsibilities are known.
Start with the workflow
Tell us about the organization, current capabilities, case mix, software environment, production pathway, and the capacity or implementation problem you are trying to solve.
Discuss your workflow