Telemedicine and Digital Health Platforms: A Clinic Software Guide

In brief: In Türkiye, telemedicine is not just a software project; it is a healthcare service subject to regulation. The Regulation on the Provision of Remote Healthcare Services (10 February 2022, Official Gazette No. 31746) requires providers to obtain an activity authorization certificate from the Ministry of Health and to use secure software produced or registered by the Ministry. For a private clinic, the first step is therefore not choosing a technology stack, but confirming the necessary permits and software status. Then plan video visits, appointments, e-Nabız/e-prescription integrations, KVKK, and information security.

Last updated: September 2026. This article is not legal advice. Contact the Ministry of Health, Provincial Health Directorate, and a healthcare-law adviser for definitive requirements.

Why is telemedicine growing?

Telemedicine can save patients time and travel, support chronic-care follow-up, extend access to rural and remote regions, and help clinicians use their time more efficiently. Türkiye's Ministry of Health also offers remote consultations through its own Dr. e-Nabız system, which patients can access with an MHRS appointment (Ministry of Health, HSGM).

Regulation: the first question to answer

Summaries of the regulation from the Istanbul Medical Chamber and legal practices outline the following:

• Services that can be provided remotely: Remote examinations, medical observation and follow-up, monitoring diagnosed conditions, medical advice and consultations, clinical measurements such as blood sugar and blood pressure, and treatment or medication management.
• Activity authorization: Healthcare facilities providing remote services need an activity authorization certificate from the Ministry of Health.
• Software: Services must use secure software produced or registered by the Ministry.
• Integrations: e-Nabız, e-prescription, and e-report procedures can be carried out as part of remote consultations.
• Services that cannot be remote: Emergencies and cases that require in-person evaluation.

In other words, a plan to “write my own video-call app and use it to provide clinical care” has to be assessed against the authorization and software requirements. For every project, first confirm which software is allowed, under which authorization, and for what scope of care. This is the first question we often receive as telemedicine developers, and the honest answer is: clarify permits and registration first.

Technical components of a telemedicine platform

Within the applicable regulatory framework, a platform may include:

1. Appointments and identity verification

Patient booking, clinician calendars, reminders, secure identity verification (for example, e-Devlet or an appointment number), electronic consent, and a privacy notice before the consultation.

2. Video consultations

WebRTC-based encrypted audio and video, resilience on low-bandwidth connections, screen sharing and document/image sharing, and recovery from dropped connections. Whether a consultation can be recorded, and how a recording is stored, must be settled under the applicable rules and patient consent.

3. Patient records and clinical documents

Medical history, consultation notes, diagnoses, treatment plans, and attachments such as lab results and images. Records must remain intact and access must be traceable: who saw what, and when.

4. e-Prescription and e-Nabız integrations

Connect prescriptions and reports to Ministry of Health systems and the patient's e-Nabız record. These integrations use official services and are available to authorized organizations.

5. Remote monitoring and connected devices

Collect blood pressure, glucose, and pulse measurements from devices for chronic-care follow-up, then alert the clinician when thresholds are crossed. Medical-device rules may also apply, so assess the product scope legally.

6. Billing and reporting

Track consultation fees, insurance and contracted-provider procedures, clinician activity, patient feedback, and consultation duration.

Health data and security

Telemedicine processes one of the most sensitive data categories: health information. Minimum safeguards include:

• KVKK: Health data is special-category personal data. Provide notice, obtain explicit consent when required, minimize data, and define retention periods.
• Encryption: Protect data in transit (TLS) and at rest; apply additional controls to any recordings.
• Access controls: Use role-based permissions, multi-factor authentication, and activity logs.
• Backups and continuity: An outage can affect patient safety, so plan backups and disaster recovery.
• Interoperability: Standards such as HL7 FHIR can make secure data exchange with other systems easier.
• AI: If AI is used for triage or summaries, follow the data authority's generative AI guidance and keep a person responsible for review.

Promotion rules

Telemedicine promotion is also subject to healthcare promotion rules: advertising, promoting fees and campaigns, and using patient testimonials are restricted or prohibited. See our private clinic website guide for more detail.

Eight criteria for choosing clinic software

1. Regulatory fit: how the activity permit and software requirements are met
2. e-Nabız, e-prescription, and MHRS integration status
3. Video-call quality, encryption, and resilience
4. Patient records and role-based access
5. KVKK compliance, retention, and deletion workflows
6. Information security: backups, logs, and penetration tests
7. Appointments, reminders, and patient communication
8. Support, training, and long-term maintenance

What Aktaş Digital can provide

Our telemedicine and digital health platform includes WebRTC video consultations, FHIR R4-compatible patient data management, e-prescription and MHRS integration foundations, and a KVKK-aware architecture. For every project, we first clarify the regulatory scope—permits, software registration, and which service can be delivered through which channel. We recommend working with a healthcare-law adviser. Tell us what you need through our project inquiry form.

Frequently asked questions

Can a private clinic build its own telemedicine platform?

Under the regulation, providing remote healthcare requires an activity authorization certificate from the Ministry of Health and secure software produced or registered by the Ministry. Confirm these requirements with the Ministry and your Provincial Health Directorate first.

Which services can be provided through telemedicine?

Remote examinations, monitoring, follow-up, medical advice, and consultations may be provided remotely. Emergencies and situations that require an in-person assessment cannot be handled remotely.

Can I issue e-prescriptions during a remote consultation?

The regulation and Ministry guidance allow e-prescriptions and e-reports within remote healthcare services. Integrations must use the official systems.

Can a consultation be recorded?

Recording depends on applicable rules, patient consent, and retention and security safeguards. Obtain legal guidance before enabling it.

What security measures does video consultation need?

Encrypted communications, strong identity verification, role-based access, activity logging, secure storage, and regular security testing.

Conclusion

Telemedicine success depends less on a polished video app than on the right authorization, approved software, and strong data security. With those foundations in place, remote care can improve the patient experience and clinic efficiency.