We’ve added new functionality to the NexHealth Developer Portal – increasing your visibility into Synchronizer performance and usage across all your practice locations.

Onboard practices quickly with the new Developer Portal

We now support reading patient recalls from more health record systems so developers can build automated messaging, analytics, and other tools to help practices keep patients coming back.

We’ve updated the Synchronizer API to let developers sync more data with popular health record systems through a single integration. You can now read patient address information for Dentrix, Dentrix Enterprise, Eaglesoft, and Open Dental. We’ve also enabled checked_out status for eClinicalWorks so developers can use that data to trigger timely post-appointment messages.

Last month, we shared how to use appointment_descriptors to categorize appointments based on procedure codes and EHR-specific appointment types. Now, we’re excited to announce that it’s possible to read EHR-specific appointment types for more health record systems: athenahealth, Dentrix, Dentrix Enterprise, Eaglesoft, and Open Dental.

Categorizing appointments logically and accurately is one of the most important parts of building a dental or medical app. This month, we’ve got tips for how to do that using appointment_descriptors and appointment_types. 

Learn about the NexHealth Partner Program and the latest Synchronizer API product updates.

We’re excited to announce that the Synchronizer API now supports athenahealth. This means you can sync bidirectionally with athenahealth via the same Synchronizer API endpoints that already support dental practice management systems like Dentrix and Open Dental as well as medical EHRs like eClinicalWorks and DrChrono.

We’re excited to announce the NexHealth Partner Program, a new way of promoting Synchronizer-integrated apps to our install base of 8,000+ dental and medical locations. We’ve also got details on the latest Synchronizer API product updates, as well as the story of how a leading dental service organization (DSO) uses the Synchronizer API to connect internal systems.

This month, we’ve got the story of how Ooma (NYSE: OOMA) built a patient call pop in just five weeks using the NexHealth Synchronizer API. We’ve also included information about our upcoming Athenahealth beta, a new video about the origins of the Synchronizer, and details about our recent API rebrand.