For polyclinics

Polyclinic software for several doctors and specialties.

HospiX is polyclinic software - a healthcare information system for an institution with several doctors and several specialties. Everything that makes a practice more complex as it grows - packages, laboratory, insurers, partners, roles - is part of the same system here, not a separate program.

Several doctors, one schedule

The Planner shows every doctor and calculates availability for each one individually. The system knows which doctor provides which service, so when booking it offers only those who actually perform it - which is the difference between a calendar and a schedule.

Specialties are kept as a separate catalogue and linked both to doctors and to services, so the offering filters itself.

  • Availability per doctor, with a doctor-to-service link
  • Specialties and skills as separate catalogues
  • Schedule search by patient, service, or note

Packages that break themselves down

A package is a set of services and tests sold as a whole. When a package is booked, the system breaks it down into individual services and lab tests and distributes them to the doctors who provide them - one package can become several appointments with different doctors.

At billing a package behaves the other way round: it is charged as a single line item at its own price, no matter how many appointments it broke down into.

Several payers, several price lists

A polyclinic rarely has one price per service. HospiX keeps parallel price lists - standard, per insurer, per partner, and purpose-built - and at billing selects the one that applies to that payer.

Prices can also be changed in bulk: by copying a price list, raising or lowering it by a percentage, or including and excluding items. Every price change stays on record.

  • Standard, insurer, partner, and purpose-built price lists
  • Bulk changes and price list copying
  • Price history - who changed it, from what to what

The laboratory inside the system

A lab referral is issued from an appointment, the result returns to the record as a PDF, and tests enter the invoice as individual line items. There is no second program and no re-typing between systems.

Roles, trail, and reports

Five roles with rights checked on every route, an immutable audit log, and staff profiles with biography, specialties, and languages. A daily business overview arrives by e-mail automatically, and the monthly settlement per partner on a set schedule.

Administrator reports for a chosen period - reversed invoices, deleted lab referrals, business report - are generated as PDFs and kept.

Open to a patient portal

The whole API is described by an OpenAPI contract, so the system can connect to a patient portal: online appointment requests arrive in a queue where they are accepted, declined, or answered with an alternative slot. The portal itself is a separate product - HospiX exposes the side facing it and remains the canonical source of appointments.

Frequently asked questions

What if a package covers services with different doctors?

The system breaks the package down and creates an appointment with each doctor providing their service. Billing still goes through as a single line item, at the package price.

Can every partner have their own prices?

Yes. A partner price list takes precedence over the insurer and standard lists, and the price difference is applied automatically at billing.

How is it controlled who sees what?

Through five roles - administrator, doctor, nurse, consultant, super-administrator. The right is checked on every route, not merely by hiding menu items.

Is there a record of who changed what?

Yes - an immutable audit log records who did what and when, and it is available to the administrator.

Does HospiX connect to a patient portal?

Yes, through an OpenAPI contract and an adapter. Requests from the portal arrive in a queue inside the HIS, and the HIS remains the source of truth for appointments. The portal is a separate product and is contracted separately.

What does the switch look like for an institution with several doctors?

We move your data across during onboarding - from an Excel or CSV sheet, or from your old system's database - to the extent we agree, based on what can be exported (the app itself has no self-serve Excel import). How long onboarding takes depends on the number of users and specialties; in the demo we walk through that conversation with your numbers.

Show us your polyclinic

In the demo we walk a flow with several doctors and several payers - a package that breaks down, a lab referral, and an invoice with co-payment.

Book a demo

Modules

The modules a practice actually uses, over one patient record

The institution picks the modules it needs - all working on the same patient record and the same audit trail.

Clinical 01-04

01

Planner

Daily and weekly calendar, drag-and-drop scheduling, color-coded statuses, and filters to customize the view.

02

Patients

Registry with visit and service history, alerts, policies, referrals, documentation, and laboratory.

03

Medical documentation

Reports, anamnesis, and templates, with ICD-10 and PDF, patient consents and approvals, plus a history of past medical reports.

04

Laboratory

Test catalog, panels, requisitions, and results.

Business 05-09

05

Billing & invoices

Per-service or package billing, discounts, reversal, and reports.

06

Insurance & partners

Policies, co-pay, insurance referrals, and partner commissions.

07

Price lists

Hierarchical per partner and insurer, or standard (default), with price-change history.

08

Administration

Staff, audit log, and business reports.

09

Work schedule and shifts

Staff work shifts and management of shifts and rosters.

And more - parts of the system the grid does not showService packagesStaff specialties and skillsNurse reportsPatient consents and approvals (PDF)Report and anamnesis templatesClinical calculators (BMI, HOMA-IR, FIB-4, FAI)Daily and monthly email reportsPatient PortalAppointment timing analytics