A Define product

Medaris

Medical information system

beta

Private clinics and medical centres in Kazakhstan — from a single branch to a chain

Become a pilot partner

The problem

What usually hurts

If nothing on this list sounds like you, you probably don’t need this product — and we’ll say so.

Bookings are kept in a logbook and Excel: double bookings for the same slot, lost records.
Registering a visit with the patient’s history takes tens of minutes, and the queue at reception keeps growing.
Reports for government systems are compiled by hand and often have to be resubmitted.
Management cannot see doctor workload or revenue by service without a manual export.
Off-the-shelf MIS make the clinic rebuild its work around the software, not the other way round.

Contents

What’s inside

Reception and scheduling

Online booking and doctors’ schedules in one window: free slots, rescheduling, cancellations, patient reminders. Double booking for the same slot is ruled out by the data model itself.

Electronic patient record

Visit history, prescriptions, documents. The doctor’s workspace is built around ‘fewest clicks per appointment’: one window, large controls, and only the mandatory fields the regulator requires.

Service packages and check-ups

Ready-made screening programmes are sold and tracked as a single whole rather than a scatter of separate services: you can see which stages the patient has completed and which are still to come.

Laboratory

Orders and results are linked to the visit and the patient record — doctors do not hunt for forms in email and messengers.

Exchange with government services

Reporting is generated from the clinic’s working data rather than compiled from scratch at the end of the month. The integration is under way now — it is part of the beta-stage work.

The picture for management

Doctor workload, service mix, repeat visits. The figures come from the same database as appointments — there is no need to reconcile two systems.

Origin

Born from a live project

Our model is pilot first, product second: we build a system for an operating business, take it through to everyday use, and only then turn it into a product.

Medaris grew out of the digital platform of DEYA, an operating multi-specialty medical centre (dea.kz, Petropavl). We designed the system not from a technical specification but from the daily work of the reception desk, doctors and clinic management — we spent a week observing appointments on site. That is why it has no box-ticking features, and does have the ones missing from off-the-shelf products.

View the pilot case

Why we took on an MIS at all

Off-the-shelf medical systems are usually written from the regulator’s point of view: they can submit reports, but do little for the people who sit at reception every day. The clinic bends its work to fit the system, staff start keeping a ‘parallel’ record in a notebook, and six months later the system is full of data nobody trusts.

We came at it from the other side — from the clinic’s working day. First we built a platform for a real medical centre, brought it into daily use, saw where staff stumbled, and only then started turning it into a product.

What Medaris does not do

It does not replace accounting and does not try to be an ERP. It does not handle telephony or a call centre. It does not work as a cash register. In these areas we build integrations rather than a second accounting loop — duplicating data between two systems always ends in discrepancies.

Stage

Where the product stands now

beta

Beta. The first client is being onboarded and integration with government services is in progress. This is an early stage — which is exactly why pilot clinics get priority development for their processes and a say in what the product becomes.

Status

Questions

What people ask about Medaris

What does ‘pilot clinic’ mean, and how is it different from a regular purchase?

A pilot clinic gets special terms and priority in development: your processes shape the product rather than being forced to fit it. In return, we count on your feedback and on working together on the launch. The number of pilots is limited — otherwise priority stops being priority.

How do we move off paper and Excel without shutting the clinic down?

Step by step. In the pilot we ran the system alongside the paper logbook for two weeks and trained staff during real appointments — only then did we switch the old way off. An abrupt cutover is not acceptable in a clinic: the cost of a mistake is a lost appointment.

What about personal medical data?

Data protection requirements were built into the architecture from the start, not bolted on later. Data is hosted on servers in Kazakhstan — this is required by personal data law, not a matter of preference.

What if a feature we need is missing?

We will tell you straight whether it is on the product roadmap or a separate project. We do not promise to ‘build everything’ — at beta stage an honest answer is more useful than a sale.