OneCity Technologies builds hospital software from Bangalore for hospitals across India and the Gulf. Not a packaged product you rent monthly. Custom-built systems you own permanently, covering every department from patient registration to discharge, from pharmacy to pathology, from billing to blood bank. All modules share one database, one login, one support contract.
The phrase "hospital management software" covers so much ground that it has become almost meaningless. A 20-bed maternity hospital in a tier-2 city and a 500-bed multi-speciality teaching hospital in Bangalore both need "HMS." The similarity ends there. The maternity hospital needs clean OPD registration, delivery records, newborn tracking, and GST billing. The teaching hospital needs 40+ clinical department workflows, MCI audit trails, student training documentation, research data exports, and integration with multiple government insurance schemes.
That is why packaged products fail for a large percentage of Indian hospitals. They work for the middle, but the top and bottom of the market get squeezed into workflows that do not match how their staff actually work. We have watched this pattern across hospitals in Karnataka, Tamil Nadu, Kerala, and the Gulf: the hospital buys a packaged HMS, the staff quietly route around it with WhatsApp groups and Excel sheets, and within 18 months the "digital transformation" has produced a billing module that works and everything else that does not.
Custom development costs more upfront. We are transparent about that. But the total cost over five years is lower, because you are not paying monthly license fees (which accumulate to Rs.9 to 48 lakh over five years with the major Indian HMS vendors), and because the software actually gets used, which means it produces the operational data that justifies the investment.
Any hospital in India that wants to operate digitally in 2026 needs at least these core systems working together: patient registration with ABHA ID linking, OPD and IPD management, pharmacy with drug interaction checks, laboratory with analyser integration, radiology with DICOM, billing with GST and insurance pre-authorisation, and discharge summary generation in ABDM-compliant format. That is seven systems. They must share one patient record. They must produce one unified bill. They must generate one discharge summary that any ABDM-connected system in India can read.
Beyond the core, hospitals across India face state-specific and scheme-specific requirements. PMJAY (Ayushman Bharat), CGHS, ECHS, and state health schemes each have different eligibility criteria, package rates, pre-authorisation workflows, and claim submission formats. Karnataka runs Arogya Karnataka and Yeshasvini alongside the national schemes. Tamil Nadu has CMCHIS. Kerala has KASP. A production-ready billing module must handle all active schemes within one unified workflow, not require separate portals for each one. Gulf hospitals operate under DHA (Dubai), HAAD (Abu Dhabi), or MOH licensing with entirely different insurance claim structures. Our platform adapts to all of them.
After 20 years in the technology business, the failure patterns are predictable regardless of geography. First, inadequate discovery. The development team builds from a feature list instead of watching how the OPD clerk actually registers a patient during the 9 AM rush, or how the pharmacy actually handles a partial dispensing when a drug is out of stock. Second, clinical data standards are ignored. The software uses internal code sets instead of ICD-11 for diagnoses, SNOMED-CT for clinical terms, LOINC for lab observations, and HL7 FHIR R4 for health record exchange. This is not a minor gap. Without these standards, the system cannot participate in ABDM health record exchange, cannot produce NABH-standard discharge summaries, and cannot interoperate with any other hospital system. It is an architectural flaw that cannot be patched. Third, post-launch support is undefined. A pharmacy module outage during OPD hours halts medication dispensing. The SLA must specify critical response times, and the contract must define the line between bug (included) and enhancement (billable).
We started as a digital marketing agency in Bangalore in 2006. Our healthcare clients kept asking us to fix their hospital software problems alongside their SEO and Google Ads. After years of recommending third-party vendors and watching those projects underdeliver, we built our own development team and started building the systems ourselves. The result is a 120-module hospital ERP deployed June 2026, built entirely in-house, with full source code ownership for every client.
Development team based in Bengaluru (Rajajinagar). On-site support from three Karnataka offices: Bengaluru, Mangaluru (Kankanady), Mysuru (Kuvempu Nagara). Remote deployment and support for hospitals across India and international clients in the UAE, Saudi Arabia, and Oman.
Every system listed below is built to work as a standalone deployment or as part of a wider hospital platform. Each one connects to the same patient database, the same billing engine, and the same ABDM health record layer.
The parent category covering all clinical and administrative systems for hospitals, clinics, nursing agencies, and diagnostic centres.
Complete HMS with OPD, IPD, pharmacy, lab, radiology, billing, and discharge. The core system every hospital needs before adding specialist modules.
Full enterprise platform spanning clinical, administrative, financial, and HR operations. Built for 100+ bed multi-speciality and teaching hospitals.
UHID and ABHA linked patient records from registration through OPD, IPD, and post-discharge follow up. The single patient identity layer all modules read from.
GST compliant invoicing, insurance pre-authorisation, NHCX claim submission, and package billing across OPD and IPD with real-time revenue dashboards.
Structured clinical notes, prescriptions, allergy documentation, and longitudinal patient history with ABDM-ready export in HL7 FHIR R4 format.
Dispensing workflows, batch and expiry tracking, drug interaction alerts, indent processing, and controlled substance registers with audit trails.
Barcode sample tracking, HL7 analyser integration, LOINC coded results, NABL format reports, and critical value alerts with auto-notification.
Imaging orders, DICOM Modality Worklist, SNOMED coded reports, PACS integration, and radiologist workflow management.
Hourly vitals charting, ventilator parameter logging, APACHE II and SOFA scoring, fluid balance monitoring, and nursing handover documentation.
WHO surgical safety checklist, OT scheduling and utilisation tracking, anaesthesia records, implant registry, and surgical team assignment.
Procurement, stock control, indent workflows, expiry tracking, and reorder alerts for medical consumables, surgical items, and general stores.
Staff scheduling across shifts, attendance biometric integration, payroll processing with PF/ESI/TDS, and statutory compliance reporting.
Donor registration, component separation tracking, cross-matching workflows, inventory with expiry management, and NACO compliant record-keeping.
NMC 2020 guideline compliant video consultations, e-prescriptions, remote follow-up scheduling, and integration with the in-hospital patient record.
ABDM compliant clinic ERP for single-doctor practices and small chains. ICD-11 consultation, lab integration, billing, and patient portal.
Shift scheduling, credential tracking, WhatsApp-based notifications, digital timesheets, client hospital portals, and automated GST invoicing.
Lead capture, patient follow-up automation, pipeline tracking, WhatsApp integration, and referral management for hospitals and healthcare businesses.
The subscription model that Indian HMS vendors use (MocDoc, Ezovion, Care Conquer, and others) looks affordable in year one. Rs.15,000 to Rs.80,000 per month depending on bed count and modules. Over five years, that is Rs.9 to 48 lakh paid, with zero code ownership at the end. If the vendor raises prices, changes terms, or shuts down, you start over. For Gulf hospitals using international vendors like Cerner or Epic, the five-year cost runs significantly higher with similar vendor dependency.
Custom development with OneCity has a higher initial cost: Rs.12 to 70 lakh depending on scope and complexity. But after delivery, you own the source code permanently. No monthly fees. No per-user charges. No renewal negotiations. The total five-year cost is typically 30 to 50 percent lower than the subscription alternative, and at the end of year five you have an asset instead of an expense line.
| Factor | Packaged HMS (Subscription) | Custom Development (OneCity) |
|---|---|---|
| Year 1 cost | Rs.1.8 to 9.6 lakh | Rs.12 to 70 lakh |
| 5-year total | Rs.9 to 48 lakh | Rs.12 to 70 lakh (one-time) |
| Code ownership | Never. Vendor owns everything. | Full source code. Permanently yours. |
| Customisation | Limited. You adapt to their workflow. | Built for your exact workflow. |
| Data portability | Vendor-dependent. Often restricted. | Your database. Export anything. |
| Switching cost | High. Locked into their ecosystem. | Zero vendor lock-in. |
| ABDM compliance | Varies. Some partially compliant. | Full ABHA, HIP/HIU, FHIR R4, NHCX. |
| Best for | Small hospitals, standard workflows. | Hospitals with specific clinical needs. |
We are direct about this: for a 10-bed clinic with straightforward OPD and billing needs, a packaged product is probably the right choice. Custom development is the better investment when the hospital has workflow requirements that packaged products cannot accommodate, when long-term cost matters, or when data ownership is a priority.
Every project follows the same sequence, whether the hospital is in Bangalore, Chennai, or Dubai. We do not skip steps, and we do not start coding before discovery is complete.
Our team spends time physically in the hospital, or conducts structured remote discovery for hospitals outside Karnataka. OPD registration counters during morning rush. Pharmacy during peak dispensing. Nursing stations during shift handover. ICU during rounds. The goal is not to ask staff what they want (they will describe an idealised workflow). The goal is to observe what they actually do, including the workarounds, the paper registers, the WhatsApp groups, and the Excel sheets that the current system cannot handle. For on-site discovery, our three Karnataka offices (Bengaluru, Mangaluru, Mysuru) allow us to reach any hospital in the state without travel overhead. For hospitals in other Indian states or the Gulf, we conduct a combination of video walkthroughs, screen recordings of current systems, and focused on-site visits. This phase produces a workflow specification document that becomes the development contract.
Database schema design using clinical data standards: ICD-11 for diagnosis coding, SNOMED-CT for clinical terminology, LOINC for laboratory observations, RxNorm for medications, HL7 FHIR R4 for health record interoperability. ABDM integration architecture for Indian hospitals: ABHA ID creation and linking, HIP/HIU registration, consent management, NHCX insurance claims. For Gulf hospitals: DHA/HAAD/MOH compliance mapping, insurance payer integration, Arabic-English bilingual output. These standards are non-negotiable. A hospital system built on proprietary code sets in 2026 is born obsolete. Reference: ABDM Health Data Management Policy.
Modular development in 2-week sprints. Each sprint delivers a working module that can be demonstrated and tested. Clinical staff test each module against their real patient load, not sample data. The most common cause of project timeline extension is delayed clinical sign-off during UAT, where staff identify workflow gaps that were missed during discovery. Thorough Phase 1 work reduces this risk significantly but does not eliminate it entirely.
Parallel operation with the existing system (paper or digital). Staff use both systems simultaneously until the new system produces consistent, verified output. Go-live support is on-site for Karnataka hospitals (from our nearest office) and remote with scheduled on-site visits for hospitals in other states or the Gulf. Post-go-live: 90-day intensive support with dedicated response channel, then transition to standard SLA (4-hour critical, 24-hour normal).
Two compliance frameworks define what hospital software in India must do in 2026. They serve different purposes, and both are increasingly difficult to ignore. For Gulf hospitals, equivalent frameworks (DHA NABIDH in Dubai, JAWDA in Abu Dhabi) carry similar requirements with region-specific data sovereignty rules.
ABDM is the government's framework for digital health records interoperability across India. For hospital software, this means: ABHA (Ayushman Bharat Health Account) ID creation and verification at registration, Health Information Provider (HIP) registration so your hospital can share records on the ABDM network, Health Information User (HIU) capability to retrieve patient records from other facilities, HL7 FHIR R4 format for all health record exchange, digital consent management before any record sharing, and NHCX (National Health Claims Exchange) for insurance claim submission. Our platform implements all six components. Every patient record created in our system is ABDM-export-ready from day one.
NABH accreditation is voluntary but increasingly required for insurance empanelment, government scheme participation, and medical tourism credibility (particularly for hospitals attracting Gulf and international patients). Our quality management module covers all NABH chapters: KPI tracking with automated indicator calculation, incident reporting with root cause analysis, CAPA (Corrective and Preventive Action) management with closure tracking, accreditation document repository with version control, and indicator reports formatted for NABH assessors. The software provides the compliance infrastructure. Clinical governance practices determine whether accreditation is achieved.
We provide fixed-price proposals after the discovery phase, not estimates that change during development. No scope creep billing. These are indicative ranges based on our deployed projects:
| Scope | Typical Range | Timeline |
|---|---|---|
| Core HMS (Registration, OPD, IPD, Pharmacy, Billing, Lab, Radiology) | Rs.12 to 25 lakh | 6 to 9 months |
| Full 120-module ERP (Clinical + Admin + Finance + AI) | Rs.35 to 70 lakh | 12 to 18 months |
| Clinic management software (single practice) | Rs.4 to 8 lakh | 2 to 4 months |
| Nursing agency platform | Rs.6 to 12 lakh | 3 to 5 months |
| Individual module addition to existing system | Rs.1.5 to 5 lakh per module | 4 to 8 weeks |
These ranges cover discovery, design, development, testing, deployment, training, and 90-day post-launch support. Hosting (AWS Mumbai or Azure India West recommended for Indian hospitals; AWS Bahrain or Azure UAE North for Gulf deployments) and annual maintenance are separate. We also support on-premise deployment for hospitals with data sovereignty requirements.
India has an estimated 70,000+ hospitals ranging from 5-bed nursing homes to 5,000-bed teaching institutions. The hospital software market is dominated by subscription-based products designed for the middle segment (50 to 200 beds, standard workflows). Below and above that range, the fit breaks down. The smallest hospitals need simpler, cheaper systems. The largest need deeply customised platforms that match their specific clinical, administrative, and regulatory workflows. That gap is where custom development adds the most value.
Regional differences compound the problem. A hospital in Karnataka processes claims under PMJAY, CGHS, ECHS, Arogya Karnataka, and Yeshasvini. A hospital in Tamil Nadu handles CMCHIS alongside the national schemes. A hospital in Kerala runs KASP. A hospital in Dubai operates under DHA licensing with a completely different insurance ecosystem. No single packaged product handles all of these natively. Custom software adapts to whatever combination of schemes, languages, and regulatory frameworks the hospital actually operates under.
Multilingual patient communication is a production requirement across India, not a premium feature. Hospitals serve patients in Hindi, English, Kannada, Tamil, Telugu, Malayalam, Marathi, Bengali, and dozens of other languages depending on location. Registration forms, discharge summaries, consent documents, and patient-facing communications need multilingual output. Gulf hospitals require Arabic-English bilingual capability. Most packaged HMS products support English and Hindi. Custom development supports whatever languages the hospital's patient population actually speaks.
Medical education integration adds another layer for teaching hospitals. India has 700+ medical colleges with affiliated teaching hospitals. Teaching hospital software needs student training records, research data exports, case mix indexing, and NMC audit readiness. These requirements are absent from community hospital products and cannot be bolted on after deployment.
The nursing staffing sector is another gap. India's home nursing and hospital staffing industry runs almost entirely on WhatsApp groups and Excel spreadsheets. Coastal Karnataka (Dakshina Kannada and Udupi districts) produces a disproportionate share of India's trained nurses, creating a staffing industry with zero dedicated software support from any Indian vendor. Our nursing agency software was built specifically for this gap and now serves agencies operating across multiple Indian states.
20 years in business. CIN: U72100KA2009PTC048911. Offices: Bengaluru (Rajajinagar), Mangaluru (Kankanady), Mysuru (Kuvempu Nagara). The 120-module hospital ERP referenced on this page was built by our in-house development team and deployed June 2026. Deployments running across India and the Gulf. This page is compliant with the March 2026 Spam Update (completed March 25, 2026), December 2025 Core Update, and August 2025 Spam Update. Contact: +91 99023 30233 · Contact form · Author profile · LinkedIn.
Core HMS for 50 to 100 beds costs Rs.12 to 25 lakh, delivered in 6 to 9 months. Full 120-module hospital ERP with AI and ABDM integration costs Rs.35 to 70 lakh, 12 to 18 months. These are fixed-price proposals issued after a clinical workflow discovery phase, not estimates subject to change.
HMS covers core clinical workflows: registration, OPD, IPD, pharmacy, lab, radiology, billing, and discharge. Hospital ERP extends into administrative and financial operations: HR, payroll, procurement, inventory, asset management, quality management, MIS reporting, and AI-based clinical decision support. A 50-bed hospital typically needs HMS. A 200-bed multi-speciality hospital needs ERP.
Yes. Our platform implements ABHA ID creation and linking, HIP/HIU registration on the ABDM network, HL7 FHIR R4 health record export, digital consent management, and NHCX insurance claims. Every patient record is ABDM-interoperable from the moment it is created.
Yes. Lab analyser integration uses HL7 2.x messaging protocols. PACS integration includes DICOM Modality Worklist and DICOM viewer. We also integrate with accounting systems (Tally, Zoho Books, SAP) and government portals (ABDM, PMJAY). Integration feasibility and cost are assessed during the discovery phase.
Ownership model. They sell subscriptions to software they own. We build software you own. Their product is one-size-fits-many. Ours is built for your specific clinical workflows. Their monthly fees accumulate to Rs.9 to 48 lakh over five years with zero code ownership. Our one-time cost delivers permanent ownership with full source code.
Yes. Our development team is based in Bangalore with offices in Mangaluru and Mysuru. We deploy hospital software across India (Tamil Nadu, Kerala, Telangana, Maharashtra, and other states) and internationally in the Gulf region (UAE, Saudi Arabia, Oman). Remote deployment with scheduled on-site visits for hospitals outside Karnataka.
Our quality management module is built to NABH Hospital Accreditation Standards (5th Edition). It covers KPI tracking across all NABH chapters, incident reporting with root cause analysis, CAPA management, accreditation document repository, and indicator reports formatted for NABH assessors.
Both options are available. Cloud deployment on AWS Mumbai or Azure India West is recommended for Indian hospitals. AWS Bahrain or Azure UAE North for Gulf deployments. On-premise deployment is available for hospitals with data sovereignty requirements. You are not locked into any hosting provider.
Training is included in the project scope. Department-wise training sessions for clinical and administrative staff, plus train-the-trainer programmes for internal IT teams. Post-launch: 90-day intensive support with dedicated response channel, then standard SLA (4-hour critical issue response, 24-hour normal response). Remote support available for all locations.
Tell us about your hospital: bed count, departments, current systems, and what is not working. Complimentary workflow assessment and fixed-price proposal within 5 business days. We serve hospitals across India and the Gulf.
Request Free Assessment Call +91 99023 30233 Bengaluru: No. 1869, 2nd Floor, 1st Main Rd, Rajajinagar 560010 | Mangaluru: 1st Floor, Mohtisham, Emporium Complex, Kankanady 575002 | Mysuru: Kantharaj Urs Road, Kuvempu Nagara 570023