Vortex HealthPulse
Enterprise One
One platform. One patient record. Ten healthcare business models. Software built around how your team already works, with Core AI that recommends and automates while your people approve every decision.
Chapters
| # | Chapter | What it covers | Format |
|---|---|---|---|
| 1 | Company & founder | Who Vortex is, the founder line, and what the company has proven so far | One screen |
| 2 | How Vortex works | Business first, technology second: the three-step start and the nine-phase engagement | One screen |
| 3 | Industries & integrated services | Eight industry heroes, each with its Pulse product, SmartAI-Pulse, digital products and GrowPulse on one record; corporate training | One screen |
| 4 | Product launch · Vortex HealthPulse | Evidence and market potential → why these AI features → responsible AI → data security and the market gap → the HealthPulse formula → ten modules → flagship deployments | Hero section |
| 5 | How Vortex engages | Engagement channels by category: providers, suppliers and dealers, technology partners and joint ventures, ecosystem bodies, finance and facilitators | One screen |
| 6 | Data protection, in detail | Identity, encryption, privacy, audit, resilience and AI governance; what the database enforces, not just the screen | One screen |
| 7 | Technology | The current HealthPulse stack: React, Vite, TypeScript, Supabase Postgres, Edge Functions, WhatsApp Business Platform, Netlify and Cloudflare | One screen |
| 8 | Connect with Vortex | Two QR codes: WhatsApp the founder, book a free Pulse Check; every contact channel | Closing |
Vortex Digital Solutions Private Ltd
A Chennai software company that builds operating systems for businesses whose work happens on a floor, in a ward, at a counter or on a road, where the owner cannot see everything at once.
22+ years leading digital transformation in complex, production-scale operations.
Enterprise supply chain and operations leadership at Ford, Timken and St John Freight before founding Vortex. He has run the operations Vortex now digitises, which is why every engagement starts with the operating model and not with a product.
"Software connects. AI elevates. People decide."
Business first. Technology second.
| Engagement phase | What happens |
|---|---|
| 1 · Enquiry | Call, WhatsApp, email or the website |
| 2 · Requirements | Requirement session, feasibility assessment of complexity, findings communicated |
| 3 · Quotation | Price quotation with an estimated timeline; customer accepts |
| 4 · Build | Blueprint development begins |
| 5 · Development | First-cut demo, final blueprint and demo presented, customer sign-off |
| 6 · Deployment | Staging / pre-production checks |
| 7 · Go-live | Released to production |
| 8 · Post-implementation | Support from go-live including training and troubleshooting |
| 9 · Ongoing | New features scoped and billed as new engagements |
| Design principle | In practice |
|---|---|
| Discover → Analyze → Design | Objectives, systems and inefficiencies before any architecture |
| Develop → Deploy | Secure, high-performance applications; migration, integration, training, minimal disruption |
| Support & Optimize | Proactive support, continuous improvement, feature enhancement |
| Keep what you run | Your ERP, accounting, hospital or pharmacy software stays; we add the module that fixes the gap |
| Four deployment modes | Standalone module · Overlay on your data · In-house department of Enterprise One · Enterprise One with migration |
| Smallest stack that lasts | We choose the smallest stack that solves the problem and is still maintainable in three years |
Industries and the services that run on one record
Every industry gets one Pulse product family. The same three pillars run on every one of them, on the same record: the Pulse software that connects the operation, the SmartAI-Pulse layer that elevates it, and digital products and GrowPulse that bring customers in and keep them. Buy Enterprise One, or start with one module beside the software you already run.
| Industry hero | Pulse product | Modules on one record | SmartAI-Pulse layer | Digital products | GrowPulse growth |
|---|---|---|---|---|---|
| Hospitals, clinics & healthcare UNDER PRODUCTION DEPLOYMENT · GO-LIVE 15 NOV 2026 | Vortex HealthPulse 10 modules · Enterprise One | Front desk → consultation → pharmacy → lab → billing → recall; specialty clinics, dental, eye care, wellness & AYUSH, pharmacies, labs, doctors platform, equipment service cloud, home care | SmartAI-Pulse: predict · automate · approve · audit | Websites, customer & staff apps, enquiry capture | GrowPulse: Google, ads, WhatsApp journeys, CRM, conversion analytics |
| Fuel retail LIVE IN OPERATIONS · SINCE 1 SEP 2026 | Vortex SitePulse 6 modules · Enterprise One | Forecourt, wet stock, dry stock, sales, billing & payment, outlet intelligence; read-only mirror of the forecourt controller, no new hardware | SmartAI-Pulse: predict · automate · approve · audit | Websites, customer & staff apps, enquiry capture | GrowPulse: Google, ads, WhatsApp journeys, CRM, conversion analytics |
| Logistics & distribution | Vortex DeliveryPulse 16 modules | Trip & load, fleet utilisation, freight audit, yard & dock, driver & duty, last-mile proof; warehouse inbound, slotting, pick & dispatch, stock accuracy, labour, automation interface; reroute, exception control, control tower, inventory positioning | SmartAI-Pulse: predict · automate · approve · audit | Websites, customer & staff apps, enquiry capture | GrowPulse: Google, ads, WhatsApp journeys, CRM, conversion analytics |
| Manufacturing | Vortex ProductionPulse 12 modules | Demand forecast, orders, material planning, procurement, scheduling, quality & maintenance, stores, shop floor & OEE, job work, costing & margin, dispatch & compliance, plant intelligence | SmartAI-Pulse: predict · automate · approve · audit | Websites, customer & staff apps, enquiry capture | GrowPulse: Google, ads, WhatsApp journeys, CRM, conversion analytics |
| Hospitality & food service | Vortex StayPulse 4 modules | Guest & booking, kitchen & production, supply & food safety, multi-site margin | SmartAI-Pulse: predict · automate · approve · audit | Websites, customer & staff apps, enquiry capture | GrowPulse: Google, ads, WhatsApp journeys, CRM, conversion analytics |
| Education | Vortex EducationPulse 4 modules | Admissions, academic operations, student success, fees & finance | SmartAI-Pulse: predict · automate · approve · audit | Websites, customer & staff apps, enquiry capture | GrowPulse: Google, ads, WhatsApp journeys, CRM, conversion analytics |
| Dealerships, franchises & agencies | Vortex NetworkPulse 6 modules | Outlet onboarding, territory & lead, service & workshop, parts & inventory, standards & audit, network finance | SmartAI-Pulse: predict · automate · approve · audit | Websites, customer & staff apps, enquiry capture | GrowPulse: Google, ads, WhatsApp journeys, CRM, conversion analytics |
| Retail & wholesale | Vortex RetailPulse 5 modules | Merchandising, stock & replenishment, store operations, customer & loyalty, retail intelligence | SmartAI-Pulse: predict · automate · approve · audit | Websites, customer & staff apps, enquiry capture | GrowPulse: Google, ads, WhatsApp journeys, CRM, conversion analytics |
Vortex HealthPulse Enterprise One
4.1 What the evidence says: the market is ready, the structure is missing
Most hospitals are integrated: everything is recorded. Very few are intelligent: nothing warns that tomorrow's OPD will overflow, that a batch expires next week, or that a patient is about to miss a follow-up. The numbers below are from public sources, each with its context; they describe the opportunity and the obligation.
| Figure | Source and context | What it means for a hospital or clinic |
|---|---|---|
| 105 crore+ health records linked to ABHA; 93.95 crore+ ABHA IDs; 5.33 lakh facilities and 9.85 lakh professionals registered | Ayushman Bharat Digital Mission, Mission Steering Group, July 2026; about 10 crore records linked every 2–3 months | The digital rails are built. The question is whether your operation is structured to use them. |
| EMR adoption in India about 35%; most providers still in controlled AI pilots; frontier model costs down about 92% since 2023 | Bain & Company with HealthQuad, "AI in Indian Healthcare Delivery", September 2026 | Two-thirds of the market is still on paper or disconnected software. The cost barrier to AI has fallen; the implementation barrier has not. |
| Hospital IT budgets to rise 20–25% over the next 2–3 years; 60%+ name capability building as the biggest challenge | CII–EY HealthTech Survey 2025 | Owners are already investing. The gap is structure and governance, not intent. |
| 97% of primary-care doctors in India ready for AI; 75% of consumers ready for AI-powered care | ZS Future of Health 2025 (India) | Readiness is not the barrier. Implementation is. |
| NABH digital health standards: digital maturity 3.42 → 4.35; clinical use of records 3.00 → 4.37; one hospital cut revenue leakage from 33% to 7% | ISB white paper on 20 NABH-DHS certified hospitals, mostly SME and non-metro, August 2026 | Disciplined digital operations pay back in leakage, not just in reports. |
| DPDP Rules notified November 2025; most data-fiduciary obligations, including 72-hour breach reporting, due by about May 2027 | Digital Personal Data Protection Act 2023 and Rules 2025; KPMG healthcare note | Every hospital has about six months to show consent records, purpose limits and breach readiness. |
| 15,791 hours of documentation saved across 2.58 million encounters; 84% of physicians reported better patient communication | Permanente Medical Group ambient-AI scribe programme, 2023–24 | AI gives clinicians time back. The doctor still reviews and signs every note. |
| No-shows cut by 16% among flagged patients once a prediction was followed by a confirmation call | Johns Hopkins clinics | Prediction plus a human action is where the value is. |
4.2 Why these AI features: industry pain points the evidence points to
| Live pain point on the floor | What usually happens today | HealthPulse feature that answers it | Evidence it draws on |
|---|---|---|---|
| Queues run from memory | Front desk arbitrates walk-ins and appointments by instinct; patients ask "how long?" | Smart queue, digital token, TV display in Tamil and English; Pulse Command forecasts tomorrow's load | ZS readiness; NABH-DHS efficiency gains |
| Follow-ups depend on the patient remembering | Recalls lost; revenue and continuity lost with them | Recall engine with next-review date on every consult; no-show risk scoring; second reminder only after approval | Johns Hopkins 16% no-show reduction |
| Expiries found on the shelf | Returns missed; working capital tied in slow stock | Batch and expiry bands; first-expiry-first-out; return list drafted by distributor; chronic refill nudges | ISB leakage finding |
| Charges missed between counters | Pharmacy, lab and procedure lines slip between departments | Estimate slip and billing gates enforced in the database; consolidated OP/IP bills; reconciliation against existing billing | ISB: leakage 33% → 7% |
| Reports take three phone calls | Nobody can say where the sample is | Sample journey with barcode and TAT promise; breach notice before the patient calls; report on WhatsApp | Bain–HealthQuad: 65% still disconnected |
| Doctors write everything twice | Handwritten files, re-typed prescriptions | Doctor cockpit with history, structured prescription, letterhead PDF on WhatsApp | Permanente: 15,791 hours returned |
| Consent and audit exist only on paper | DPDP obligations arriving by May 2027 | Consent recorded with wording, signer and version; append-only audit log; role-based access in the database | DPDP Act 2023 and Rules 2025 |
4.3 Using AI responsibly in healthcare
| Responsible-AI ladder | What the system may do |
|---|---|
| 1 · Observe | Read the record, compute KPIs |
| 2 · Inform | Show forecasts, exceptions and reasons |
| 3 · Recommend | Draft the recall batch, the return list, the extra OPD slot |
| 4 · Act with human approval | A named role approves, defers or rejects; nothing executes before approval |
| 5 · Act within audited guardrails | Routine, low-risk steps run on rules, every one logged |
Each step is earned with measured accuracy on the organisation's own data. Clinical decisions always stay with clinicians.
| Where AI must not decide | Why |
|---|---|
| Final diagnosis, treatment and prescribing | Clinical judgement and liability stay with the doctor |
| Emergency triage | Time-critical, context-rich, human |
| Breaking bad news, consent | Human dignity and legal validity |
| Anything that moves money, medicine or a patient promise on its own | A named person approves; the audit ladder records who, what, when and why |
| Documented risk | Control built into HealthPulse |
|---|---|
| Models that work elsewhere fail on local data (sepsis model AUC 0.63 in external validation, 2021) | Forecasts computed on the hospital's own history; validated before go-live; monitored after |
| Automation bias: staff follow wrong AI advice | Reason and expected impact shown on every card; approval required for important actions |
| Misuse of AI chatbots: ECRI's number one hazard for 2026 | Bounded, reviewed assistant; no clinical advice; Tamil and English intent confirmation before anything changes |
| Loss of access to electronic systems: ECRI number two | Manual fallback designed; restore drill and recovery playbook before go-live |
India already has the rulebook: ICMR ethical guidelines for AI in healthcare (2023, ten principles) and WHO guidance on large multi-modal models (January 2024). The approval ladder and audit trail implement them.
4.4 Data security, and where the market leaves gaps
Patient data is sensitive personal data under the DPDP Act 2023. A hospital software decision in 2026 is a data-protection decision: who can read a row, where it is stored, what happens when a laptop is lost or a system is down, and whether consent can be produced on request. The segments below are categories met in the market, not named companies.
| Market segment we meet | Typical strength | Typical gap | How HealthPulse is positioned |
|---|---|---|---|
| Low-cost clinic EMR (subscription SaaS) | Very low published price, free trial, AI note-taking, WhatsApp booking | Outpatient only; no inpatient, lab system, pharmacy chains or multi-site; little governance beyond the doctor approving notes; no Tamil interface found | Depth: inpatient, lab, pharmacy chains, five-site network view, governance and Tamil, with a local team that owns go-live |
| Free or open-source hospital software | Broad module list on paper; low licence cost | Self-hosting needs in-house IT; AI and health-ID integration on the roadmap; no visible support team, SLA or references | Hosted in India with daily backups, point-in-time recovery, MFA and a named team; AI live today; the licence is the smallest cost, the first thirty days decide |
| Enterprise engineering and integration firms | Strong FHIR/HL7 and cloud engineering, often export-oriented | Remote delivery; little hospital-workflow product depth for Indian tier-2 operations | Partner at the integration layer; Vortex keeps workflow ownership and local adoption |
| Queue kiosk and hardware vendors | Proven kiosks and signage at bank scale; financial strength | No HMIS, EMR, pharmacy or lab software; English-only voice; capital-heavy projects | HealthPulse as the record behind the kiosk; joint demos rather than competition |
4.5 The HealthPulse formula
| Integrated software tells you | Intelligent software also tells you |
|---|---|
| How many patients came yesterday | How many will come tomorrow, and when |
| What stock you have now | Which batch will expire or run out next week |
| Which bills were raised this month | Which charges are likely to be missed today |
| Who missed their appointment | Who is likely to miss, so you can call first |
4.6 Ten modules, three sizes, four modes, one record
Every module ships in three sizes (solo or single site, growing with several units, multi-site network) and deploys in four modes. All ten are built and ready for demo on synthetic data; every clinic, patient and bill shown is fictional.
| Module | Healthcare model | Hero applications | Size 1 | Size 2 | Size 3 | Status |
|---|---|---|---|---|---|---|
| B1 | Specialty & multi-specialty clinics | Smart queue and one calendar; structured consult and recall engine; own-channel bookings and no-show risk | Solo specialist | Multi-specialty | Chain, 3+ branches | BUILT · READY FOR DEMO |
| B2 | Pharmacies & chains | Batch and expiry control, first-expiry-first-out; prescription intake, lost sale and substitution, Schedule H/H1/X registers; chronic refill nudges and store balancing | Standalone chemist | 2–10 outlet chain | Large chain / franchise | BUILT · READY FOR DEMO |
| B3 | Diagnostics labs, scan & X-ray | Sample journey and TAT by test with breach notice; home collection and routes; report delivery and referral desk | Standalone lab | Lab + collection centres | Multi-city hub and spoke | BUILT · READY FOR DEMO |
| B4 | Holistic wellness & AYUSH | Course tracker; therapy room and therapist scheduler; package billing, margin and multilingual enquiries | Single practitioner | Therapy centre / retreat | Multi-branch network | BUILT · READY FOR DEMO |
| B5 | Dental clinics & chains | Staged treatment plan and tooth chart; lab case tracker and consumables; chair utilisation and recall | Single dentist, 1–2 chairs | Multi-chair centre | Dental chain | BUILT · READY FOR DEMO |
| B6 | Eye care clinics & networks | Patient flow board; counselling funnel and IOL stock; spectacle orders, camp referrals and devices | Clinic with optical counter | Eye hospital with surgery | Network with vision centres | BUILT · READY FOR DEMO |
| B7 | Equipment Service Cloud: suppliers, dealers & service | Installed base and AMC; service ticketing with SLA, parts by serial; rentals, quotes and dealer portal | Dealer / rental shop | Regional distributor | Multi-state / OEM partner | BUILT · READY FOR DEMO |
| B8 | Home care, nursing & elder care | Visit proof and family update; roster and replacement pool; discharge referrals and shift billing | Single agency | Multi-service provider | Multi-city, hospital-linked | BUILT · READY FOR DEMO |
| B9 | Doctors & doctor-service platforms | One calendar and own channel with fees-saved calculator; unified visit record; practice dashboard and white-label operator portal | Individual doctor | Doctor group / polyclinic | Platform operator | BUILT · READY FOR DEMO |
| B10 | Hospitals & networks · Enterprise One | Running token and TV, self check-in, vitals gate, doctor cockpit, pharmacy, lab, admission to discharge, OP/IP billing, insurance claims, WhatsApp, reconciliation, masters import, multi-branch, migration beside current software | Single site | Hospital with ICU and inpatient wing | Multi-branch network | BUILT · READY FOR DEMO |
| Platform feature on every module | What it does |
|---|---|
| One HealthPulse interface | Same header, KPI strip, worklist, record panel and approvals rail everywhere; light and dark theme; Tamil where patients look |
| Front desk and billing | Appointments and walk-ins in one list, consent and optional health ID on every record; exempt and taxable lines on one invoice, posts to accounting after a feasibility check |
| Tamil front desk | Patients ask by voice or text in Tamil or English; the desk confirms before anything changes |
| Dashboard and approvals | Owner's KPIs, exceptions, and every SmartAI-Pulse recommendation waiting for a decision |
| Pulse Command | Next-7-day forecast from the module's own history; suggested actions queued for approval, never sent alone |
| Connect your data (overlay) | Keep the current software; drop an export or connect an interface; exceptions appear in seconds |
| WhatsApp engine | Reminders, notices, reports, bills and renewals as approved batches, Tamil or English, opt-in and STOP handling, delivery status on the record |
| Compliance panel and audit ladder | DPDP, ABDM, Bio-Medical Waste Rules, clinical establishment rules, GST split, Telemedicine Guidelines, NABH; who recommended, approved and changed what, exportable |
| Deployment mode | When to choose it | Exchange with your systems |
|---|---|---|
| 1 · Standalone module | One module beside the software you already run; live in weeks | Masters by export; bills stay where they are; nothing written into your software |
| 2 · Overlay: connect your data | Keep every system; get exceptions and forecasts on top | Read only; scheduled exports first, interfaces where they exist |
| 3 · In-house department of Enterprise One | The pharmacy, lab, dental or eye module on the hospital's record | None outside Enterprise One; insurer, TPA, analysers and imaging through available interfaces |
| 4 · Enterprise One with migration | The single platform from go-live; issues numbers, raises bills, runs pharmacy, holds results, records claims, produces MIS | Read-only bridge to the old system; parallel run, rehearsal, restore drill and training before cutover; never a write-back |
4.7 Flagship deployments
A 50-bed private multi-speciality hospital with ICU, in-house laboratory, X-ray and pharmacy, and a 24×7 emergency line. Vortex HealthPulse Enterprise One is being deployed as the hospital's single operating platform: running token and TV display, vitals gate, doctor cockpit, pharmacy, laboratory, admission to discharge, OP and IP billing, insurance claims, WhatsApp in Tamil and English, reconciliation and MIS. It runs read-only beside the current system until cutover, with parallel run, rehearsal and a restore drill first.
Go-live: 15 November 2026.
A read-only mirror of a closed forecourt controller: tank levels, twelve nozzle meters, prices and end-of-day sales on desktop and mobile, read from equipment with no published interface, with no new hardware on the forecourt and no write access to the controller. Built and taken to production in three and a half weeks; running continuously since go-live. End-of-day figures reconcile against tank movement rather than nozzle totals, and the dealer sees the station from a phone.
Live in operations since 1 September 2026.
Engagement channels by category
Vortex works through five channels. Each starts with a free Pulse Check and a bounded first phase; none starts with exclusivity or a price list.
| Category | Who they are | What Vortex offers | Engagement model | First step |
|---|---|---|---|---|
| Care providers | Hospitals 20–200 beds, specialty and multi-specialty clinics, labs and scan centres, pharmacies and chains, dental, eye care, wellness and AYUSH centres, home-care agencies | HealthPulse Enterprise One, or one module beside the software they run; GrowPulse for visibility | Pulse Check → one-area pilot with baseline and acceptance criteria → expand with evidence | 30-minute Pulse Check with the administrator and the owner |
| Medical equipment suppliers, dealers and service providers | Equipment, diagnostics, surgical and consumables dealers; service engineers; rental businesses | Equipment Service Cloud: installed base, AMC, calibration and licence renewals, SLA tickets, rentals and quotes; a referral channel into the hospitals they have equipped | Dealer subscription plus referral partnership with a documented fee structure | Live module walkthrough; one dealer pilot |
| Technology partners and joint ventures | Clinic EMR vendors, integration and FHIR engineering firms, kiosk and queue hardware makers, open-source hospital software communities, health-tech sponsors | SmartAI-Pulse as an intelligence layer over an existing EMR; HealthPulse as the record behind kiosks; local implementation and adoption for remote engineering teams | Integration-layer partnership or joint venture with defined account ownership, contracting party, scope, support escalation, payment trigger and branding; one named opportunity first | Technical call on the integration layer; joint demo |
| Ecosystem and institutions | Medical associations and their chapters, hospital federations, business referral networks, chambers, medical colleges, startup and innovation programmes | Member demo evenings, free Pulse Checks for members, co-branded knowledge sessions on responsible AI and DPDP readiness, internships and research pilots | Member-benefit agreement; event partnership | Introduction through an office-bearer; one member session |
| Facilitators, finance and insurers | Medical tourism facilitators, patient-guidance companies, banks and NBFCs serving SMEs, insurers and TPAs | CRM and WhatsApp journeys for enquiry-to-admission; software EMI and SME finance for hospital buyers; claims status on the admission record | Lightweight package for facilitators; referral or financing arrangement with finance partners | Product sheet exchange; named contact for SME finance |
What the database enforces, not just the screen
| Control area | What is implemented | Why it matters in healthcare |
|---|---|---|
| Identity and least privilege | Named account for every member of staff with one or more of thirteen roles; role and purpose-based access enforced in the database with row-level security; a staff account can be marked view-only so the database refuses every change; MFA for administrator, billing and doctor roles; session timeout; rapid deprovisioning | Vitals, prescriptions and billing are visible only to the roles that need them; a shared login cannot exist |
| Sign-in | E-mail and passcode; in production also a one-time 6-digit code to the staff e-mail; the patient portal has its own gate and can only read rows for its own mobile; the browser's public key can never read patient rows | Front-office staff cannot reach clinical data; a patient cannot reach another patient |
| Encryption and secrets | TLS 1.2+ in transit; AES-256 encryption at rest; managed keys; secrets in the platform secret store, never in code; minified production build with an obfuscation pass | Lost laptops, intercepted traffic and copied code do not expose data |
| Privacy and consent (DPDP Act 2023, Rules 2025) | Purpose labels and consent records with wording, signer, time and version; WhatsApp consent and admission consent stored; data minimisation; retention schedule; named grievance contact for access, correction and erasure requests; data stays in India (Mumbai region) | The hospital can produce consent and purpose on request, ahead of the obligations falling due in 2027 |
| Data boundary | No patient data to an external service, analytics tool, log or AI prompt; forecasts computed inside the database; demo and test sites hold synthetic data only | AI features do not create a new data leakage path |
| Audit and monitoring | Append-only audit log of who viewed or changed what; every recommendation, approval and override recorded with who, when and why; exportable governance pack (approval matrix, model register, data-minimisation map); log retention per CERT-In directions | Every clinical, financial and AI decision is traceable for the owner, the auditor and the regulator |
| Resilience and assurance | Automated daily backups with point-in-time recovery; restore drill and written recovery playbook before go-live; environment isolation (dev, test, production, each with its own database); 183 unit tests across 28 files, visual checks and as-user database smoke tests before every deploy; uptime and error monitoring | A hospital cannot stop while software is improved; manual fallback and tested recovery are part of the design |
| Migration safety | Read-only bridge to the existing hospital and pharmacy systems; parallel run, rehearsal and restore drill before cutover; never a write-back into the old system | The old system remains intact until the hospital decides to cut over |
| AI governance | Approved use cases; bounded data access; human review; model register; clinical decisions stay with the doctor; the responsible-AI ladder in section 4.3 | Responsible AI is a product rule, not a policy document |
| Communications | WhatsApp Business Platform on the hospital's own number with approved Tamil and English templates; opt-in recorded; STOP handling; delivery and read status on the record; a production number never used by hand | Patient messaging is consented, traceable and cannot be hijacked by a personal phone |
Durations and deadlines cited from the DPDP Rules are marked for verification with the hospital's legal adviser. Controls are configured to the selected product, deployment mode and data classification.
The current HealthPulse stack
| Layer | Technology in use | Why this choice |
|---|---|---|
| Front end | React 18 built with Vite; TypeScript; TanStack Router; Tailwind CSS; progressive web app; responsive and mobile-first | Runs in Chrome or Edge on the hospital's PCs, the desk laptop, the TVs and the patient's phone with nothing installed; fast on a patchy connection |
| Database | Supabase Postgres (PostgreSQL) with row-level security in the Mumbai region; database triggers and stored procedures; pg_cron for the clock | Every rule, numbering series, gate, estimate, bill, forecast and audit entry lives in the database, so policy is enforced even if a screen is bypassed |
| Authentication | Supabase Auth: named staff accounts, fenced patient-portal login, one-time codes, MFA for sensitive roles | Identity is the first control |
| Server functions | Supabase Edge Functions (Deno): WhatsApp sender and webhook, bill renderer, staff one-time code, portal sign-in, pre-authorisation e-mail, voice agent, pharmacy bill file ingest | Serverless, event-driven, no servers to patch |
| Storage | Supabase Storage in private buckets for PDFs; documents rendered in the browser from the hospital's own captured layouts | Prescriptions, bills, reports and registers print in the hospital's established formats |
| Messaging and voice | WhatsApp Business Platform (Cloud API) with approved Tamil and English templates; browser speech for the Tamil and English voices on the device | Patients are reached in their language on the channel they already use |
| Intelligence | SmartAI-Pulse: rules and optimisation first, forecasts computed inside the database, AI only where it improves a decision; human-in-the-loop approvals; model register; bounded data access | Explainable recommendations, no patient data in prompts |
| Integration | Read-only integration from existing systems through a SELECT-only login the hospital's administrator creates, or audited spreadsheet import; REST and webhook pipelines; accounting, insurer and TPA portals, analysers and imaging through available interfaces | Keep what you run; confirmed by a technical feasibility analysis before it is quoted |
| Hosting and delivery | Netlify hosting with edge CDN; Cloudflare in front of production host names for DNS, firewall, rate limiting and access rules; CI/CD with automated build and deploy; three isolated environments (dev, test, production) | Zero-downtime releases; the demo, test and production worlds never touch |
| Quality | Git with branch per task, pull-request review and a protected main branch; 183 unit tests across 28 files; visual checks and as-user database smoke tests before every deploy | Changes reach a hospital only after they have been reviewed and tested |
Vortex owns every platform account except the WhatsApp Business account and number, which belong to the hospital.
Two ways to start today
| Channel | Detail |
|---|---|
| Company | Vortex Digital Solutions Private Ltd |
| Founder | Magesh Raman |
| Email (founder) | mageshraman@vortex-digital.tech |
| Email (general) | info@vortex-digital.tech |
| Phone / WhatsApp | +91 97909 28123 · wa.me/919790928123 |
| Website | vortex-digital.tech |
| Office hours | Mon – Sat · 9:00 AM – 6:00 PM |
| Location | Medavakkam, Chennai 600 100, Tamil Nadu |
| Social | Link |
|---|---|
| linkedin.com/company/vortex-digital-tech | |
| instagram.com/vortexdigitech | |
| facebook.com/Vortexdigitalsolutions | |
| Chat with Vortex | |
| Free consultation | vortex-digital.tech/contact |
| At the expo | Stall F2 · Hall A · Ida Scudder Auditorium, Madurai · 31 Oct – 2 Nov 2026 |
Every clinic, hospital, patient, bill and number in the demonstrations is synthetic. Integration with existing software is subject to a technical feasibility analysis of your current system. Clinical decisions stay with the doctor.