Settings

Software that bends to the clinic

Every clinic is a little different, and most systems handle that by asking you to open a ticket. Services, prices, forms, roles, branches and templates are settings, changed by your own manager, on a Tuesday, without asking us.

Request a demo All features

Users14 accounts · 6 roles BranchesRiyadh · Jeddah · Cairo Permissions6 permission groups Procedures212 procedures · 38 conditions Price listsStandard and insurance Custom formsConsent, medical history Print & templatesInvoices, prescriptions ZATCAPhase 2 · connected Referral sourcesTrack where patients come from QuestionnairesMedical history, feedback AutomationsTasks and messages on events Business registrationCR, VAT and clinic licence Advanced settingsNumbering, currency, tax and defaults Patient remindersAppointment, recall and payment reminders Medical optionsAllergies, conditions and medications Clinical optionsTreatment stages, surfaces and notes

The things that differ between clinics

A polyclinic is several clinics that disagree with each other about almost everything. Each department can be set up as itself.

Services and procedures, per specialty
Price lists per insurer, per plan and per branch
Intake and clinical forms per specialty
Session lengths and room requirements per service
Numbering, currency, tax and defaults per branch

Who may do what

Permissions are the setting clinics get wrong most often, usually by being too generous because being precise was too hard.

Roles built from permissions, not chosen from three presets
Per branch, so a manager manages one location
Per record type, so reception is not given clinical notes
Approval thresholds for discounts and refunds
A change of role that takes effect without a re-login

Changed by you, and recorded

Configuration that anyone can change and nobody can audit is its own kind of problem. Every change is a change with a name on it.

Edited by your manager rather than requested from support
Every settings change in the audit log, with who made it
Changes that affect history do not rewrite it
Templates for invoices, prescriptions and reports
A branch that runs differently without a separate account

Who changes settings

The point is that this is not a list of things only we can do.

Clinic managers

Prices, services, forms and rotas, without a ticket.

Owners

Permissions and approval thresholds they can actually reason about.

Department heads

Their own forms and session lengths, not the clinic’s average.

Configured once versus configurable

Both are set up at the start. Only one of them survives the clinic changing its mind.

The way it is done now

A ticket to change a price
One form for every department
Three permission presets
One set of defaults for the group
Settings changed by nobody in particular

With Medicolize

Edited by your manager
A form per specialty
Roles built from permissions
Defaults per branch
Every change with a name on it

Questions

Settings — what clinics ask

Can we change prices ourselves?

Yes, per service, per insurer, per plan and per branch, by your own manager. A price change is not a support request.

Can each specialty have its own forms?

Yes. Intake, clinical and consent forms are set per specialty, because a dermatology intake and a physiotherapy intake have very little in common.

How granular are permissions?

Roles are built from individual permissions rather than picked from presets, and they apply per branch and per record type — so a receptionist can be given billing without clinical notes.

Can one branch run differently from another?

Yes: its own numbering, currency, tax defaults, services, prices, forms and rotas, on one account rather than two.

Are settings changes recorded?

Yes, in the audit log with who made them and when. Configuration nobody can audit is a problem of its own.

Keep going

Put Settings in front of your own week

Half an hour on your own services, packages and price list. Someone calls you back within a day.

Request a demo WhatsApp us