PERSONA WORKFLOWS

See how each connected persona participates in the PlexoGrid ecosystem.

Each persona chip on the homepage opens the matching section below. This public guide explains intended journeys, current maturity and how roles stay connected — without mixing responsibilities. Registration, clinical and institutional actions remain inside the authenticated app.

HOW THE ECOSYSTEM CONNECTS

One identity. Multiple permitted roles. Shared context without mixing responsibilities.

PlexoGrid separates identity, persona, institution membership and permissions. That allows a patient, doctor, student, employee, vendor or partner to participate in connected journeys while each workspace exposes only the information and actions appropriate to that role.

Patient → DoctorAppointments, records, consultations, explanations, follow-up and communication remain tied to authenticated clinical context.
Patient → HospitalRegistration, billing, insurance, documents, counselling, service requests and follow-up connect the care journey to institutional operations.
Doctor → Hospital / TeamsProfessional identity connects to institution-granted clinical and administrative workflows while preserving accountability.
College → StudentsTrainee identity can stay affiliated to the college, with academic, posting and later professional identity kept on distinct role boundaries.
Hospital → CollegeEducation, clinical postings, training, research and faculty relationships can connect academic and clinical environments where authorised.
Institution → Vendor / PartnerKYC, catalogue, marketplace, procurement, campaigns and commercial relationships connect participating organisations.
Counsellor → Patient / TeamFollow-up, education, requirement capture and escalation can connect front-line counselling with the responsible internal teams.
Founder / Platform → EcosystemPlatform-level rollout, verification, audit and commercial policy remain separate from hospital and persona-level operational authority.
GROWTH, RELATIONSHIP & SERVICE CAPABILITIES

Clinical care and account growth can use the same connected context.

These capabilities are part of the PlexoGrid operating model, but their implementation maturity varies. Status labels below distinguish what is already available from capabilities that are partial, feature-gated, Founder-decided, or still rolling out.

PARTIAL / EXPANDING

B2B & B2C lead generation

Capture referral, campaign, geography, corporate, insurer, TPA, camp and other acquisition context so institutions can understand where enquiries and patient/client opportunities originate.

PARTIAL / EXPANDING

Lead & client qualification

Structure enquiry context, eligibility, service need, payer type, urgency and next action so teams can prioritise suitable opportunities rather than handling every enquiry as an unqualified message.

ROADMAP / DOMAIN REGISTERED

CRM & pipeline management

Progress relationships from enquiry through counselling, conversion, service delivery, follow-up, retention and growth. CRM is a canonical administrative domain, but a universal end-to-end CRM is not yet fully live across every persona.

AVAILABLE BY PERSONA

Self-service onboarding & account management

Patients, doctors, institutions and vendors have different levels of self-service or institution-guided onboarding. Vendor self-service is mature; institution and doctor application/credential flows exist; other personas remain more institution-driven.

TARGET EXPERIENCE

AI product, feature & field explanations

The intended experience is contextual help on every page and field, including simple explanations, guided next steps and AI assistance. Universal field-level AI explanation is not yet a production-wide guarantee.

FOUNDER-DECIDED POLICY / STAGED

Subscription & wallet replenishment

Commercial policy includes subscription-linked wallet top-up, rollover and replenishment semantics. Implementation is being reconciled across subscription authority, wallet and credit-engine layers.

PARTIAL / STAGED

Counsellor modules & requirement handling

Support counselling, patient education, incomplete-information follow-up, responsibility assignment, language/specialty matching, structured notes and escalation to the relevant clinical or administrative team.

ROADMAP REGISTERED

Footfall, referral & conversion mapping

Relate physical and digital footfalls to campaigns, camps, referrers, counsellors, marketing executives, hospitals, corporates and payers to understand conversion and growth opportunities.

PARTIAL / EXPANDING

Upsell & cross-sell of beneficial services

Use eligibility, current care context, subscription, marketplace and service information to surface genuinely useful adjacent services — not indiscriminate selling — subject to consent, clinical appropriateness and commercial rules.

PARTIAL / EXPANDING

Escalations & internal coordination

Route unresolved requirements, grievances, billing issues, service gaps and follow-up tasks to the correct internal owner while preserving status, responsibility and auditability.

ROADMAP / MANAGEMENT MODEL

Large account-volume management

Use queues, segmentation, dashboards, SLA views and prioritisation so teams can manage high client volumes without losing ownership, ageing visibility or next-action discipline.

ADVISORY / EXPANDING

Account growth opportunities

Combine usage, campaign, relationship, revenue, referral, wallet and service signals to identify retention, expansion and re-engagement opportunities. AI commercial advice remains feature-gated and advisory.

ROLE MODEL / EXPANDING

Sales & account-team leadership

Support manager/executive responsibility structures, team-level visibility, escalation authority, workload distribution and performance review for small or large commercial teams.

CORE PLATFORM VALUE

Integrated EMR & operational context

Clinical records, encounters, orders, prescriptions, documents, billing, insurance and hospital operations can share authenticated context so commercial or service teams do not need to reconstruct the patient journey from disconnected systems.

PERSONA-BY-PERSONA GUIDE

Select the same persona you clicked on the homepage.

Each section explains what that persona needs, what features and benefits matter most, and how the workspace connects to the rest of PlexoGrid. Status labels are truthful: they do not present expanding or planned journeys as universally live.

CREDENTIAL ONBOARDING IMPLEMENTED

Doctors

Canonical onboarding documents

  • Medical registration certificate.
  • Postgraduate qualification evidence.
  • Government photo ID.
  • Medical licence specimen.
  • Board certification where applicable.
  • Other supporting credential documents when required.

Clinical & operational benefits

  • Connected patient identity, encounter, documents, investigations, prescriptions and follow-up context.
  • Role-aware access inside participating hospitals without creating a separate professional identity for every institution.
  • Teleconsultation, communication, referral and additional professional services as enabled.
  • Less duplicate data entry and fewer disconnected hand-offs between clinical, billing and patient-service teams.

Commercial & relationship benefits

  • Structured referral and enquiry context for appropriate professional services.
  • Better visibility into patient follow-up, retention and service continuity without turning clinical care into indiscriminate sales activity.
  • Potential AI explanations, patient education support and qualified opportunities as those capabilities are enabled.

Connected to

Patients, hospitals, healthcare teams, paramedical staff, medical/dental colleges and authorised ecosystem services.

APPLICATION WORKFLOW IMPLEMENTED

Hospitals

Canonical institution documents

  • Registration certificate and healthcare licence.
  • GST certificate and PAN/tax document.
  • Authorization letter and applicant identity evidence.
  • Accreditation, ownership authorization and supporting documents where applicable.

Clinical & operational benefits

  • Integrated patient registration, clinical workflows, documents, pharmacy, billing, insurance, RCM, workforce and analytics.
  • One longitudinal context across front desk, clinician, diagnostics, pharmacy, billing, insurance and follow-up teams.
  • Auditability, role-aware access and clearer accountability across departments.

Growth, account & revenue benefits

  • B2C patient lead capture and B2B corporate/TPA/insurer/referral relationship management as growth modules mature.
  • Campaign, camp, referral and footfall attribution to understand acquisition sources and conversion.
  • CRM/pipeline, counsellor follow-up, escalation coordination, account retention and service-growth opportunities as enabled.
  • Subscription/wallet visibility, RCM collections, receivables monitoring and commercial dashboards.
  • Support for small or large account/sales teams through queues, manager/executive roles and workload visibility as these modules expand.

Connected to

Patients, doctors, staff, medical/dental colleges, vendors, partners, corporates, insurers/TPAs and PlexoGrid platform services.

INSTITUTION WORKFLOW AVAILABLE / EDUCATION EXPANDING

Medical/Dental Colleges

What you need

Institution onboarding uses the applicable registration, licence, tax, authorization, accreditation and ownership evidence required for the organisation. Student-specific public document packs are still being finalized.

Academic & clinical benefits

  • Connect academics, faculty, clinical postings, hospital training and research context within the wider ecosystem.
  • Potential continuity from education to supervised clinical environments without duplicate identities.
  • Shared institutional administration, documents, communication and operational tooling as enabled.

Growth & relationship benefits

  • Manage institutional partnerships, outreach, camps, training relationships and prospective-student or professional engagement as the CRM/growth layer matures.
  • Connect affiliated hospitals, vendors and partners while keeping educational and clinical responsibilities distinct.
  • Use structured communication and dashboards for large cohorts and multi-site relationships.

Connected to

Students/trainees, faculty, doctors, hospitals, healthcare teams, vendors, partners and research/training environments.

TRAINEE IDENTITY DESIGNED / EXPANDING

Medical/Dental Students

This is a student/trainee PlexoGrid identity, not a licensed-doctor workspace. Features below are expanding; nothing here is presented as universally LIVE for every college.

What you need

  • A student/trainee PlexoGrid identity, distinct from a later professional (doctor) identity.
  • Medical/Dental College affiliation to the participating college — Colleges and Students are not the same persona.
  • Register / enrolment context as the college enables it. A single universal public student document pack is not yet finalized.
  • College- or hospital-requested identity evidence where the institution requires it.

Academic & clinical-posting journey

  • Academic and clinical-posting context can stay connected to the affiliated college.
  • Learning and training workflows can be used as enabled — they are not claimed as universally live for every college.
  • Teaching resources can be surfaced as the college enables them.
  • Assessments and training activities can be used as enabled.
  • Research and education participation can be offered as enabled by the college or affiliated hospital.
  • Communication, announcements and Message Board-style cohort updates can keep trainees informed inside the trusted college space as enabled.
  • Permitted clinical-posting connections exist only where the college and hospital have authorised that relationship.

Progression & privilege boundaries

  • A student/trainee workspace is not a substitute for a licensed professional workspace.
  • Student status does not grant independent clinical privilege or Doctor permissions.
  • Transition to a later professional identity must remain canonical and audited through the applicable credential and onboarding path — it is not automatic.
  • Privacy and role boundaries remain in force: trainees see only the academic, posting and communication context their college or authorised hospital permits.
  • Clinical records and patient work remain outside the student role unless a separately authorised clinical responsibility exists.

Connected to

Medical/dental colleges, authorised hospital postings, faculty/healthcare teams and, later, a professional identity if independently credentialed.

INSTITUTION-DRIVEN ACCESS

Healthcare Teams

What you need

  • Institution-created staff/employee relationship.
  • Approved identity, department and role assignment.
  • Employer-specific HR evidence where required.

Operational benefits

  • Connected workflows across reception, billing, insurance desk, OT, pharmacy, diagnostics, nursing, optometry, technicians and management according to role.
  • Attendance, leave, payroll, announcements/inbox and profile functionality where enabled.
  • Shared patient/service context reduces repeated phone calls and manual cross-department chasing.

Client-service & account benefits

  • Coordinate enquiries, counselling, follow-up, escalations and unresolved requirements with the correct internal owner.
  • Manage queues and high patient/client volumes with visible priorities and next actions.
  • Support account retention and beneficial cross-service coordination while preserving role and consent boundaries.

Connected to

Hospital Admin, doctors, patients, counsellors, billing/insurance teams and other authorised departments.

INSTITUTION-DRIVEN ACCESS

Paramedical Staff

What you need

Institution-approved identity, department/designation and the professional/HR evidence required by the employer for the relevant paramedical role.

Clinical benefits

  • Access only the patient, task, order, document or workflow context needed for the assigned responsibility.
  • Reduce manual hand-offs between diagnostics, nursing, optometry, technicians, OT and clinicians.
  • Improve continuity, traceability and task completion around the patient journey.

Service benefits

  • Structured task queues, follow-up and escalation can help staff manage larger workloads without losing ownership.
  • Contextual guidance and AI-based explanations are intended to reduce uncertainty at page/field level as the universal help layer is rolled out.

Connected to

Doctors, healthcare teams, patients, diagnostics, pharmacy, billing and hospital administration according to permissions.

PARTNER MODEL EXPANDING

Partners

What you need

Requirements depend on partner type — referral, service, technology, corporate, insurer/TPA, outreach, education or other approved relationship. A single universal public partner document pack is not yet appropriate.

Business benefits

  • B2B relationship tracking, referral/campaign attribution and structured account ownership as growth modules mature.
  • Clearer qualification, onboarding, service scope, communication and escalation between organisations.
  • Potential pipeline, renewal, retention, cross-sell and account-growth visibility without mixing partner data with clinical records.

Connected to

Hospitals, doctors, vendors, corporates, insurers/TPAs, medical/dental colleges and other authorised ecosystem participants.

SELF-SERVICE PORTAL AVAILABLE

Vendors

What you need

  • Email or phone, password, display name and vendor identifier for registration.
  • KYC/business evidence according to category and marketplace policy.
  • GST evidence where applicable.

Commercial benefits

  • Self-service onboarding, KYC, catalogue and marketplace participation.
  • Wallet, messaging, session management and MFA capabilities.
  • Institution-facing procurement and supply relationships across multiple authorised organisations.
  • Better product/service discovery, qualified institutional opportunities and potential cross-sell/upsell when genuinely relevant to buyer needs.
  • Future AI explanations can help buyers and vendor teams understand product, feature and field-level information more consistently.

Account-management benefits

  • Maintain a verified commercial presence instead of recreating credentials for each customer relationship.
  • Coordinate support, escalations, renewals, catalogue updates and growth opportunities through a single vendor workspace as integrations expand.

Connected to

Hospitals, procurement, finance, marketplace operations, partners and platform commercial services.

AVAILABLE / EXPANDING

Patients — International & Domestic

What you need

  • Identity/contact details and authenticated sign-in.
  • No single universal mandatory document pack for every patient.
  • Insurance information, records and supporting documents only when relevant to the hospital or service selected.

Clinical benefits

  • Hospital discovery, patient records, documents, appointments and connected care context.
  • Family/insurance links, Message Board, notifications and additional interactions as enabled.
  • Less repetition of history and documents across connected workflows.
  • Better continuity between doctor, hospital, diagnostics, pharmacy, billing and follow-up.

Self-service & service benefits

  • More ability to understand options, submit information, track requests and communicate without unnecessary calls or visits.
  • Medical-tourism pathways can connect international and domestic patients to participating hospitals and doctors while keeping clinical records inside authenticated workflows.
  • Contextual AI explanations are intended to make pages, fields, services and features easier to understand as that help layer expands.
  • Qualified service suggestions should be based on relevance, eligibility and benefit — not indiscriminate selling.

Connected to

Doctors, hospitals, counsellors, billing, insurance, authorised family relationships and enabled ecosystem services.

Important: document requirements, commercial capabilities and available modules vary by country, institution, specialty, partner category, subscription and rollout stage. This public page explains the current PlexoGrid operating model; the authenticated application and current institutional/commercial policy determine what is actually requested or enabled in a specific case.