Platform
Separate modules, one set of foundations
Hospital software usually fails in the gaps between systems. HealthcareVedas is built so the inventory analysis, the SOP it changes and the audit record of that change all sit in the same place.
Shared foundations
What every module inherits
These are decided once at the platform level, so no individual module has to reinvent access control, ingestion or export.
One records layer
Stock analyses, SOP revisions, audit findings and training records live in the same database, so a CAPA action can reference the analysis that triggered it.
Roles, not logins
Access follows the role — pharmacy, quality, administration, consultant — rather than being granted per file. Adding a colleague does not mean forwarding a spreadsheet.
Excel-first ingestion
Every analytical module accepts the exports your existing systems already produce, with guided column mapping instead of a required template.
Modules, not a monolith
Adopt one module without the others. They share the foundations, but each is useful on its own from the first upload.
Exports that travel
Anything you can see, you can export — Excel for committees, PDF for assessors. Nothing is trapped in the platform.
Audit trail throughout
Every record carries who changed it and when, because documentation that cannot be traced is not much use at an audit.
Security posture
How we intend to handle your data
HealthcareVedas is pre-launch, so these are design commitments rather than audit results. We would rather state them plainly now and be held to them than claim certifications we do not hold.
Role-based access
Pharmacy, quality, administration and consultant roles see only the records their role requires.
Encryption in transit and at rest
Managed Postgres with TLS throughout, so uploads are never handled over plain HTTP.
Audit trail on every change
Who changed what, when, and the previous value — retained for the configured period.
No patient-identifiable data
The platform is built for operational and inventory records. Clinical identifiers are out of scope by design.
Credentials in environment config
No keys in the codebase; every secret is supplied through environment variables per deployment.
Your export, your data
Uploads stay tied to your organisation, and exports are available in open formats at any time.
Roadmap
What we are building, in what order
We publish the sequence rather than dates. A module moves when it is genuinely usable, not when a quarter ends.
3 modules
2 modules
Stages mean exactly what they say: in build is being written now, planned is specified but not started, and exploring means we have not committed to building it at all.
Technology
What it is built on
Mainstream, well-supported tooling. The interesting problems here are in hospital operations, not in novel infrastructure.
- InterfaceNext.js, TypeScript, Tailwind CSS, shadcn/ui
- Data and authSupabase — Postgres, row-level security, managed authentication
- HostingVercel, with environment-scoped configuration
- Source controlGitHub, with review before anything reaches production
Early access
Bring your operations onto one platform
HealthcareVedas is being built module by module with the hospitals, pharmacies and consultants who will use it. Tell us which module matters most to you and we will show you where it stands.