This site uses only cookies that are necessary for its operation and security. No optional services are currently in use.

Skip to content
NuWide

Digital design & engineeringRéunion — France — Remote

Healthcare · teleconsultation

Praticéo — Appointment and teleconsultation platform

A web platform that connects patients and practitioners: appointment scheduling, in-person consultations or teleconsultations, calendars, patient management, messaging, and payments—all in a single environment.

Visit the websitePraticéo (new tab)

Context

Multiple business use cases, a single user experience to build.

Praticéo is designed for medical and paramedical professionals and certain wellness practitioners, as well as their patients.

On a daily basis, a practitioner often manages their business using separate tools: a calendar, an appointment scheduling service, a video conferencing tool, email and phone communications, a payment solution, and administrative tools. Each one works on its own, but nothing ties them all together.

The goal, therefore, was neither a showcase website nor a simple online calendar, but a comprehensive business environment: simple for the patient, feature-rich enough for the professional, and capable of evolving without having to rebuild its architecture every time a new feature is added.

Simplify the user experience without artificially simplifying the system that powers it.

Solution

A platform designed around the patient user journeys and the practitioner’s daily routine.

Praticéo is designed as a system: several interconnected spaces and services that share the same data—practitioners, availability, reasons for visits, appointments, patients, communications, and payments.

Patient user journeys

  1. Practitioner
  2. Availability
  3. Reason
  4. Appointment
  5. In-person or video conference
  6. Payment if necessary
  7. Follow-up

Daily practitioner

  1. Calendar
  2. Availability
  3. Appointment
  4. Patients
  5. Consultations
  6. Messaging
  7. Payments
  8. Business

Each screen is part of one of these two user journeys: you don’t switch between tools; you move through a single system.

Experience

Two users, two needs, one system.

The patient

Visitors rarely come by and need to find what they’re looking for quickly. The interface streamlines each step to the essential decision.

  • Who to contact to schedule an appointment
  • For what reason
  • When
  • In-person or via teleconsultation
  • How to find your appointment later

The practitioner

He uses the tool every day. The interface is more compact, organized for efficiency rather than exploration.

  • Planning
  • Appointments and availability
  • Patients
  • Consultations
  • Messages
  • Business monitoring

Maintaining a simple patient experience without compromising professional tools: the interface is part of the product architecture. It is designed in tandem with the data, roles, and access rights.

Features

What the platform offers today.

Appointment

  • Availability as determined by the practitioner
  • Reasons for consulting
  • In-person or teleconsultation appointments
  • Automatic reminders and notifications

Calendar

  • Practitioner calendar
  • Appointments scheduled by patients and the practitioner
  • Practitioner-side business management

Teleconsultation

  • Visio integrated into the appointment user journeys, with LiveKit
  • Patients can access their appointments through Praticéo without needing any additional external tools.

Patients

  • Practitioner’s patient list
  • Information required for the service to function
  • Communication with the practitioner in accordance with applicable rights

Messaging

  • Secure messaging integrated into the Praticéo environment

Payments

  • Online payment via Stripe Connect Express
  • Practitioner-focused payments, with no platform commission on consultations

Architecture

Distinct building blocks, each in its place.

The Nuxt frontend powers the patient and practitioner interfaces. The Django backend handles business logic, permissions, and APIs. PostgreSQL stores the service’s structured data.

Video conferencing and payments are handled by specialized components—LiveKit and Stripe Connect Express—that are integrated into the user journeys rather than added as separate elements. This separation makes it possible to add a business feature without having to rebuild the entire system.

Backend
Django / Python
Frontend
Nuxt / Vue
Database
PostgreSQL
Teleconsultation
LiveKit
Payments
Stripe Connect Express
Infrastructure
Servers in France

Security and infrastructure

Access and communication that require precision.

Praticéo connects patients and practitioners for appointments, consultations, and communication. Security measures focus on a few specific areas:

  • Distinct roles—patient, practitioner—that determine what each user can see and do.
  • Messaging and teleconsultations are integrated into the platform, rather than relying on third-party tools.
  • No AI features are used during consultations, and no data is recorded: the video call simply connects the practitioner and the patient.
  • Payment processing is available only after the practitioner’s profile has been verified.
  • French server infrastructure tailored to the project’s requirements and to hosting the relevant services.

Product selection

A business rule translated into a technical choice.

Praticéo is based on a subscription paid by the practitioner, not on a commission charged for each consultation.

This decision has a direct impact on the architecture: patient payments are routed to the practitioner via Stripe Connect Express, rather than being collected by the platform for its own account. The choice of payment tool stems from the business model, not the other way around.

Summary

What the project helped build.

  1. 01A unified environment, rather than a collection of disparate tools.
  2. 02A unique experience: simple for the patient, comprehensive for the practitioner.
  3. 03A teleconsultation integrated into the appointment process.
  4. 04A payment architecture consistent with the business model.
  5. 05A clear separation between interfaces, business logic, and data.
  6. 06A foundation capable of supporting new business functions.

Next steps

Planned updates

Planned features: These are not part of the currently available service.

  • Patient Follow-up file
  • Questionnaires and medical history
  • Exercises or content provided by the practitioner between appointments
  • Enhancing communication between patients and practitioners

The current architecture was designed to accommodate these additions gradually, without the need for a complete rebuild.

Your project

Do you have a project with similar business requirements?

Whether it’s a platform, a business tool, or user journeys involving multiple user profiles: let’s discuss your context before we talk about screens.

Learn about our approach to business platforms