Home / Medical Practice Software
Practice software built around how your practice actually works.
Patient records, scheduling, billing and clinical notes, fitted to your workflow instead of the other way round.
Does this sound like you?
- “We’ve adapted our practice to fit the software, instead of the other way round.”
- “Feature requests go into our vendor’s queue and never come out.”
- “Our patient and billing data is stuck inside a system we can’t extend or export cleanly.”
- “When something breaks, we submit a ticket and wait. Nobody understands our actual setup.”
What I’d do.
Understand how your practice actually runs.
Patient flow, scheduling, billing and clinical notes, before proposing anything.
Check what data protection needs apply, and scope honestly.
Privacy and compliance requirements are agreed up front, not discovered later.
Build with your staff’s input at every stage.
So the system matches how people actually work, not how software assumes they should.
Proof.
What I built for a medical and dental practice.
I designed and built a complete practice management platform: patient records, medical aid billing and claims, multi-practitioner appointment booking, and dental charting with treatment tracking, all in one system with role-based access and audit logging.
See the practice platform project →Excellent service, highly recommend.
How it starts and what it costs.
Tell me how your practice runs today, and what’s not working. That’s enough for a first conversation. If it needs more digging before I can quote responsibly, the next step is a separately paid discovery piece.
For your technical person
What this covers
Patient records, medical aid billing and claims, multi-practitioner appointment scheduling, clinical notes and dental charting with orthodontic tracking, patient self-service and role-based permissions.
Stack and architecture
React, Next.js, Node.js, TypeScript, PostgreSQL. Multi-tenant architecture, role-based access control, audit logging, consent workflows, and encryption at rest and in transit.
The platform’s API layer covers 300+ endpoints across patients, billing, medical aid claims, appointments, dental charting, orthodontic tracking, clinical notes, files and notifications.
Data protection
POPIA aware data handling on every build.
Background
- 26years in IT
- 15+years building software
- 300+API endpoints in the platform
Questions owners ask.
Is this software already built, or would it be built from scratch?
That depends on the fit. In some cases the practice platform I have already built can be adapted. In others, I scope new modules or deeper custom work around how your practice actually operates.
How long does it take to get set up?
The delivery window is set in the written quote once the workflow, data, hosting, migration and acceptance requirements are understood. If those details are still uncertain, the next step is a separately paid discovery piece.
What does it cost?
Pricing depends on the modules, users and rollout involved. I give clear pricing after understanding your practice and the delivery model that fits.
Can you migrate data from our current system?
Migrating patient records, billing history and appointment data from another system is something I scope as part of the build, checking data integrity as part of that work.
Do you provide ongoing support?
The quote defines written acceptance and 14 calendar days of defect only correction. Later maintenance, operational support and feature development are quoted separately.
How are privacy and security requirements handled?
Privacy, hosting, access control, audit and data handling requirements are scoped per practice. Where a practice has specific regulatory or organisational requirements, those are handled as part of the plan.
Related help.
Tell me how your practice runs today.
+27 87 150 9305Monday to Friday, 09:00 to 20:00 SAST. Or email info@antondevilliers.com.