Skip to content

Create an account

HekimBis home
A young patient on a tram looking at a phone, wearing earphones

A patient portal that opens under your clinic's name

Your patients manage appointments, complete forms and consents, and see only the results and documents the physician has released, in an account that carries your clinic's name and colors. The account is the secure way in to the patient's own health file.

Patients run their appointments, forms and payments from their own account

Because appointment changes, forms, consents and document requests are made in the patient's own account, the front desk handles fewer calls and paper forms. Lite covers the secure account, forms and consents, released content and messaging; Pro adds advanced flows and the payment view; Clinic adds the branch and organization experience.

Appointments
Patients see available slots, book, change, cancel and confirm, and check in on arrival. Slots come from the clinic's real calendar, so double bookings do not occur. An offer for a freed slot reaches the portal from the waitlist.
Forms and consent
The pre-visit questionnaire, privacy notice and consents are completed in the portal, and files can be uploaded. Privacy notice, explicit consent and clinical consent are separate records, and patients can withdraw consent.
Results and documents
Laboratory results, reports, documents and care instructions released by the physician appear here. Every view is written to the audit log.
Payment
Patients see their balance, payment plan and receipts. Online payment is made on the payment provider's hosted page; card details never enter HekimBis.
Messages and requests
Secure messaging separates clinical and operational topics, and the screen shows an emergency notice and the response-time target. Data access, correction and copy requests, and account closure, are submitted here too.
Dependent accounts
A parent or guardian manages the appointments, forms and documents of their child or of the person in their care from their own account.

A result reaches the patient when the physician releases it

Something appears in the portal only when the physician says “release”. A result or document does not reach the patient on creation; the physician reviews and releases it, the patient receives a generic notification and looks after a secure sign-in. A record released by mistake can be withdrawn.

Patient05End

Patient signs in and views

The content opens after an identity-verified sign-in; the view is written to the audit log.

  • The process is complete here.
5 / 8

All steps

  1. 01 Result or document created (Clinic) A lab result, report or document is saved. It is not yet released and is invisible in the portal.
  2. 02 Physician reviews (Physician) The physician reviews the content; for critical results an acknowledgement is recorded.
  3. 03 Release (Physician) The physician opens the content to the patient with an explicit action; release is always the physician's decision.
  4. 04 Patient notification (Portal) A generic notification and a secure link go to the patient; no result or diagnosis is included.
  5. 05 Patient signs in and views (Patient) The content opens after an identity-verified sign-in; the view is written to the audit log.

Alternative path from 03 Release; it returns to the main flow at 02 Physician reviews.

  1. 03a Withdraw release (Physician) If a mistaken release is noticed, the physician withdraws it; the content leaves the portal, past views stay in the audit log, and the content returns to review.

05 Patient signs in and views

The clinic knows every window it opens to a patient

The point of the portal is not to show patients more, but to show the right information at the right time. The clinic keeps the release decision and can follow from the record what the patient saw and when.

Release decision
Every result and document is released by an explicit action of the physician. A mistaken release is withdrawn; the content leaves the portal and earlier views stay in the audit log.
View record
Every item the patient opens is written to the audit log with who viewed it and when.
Generic notification
A notification carries a general sentence and a secure link; the result, diagnosis and reason for the visit open after sign-in.
A separate access model
The portal is tied to the clinic's patient file and requires identity verification; a public search never opens a path into a patient file.
A physician reviewing a result file at her desk before releasing it to the patient

In guardian and dependent accounts, access is granted on proof

Access to the health information of a child or a person in care does not open by someone simply stating who they are. The clinic records proof of the relationship, and access is defined by a scope and a term. A parent books their child's appointment, completes the forms and sees released documents from their own account.

When the child comes of age or the guardianship ends, the term expires and access closes.

  • Proof of the relationship is recorded, and access stays closed until the proof is complete.
  • The access scope, for example appointments only or appointments and documents, is defined separately.
  • When the term ends, access closes; earlier views stay in the audit log.
  • Every action taken on behalf of a dependent shows which account performed it.
A parent looking at a phone in a paediatric waiting room, with blurred toys behind.
  • Türkçe
  • English
  • العربية
  • Русский
  • Deutsch

Patients write in their own language, and Arabic runs right to left

Patient screens are offered in Turkish, English, Arabic, Russian and German, and the Arabic interface is laid out right to left. The language base is the same in every plan. Clinical and legal texts such as consent and privacy notices are translated with human approval; a machine translation stays an assistive draft until approved.

Health tourism

Frequently asked questions

See all questions
Does the patient portal appear under my clinic's brand?

Yes. The portal is offered under your clinic's own brand, and patients sign in to their own clinic's portal. Brand settings are defined during setup.

Can a patient see a result before the physician?

No. The portal works on an explicit release model: an unreleased result, report or note never appears on the patient side. After release, the physician can still withdraw it if needed.

Does the notification show the result?

A notification carries a general sentence and a secure link; it contains no result, diagnosis or reason for the visit. Details open only after the patient signs in.

Can patients pay from the portal?

Balance, payment plan and receipts appear in the portal. Online payment is made on the payment provider's hosted page; card details never enter HekimBis.

Can patients make requests about their own data?

Patients can submit data access, correction and copy requests and ask to close their account from the portal. The requests reach the clinic as tasks and are tracked against KVKK deadlines.

What determines what a patient sees in the portal?

Results, reports, documents and care instructions released by the clinic are visible. Appointments, forms, consents, balance and messages are the patient's own transaction screens.

How does a patient book from their phone?

In the portal the patient picks an available slot from the physician's real calendar, so double bookings do not occur. Confirmations and reminders follow the patient's communication preference, and the patient can check in from the portal on arrival.

Can the portal be used on a phone?

The portal is a web surface patients reach with their secure account, and it works on a phone screen too.