The clinical decision with the physician, the record with the clinic
Software's job is not to decide in the physician's place but to put the information a decision rests on in front of the right person, at the right time and safely.
Vision
A way of working in health care in which every clinic can manage patient information safely and keep the physician's decision at the center.
Mission
To build software that simplifies daily work for physicians and clinics and respects regulation and privacy, and to make sure everything we describe on the site really works in the product.
Three principles
We make product decisions by these three principles.
- The clinical decision belongs to the physician
- Automation and AI produce drafts and suggestions; the record, the signature and the decision are the physician's responsibility.
- Privacy
- Clinical data stays within the organization's boundary; access is limited by role, branch and care relationship, and every action is written to the audit log.
- What we say works
- Every capability we describe on the site and in meetings works in the product today; what we write follows how the product behaves.
The principles are product behavior, not slogans
Each principle has a behavior in the product that corresponds to it.
The physician signs, the record locks
A signed record cannot be edited; a correction is made through a reasoned, traceable correction entry.
Clinical recordsAI produces drafts
AI output is not final without the physician's approval; its source, output and change trail are kept.
AI assistantA physician approves before a result is published
Results become visible on the patient portal with the physician's approval or under the organization's rule.
Patient portalOrganization data stays with the organization
Data is separated by organization and is not opened to another organization on its own.
SecurityEvery access is recorded
Every access to a patient file is written to the audit log with who made it, when and for what purpose.
SecurityNotice, consent and approval are separate records
The privacy notice, explicit consent and clinical consent are kept with their own text, version and evidence.
KVKK complianceThe data belongs to the clinic
The authorized owner can export the clinic's data in every plan, without restriction.
Data migration
When do we count a feature as finished?
A feature is not finished until it has been shown to be correct, secure, understandable, outage-resistant, recoverable and supportable.
- Correct
- A signed record cannot change without a trace, a result is not attached to the wrong patient automatically, and no time slot is booked twice.
- Secure
- One organization's, branch's or patient's data is not opened to anyone else, and unauthorized access attempts are tested and rejected.
- Understandable
- Every action shows a clear success or error state. The user does not meet a dead-end screen or a wrong click that cannot be undone.
- Outage-resistant
- Data is not lost in an internet or service outage; the local queue and replay protect national data submission too.
- Recoverable
- Backups are actually restored; lowering a plan or closing an organization does not lose data.
- Supportable
- Day-to-day tasks can be solved by the clinic's own team without going to the support team, and support access depends on the clinic's approval.
Our view of regulation
Privacy notice and explicit consent are kept apart. They are not merged into one approval; each carries its own text, version, user action and evidence record.
Signature evidence is named by its components: the signature pad, a one-time verification code, a timestamp and the audit log secure the integrity of the evidence.
Production health data is kept in Türkiye. The privacy notice, explicit consent and clinical consent are stored as separate records.
The patient-facing portal, forms, consents and communication are offered in Turkish, English, Arabic, Russian and German. Clinical and legal translation is published with human approval and a version record.
Frequently asked questions about our vision and principles
Who makes the clinical decision?
The physician. Automation and AI produce drafts and suggestions; the record, the signature and the decision are the physician's responsibility.
Where can I verify these principles?
The security, KVKK and payment security pages describe the related behavior in detail, and we can show it in the product together in a demo.
Where is patient data stored?
Production health data is kept in Türkiye, and an organization's data stays with the organization.
What does the AI assistant do?
It prepares dictation, note and summary drafts and warns about missing fields. The physician approves and signs the record, and the source, output and every change are kept on record.
Who owns the patient data?
The clinic. The authorized owner can export the clinic's data in every plan, without restriction.
Why are the privacy notice and explicit consent kept apart?
The notice tells who processes the data and for what purpose; explicit consent is a separate permission given for a specific processing. HekimBis keeps them with separate text, version and evidence.
Are patients served in several languages?
The staff interface is in Turkish and English; the patient-facing portal, forms, consents and communication are in Turkish, English, Arabic, Russian and German. Clinical and legal translation is published with human approval.
Keep reading
Related pages
Company and support
- CareersWorking principles, open positions, and the application process at HekimBis.
- KVKK complianceHow personal health data is processed, data subject rights, and requests.
- ContactReach us for a demo, a quote, data migration, or support.
- Privacy policyHow personal data is processed on the website and in our services.