Start with the plan closest to your facility, then confirm the exact modules, users, migration, training, workflow configuration and integrations before purchase. You know what is included before rollout starts.
Clinics and hospitals should not be forced into the same package. Select your facility first, then choose subscription pricing or request a one-time commercial quote.
For doctors & clinics
Prices below are starting points for standard subscription scope. Your final proposal confirms modules, users, branches, migration, implementation and any separately scoped requirements.
Best fit: 1 doctor
Starting plan for a focused digital clinic workflow
Typical workflow coverage
Best fit: up to 3 doctors
For clinics adding doctors, staff and more structured daily operations
Typical workflow coverage
Best fit: up to 6 doctors
For multi-doctor clinics that need broader operational coverage
Typical workflow coverage
The exact plan matters because a hospital usually needs deeper inpatient, departmental and integration workflows than a clinic.
This table shows typical applicability, not a contractual module entitlement. The commercial proposal is the source of truth for the exact plan and implementation scope.
Software price alone does not tell you whether the rollout will work. These are the areas we review before finalizing your scope.
We identify the departments, users, features and day-to-day workflows that need to be covered before the commercial scope is finalized.
Existing ZentroHMS forms, fields, print formats, permissions and operational steps can be configured to the agreed implementation scope.
Existing spreadsheets or software data are reviewed so the proposal can define what can be migrated, cleaned or mapped before go-live.
Training is planned around the actual users and modules selected, from doctor/front-desk clinic workflows to department-wise hospital rollout.
A fair quote should reflect the real implementation. We look at facility size, modules, migration and integrations rather than pretending every organization has the same requirements.
A solo clinic, 20-bed nursing home and multi-branch hospital group require different user, department and rollout scopes.
OPD-only clinics cost differently from hospitals requiring IPD, pharmacy, inventory, diagnostics, insurance, radiology and multi-branch workflows.
Data quality, source systems, print formats, role setup and workflow changes determine how much implementation work is required.
DICOM/PACS, external services, dedicated infrastructure and other integrations are assessed before they are added to the commercial scope.
Separately scoped when required
The purpose of the demo and proposal is to separate standard product configuration from new development or external infrastructure before you pay.
Clinic subscription plans currently start at ₹999/month for a solo-doctor setup, with broader clinic plans at ₹1,999/month and ₹3,999/month. One-time licensing is available by custom quote after we review your doctors, users, modules, migration and implementation needs.
Hospital subscription pricing currently starts at ₹5,999/month for smaller inpatient facilities, while the Complete Hospital plan starts at ₹7,999/month. One-time licensing, multi-branch, integration-heavy or larger rollouts are quoted after the required modules and implementation scope are reviewed.
Monthly pricing lowers the upfront cost and works well for organizations that prefer an operating-expense model. If you prefer a one-time license, contact us for a custom commercial proposal based on your facility, modules, users, implementation and support requirements.
No single price should be assumed to include every module, integration and custom requirement. The plan cards show the typical fit for each level; the final proposal confirms the exact modules, users, branches, implementation work and support scope.
Agreed configuration of existing ZentroHMS forms, fields, print formats, permissions, approvals and operational steps can be included within the implementation scope. New modules, major bespoke development and unrelated third-party integrations are separately scoped.
Migration is first assessed based on the source system, file format, data quality and fields required. The proposal then states what migration is included and whether advanced cleanup, mapping or historical imports require additional work.
DICOM/PACS workflows require a technical assessment of the imaging equipment, network, AE Titles, required services, PACS/storage setup and gateway requirements. Software integration and any hardware or storage requirements are therefore scoped explicitly rather than assumed to be included in every hospital plan.
AMC and ongoing support terms for a one-time license are defined in the custom commercial proposal. The exact maintenance coverage, renewal terms and separately scoped services are confirmed before purchase.
Bring your departments, doctor/user count, current software or spreadsheets, required modules and integration needs. We’ll use them to define the rollout and commercial scope.