Connecting patient scheduling and point-of-sale operations with clinical records through custom middleware.
Client Context & The Dual-System Challenge
The client in this case was a clinic providing medical and aesthetic services in the area. Because so many of its services fall under the medical-spa category, the clinic utilized Meevo, a software platform specializing in front-of-house management, appointment scheduling, and point-of-sale operations for these types of businesses.
Meanwhile, the medical side of its operations required a dedicated Electronic Health Record (EHR) system for managing patient information and clinical documentation. The clinic relied on DrChrono for these functions.
The fundamental problem was that the two software platforms had no native means of communicating with each other. Initially, information moved between them through manual data entry, creating opportunities for data inconsistencies, duplicate records, missed appointments, and other administrative errors.
Meevo served as the clinic’s primary patient intake and scheduling system. On the other side of operations, DrChrono handled patient records and clinical workflows. Patients entered the process through Meevo, but their information also needed to be available in DrChrono before scheduled services could take place.
To accomplish this, staff members were manually transferring patient information and keeping appointment records synchronized between the two platforms. This was not only a bottleneck due to the time involved, but also introduced the ongoing risk of human error.
As the clinic’s operations grew, maintaining this manual connection between two otherwise disconnected systems became increasingly impractical.
Why Meevo + DrChrono?
The decision to maintain both platforms was driven by the different operational strengths each brought to the business.
Meevo provided the specialized scheduling, booking, and point-of-sale functionality needed to manage the clinic’s aesthetic and medical-spa services. DrChrono provided the dedicated EHR capabilities necessary for clinical documentation, patient history, and medical office management.
Neither platform was a practical replacement for the other. The clinic needed both, but the lack of a native integration meant staff had to serve as the connection between them.
Rather than forcing a change to either established system, we set out to build a solution that would allow them to operate as a coordinated environment.
The Integration Gap & Manual Workflow Bottlenecks
The biggest challenge wasn’t simply transferring patient records. It was keeping patient and appointment information consistent as it changed throughout the normal course of business.
Consider a typical patient workflow:
- A new patient enters their information through Meevo.
- An appointment is scheduled with a particular provider for a specific service.
- That patient and appointment information must also be available in DrChrono.
- If the patient changes their appointment time or other details, those changes need to be reflected in DrChrono.
- Clinical staff rely on DrChrono for the patient information and documentation associated with the visit.
Without an integration, each of these steps introduced additional administrative work.
Appointment changes made in Meevo required corresponding updates in DrChrono. New patient records had to be recreated or manually entered. Changes to demographic information could result in discrepancies between the two systems.
The result was a workflow that depended heavily on staff remembering to make corresponding updates in multiple places.
Limitations of Standard Approaches
We evaluated the available options, but conventional approaches weren’t particularly well suited to this problem.
Generic import/export functionality, including CSV-based data transfers, could move information between systems but offered no practical solution for keeping records synchronized as changes occurred.
Similarly, the existing integration options available within DrChrono, including connections to services such as Google Calendar and Weave, didn’t address the specific requirements of connecting Meevo’s scheduling and patient management functionality.
The clinic didn’t need another reporting or data migration tool. It needed an ongoing communication layer between two otherwise independent software platforms.
That meant developing a purpose-built integration.
Custom Middleware Solution: Architecture & Implementation
We approached the project by developing a custom middleware application that would serve as the communication layer between Meevo and DrChrono.
Rather than attempting to modify either platform or introduce a third-party application with limited integration capabilities, we built an independent service responsible for retrieving, transforming, and synchronizing the relevant data.
The middleware handled several primary responsibilities:
- Patient record synchronization: New patient records created in Meevo were automatically transferred into DrChrono, with matching logic to determine whether a corresponding patient record already existed.
- Appointment synchronization: Appointment details, including dates, times, patient associations, and provider assignments, were transferred to DrChrono.
- Appointment change monitoring: Changes to existing appointments and cancellations in Meevo were identified and reflected in DrChrono.
- Data transformation: Custom mapping logic accounted for differences in how each platform structured and identified patient and appointment information.
- Error handling: Logging and error reporting provided visibility into synchronization issues and helped identify records requiring attention.
- Ongoing synchronization: Scheduled and event-driven processes kept information moving between the platforms without requiring staff to initiate manual transfers.
Building the Data Mapping Layer
One of the more important parts of the implementation was accounting for the differences in how Meevo and DrChrono represented their data.
Even when two systems maintain essentially the same information, their underlying data structures, field names, identifiers, and relationships can be quite different.
For example, a patient record in one system doesn’t necessarily correspond directly to a patient record in another. The integration has to account for those relationships and maintain a reliable association between the two.
We developed custom mapping routines to handle these differences, ensuring that patient demographic information and appointment details were translated into the appropriate structures before being submitted to the receiving platform.
This also required accounting for existing records, rather than simply creating new ones every time information was transferred. Maintaining those relationships was critical to avoiding duplicate patient records and ensuring that subsequent appointment updates reached the correct patient.
The Patient Matching Challenge
One of the more complicated aspects of this integration was establishing reliable patient identity matching between the two platforms.
Although both systems maintained patient records, they approached patient identification very differently.
Meevo primarily relies on email addresses as its patient identifier and doesn’t require a date of birth during intake. DrChrono, like most EHR platforms, relies much more heavily on patient name and date of birth when identifying and maintaining patient charts. There were also structural differences between the two systems: DrChrono maintains a separate middle-name field, while Meevo does not.
These differences created a significant challenge. A simple email-address lookup wasn’t sufficient to reliably identify existing patients in DrChrono, and a straightforward name comparison could produce incorrect matches or duplicate records.
We developed a multi-level patient matching process to address these differences. Before creating a new patient record in DrChrono, the middleware evaluates available demographic information against existing records using multiple matching criteria and fallback conditions.
This layered approach was designed to identify existing patients even when the information provided by Meevo didn’t perfectly match the structure or completeness of the corresponding DrChrono record.
The goal was to avoid creating duplicate patient charts while ensuring that new patient records were associated with the correct individual.
In a healthcare environment, this distinction is particularly important. A duplicate chart is more than an administrative inconvenience; it can fragment a patient’s clinical history and create additional work for clinical staff.
How the Sync Engine Works
The integration was designed primarily as a one-way data pipeline, with Meevo serving as the originating system and DrChrono receiving the relevant patient and appointment information.
Our middleware monitors Meevo through two mechanisms: its standard API and its Daily Data Stream service. Using these data sources, the application identifies newly created patient records and appointments, as well as changes to existing appointments and cancellations.
Once relevant information is identified, the middleware processes the incoming data, performs the necessary validation and transformation, and submits the resulting records or updates to DrChrono through its API.
This approach allows the integration to operate independently of both platforms while maintaining a consistent flow of information from the scheduling and intake environment into the clinical system.
Importantly, the middleware doesn’t simply copy records. It evaluates existing patient information, establishes the correct relationship between records in both systems, and determines whether an incoming appointment represents a new booking, an update, or a cancellation.
Logging and error handling are incorporated throughout the process, providing a record of synchronization activity and making it easier to identify and troubleshoot issues when they occur.
The result is a coordinated workflow in which staff no longer have to serve as the manual connection between the clinic’s scheduling system and its EHR.
Outcomes, Time Savings & Operational Improvements
The biggest improvement was eliminating the need for staff to manually maintain patient and appointment information across two separate platforms.
Information entered through Meevo could flow into DrChrono automatically, reducing repetitive administrative work and allowing staff to focus on patient-facing responsibilities rather than data entry and reconciliation.
The integration also improved consistency between the two systems. Changes that previously required multiple manual updates could now be handled through the middleware, reducing the opportunity for discrepancies and missed updates.
Key operational improvements included:
- Reduced administrative workload: Staff no longer needed to manually recreate patient records and transfer appointment information between systems.
- Improved data consistency: Automated synchronization reduced discrepancies between patient demographics and appointment records.
- Fewer duplicate records: Multi-level patient matching helped identify existing patients before creating new charts.
- More reliable scheduling workflows: Appointment changes and cancellations could be propagated to DrChrono without relying on staff to remember to update each platform.
- Improved operational visibility: Logging and error reporting provided a clearer picture of synchronization activity and potential issues.
A Better Approach to Disconnected Healthcare Software
This project is a good example of a problem that frequently occurs in specialized business environments: organizations adopt multiple software platforms because each serves a particular operational need, but those platforms weren’t necessarily designed to work together.
Replacing either system would have meant sacrificing functionality that was important to the clinic’s operations. Continuing with manual data entry wasn’t a sustainable long-term solution.
Custom middleware provided a practical alternative. By building an integration specifically around the clinic’s workflow, we were able to preserve its existing software investments while eliminating much of the friction associated with operating two disconnected systems.
The same approach can be applied to other healthcare and service-based businesses that rely on specialized scheduling, point-of-sale, practice management, and EHR platforms.
When off-the-shelf integrations don’t exist, custom software can bridge the gap without requiring an organization to compromise on the tools it already depends on.