Skip to main content

Introduction

This document outlines the consultation process flow involving a patient, a tenant healthcare platform, Tenang API, and Nesya (a consultation interface). The goal is to automate the user journey from registration to receiving post-consultation summaries.

Consultation Workflow

Actors (Swimlanes)​

ActorDescription
PatientThe end-user seeking consultation
Tenant PlatformThe partner platform handling patient registration and payment
Tenang APIBackend service handling consultation link generation and flow
NesyaConsultation interface (likely AI or human-based communication)

Step-by-Step Workflow​

1. Complete Registration & Payment​

  • From: Patient ➝ Tenant Platform
  • Action: Patient fills out a registration form and completes the payment process for the consultation.
  • From: Tenant Platform ➝ Tenang API
  • Action: The platform sends a request to the backend to generate a unique consultation session link.
  • From: Tenang API ➝ Tenant Platform
  • Action: Tenang API returns a unique link associated with the consultation session.
  • From: Tenant Platform ➝ Patient
  • Action: The patient is redirected to the provided consultation URL.

5. Start Consultation​

  • From: Tenang API ➝ Nesya
  • Action: Upon accessing the link, the consultation session is initiated through Nesya.

6. Send First Message & Start Timer​

  • From: Nesya ➝ Tenang API ➝ Patient
  • Action: Nesya sends a greeting or opening message; the consultation timer is started.

7. Consultation Ended​

  • Implicit Action
  • Description: The session ends either after time expires or based on user/system action.

8. Send Detailed Consultation​

  • From: Nesya ➝ Tenang API
  • Action: Nesya sends the full transcript or session data to Tenang API for storage/reporting.

9. Display Consultation Summary​

  • From: Tenang API ➝ Tenant Platform ➝ Patient
  • Action: A summarized consultation report is displayed to the patient for their records.

Information Flow​

  • Frontend (Patient & Tenant Platform):

    • Manages registration, payment, session redirection, and summary display.

  • Backend (Tenang API):

    • Handles consultation session lifecycle, API routing, and data hand-off between actors.

  • Consultation Interface (Nesya):

    • Engages the patient, tracks time, and returns session results to the backend.

Implicit Decision Points​

  • Payment Verification: Ensures payment is valid before link is generated.
  • Session Completion: Triggers when the consultation time expires or is ended manually.

Objective​

To provide an integrated, seamless consultation experience for patients by linking a tenant healthcare platform to the Tenang API and Nesya consultation interface—automating everything from registration to post-session reporting.