

Recently named the 2024 NADL Educator of the Year, Jimmy Stegall is an industry titan with over 40 years of expertise. He has led a premier dental lab, educated thousands, and pioneered innovations in implant and prosthetic restoration.
His unique workflow ensures a superior fit and enables dentists to deliver dentures in just two appointments, reducing patient discomfort and rework.
Elevate your practice with predictable, time-saving results crafted by an authority who understands the clinical and operational demands of dentistry.
Use your intraoral scanner to capture a digital impression and create a 3D digital model of your patient’s oral anatomy.
Jimmy Instructs dentists to use one of three workflows, depending on the case:



After completing the intraoral scan, you will need to gather and organize the following essential details for the treatment plan:
Visit evidentdigital.com to sign in or create your account.

Scroll to the Removables section, click the "Order Now" button under "Digital Complete Dentures".

Select Jimmy Stegall Dentures and fill the complete Rx form.

This guided ordering form ensures that the vision of both the patient and the doctor is precisely communicated to our design team. You can choose to rush this case to get your designs back as soon as possible (2 - 5 hours).
Once you've filled in your patient and practice information, follow these steps to complete the form:

4. Is This An Immediate Denture?
5. Select Desired Base Thickness
6. *Default Teeth Segmentation

7. Desired Overjet & Overbite
8. Gingiva Esthetics/ Festooning
9. Support Bars for Printing

10. Digital Tooth Library
11. Are You Fabricating In-House?

12. RX Notes
13. Upload Required Files
14. Review and Submit


Once complete, you will receive the following files:


For detailed process and workflow instructions specific to your 3D printer model and resin,
please contact your 3D printer manufacturer’s support team.

2. Wash

3. Cure


If you have any questions about the process, feel free to visit www.evidentdigital.com to connect with our support team.

Designs you order from EviSmart arrive in your Oqcam already formatted. Named the way your nesting rules expect, with shade and material attached, and pointed at the machine that case belongs on.
The routing is decided per case. An implant case sends the crown to the mill and puck you cut implant crowns on, and the model to the printer you print models on. Different case types, different machines, chosen automatically rather than by a tech working through a dropdown for every file.
The trigger is QC approval. EviSmart designs your cases your way. The same team works on all your cases and learns what a good case looks like to you. Once your case passes our QC, it triggers a greenlight to send the design directly into your Oqcam account in under a minute.
Once the file arrives in your Oqcam, all your CAD/CAM technicians can review the nested design before starting the mill. That final QC step does not change and is not meant to.
Setup is one session. We connect your Oqcam account and agree where each of your products should go, using the routes and materials you have already built there. Nothing new to create, and you only revisit it if something changes.
Automatic sending only works if you trust what is being sent. Once a case is nested it gets cut, and a design that was not right is wasted material.
You choose what flows. During setup we map only the case types you want moving on their own. Anything unmapped never sends. It waits for you exactly as it does today.
Most labs start narrow. Bread and butter work first, night guards and posterior single units, then widen once they have watched it run for a few weeks. The lab that has been live longest started exactly there and has added case types since.
Your approval stays. This removes the file shuffling between design and CAM. It does not remove your eyes from the build.
For labs outsourcing design work the math gets compelling somewhere north of 30 cases a day into nesting, because that is where the handoff stops being an annoyance and starts being a role.
Not touchless design. Touchless handoff. Every step in that chain that requires judgment should keep requiring judgment, and every step that never did should stop requiring a person.
Nesting requires judgment. Confirming a build requires judgment. Renaming a file so software can read it does not, and never did. It was a workaround that quietly became somebody's job.
Nobody pays you to rename files.