Appointment and capacity management
The appointment diary, room and clinician resources, occupancy rates and empty slots are measured. The no-show rate is reported by patient group and hour; lost capacity becomes visible.
INDUSTRY SOFTWARE · CLINICS AND POLYCLINICS
Clinic software that connects the flow from appointment to treatment plan, from reminders to the patient journey
We are not trying to replace your clinic's core patient record system. We bring appointments and patient flow, treatment plan tracking, reminder and recall processes, consumables and stock management, the health tourism patient journey and reporting together in a layer built with regulatory boundaries in mind. The source code stays with you.
7 modules Appointments and flow, treatment plans, reminders, consumables and stock, health tourism journey, reporting, integration
Regulation first The rules on the core patient record system and data submission are discussed in the first meeting
KVKK focused Health data is special-category data under KVKK (Turkish data protection law); access, retention and audit trails are built accordingly
100% source code The software and the data stay entirely with you
Does this sound familiar?
Patient records are kept, but appointments, follow-up and recalls depend on individuals
In clinics, the medical record is usually held in a system. The gap is not on the medical side but on the business side: filling the diary, chasing unfinished treatments, bringing patients back and controlling consumables run on individual effort in most clinics.
- The appointment diary is not managed for occupancy. Because empty slots and no-shows are not measured, lost capacity stays invisible; the clinic can look full while a significant share of chair hours sits idle.
- The no-show rate is known, but its causes and the patient groups it concentrates in are not analysed. Because reminders run irregularly, at the mercy of staff workload, the patient group that most needs reminding is often never called.
- In multi-session treatments, unfinished plans are not tracked. When a patient stops coming after a session, nobody notices; the treatment goes unfinished and the planned revenue never materialises.
- Patient recalls and check-up appointments depend on people's memory and notebooks. When staff change, follow-up breaks off entirely and the relationship with those patients quietly ends.
- Consumables and items such as implants are not linked to treatments. Because nobody knows what a procedure actually costs, pricing is done by looking at the market, not at your own cost.
- Productivity is not measured by clinician and procedure. Because chair and room utilisation is invisible, new investment decisions are made without knowing whether existing capacity is actually full.
- For health tourism patients, the journey from first contact to flight, treatment and aftercare sits in fragments across different channels and different people. At which stage the patient drops out cannot be measured.
- The real contribution of patients arriving through agencies and referral channels is not calculated net of commissions and cancellations. The channel that sends the most patients may not be the one that earns the most.
- Patient communication runs over personal phones and messaging apps. Records do not stay with the institution, health data accumulates on personal devices, and this poses a serious risk for both follow-up and data security.
- Consent forms and information documents are kept on paper. When a record is requested it is hunted down in the archive; which version of the document was signed is usually never recorded at all.
The sector's software landscape today
Which software do clinics use today, and where does it get stuck
Unlike other sectors, software in healthcare is intertwined with the regulatory framework. On the core patient record side there are established providers and requirements; the gap usually opens on the business and patient relationship side.
| Layer | Software in use today | The gap it leaves |
|---|---|---|
| Hospital and clinic information management systems | Products of healthcare information management system providers (Akgün, Probel, Monad and similar companies) | They are the established solutions for patient records, medical records and data submission to the Ministry. Because such software is subject to registration and approval processes and data submission obligations, this is not an area that can be changed freely; the core system stays in place in most clinics, and it should. These systems focus on the medical record; business questions such as diary occupancy, reminders, channel analysis and cost per procedure fall outside the scope of most installations. |
| Public systems and data submission | e-Nabız, Medula, MHRS and related public interfaces | Healthcare providers' data submission and authorisation transactions run through these systems and are mandatory. Access to these interfaces is subject to an authorisation regime; it is not an area any software can freely connect to. Keeping these operations in your existing core system is therefore both correct and, in most cases, the only option. |
| Appointments and patient communication | Phone, messaging apps, calendar software, call centre tools | In most clinics this side is not systematic. Diary occupancy, the no-show rate and the reminder process go unmeasured; records stay on individuals' phones. That produces both operational blindness and a data security risk: health data spreads across personal devices and beyond the institution's control. It is also usually where the fastest gains can be made in clinics. |
| Accounting and bookkeeping | Logo, Mikro, Netsis and similar systems | Necessary on the financial side, and they stay in place. But they do not produce business indicators such as cost per procedure, consumables usage or clinician productivity. In these systems the clinic's profitability appears as total income and expense; the question of which procedure or which clinician earns what goes unanswered. |
| Health tourism processes | Spreadsheets, messaging groups, agencies' own panels | The journey from first contact to post-treatment follow-up runs in fragments, and each fragment sits with a different person. What a patient from a given channel actually contributes, and at which stage patients are lost, goes unmeasured. This is the main reason advertising and agency budgets are spread inefficiently; the channel with the biggest spend may not be the one that brings the most. |
| Stock and consumables management | Excel sheets, store ledgers | In most clinics, consumables and items such as implants are tracked without being linked to treatments. The true cost per procedure is therefore unknown. Expiry date and lot tracking stay equally weak; unusable material is only discovered at a count, when it is written off. |
Our approach
A layer built not to replace the core system but for the business and patient relationship side
Honesty is the first requirement in this field. Your core patient record system and your links to public systems are subject to regulation, and we make no claim to replace them. The layer we build fills the business gap that system leaves open.
Treatment plan and session tracking
In multi-session treatments, the plan and the completed and pending sessions are tracked. Unfinished treatments drop onto a list; when a patient does not return after a session, it shows as a record.
Reminder and recall flow
Appointment reminders, check-up calls and post-treatment follow-up are tied into a regular flow. Communication runs through the institution's channel; the record stays in the system, not on a staff member's phone.
Consumables, implant and stock management
Consumables and items such as implants are linked to the procedure and the patient; expiry dates and lots are tracked. A true cost per procedure takes shape.
Health tourism patient journey
From first contact through quotation, travel, treatment and aftercare, the journey runs in a single record. At which stage patients are lost, and what each channel actually contributes, is measured.
Business dashboard
Occupancy, revenue and cost reports by clinician, procedure, room and channel. The clinic is monitored as a working business, not as a single turnover line.
The systems we build
Systems we build for clinics
Not every clinic needs all of them. In a single-site clinic, appointments and reminders alone make the biggest difference, while in health tourism the patient journey comes to the fore.
CRM
Appointments, patient flow and reminders
Diary and resource management, occupancy measurement, reminder and recall flows; communication running through the institution's channel and being put on record.
Detailed page → ERPTreatment plan and session tracking
Plans for multi-session treatments, completed and pending sessions, the list of unfinished treatments and follow-up tasks.
Detailed page → WMSConsumables, implant and stock tracking
Linking consumable and implant items to procedures and patients, lot and expiry-date tracking, critical stock alerts.
Detailed page → BIBusiness and channel dashboard
Occupancy, revenue and cost reports by clinician, procedure, room and referral channel; comparing channels' net contribution.
Detailed page → APIIntegration with your existing system
Matching appointment and patient information to the extent your core patient record system allows; the integration route is decided together with your provider.
Detailed page → QMSConsent and document management
Capturing informed consent and information documents digitally, storing them with their version and linking them to the patient record.
Detailed page → APIData governance and access logging
Role-based access, retention periods and an audit trail of who accessed which record, built on the premise that health data is special-category data.
Detailed page → Integration with your existing ERP
We do not replace your core system, we work alongside it
Your patient record system and your links to public systems stay in place. The layer we build works on the business side and matches with the core system through the methods that system permits.
Our integration approach →- Matching appointment and patient information with your existing patient record system; the integration method follows the interface your provider permits, and what is possible is put in writing at the start of the project.
- Payment, account and invoice matching with accounting systems such as Logo, Mikro and Netsis; per-procedure revenue and the financial record meet on the same ground.
- Connecting corporate communication channels; moving patient communication from personal phones to institutional records so that correspondence stays with the institution.
- Enquiries from the website and advertising channels land directly in the system and are tracked by channel; which channel loses patients at which stage becomes measurable.
- Connecting payment and instalment systems to collections tracking; the treatment plan and the payment plan run in the same record.
Outcomes
What changes once this layer is in place
- Diary occupancy and idle capacity are measured; the no-show rate is visible by patient group and hour.
- Unfinished treatments drop onto a list; when a patient disappears between sessions, it gets noticed.
- Reminders and recalls are tied to the system, not to a person; follow-up does not break when staff change.
- Consumable and implant usage is linked to procedures; a true cost per procedure takes shape.
- Expiry dates and lots are tracked; losses from unusable material fall.
- Productivity is visible by clinician, room and procedure; capacity planning rests on measurement.
- In health tourism, the patient journey runs in a single record; the stage at which patients are lost is measured.
- Referral channels' net contribution is compared with commissions and cancellations deducted.
- Patient communication runs through the institution's channel; records stay with the institution and the data security risk falls.
- Consent and information documents are stored digitally; no archive trawl is needed when a record is requested.
Process
A realistic five-stage path that begins with discovery.
- 01
Initial meeting and the regulatory boundary
1 weekWe discuss your clinic's structure, your current patient record system and the point that hurts most. In this sector the first thing to discuss is the boundary of scope: which areas are regulated and untouchable, and which are open. We do not quote before that is clear.
- 02
On-site discovery
1 weekWe observe the flow on site, from reception to examination and from sterilisation to the store. We map where patients wait, the real workload on staff and which record is kept where.
- 03
Scope and pilot design
1 weekWe decide which module to build first; appointments, reminders and treatment plan tracking usually deliver the highest return. Data access and retention rules are put in writing at this stage.
- 04
Development and pilot use
based on scopeThe system is developed and run in parallel with the existing routine in a limited area. Permissions and access controls are tested separately; with health data, that test is never skipped.
- 05
Rollout and handover
based on scopeOther modules are added in turn and integrations are switched on. Users are trained, and the documentation and source code are handed over. Maintenance and support run under a separate agreement.
Why Pan Innovation House?
Not a software vendor, but a digital transformation team that knows the shop floor.
A team that states the boundary upfront
Healthcare has regulated areas, and a proposal that presents them as open causes trouble at the first inspection. We state in writing at the first meeting what can and cannot be done.
We will not try to replace your core system
Your patient record system stays in place. The layer works on the business side and matches through the methods that system permits; we do not aim for conflict with your provider.
We treat health data as special-category data
Access rights, retention periods and audit trails are built in from the start. This is not solved with a security layer bolted on later; it is part of the architecture.
Source code and data stay with you
Everything we produce, source code included, belongs to you. Patient data stays in your own environment; in this sector, that is a requirement beyond debate.
Staged rollout
We do not change everything at once. We start with appointments and reminders and expand as the gains show; progressing without disrupting patient flow is essential.
A handover-ready delivery
Documentation and a handover package are part of the job. If another team takes over tomorrow, we deliver in a state they can take over.
Frequently asked questions
Common questions about Clinic and Polyclinic Businesses software.
Does it replace our existing patient record system?
No, and that is a deliberate boundary. Healthcare information management systems are subject to registration and approval processes and data submission obligations; this is not an area that can be changed freely. The layer we build works on the business side: appointments, follow-up, reminders, consumables management and reporting. How it matches with your core system is decided by looking at the integration method your provider permits.
Can you connect to the public systems?
Access to these interfaces is subject to an authorisation regime and is not an area any software can freely connect to. We therefore recommend that data submission and authorisation transactions stay in your existing system. We investigate what is possible at the start of the project, specifically for your institution and your current provider, and state it in writing; we do not make promises on guesswork.
How is patient data security handled?
Health data is special-category personal data and the architecture is built accordingly: role-based access, per-record permissions, an audit trail of who accessed which record and when, defined retention periods and data kept in your own environment. Legal assessment is your lawyer's domain; we build the technical counterpart of those decisions and produce the evidence.
What changes for our health tourism patients?
The biggest difference is that the journey is gathered into a single record. First contact, quotation, travel plan, treatment and aftercare run in the same record; where communication breaks off is measured. For patients arriving through agencies, the channel's net contribution is calculated with commissions and cancellations deducted; most clinics never do that calculation.
We run patient communication over messaging apps.
That is common, and it carries two problems: records do not stay with the institution, and health data accumulates on personal devices. Our recommendation is to move communication to the institution's channel and put it on record. The transition is staged; unless an interface is built that preserves the pace staff are used to, the transition will not stick.
We are a small clinic; won't this be too heavy for us?
Scope is built to scale. In a small clinic, diary occupancy, reminders and unfinished-treatment tracking alone usually make the biggest difference. We do not recommend building a full-scope system from day one; an unused module is a cost paid for and never recovered.
How soon can we start using it?
The timeline depends on scope and is given in writing after discovery. This sector carries one further uncertainty: your current provider's response time on integration. We mark that as a separate dependency in the plan rather than compressing it into a single promised number.
What do we end up with?
A working system, its source code, the database and handover documentation; a written definition of access rights and retention rules. User training and initial support are part of the scope. Maintenance and development then run under a separate agreement.
Let us start together
Let's define the boundary first, then the scope, together
Let us examine your clinic's flow on site and clarify together which areas are subject to regulation and where quick gains can be made.
Related services