How are Remote Healthcare Services Structured? Digital Service Model
The digital health service infrastructure ranges from patient onboarding to health packages, messaging, and video consultations.
How are Remote Healthcare Services Structured? Digital Service Model
Remote healthcare is not just about video calls. It requires the management of various processes together, from patient enrollment and health package definition to healthcare professional assignment and messaging/video consultations. TURP supports the structuring of these components within the same digital health infrastructure.
With the digitalization of healthcare services, the concept of "remote healthcare" is often associated only with video consultations between a patient and a healthcare professional.
However, video conferencing is only one point of contact for remote healthcare services.
A healthcare organization needs a broader operational structure to be able to provide services remotely.
Which patient will receive which service?
How long will the service be offered?
Which healthcare professional will be associated with the patient?
Which digital services will be included in the package?
Through what channels can the patient reach a healthcare professional?
How will the follow-up process be managed?
In TURP's remote healthcare approach, these questions can be addressed as parts of the same service model rather than independent features.
Remote healthcare begins before an appointment.
The moment a patient and a healthcare professional meet on screen is actually a step in the middle of the digital service process.
Before that, the patient needs to be registered in the system and the service they will receive needs to be defined.
According to TURP's resources, the patient onboarding process includes steps such as patient creation, invitation via phone number, package invitation via SMS, verification, and package activation.
On the package side, elements such as the name, description, duration, and fee of the service can be defined; after payment, the package is activated and the patient is included in the active follow-up process.
Therefore, the starting point for remote healthcare is:
"Start video call"
not;
"Define which digital health service will be offered to the patient and with which model."
It can be considered as such.
1. Packaging Healthcare Services
For digital health services to be scalable, it is important that service content is definable.
In TURP, healthcare services can be configured through packages.
The project resources include functions such as creating a new health package, defining package name and description, and adding package images. There are also features for determining package duration and pricing. TURP_Eczacibasi_Evital_Application…
This structure enables healthcare organizations to create different models for different patient groups or service scenarios.
For example, different service packages with varying scopes and durations can be defined within the same digital infrastructure.
The key point here is that technology should not overshadow healthcare.
First, the service model is defined; digital tools then support this model.
2. Patient-Service Matching
The mere existence of a health package within the system is not enough.
The right patient needs to be matched with the right service.
In the TURP onboarding process, the steps involved are defined as showing the patient the package information, determining the package duration, completing the payment process, activating the package, and initiating the patient into the active follow-up process.
This approach allows digital healthcare to be managed not simply as "access to the platform," but as a specific service process associated with the patient.
This makes a significant difference, especially for corporate use.
Because a healthcare organization needs to be able to manage not only who is registered in the system , but also who is actively using which service .
3. Involving Healthcare Professionals in the Process
On the other side of remote healthcare is the healthcare professional.
The TURP patient management structure supports the assignment of a doctor, nurse, or staff member to a patient, and the ability to change assigned staff members when necessary.
This feature transforms remote healthcare from an anonymous digital channel into a process conducted between a specific patient and a healthcare team.
So the structure is:
Patient → Service Package → Healthcare Team
It can be established in this way.
This correlation becomes particularly important in operations involving multiple healthcare professionals and a large number of patients.
4. Messaging can be part of the monitoring process.
Not every remote healthcare interaction needs to be a video call.
TURP resources include features such as access to messages via patient profile, a patient-specific communication area, and the ability for healthcare professionals to communicate directly with patients.
The noteworthy point here is that messaging is not treated as a separate communication application.
It is clearly stated in the source:
"Communication should be conducted on the same platform as the follow-up process."
The feature is being defined.
This is an important architectural approach for digital healthcare.
When patient management is conducted in one system, communication in another, and healthcare services through yet another channel, the process can become fragmented.
In the TURP approach, communication can be integrated within the patient follow-up structure.
5. Video calling is not a standalone feature, it is part of the service.
TURP supports conducting remote video consultations with patients.
More importantly, however, the sources describe video conferencing as a service that can be included in a health package . Furthermore, offering video conferencing services on a package basis and conducting remote healthcare services digitally are also among the existing functions.
This approach distinguishes two different models:
Software with video calling feature
And
A platform that manages video conferencing as part of defined healthcare services.
From TURP's perspective, the essential value lies in the second model.
Because technology is not an end in itself, but rather one of the tools that enables the delivery of healthcare services.
6. Files and Medical Images Can Also Be Part of the Remote Process
In remote healthcare, communication is not limited to voice and video.
In some procedures, a healthcare professional may need access to medical images or patient-related documents.
In addition to file sharing, TURP resources also include DICOM image sharing and viewing functionality. The DICOM feature is defined to support the digital sharing and viewing of medical images through the platform.
This feature expands remote healthcare beyond just communication, extending it into a broader digital clinical workspace.
Talking to a patient is a process.
Accessing the patient's relevant information is a different process.
Viewing medical images is a different process.
The value of a digital health platform lies in its ability to support the use of these different functions within the same service flow when needed.
7. E-Prescription: Another Component of the Digital Service Flow
E-prescription functions are also defined within the scope of clinical procedures in TURP resources.
The platform includes processes such as creating an electronic prescription on behalf of the patient, verification by a healthcare professional using an e-prescription password, and redirection to the prescription screen after verification.
This feature shows us why remote healthcare shouldn't be considered solely under the heading of "communication."
Because the need for the actual use of digital health services is:
The meeting was held → the process is complete.
It may not be like that.
The service may include various clinical or operational procedures.
Therefore, the platform architecture needs to support not only the communication moment but also the workflows surrounding the service.
8. Patient Information Process
In remote healthcare services, it is also important for the patient to be informed about the process.
The TURP framework defines a structure for centralized and controlled patient information processes. The aim is to support patients in accessing necessary information regularly regarding their follow-up and healthcare processes.
At this point, we can consider digital healthcare through three key user actions:
The patient has access to the service.
The healthcare professional provides the service.
The platform supports the operational process between the two parties.
The Key Issue in Remote Healthcare: Process Design
When choosing technology for digital health, questions like "Does it offer video calling?" or "Does it offer messaging?" are important.
However, these alone are not sufficient for corporate use.
More comprehensive questions include:
How is the patient included in the system?
How is it determined which service you will receive?
How are the duration and scope of the service defined?
Which healthcare professional is the patient being referred to?
Which service includes messaging and video calling?
How are post-service clinical and operational processes managed?
The scalability of remote healthcare depends on the interconnection of these processes.
Not a Single Feature, but a Chain of Services
Therefore, it would be more accurate to evaluate TURP's remote healthcare model not through a single function, but as a service chain:
Patient Invitation
↓
Verification
↓
Health Package
↓
Package Activation
↓
Health Team Assignment
↓
Messaging / Video Calling
↓
Related Clinical and Digital Procedures
↓
Continuation of the Follow-up Process
In this structure, technology plays a binding role rather than a visible one.
The goal is not to show the patient as many digital features as possible; it is to transform the different stages of the service offered by the healthcare institution into a manageable digital flow.
TURP: The Digital Infrastructure for Remote Healthcare Services
TURP does not view remote healthcare services solely as a digital connection established between a patient and a healthcare professional.
The overall structure of the platform is positioned to bring together different processes such as patient management, remote healthcare services, clinical communication, medical device integration, and health data management in a common infrastructure. (Pasted text(20260826-170…)
Therefore, the core idea behind TURP's remote healthcare approach is:
The goal is not "to create a video conferencing system," but "to create a healthcare process that can be delivered digitally."
The patient is included in the service.
The scope of service is defined.
A healthcare professional is assigned to the process.
Communication and negotiation tools are used when necessary.
The relevant clinical processes support the same digital service structure.
Thus, remote healthcare transforms from a one-time digital interaction into a manageable service model .