Product Definition · Roles & Access

Clinic Management Software

Consolidated role plan, MVP implementation scope, responsibilities, optional modules, and platform administration model for a configurable clinic product serving small clinics through large multispecialty facilities.

Multi-tenant SaaSRole-based accessConfigurable modulesClinic-size flexible

1. Overall role model

The product has platform-level administration, clinic-level administration, clinical roles, operational roles, and optional external/specialty roles. A role describes a user's job; permissions define what that user can actually do.

2
Administration levels: platform and clinic
10
Initial role/workflow items in the agreed development list
Optional
Pharmacy, lab, insurance, diagnostics and other modules can be enabled per clinic

Platform level

Dev Admin / Platform Super Admin operates the SaaS platform across tenants: tenant management, feature flags, entitlements, platform configuration, integrations, security, audit and system health.

Clinic level

Clinic Owner / Clinic Administrator configures one organization or clinic: staff, departments, working hours, clinic branding, operational settings and enabled features within platform policy and subscription entitlements.

Operational level

Receptionist, Nurse, DMO, Consultant Doctor, laboratory staff, pharmacy staff and billing staff perform patient-facing clinical and administrative workflows according to assigned permissions.

Key design rule: One employee may hold multiple roles in a small clinic if permitted. Larger facilities can separate duties more strictly. Not every clinic needs every role or module.

2. MVP implementation scope

Build a usable end-to-end clinic journey first, with platform and clinic administration to configure it. Optional services should be modules, not mandatory steps for every clinic.

Recommended MVP foundation

  • Dev Admin / Platform Super Admin: tenant setup, module/feature configuration, baseline entitlements, platform settings and administrative audit.
  • Clinic Owner / Clinic Administrator: clinic profile, users and role assignment, departments, clinic settings, working hours, fees and module preferences.
  • Receptionist: patient registration/search, appointment and walk-in handling, visit creation, queue management and basic consultation-fee collection where enabled.
  • Nurse: assigned patient queue, identity/visit verification, vitals, nursing assessment and handoff.
  • DMO: review nursing information, initial assessment, history/examination notes and handoff where the clinic uses this role.
  • Consultant Doctor: consultation, diagnosis, treatment plan, prescription, investigation orders and consultation completion.
  • Doctor Review & Follow-up: result review, treatment updates, follow-up recommendations and closure. This is a workflow/capability and may be performed by the authorized treating doctor rather than a separate login role.
  • Billing & Accounts — basic: invoices, payment recording, receipts and payment status. Advanced accounting can follow later.
  • Investigation/Lab — configurable: include basic order tracking and results if needed for pilot clinics; otherwise support printed test requests and external-lab tracking.
MVP foundation Configurable by clinic

Phase 2 / optional modules

  • Full laboratory operations: sample collection, processing, result verification and laboratory management.
  • Pharmacist / medicine dispensing, medicine catalogue, stock, batches, expiry, purchase and pharmacy billing.
  • Advanced billing, refunds, financial reconciliation, insurance/third-party claims and accounting reports.
  • Radiology/diagnostics, inventory procurement, medical records, patient portal and specialty workflows.
  • Advanced AI assistance, predictive analytics, complex multi-branch controls and advanced rollout management.

Finalize the exact MVP boundary against the first pilot clinics. The foundation should support optional modules without forcing every clinic to activate them.

3. Recommended development order

This preserves the agreed order, adding the two administration levels before the patient-facing workflow.

#Role / workflowPrimary responsibilityInitial scope
1Dev Admin / Platform Super AdminPlatform, tenants, flags, entitlements, integrations, securityPlatform foundation
2Clinic Owner / Clinic AdministratorClinic configuration, staff, departments and local settingsClinic foundation
3ReceptionistRegistration, appointments, visits, queue and basic front-desk billingCore workflow
4NurseIntake, vital signs, nursing assessment and handoffCore workflow
5DMO — Duty Medical OfficerInitial medical assessment and clinical documentationConfigurable clinical step
6Consultant DoctorConsultation, diagnosis, prescriptions and investigation ordersCore clinical workflow
7Investigation / Lab workflowTest requests, samples, processing, results and verificationOptional module
8Doctor Review & Follow-upReview results, update care plan and document follow-upCore workflow capability
9Pharmacist / Medicine DispensingDispensing, medicine inventory, batches and expiryOptional module
10Billing & AccountsInvoices, payments, refunds and reconciliationBasic MVP; advanced later

4. Core roles and responsibilities

1

Dev Admin / Platform Super Admin

Platform level

Owns the SaaS platform across all tenants; separate from clinic-level administration.

  • Create/manage tenants, organizations, clinics and branches; activate, suspend or archive under controlled policies.
  • Configure platform settings, module availability, feature flags, subscription plans, entitlements and usage limits.
  • Manage beta access, staged rollout and emergency feature kill switches.
  • Define allowed branding, themes, custom fields, templates and workflow customization.
  • Configure integrations/providers: AI, messaging, storage, payments, webhooks and external systems.
  • Monitor platform health, jobs, errors, usage, security events and administrative audit logs.
  • Manage platform access policies and controlled support access.

Controls: strong authentication, least privilege, tenant isolation, audited changes and confirmation/approval for high-impact actions.

2

Clinic Owner / Clinic Administrator

Clinic level

Manages a specific clinic or organization within the plan, entitlements and platform policies.

  • Manage clinic profile, logo, contact details, address, branches, departments, specialties and working hours.
  • Create staff accounts, assign roles, manage permitted access and deactivate departing staff.
  • Configure appointments, visit types, consultation fees, numbering rules, payment methods and operational settings.
  • Enable available modules such as laboratory, pharmacy, patient portal and insurance when entitled.
  • Customize permitted form fields, labels, templates, branding, languages and notifications.
  • Review clinic-level operational reports, audit history and configuration changes.

Boundary: Cannot override platform security, subscription restrictions or another tenant's data boundaries.

3

Receptionist

MVP

First point of contact for patient registration and front-desk operations.

  • Search existing patients and register new patients using configured demographic fields.
  • Generate unique patient and visit IDs; detect possible duplicates and route them for review.
  • Manage appointments, walk-ins, check-in, arrival status and appointment changes.
  • Manage queue tokens and route patients to nursing or the appropriate clinic workflow.
  • Record permitted consultation charges, payments, receipts and outstanding status.
  • Print/share registration slips, appointment details and authorized documents.
  • Send approved reminders, notify nursing staff and view front-desk reports.

AI assistance: smart patient search, registration form assistance, voice commands, Tamil/English message drafting and daily summaries. Review AI-suggested data before saving.

4

Nurse

MVP

Performs nursing intake and records observations before the next clinical step.

  • View assigned patients and verify patient identity and active visit.
  • Review relevant visit information and authorized history.
  • Record BP, pulse, temperature, SpO₂, respiratory rate, height, weight and configured measurements.
  • Record pain score, allergies as reported/verified, presenting information and nursing observations.
  • Save assessments with author, time, units and measurement provenance.
  • Flag concerning observations and escalate according to approved clinical protocols.
  • Complete nursing handoff and move the visit to the next permitted stage.

AI assistance: voice-based vitals entry, note drafting, completeness checks, translation and handoff summaries. Confirm parsed measurements; never delay emergency escalation.

5

DMO — Duty Medical Officer

Clinical role

Conducts initial medical assessment where the clinic's care model uses a DMO stage.

  • Review demographics, active visit, nursing notes, vitals, allergies and relevant history.
  • Record presenting complaints, onset/duration, relevant history and examination findings.
  • Document initial assessment or provisional impression within authorized scope.
  • Request investigations or document next steps only when authorized.
  • Identify urgent concerns and escalate immediately.
  • Prepare clinical notes and structured handoff to the consultant/next clinician.
  • Maintain authorship, signatures and revision history.

AI assistance: note drafting, history and nursing-note summaries, completeness checks and handoff drafting. Clinicians verify AI-generated content.

6

Consultant Doctor

MVP

Responsible for consultation and clinical decisions within the practitioner's authorization.

  • Review history, nursing assessment, DMO notes, allergies, medications and prior visits.
  • Record consultation findings, examination details and clinical notes.
  • Document working/final diagnoses and treatment decisions.
  • Create prescriptions with medicine, strength, dosage, route, frequency, duration and instructions.
  • Order laboratory/diagnostic investigations where authorized.
  • Review results, document interpretation and update the care plan.
  • Provide advice, precautions, referrals and follow-up recommendations.
  • Review, sign and finalize documents; amend through an auditable correction process.
  • Generate, print or share clinic-branded prescriptions and clinical documents.

AI assistance: voice dictation, structured notes, history/result summaries, completeness checks, patient-friendly instructions and validated medication safety alerts. AI must not autonomously diagnose, prescribe or finalize care.

7

Investigation / Laboratory workflow

Optional module

Supports in-house laboratories and tracking of tests performed externally.

  • Receive authorized orders and verify patient, visit, test and priority.
  • For in-house labs, record specimen type, unique sample ID, collector, collection time and status.
  • Track received, processing, rejected, recollection-required and completed states.
  • Enter/import results with units, reference ranges, timestamps and provenance.
  • Route results for authorized verification and publication.
  • Generate reports and notify the responsible clinician.
  • Escalate critical results using approved notification and acknowledgement procedures.
  • For external labs, print/share test requests and track status or uploaded results where supported.

AI assistance: report extraction, delay prediction and completeness checks. Use validated deterministic rules for reference-range and critical-value alerts.

8

Doctor Review & Follow-up

MVP workflow capability

A clinical workflow stage, not necessarily a separate login role; handled by the authorized treating doctor/clinician.

  • Identify test results and reports awaiting review.
  • Review results in the context of history and the treatment plan.
  • Record interpretation, additional decisions and care-plan changes.
  • Update prescriptions or order investigations when authorized.
  • Document patient communication, referrals and follow-up instructions.
  • Track follow-up status and close or continue the visit as appropriate.

Model this as permissions, tasks and visit states unless a clinic specifically needs a separate role.

9

Pharmacist / Medicine Dispensing

Optional module

Enabled for clinics with an in-house pharmacy or medicine counter.

  • Access authorized prescriptions and verify patient and prescription details.
  • Check medicine availability, strength, dosage form, batch and expiry.
  • Record actual quantities dispensed, partial dispensing and completion status.
  • Flag concerns to the prescriber; substitutions only when permitted and authorized.
  • Manage medicine catalogue, stock movements, batches, expiry, purchases, suppliers and returns as enabled.
  • Generate pharmacy invoices/receipts when pharmacy billing is enabled.
  • Audit dispensing, stock changes, returns and adjustments.

External pharmacy: Clinics without a pharmacy can still print/share prescriptions. Printing a prescription must not mark a medicine as dispensed.

AI assistance: catalogue search, document extraction, stock forecasting and anomaly flags. AI cannot change prescriptions or authorize restricted medicines.

10

Billing & Accounts

Basic MVP

Handles clinic charges and payment records; advanced accounting can follow later.

  • Create invoices for configured consultation, procedure, laboratory and pharmacy charges.
  • Record cash, UPI, card and other enabled payment methods.
  • Issue receipts and track paid, partially paid, unpaid and refunded states.
  • Manage authorized discounts, credit notes, refunds and cancellations with approval controls.
  • Track outstanding balances and reconcile daily collections by payment method.
  • Generate collection, invoice, refund and outstanding reports.
  • Support insurance or third-party payer workflows when enabled.

Smaller clinics may grant limited payment collection to receptionists; refunds and adjustments remain permission-controlled.

5. Optional and expansion roles

Add these according to clinic size, services and requirements. They are not mandatory for every clinic.

RoleResponsibilitiesWhen needed
Lab ManagerLab staff, quality processes, result authorization, turnaround monitoring and operations.Medium/large in-house lab
Radiology / Diagnostic TechnicianImaging/procedure workflow, study tracking and report coordination.Clinics offering diagnostics
Medical Records StaffScan, classify, retrieve, manage and archive authorized patient documents.High-volume clinics
Insurance / Claims ExecutiveEligibility, claim submission, supporting documents, queries and status tracking.Insurance/third-party billing
Reception / Call Center ExecutivePatient enquiries, appointment coordination, reminders and follow-up calls.High-volume/multi-location clinics
Inventory / Purchase ManagerSuppliers, purchase orders, goods receipt, stock transfers and procurement.Pharmacy or larger clinics
Physiotherapist / SpecialistSpecialty assessment, treatment plans, sessions, progress and follow-up.Specialty services
Nutritionist / DietitianNutrition assessment, diet plans, progress and nutrition follow-up.Clinics offering nutrition
Patient / Portal UserView authorized personal records, prescriptions, reports, invoices and follow-up instructions.Patient portal enabled
Auditor / Compliance OfficerReview authorized audit logs, access activity, control evidence and compliance reports.As required
Clinic Owner / Management reportingRevenue, patient volume, clinic performance, staffing and operational analytics.Owner/management access; may be a permission set
Role vs. module: A module is a set of capabilities; a role is a set of permissions. Enabling Pharmacy does not automatically create pharmacist accounts.

6. Patient workflow

Receptionist→Nurse→DMO, if used→Consultant Doctor→Investigation, if ordered→Doctor reviews results→Treatment / prescription / follow-up

After consultation, a patient may proceed to billing, an in-house pharmacy, an external pharmacy, an in-house lab, an external lab, referral or follow-up. These are workflow branches, not mandatory steps for every patient.

Example visit states

Registered→Checked in→Nursing→Initial assessment→Consultation→Awaiting results / treatment→Follow-up / completed

Permit only valid transitions. Emergency escalation must not be blocked by routine registration, billing or queue steps.

7. Dev Admin vs. Clinic Administrator

CapabilityDev Admin / Platform Super AdminClinic Owner / Clinic Administrator
Tenant lifecycleAcross tenantsOwn organization within granted scope
Feature availabilityDefines platform/plan availability and rolloutEnables entitled features for own clinic
Plans and limitsDefines plans, entitlements and limitsViews plan/usage; requests upgrades where supported
Users and rolesPlatform admin access and policyClinic staff accounts and role assignments
Branding/templatesDefines allowed customization and global defaultsSets own clinic branding and permitted templates
IntegrationsProvider options and platform configurationPermitted clinic-specific settings/credentials
Security/auditPlatform-wide controls and monitoringClinic access reviews and audit visibility
Patient recordsNo routine browsing by default; exceptional support access must be authorized and auditedAccess only as permitted; clinical details limited by need

8. Feature toggles and customization

A platform configuration and entitlement system lets small clinics keep the product simple while larger facilities enable additional capabilities.

Feature/module toggles

  • Clinical: DMO stage, consultation, prescriptions and follow-up.
  • Operations: laboratory, pharmacy, billing and inventory.
  • Patient services: portal, reminders and document access.
  • AI: assistant, voice input, note drafting and summaries.
  • Enterprise: branches, departments and advanced reports.
  • Beta features: selected tenants, staged rollout and kill switch.

Customization settings

  • Clinic logo, name, colors, theme and permitted design tokens.
  • Navigation menu visibility and ordering.
  • Custom fields, labels, form layouts and required-field rules.
  • Prescription, invoice and report templates.
  • Patient, visit, invoice and prescription numbering rules.
  • Language, date format, time zone and currency.
  • Departments, specialties, visit types, hours and fees.
  • Notification templates, triggers and provider configuration.

Configuration hierarchy

Platform defaults / policies→Plan entitlements→Organization settings→Clinic settings→User preferences

Define which settings may be overridden at each level. User preferences must not override security policy, clinical controls or subscription restrictions.

9. Security, clinical safety and business rules

  • Backend enforcement: Hiding a menu is not authorization. Every API checks tenant scope, permissions, module entitlements and workflow state.
  • Tenant isolation: A user in one clinic cannot access another tenant's data unless explicitly authorized through a controlled platform process.
  • Least privilege: Grant only the minimum access required; separate clinical, financial, platform and clinic administration permissions.
  • Audit trail: Record important changes to clinical notes, prescriptions, results, invoices, permissions, feature flags and configurations. Preserve authorship and revisions.
  • Safe deactivation: Disabling a module must not delete prescriptions, invoices, results or other records. Define read-only access, retention and export behavior.
  • Feature dependencies: Validate dependencies before enabling a module. Dispensing requires Pharmacy; pharmacy billing requires the appropriate billing capability.
  • Clinical authority: Diagnosis, prescribing, investigation ordering, result verification and treatment permissions depend on professional authorization and clinic policy.
  • Emergency handling: Urgent escalation must not wait for routine workflow completion or payment.
  • AI governance: Treat AI output as a draft/recommendation; verify consequential content, minimize data sent to external providers and record relevant actions.
  • High-impact operations: Require confirmation/approval for destructive actions, refunds, access overrides and sensitive configuration changes.
  • Privacy: Restrict sensitive patient information by role and purpose. Platform administrators should not routinely browse patient records.

10. Product design principles

Configurable, not fragmented

Use one product with modules and settings rather than separate codebases for small and large clinics.

Roles are not modules

Keep role assignments, permissions, module entitlements and workflow states separate.

Print and external workflows

Support clinic-branded PDF/print prescriptions, investigation requests, invoices and reports. Do not require an in-house pharmacy or laboratory.

AI is an assistant

Use AI for drafting, search, extraction and summaries. Use deterministic code for identifiers, billing, access checks and exact business rules.

Auditability by design

Make important state transitions, clinical signatures, payments and configuration changes traceable.

Progressive rollout

Start with the end-to-end MVP, validate with pilot clinics, then enable optional modules and enterprise capabilities.

Implementation summary: Begin with platform and clinic administration, then deliver the core patient journey—Receptionist → Nurse → optional DMO → Consultant Doctor—alongside basic billing. Keep laboratory, pharmacy and other service modules configurable. Model Doctor Review & Follow-up as a workflow capability unless a clinic has a specific reason to assign it to a separate role.