What You Need to Know About Dentsply Sirona DS Core and Scanner Integration
Honestly, when clinics ask me about DS Core, it's usually not about the cloud features or the platform itself. It's about one specific worry: "Will my scanner work?" I've been reviewing equipment specs and integration claims for the better part of 4 years now, and I can tell you—the compatibility question is where things get sticky. I'm not a software architect, so I can't talk about the API code. What I can tell you from a quality and procurement perspective is what actually happens when you try to connect a scanner to DS Core, and what the official documentation doesn't always make clear.
Below are the 8 questions I get asked most often. If you're evaluating DS Core, these are the ones you want answered.
1. What exactly is DS Core, and does it replace my existing software?
DS Core is Dentsply Sirona's cloud-based open platform. Think of it as the backbone that connects your scanner, your design software, your milling machines, and your patient data. It's not a replacement for your intraoral scanner's native software or your CAD/CAM suite. It's the layer that lets them talk to each other.
From what I've seen in practice, it works best as a central data hub. You scan on your Primescan, the data goes to DS Core, and then any authorized lab or clinician with the right permissions can access those scans through third-party software like exocad or 3Shape Dental System. So no, it doesn't replace what you have. It connects what you have.
2. Which intraoral scanners are officially supported by DS Core?
As of early 2025, the official supported scanners list includes:
- Dentsply Sirona scanners: Primescan, Primescan Connect, CEREC Omnicam
- Third-party scanners with verified integration: 3Shape TRIOS (3, 4, and 5), Medit i500 and i700, iTero Element 2 and 5D, Carestream CS 3600, and Planmeca Emerald S
That said, I've seen some gotchas. For example, the 3Shape TRIOS 3 integration works, but in my Q1 2024 audit, we found that firmware versions below 19.4.0 had intermittent data transfer stability issues. It wasn't a DS Core problem—it was a scanner firmware problem. But if you're running older firmware, you'll think the integration is broken.
Rule of thumb: Always check the scanner firmware version against the DS Core compatibility matrix on the official support portal. That list changes maybe once a quarter.
3. How does the Dentsply Sirona DS Core 3Shape integration actually work?
This is the one I get most. To be fair, 3Shape is probably the most common third-party scanner in the market, so it makes sense. The integration flow goes like this:
- You scan the patient in 3Shape TRIOS and export the case to DS Core via the TRIOS Connect plugin.
- DS Core receives the scan data and stores it in the cloud.
- A lab or clinician accesses DS Core, downloads the case into their preferred design software (exocad, CEREC SW, 3Shape Dental System, etc.), and designs the restoration.
- The finished design goes back to DS Core or directly to a milling machine (if the receiving end is in the Dentsply Sirona ecosystem).
I'll be honest—I was skeptical when I first tested this. We ran a blind test with our team: same case sent via DS Core vs. direct email. 78% identified the DS Core workflow as "more reliable" without knowing the difference. The time saving wasn't huge (maybe 4 minutes per case), but the elimination of "missing attachment" emails was a real win.
One caveat I learned the hard way: the 3Shape export must include the patient's full name and date of birth. If the data fields are incomplete, DS Core rejects the case. I skipped verifying that once back in 2023 because I was rushing—that was the one time it mattered. A $400 redo and a very unhappy lab.
4. Is DS Core compatible with non-brand intraoral scanners?
This is where I have to draw a professional boundary. I can tell you what's on the official supported list, but I can't speak to every random OEM scanner out there. What I can say from experience is that if a scanner isn't on the list, don't assume it works. I've seen clinics try to save money on a cheap scanner and then find out it exports in a proprietary format that DS Core doesn't recognize.
DS Core uses open standards (STL, OBJ, and DICOM for CBCT). If your scanner outputs one of those formats, there's a chance it can be uploaded manually. But the seamless automated integration that DS Core is designed for? That only works with certified partners.
Quick tip: Check the DS Core Partner Directory on the Dentsply Sirona website. It's updated quarterly. If your scanner brand isn't listed, you're probably looking at a manual workflow.
5. What about DS Core and CBCT integration?
DS Core supports DICOM files, which means CBCT data from Dentsply Sirona units (like the X-Mind trilogy or Orthophos SL) integrates natively. For third-party CBCT systems, you need to ensure they export standard DICOM 3.0 format. Some older machines use proprietary DICOM extensions that DS Core may not interpret correctly.
I dealt with this when we were testing DS Core with a Planmeca CBCT. The DICOM headers had some proprietary tags that DS Core didn't read. We had to use a third-party DICOM converter. It worked, but it added 2 extra steps to the workflow. The lesson: test the specific combination before committing.
6. What are the data security and HIPAA considerations
Again, getting into legal compliance territory here—I'm not a lawyer or a HIPAA expert. What I know from my role is that DS Core is hosted in AWS data centers and is SOC 2 Type II certified. Dentsply Sirona also offers a Business Associate Agreement (BAA) for US customers. You need to verify that the BAA covers your specific use case and that your clinic's internal policies accept cloud-based storage for PHI.
One thing I've observed: some clinics get caught on the data retention settings. DS Core has configurable retention policies. If you don't set them manually, the default might be longer than your clinic prefers. We set ours to 90-day auto-delete for scanned cases, and archive CBCT data separately on local servers. Works fine.
7. What's the real cost of implementing DS Core?
This is tricky because the pricing changed in early 2024. As of January 2025, DS Core has a tiered subscription model based on clinic size and data storage needs. The base tier (for single-chair clinics) is around $200 per month, and that includes basic cloud storage and integration with Dentsply Sirona scanners. The enterprise tier (multi-chair with lab collaboration features) runs higher—I've seen quotes around $500–$800 per month depending on volume.
That said, the hidden cost is training. I've seen clinics buy DS Core and then spend 3 months trying to get everyone to use it. If your team isn't comfortable with cloud platforms, factor in at least 2–3 days of training per clinician. The 12-point checklist I created after my third training mistake has saved us an estimated $8,000 in potential rework from user errors.
Pricing as of January 2025. Verify current pricing at dentsplysirona.com/DS-Core as rates may have changed.
8. Should I wait for more scanner integrations before adopting DS Core?
Look, I get why people ask this. Nobody wants to buy a platform that might not work with their future scanner. But waiting indefinitely has its own cost. In my experience, the DS Core ecosystem has added roughly 2–3 new scanner integrations per year since launch. The pace is steady. If your current scanner is supported, adopting now means you're building the workflow habit early. When your next scanner arrives, the transition is trivial.
If I could redo one thing from my early adoption period: I would have insisted on better documentation from the vendor about the exact export settings for our specific scanner model. That 30-minute clarification would have saved us a week of trial-and-error. But given what I knew then—nothing about the quirks of STL resolution settings in DS Core—my choice to go ahead was reasonable. 5 minutes of verification beats 5 days of correction.
If your scanner is on the supported list and you're okay with a cloud-first workflow, I'd say go ahead. The platform is mature enough for production use. If your scanner isn't supported, wait or accept that you'll have a manual data transfer step.
