DE

Designed for operators who run more than one room

Operations platform for networks of self-service medical rooms

Book a demo

One system runs a whole network of self-service medical rooms, where every role gets its own interface and all of them write to one record.

A week of a room’s free slots, Monday to Friday, with the count of appointments still open on each day.

Can this room take a patient in the next hour?

The answer depends on the kiosk, six devices, the consumables, the cleaning log and the door lock. It is worthless if it takes four phone calls.

A single day in a room’s schedule, marked as scheduled with one slot left.

Nobody retypes a device check before an inspection.

Maintenance intervals and metrological checks run per device. You keep the device registers the MPBetreibV asks for in the same system, and the checks fill themselves in from the work orders that were actually carried out.

Three roles — network operations manager, medical lead and field service — each with the permissions it carries.

Operations staff keep a room running without opening a patient record.

Every site you add puts more people within reach of a patient record. Under the GDPR that separation has to be a control rather than a matter of trust, so it runs through roles and permissions. Every read is logged.

A site card for Werneuchen, marked operating, with its address and its opening hours.

You can change how a room is staffed after it is already running.

A room runs with a doctor on site, with an assistant on site, or with nobody. You decide that per site and you can decide it again later.

By role

Stay in control of your sites – remotely and efficiently.

  • One board for every site.
  • Problems become visible early.
  • Supplies stay ahead of demand.
  • Completed work stays transparent.
  • Payments stay aligned with service.

Medical expertise reaches beyond the room.

  • Walk into the consultation with the data already in front of you.
  • Connect securely through video and chat — on your infrastructure.
  • Review, approve, and move on — the work is already prepared.
  • Focus on what needs you. Let the rest run in the background.
  • Know what changed, who approved it, and when.

Complete measurements and documentation at the point of care.

  • Guided protocols, step by step
  • Contraindications caught before the offer
  • Measurements attach themselves to the visit
  • Handover is a record with an owner
  • The doctor’s console, scoped by permission

Healthcare that fits around you.

  • See the current price before you book.
  • Each booking comes with its own secure door code.
  • Consent is clear, easy to understand, and always versioned.
  • The help button connects you directly to a named contact.
  • Your readings remain clear and accessible afterwards.
The Control Center platform core screen, listing roles, the staff who hold them and their MFA state.

What it covers

The platform starts at the site register and ends at the accounting export.

The kiosk application, the medical device firmware, the video service and the payment terminal stay yours. AbiKiosk integrates with them and holds the records they produce.

The network

Physical assets, and whether
they are working right now.

  • Site registry and lifecycle
  • Kiosk and signage fleet
  • Medical devices and check intervals
  • Consumables and hygiene
The Sites board, one row per room with kiosk state, visits today, open work orders and lowest stock.

The care

What is offered, who received it,
and what was recorded.

  • Service catalogue and protocols
  • Patients and consents
  • Visits and records
  • Doctor pool and consultations
The Visits board, showing today’s bookings with the channel each came through and its single-use door code.

The business

See what flows in, out,
and keeps rooms running.

  • Payments and payouts
  • Campaigns and feedback
  • Incidents and field dispatch
  • Accounting export
The Payments and finance board, with settled totals, split by payment method and revenue by site.

The platform

Seamless kiosk
management.

  • Identity, roles and audit trail
  • Search across every entity
  • Notifications and accounts
  • Open API
The Platform core screen, listing roles, the staff who hold them and their MFA state.
Book a demo

Data protection

Operator duties become workflows that produce their own evidence.

Video and chat on Matrix

Consultations and secure messaging run on Matrix, an open, federated protocol that can be hosted on infrastructure the operator controls. No consumer messaging service sits in the consultation path. Matrix is also the protocol the gematik TI-Messenger specification builds on.

Roles decide who can open a record, and every read can be logged

Running a network means more people can reach patient records. The operator decides who holds which role. Operations staff see that a measurement was flagged. They do not see the measurement. The boundary is enforced by role, not by convention, and every read is written to the audit trail.

Consent, access and retention

Consent is versioned and keeps its full history, so it is always answerable which version applied on a given day. Access to a record is scoped by role and logged on every read. Retention rules are configured per record class, and that is where the operator decides how a long statutory retention period and an erasure request fit together.

Device schedules and the work actually done

Maintenance and metrological-check intervals are scheduled per device, and each work order records what was carried out, by whom and when. Those records export as the evidence for the operator’s Medizinproduktebuch under the MPBetreibV. Medical content is versioned with sign-off history, and logging is append-only.

Integrations

It connects to the hardware and the video stack you already chose.

01

Kiosk application

Visit sessions, questionnaire responses, telemetry, help-button events.

02

Device gateway

Measurements with device provenance, health checks and self-tests.

03

Video and chat

Matrix. Consultation events, transcript references, documents.

04

Payments

Transactions, refunds, settlement files.

05

Accounting

DATEV-compatible export.

Appearance

The console can wear the operator’s brand, not ours.

Your mark and your colours

Logo, accent colour and the name in the shell belong to the operator. Staff sign in to something that looks like the organisation they work for, not like a supplier they have never heard of.

Light and dark

Both themes ship, and the choice follows the person rather than the device. A room with the blinds down and a desk at head office do not have to agree about it.

Text size that moves the whole interface

Three steps, moving type, controls and spacing together rather than only the type. A tablet held at arm’s length is a different instrument from a desk monitor.

One record. Your language.

Translated in full, and the language follows the user, so a German site doctor and an English-speaking network manager read the same record each in their own.

Questions

The questions that come up before a demo.

What runs where?

Two consoles over one record. Control Center runs the network from a desk. Clinic runs a single room from a tablet. A visit is the same record in both, seen through two permission profiles and written to one audit trail.

Which operating systems do you support?

It is a web application, so the consoles run in a current browser on the desktops and tablets an operator already has, Windows included. Nothing is installed on the workstation and nothing is tied to one vendor’s hardware.

Can it run in our own cloud?

Yes. It can be hosted by us or deployed into infrastructure the operator controls. Which of the two, and in which jurisdiction the data sits, is scoped per engagement rather than fixed by the product.

How do measuring devices connect?

Device integration is a defined boundary in the platform: a measurement arrives with its device provenance and is bound to the visit that produced it. Which devices and which transports are onboarded is scoped per engagement.

Can we keep our own video system?

Video and secure chat run on Matrix by default. Consultation events, transcript references and documents attach to the visit through a defined interface, so another provider can take that place where an operator already runs one.

Can it reach our existing support desk?

Incidents and work orders are records with their own history, owner and resolution. Forwarding them into a hotline, mailbox or ticket system an operator already runs is an integration scoped per engagement.

Which languages does the interface speak?

English and German, translated in full rather than machine-filled. The language follows the user, so a German site doctor and an English-speaking network manager read the same record in their own language.

Who owns the data?

The operator does. Records export in open formats, and the accounting month leaves as a DATEV-compatible export. Nothing about the design requires an operator to stay in order to keep reading what it collected.

Scale your rooms, not your costs.

That’s what one system makes possible.

Book a demo

Or write to info@lembitech.com
AbiKiosk by Lembitech Data protectionPrivacy PolicyTerms of Use