FAQ

The platform is designed for patients, clinics, doctors, laboratories, and administrators. Patients use it to browse providers, book appointments, follow notifications, and review records. Clinics and laboratories use it to manage services, schedules, requests, and reports. Administrators supervise users, approvals, reviews, and shared service information.

A patient can create an account through the registration flow and then verify access according to the available verification steps. The platform also supports sign-in, password recovery, and profile updates. Exact screen names may differ between mobile and web interfaces, but the purpose is to keep account access clear and recoverable.

Clinic registration is handled through a provider registration flow and may require administrative approval before the clinic account becomes active. This allows the project owner to review provider information before the clinic manages services, doctors, schedules, appointments, and reports inside the platform.

A patient can browse clinics or doctors, review available information, check available times when they are published through provider schedules, and submit an appointment request. The provider side can then act on the request according to the workflow, such as accepting, rejecting, finishing, or updating related information.

The platform includes cancellation and rebooking-related flows. Whether a specific appointment can be changed depends on the appointment status, provider rules, and the conditions shown in the service flow. Users should review the available actions on the appointment details screen before assuming that every booking can be changed.

Available times are based on provider schedules and the appointment flow exposed by the system. The platform checks availability through the configured service logic, then presents times that can be requested. If no time appears, the provider schedule or service conditions may not currently expose an available slot.

Users can browse laboratories and lab tests, add tests to a cart, review checkout information, and submit a lab-related request when the flow is available. Laboratory activity remains connected to the user journey so results and records can be easier to follow after the request is processed.

The platform includes lab result and medical record views. When a result is made available through the supported workflow, the user can review it from the related record area. Availability depends on the provider completing the relevant steps and entering or attaching result information where supported.

The platform includes payment-related features such as checkout summaries, saved payment cards, coupons, and payment metadata. The exact payment method, charge timing, refund handling, and provider policy must be confirmed from the service details and the rules configured by the project owner.

Yes, the platform includes notification features for users and clinics. Notifications can cover appointments, lab orders, results, payment-related activity, password changes, account updates, and system messages. Users and clinics may also have notification settings that control how they follow important activity.

Yes. The public website and service messages support Arabic and English, and the interface changes direction between right-to-left and left-to-right layouts. This helps Arabic and English users work with the same platform while keeping text and navigation readable.

The public contact page allows users, clinics, laboratories, and partners to send messages about support, provider registration, privacy questions, technical issues, and general inquiries. The team can review the message and respond through the available contact channel according to current operational capacity.

The platform includes forgot-password and reset-password flows for users and clinics. Follow the recovery steps shown in the account interface. You may be asked to verify ownership through the available confirmation method before creating a new password.

Account data is used to operate the service, identify the user, support bookings, show relevant records, send notifications, and manage security-related actions. Access should be limited according to the role and the operational need. The privacy policy explains the main categories in more detail.

Yes. The clinic-side tools include doctor management, profile details, specializations, and availability. This allows a clinic to keep doctor information connected to schedules and services. The exact number and permissions depend on the configuration approved by the project owner.

The platform includes specialization and sub-specialization data connected to doctors and clinic services. This helps patients understand provider focus areas and helps clinics organize services. The details shown depend on the information configured and approved for each provider.

Users can submit reviews for clinics, doctors, and laboratories in supported contexts. Reviews should reflect actual service experience and may be subject to moderation or rules configured by the project owner. The platform should not be used to publish misleading, abusive, or unrelated content.

Clinics can manage enabled services such as specializations or laboratory tests according to their type and configuration. Administrators can also manage shared service information. Adding a new service publicly should be tied to real provider capability and approved operating rules.

The platform includes mobile-oriented user and clinic flows, and the public website is responsive. Important actions such as browsing providers, managing account activity, notifications, appointments, and records are designed to remain understandable on smaller screens.

Yes. Clinic-side features include report summaries, generated reports, exports, and downloadable report files. These reports help provider teams review activity and revenue-related information, but they should be used as operational support rather than a replacement for professional financial or clinical review.