Skip to content

Create an account

Sign in
HekimBis home

Infrastructure

Health data in Türkiye, infrastructure that survives outages

A clinic software's infrastructure is the foundation of everything you see on screen. Here we describe it not by what it is built with but by what it gives your clinic: where the data lives, what happens in an outage and whether a backup can really be restored.

Try it free for 7 daysRequest a demo
A small device with one green status light mounted with tidy cabling in a technical cabinet

Where does the data live, and how is it reached?

Production health data and its backups are kept inside the Türkiye data residency boundary. The application, the data and the backups run within organization isolation.

Devices and the Edge Connector at the clinic stay on the clinic's own network. No inbound connection port is opened from the internet to the clinic; connections are made only outward.

Patients and staff reach the system through web and mobile clients, passing role and context checks. Data, including caches, search and file access, is separated at the organization and branch boundary.

Security

What the infrastructure gives you

Redundancy
The service is built so that it does not depend on a single point. Failover and queue replay are tested so that work continues even if one component goes out.
Backup and restore rehearsal
Backups are encrypted, can return to a specific point in time, and restores are actually rehearsed. After a restore, reconciliation keeps deleted or canceled data from becoming active again.
Monitoring
Health checks and alarms watch the service continuously, and release and rollback procedures are written down. Personal and health data is masked in monitoring records.
Incident response
There is a defined procedure for security incidents and data breaches, with assigned responsibilities and an on-call rota.

A secure bridge from the clinic network to HekimBis

Data from a device reaches HekimBis without opening a port to the clinic, and waits locally if the connection drops.

Clinic screen04End

Clinic screen

The result appears on the patient's record.

  • The process is complete here.
4 / 8

All steps

  1. 01 Device message (Device) A device on the clinic network sends a result.
  2. 02 Outbound, encrypted connection (Edge Connector) The Edge Connector carries data outbound only.
  3. 03 Accepted in Türkiye (HekimBis (Türkiye)) Accepted and stored inside the organization's isolation boundary.
  4. 04 Clinic screen (Clinic screen) The result appears on the patient's record.

Alternative path from 02 Outbound, encrypted connection; it returns to the main flow at 03 Accepted in Türkiye.

  1. 02a Internet down (Edge Connector) Data waits in the local encrypted queue.
  2. 02b Connection restored (Edge Connector) The queue is resent without loss or duplication.

04 Clinic screen

What happens if something goes wrong?

Every scenario has a written response.

  • If a component of the service goes out

    Failover takes over, and queued work is replayed.

  • If the internet drops at the clinic

    Devices keep working locally. The Edge Connector holds data in an encrypted queue and sends it without loss or duplication when the connection returns.

  • If data is changed in error

    The system returns to a specific point in time, and reconciliation follows so that deleted or canceled data does not come back.

  • If a security incident is suspected

    The defined procedure runs: assigned owners, release rollback and an alert path.

  • If a new release causes a problem

    The written rollback procedure is applied.

A backup is only a backup if it can be restored

  1. 1

    Encrypted backup

    Backups are kept encrypted and stay inside the Türkiye data residency boundary.

  2. 2

    Point-in-time recovery

    Backup sets can return to a specific point in time.

  3. 3

    Restore rehearsal

    Restores are actually rehearsed on a regular basis.

  4. 4

    Reconciliation

    Deleted or canceled data is kept from becoming active again.

Frequently asked questions about infrastructure

FAQ
In which country is my data kept?

Production health data and its backups are kept in Türkiye.

Do my clinic devices keep working if the internet drops?

Yes. Devices keep working on the clinic network. The Edge Connector stores data locally, encrypted, and sends it without loss or duplication when the connection returns.

Are backups really tested?

Yes; restore rehearsal is part of backup. Rehearsal results are shared on request.

Where can I follow service status?

Current service status is followed on the system status page, and contractual service levels are in the contract.

Can I get information for a technical security assessment?

Yes. Request a security meeting, and we will go through your detailed question list together.

How long are backups kept?

Backup retention follows a fixed life cycle and never exceeds the retention rules of live data. Numeric periods are in the policy version approved by legal and the product owner.

Is the infrastructure separated by organization?

Yes. Data, including caches, search and file access, is separated at the organization and branch boundary, and one organization's data is never opened to another.

Keep reading

Related pages

Integrations

Company and support