Pterion · Software
Software built for one clinic.
Off-the-shelf software is built for the average clinic, and no clinic is average. We build the registration, scheduling, records and charting systems a clinic actually needs, around the systems it cannot change, and we stay to run them.
Assess Design Build Operate
What it involves
Assess, design, build in small releases, and stay.
- 01
Assess. A day with the people who do the work, watching what they type, count and chase. The software is designed from the desk, not from a requirements document.
- 02
Design around what cannot change. The EMR, the government portal, the payment terminal, the licences already paid for. Good clinic software fits between them rather than replacing them.
- 03
Build in small releases. The first version does one job and is used before the second is written. Staff verify; the software types.
- 04
The record is legal. Anything that writes to a medical record has a verification step, a log, and a way back.
- 05
Patient data stays in the clinic’s tenant, under PHIPA, never on ours. Access is by role behind two-step sign-in, changes to a record are logged, and no patient data goes into code, test data or repositories. Every release ships with documentation for the people who use it.
- 06
Operate. The Monday-morning question, the portal that changed overnight, the report the accountant wants. We stay, on a monthly arrangement agreed in advance.
What we have built
- Registration: from triple data entry to a single check Three chances to mistype a date of birth on a legal medical record became one verification. Applies to Medical · Dental
- Physician scheduling that stopped being a monthly argument The rota is generated against the clinic’s own fairness rules; a physician adjusts it on a calendar instead of building it on a Sunday. Applies to Medical · Dental
- Hundreds of private-pay patient leads, tracked from first enquiry to booking Each enquiry is recorded once and followed up on a schedule rather than forgotten, and what a person was told is on file for the next call. Built on licences the clinic already held, with patient data in the clinic’s own tenant. Applies to Medical · Dental · Aesthetics
- Prepaid packages and payments, counted once Every session links to the payment that funded it; a duplicate payment is flagged for a person, never silently dropped or double-counted. Applies to Dental · Aesthetics
- Automated anesthesia charting Monitor readings are captured straight into the anesthetic record as the case runs, so the chart is written during the case rather than reconstructed after it. Applies to Medical · Dental
- One workbook, every Monday The numbers that run the clinic are on one sheet every Monday morning without anyone exporting anything. Applies to Medical · Dental · Aesthetics
What we will not do
- Replace an EMR that works. We build around it.
- Build what a licence the clinic already owns would do. We have said “do not build” and put it in writing.
- Write into a medical record without a verification step and a log.
- Promise a date we have not scoped. Every release carries its own dates, in writing.
Questions clinics ask
- What have you built for clinics like mine?
- Registration that happens once, a rota built against the clinic’s own rules, a system that tracks hundreds of private-pay patient leads from first enquiry to booking, a prepaid-package ledger that counts every session once, an hourly operations dashboard, and anesthesia charting that writes the record as the case runs. Each is described, without names, in the case studies.
- How long does it take?
- It depends on the job. A single-job system goes live as a first release before the second is written; larger systems ship in releases. Every scope carries its own dates, in writing.
- What happens if you are not there on a Monday morning?
- Operating arrangements state a response time in writing, and every release ships with documentation for the people who use it. We built these systems first for clinics where Monday morning was ours.
The first step
Describe the job the software has to do, in a paragraph. We reply with a short written note: whether to build it at all, what we would build first, what it would run on, and what it would cost. No obligation.
Start with an assessment No obligation · a diagnosis first
What it costs
Each release is quoted on its own, as a fixed scope, in writing, before work starts. Operating the system is a monthly amount agreed in advance. Nothing is billed that was not quoted.
We have run the front desk we are selling the fix for.
Being a clinician is hard enough. Running the business around it is not taught in professional school, and the field is corporatizing around the owners who learned it the hard way.
We exist to help clinician-owned clinics stay independent and succeed: to make the operation efficient, to teach what we had to learn ourselves, and to give owners back the part of the work they love.
an assessment.
No obligation · a diagnosis of the problem and what can be done about it · every scope quoted on its own