الصحة والعيادات
نبني أنظمة تنسجم مع سير العمل السريري الحقيقي في كل فروع الصحة: المستوصفات والعيادات الخاصة، والأسنان (مخطط الأسنان وخطة العلاج)، والعلاج الطبيعي (باقات الجلسات)، وعلم النفس (وصول سري للملفات)، والتغذية، والبصريات (استحقاق النظارات)، ومراكز السمع، والصيدليات (باركود تتبّع الدواء والتعويض)، ومختبرات التحاليل (باركود العينات وتنبيه القيم الحرجة). تُعالَج بيانات الصحة الشخصية وفق أنظمة الخصوصية.
One clinical backbone, from exam to collection
A healthcare organization's day flows as a chain: the patient books, is received, examined, gets tests and a prescription, and the visit is billed and collected. Vosetu keeps that chain unbroken in one system — from appointment to the electronic patient record, from e-prescription to reimbursement authorization, from the till to the end-of-day report, on the same data, the same permissions, the same audit trail.
Health data is not an ordinary record. Personal health data is processed under the special-category rules of privacy law: who opened which file and when is logged, access to confidential files such as psychology and counseling is restricted by role, and retention periods and access logging are built into the architecture from the start — not patched on later.
- Appointment → collection chain
- Electronic patient record
- Privacy & confidential-file access
- Role-based access + audit trail
The backbone of healthcare software
Appointment & patient flow
From the appointment calendar to the waiting room, from the exam to tests and prescriptions, the path a patient follows is managed in one flow. The physician, receptionist and cashier look at different steps of the same record; nothing is entered twice. SMS and email reminders cut the no-show rate.
- Calendar, queue and waiting management
- Electronic health record (EHR)
- SMS/email appointment reminders
Confidential files & role-based access
Health data is special-category data; not everyone may see every file. Access to sensitive records — a psychologist's session note, a counseling record, a diagnosis history — is restricted by role. Who opened which record and when is written to an immutable audit log — privacy is the default behavior.
- Fine-grained roles and permissions
- Confidential-file access boundary
- Immutable access/audit log
Official integrations
The system talks to healthcare's official backbone: reimbursement and invoicing via Medula, drug-barcode tracking via İTS, the national health record via e-Nabız, eyewear and report entitlements via SGK. Adding a new service means writing an adapter without touching the core; when a rule changes you edit one place.
- Reimbursement authorization & invoicing
- Drug-barcode tracking & national record
- State entitlement queries and reporting
Solutions that fit every branch of healthcare
Each branch has its own workflow, its own screens, its own official integrations — yet they all share the same patient, permission and data model.
Polyclinic & private practice
Examination, diagnosis and e-prescription; end to end with MEDULA authorization and the patient follow-up file.
Dental clinic
Treatment plan over the odontogram, session tracking and lab/prosthetic work orders on one screen.
Physiotherapy
Prescribed session packages, ROM and VAS measurement, with attendance and progress charts.
Psychology & counseling
Confidential file access, test/inventory administration and session notes protected by role-based access.
Dietetics
Personalized nutrition plans, anthropometric measurement and weight/composition tracking charts.
Optics
Prescription and diopter records, frame/lens stock and sales with SGK eyewear-entitlement queries.
Hearing center
Audiometry records, SGK device reports and serialized device inventory in one file.
Pharmacy
İTS barcodes, expiry tracking, colored prescriptions and on-call scheduling in end-to-end sales management.
Diagnostic lab & imaging
Sample barcoding, panic-value alerts and a result flow with quality control (QC).
In healthcare, privacy is not a setting — it is the architecture itself. Who may open which file, how long it is kept, and that every access leaves a trace are decided in the first line — patient trust can never be a feature added later.
What ships as standard in every healthcare deployment
How we bring your clinic live
Discovery & branch workflow
We map your organization's real workflow: which branch, which official integration, which role sees which data — we clarify it together.
Migrating existing patient data
We map, validate and migrate patients, files and past records from your old program into the new system in a privacy-compliant way — no patient is lost.
Setup & official integration
We set up users, roles and permissions, then bring the Medula, İTS, e-Nabız and SGK connections live after testing them in a live environment.
Training, go-live & care
We train your team on site and stand by in the first days; then we continue updates and support under an SLA maintenance plan.
From our healthcare family
Our product prototypes focused on different branches of healthcare share the same core and security model — every lesson learned in one carries into the next.
Medora
Polyclinic and private-practice management: appointments, electronic patient records, e-prescription and MEDULA authorization.
Dentora
Dental clinic solution: treatment plans over the odontogram, session tracking and lab/prosthetic work orders.
Ecora
Pharmacy management: a sales flow with İTS barcodes, expiry tracking, colored prescriptions and on-call scheduling.
Bakora
Home care and field health: visit planning, care records and location-based tracking with a mobile team.
Physiotherapy & session management
A branch-specific solution definition for prescribed session packages, ROM/VAS measurement and progress tracking.
Lab & imaging
A lab result-flow definition with sample barcoding, panic-value alerts and quality control.
The technology we build on
- .NET 9
- ASP.NET Web API
- PostgreSQL
- Medula
- İTS
- e-Nabız
- SGK
- SMS
- Flutter
- Role-based access
- Encryption
- Audit trail
Frequently asked
Is patient data processed in line with privacy law?
Yes. Personal health data is treated as special-category data: disclosure and explicit-consent processes, retention-period rules, role-based access and an immutable audit trail are built into the architecture. Access to confidential files (e.g. a psychologist's session note) is restricted by role and every access is logged.
Is there Medula, İTS and e-Nabız integration?
Yes. Reimbursement and invoicing via Medula, drug-barcode tracking via İTS, the national health record via e-Nabız and entitlement queries via SGK are supported. Each official service is added as an independent adapter without touching the core; when regulation changes only that adapter is updated.
Can our patient data be migrated from our old program?
Yes. Patient records, files and past transactions are mapped, validated and migrated to the new system in a privacy-compliant way. We validate on a sample before migration; we complete the transition without losing any patient or historical record.
Is it suitable for a multi-branch healthcare organization?
Yes. Branches are managed in one system with a shared patient and permission model; each user sees only the data of the branch and role they are authorized for. Central reporting compares branches while clinical data stays separated and protected per branch.
Do you provide training and support after setup?
Yes. We train your team on site or remotely and stand by in the first days of go-live. After that, post-launch maintenance with an SLA is standard: bug fixing, security and regulatory updates, and new development requests are handled under contract.
Let's grow your clinic with the right software
We'll listen to your branch and workflow and map out where to start, together. The first conversation is non-binding.