Every appointment type
With its real duration, provider requirements and resource requirements. Real, not what the manual says.
Healthcare scheduling
Booking is the easy part. Your schedule is the hard part. If one location, one record system and standard appointment types cover your rules, buy a product. We build when the rules, the locations, or the record systems do not fit what off the shelf tools model.
Name the system you run. You get back whether real time availability and booking are possible on it, or only appointment requests.
One location, one record system, standard appointment types: Zocdoc, Phreesia and NexHealth do booking, reminders, forms and texting well. Custom doctor appointment app development recreates commodity features at higher cost. Build when your situation looks like one of these.
Before we quote, we document how scheduling actually works in your practice. Not the manual version. The version the front desk runs when the phone rings.
With its real duration, provider requirements and resource requirements. Real, not what the manual says.
Referral, authorisation, eligibility, prior visit, records received.
Including the ones that exist because of one clinician's preference.
The calls where the answer is "it depends", and what it actually depends on. This is where automations fail.
Rule by rule. Sometimes this document is the reason not to hire us.
Real time booking depends on what your vendor exposes, not on what we wish they exposed. Below is what we have confirmed for common systems. We confirm write access on your tenant before we quote.
| System | What we have confirmed |
|---|---|
| Epic | Availability query, booking and cancellation APIs, plus HL7 v2 events for booking, cancellation, modification and no show. Some scheduling access comes through Vendor Services at $1,900 a year. No central endpoint, so each customer organisation approves its own connections. |
| Oracle Health | FHIR R4 Appointment supports retrieve, create and patch. Proprietary scheduling code sets still need mapping. |
| athenahealth | Booking, rescheduling and cancellation documented, with departments, providers, appointment reasons and open slots. One of the most workable ambulatory targets. |
| Elation Health | Full schedule management and CRUD on Appointment. Technically the most open we checked. |
| DrChrono | Developer API with appointment support. Fine for smaller groups and digital health products. |
| Tebra (Kareo) | SOAP APIs. A practice built its own iOS app on them to view, book and change appointments. Legacy protocol adds time. |
| eClinicalWorks | Provider facing FHIR and healow FHIR documented. A universal third party write path is not. Confirm per tenant. |
| NextGen | Patient access FHIR is well documented. General third party scheduling write is not. We will not promise it until your vendor confirms. |
| Dentrix, on premise | Scheduling API for commercial programme participants, working through a local service at the practice. Published fees are $5,000 read setup, $5,000 write setup, plus monthly royalties. No HL7. |
| Dentrix Ascend | Gated developer programme, application review, an agreement and a 60 day initial sandbox. REST endpoints across schedule, with streaming events. |
| Open Dental | Public REST API with web scheduling, update and confirm operations. The most open dental system we checked. |
| PIMSY and other behavioral health | Vendor states bidirectional API. Route level scheduling documentation is not public. Our own six years of production experience against it is worth more here than the claim. |
We will never write that we integrate with any EHR. Each connection is confirmed on your tenant, with vendor fees visible as your cost rather than buried in ours.
Patient facing booking with your rules applied, staff tooling for the exceptions, and the record system staying the source of truth.
Real availability, your rules applied, and nothing to download. Web first is deliberate, because a store listing is not an adoption strategy.
Patients choose inside limits you set: which types are self bookable, which providers, how far ahead, what needs a human first.
One experience across locations that run different configurations, or different record systems entirely.
Intake, eligibility, referral and authorisation checked before a booking is confirmed rather than discovered afterwards.
Filling a cancellation with the right patient for that slot, not the first one who answers.
Because the front desk still owns the exceptions, and they need the context the automation collected.
Ranges from projects we have delivered, not a price list. The final number depends on how many record systems, how many rules, and what each vendor allows.
Patient booking with one record system integration
$15,000–$25,000
Or more than one record system
From $25,000
Support and interface maintenance
Monthly, priced separately
How many record systems and whether each allows write, how many appointment types and rules, whether eligibility or authorisation gates are in scope, multi location routing, whether native apps are needed or web is enough, staff tooling.
Your record system vendor's own fees. Dentrix on premise publishes $5,000 for read setup, $5,000 for write, plus monthly royalties. Epic Vendor Services is $1,900 a year. Others have programme costs they do not publish. We get a vendor quote before agreeing a fixed scope, and it stays visible as your cost rather than buried inside ours.
HHS does not certify software as HIPAA compliant. We sign a BAA, document where PHI lives, and build the safeguards your risk analysis expects. No certificate on the wall, but an architecture you can show an auditor.
So does every subprocessor that touches PHI, including cloud providers, support tools and any AI service in the workflow. You get that list by name.
Showing where PHI lives, who holds production access and how it is approved, how our support people reach a running system, what is logged and for how long.
Role based, audit logged, and our access is removed at handover.
HIPAA does not prohibit offshore development, and HHS is clear that ePHI processed overseas raises considerations your risk analysis has to cover. Rather than claiming nobody touches data, we show you which environments hold PHI and who can reach them.
Tracking SDKs in a health app can process sensitive data, and we tell you what each one sends.
CLIENT REVIEWS
Maurice DarbyshireinFounder, CASSA“Attract Group's efforts resulted in a bug-free app that beta users could easily navigate. The team provided frequent updates on their progress and was highly accommodating throughout the engagement. Attract Group was organized and responsive.”
Pavel YeliseevinCTO, Libernetix“Attract Group provides outstaffing services for a fintech company. They take the time to better understand our requirements and provide the best options. Attract Group delivers on time, and their communication is quick.”
Fathi M. AlbatieinBroadcast Project Lead, SportHub“Attract Group has deployed top-notch professionals who manage the project efficiently and ensure timely delivery of outputs. They also impress us with their transparency in their technical skills and business consulting values.”
01–03 / 06 CURATED · 39 TOTAL ON CLUTCH
Every new senior counselling referral goes to the nearest therapist with available capacity and is confirmed in seconds. The arbitration happens inside the record system, not in a parallel app. That is the pattern this work needs.
Six years, December 2018 to November 2024. Every new senior counselling referral goes to the nearest therapist with available capacity and is confirmed in seconds. The arbitration happens inside PIMSY, the behavioral health record system, rather than in our app. That is the pattern this work needs: the record system stays the source of truth.
Clinic and hospital operations software with appointment search and sorting, and a queue and consultation view carrying payment history and position in line. Built to remove manual appointment making and phone calls. Client confidential.
Telemedicine platform for public schools: urgent care access with scheduling and clinical workflow support for school environments.
FAQ
Build versus buy, record system access, patient adoption, support and when we tell you not to do this.
Tell us which EHR or practice management system you run, how many locations, and which scheduling rules matter most. We respond with whether real time booking is possible and what a build would include.