IT support built around healthcare in Kolkata
Kolkata has a strong private healthcare sector, much of it along the EM Bypass corridor and in the older central districts, and it draws patients from across eastern India and neighbouring countries. That regional catchment matters technically: patient volumes are high relative to the size of the estates, and records systems carry more history than the buildings suggest. The recurring finding is a hospital or diagnostic chain running software that has been in place for a decade, where the vendor is still supporting it but nobody has documented the environment around it. Our first deliverable is usually that documentation, because changing an undocumented clinical system is how outages happen. Then the ordinary work: segmentation, backup that includes the image archive, named accounts instead of shared reception logins, all of it delivered remotely.
- 30 min
- Managed response SLA
- 24/7
- Monitoring and cover
- Remote-first
- Plus scheduled visits to Kolkata
- Microsoft
- Partner-led 365 and security
healthcare in Kolkata, and where it sits
Kolkata splits cleanly between its newer technology districts and its historic commercial core. Salt Lake Sector V and New Town carry the IT and ITES campuses; BBD Bagh and Dalhousie hold government offices, banks and long-established trading houses; Park Street and Camac Street carry corporate and professional offices; and the EM Bypass corridor has drawn healthcare and newer commercial development.
Kolkata businesses skew older and more established than in the newer metros, particularly around BBD Bagh and the trading houses, which means IT estates frequently carry a decade or more of accumulated decisions nobody currently employed made. The first job is usually documentation rather than improvement, because you cannot safely change what has never been mapped.
What we find going wrong
Every sector has a failure profile. For healthcare it looks like this, and it is what an engagement is scoped to address.
- Shared reception logins, so the audit trail cannot attribute a record access to a person
- Clinical machines left on unsupported operating systems because the vendor certified only that version
- Ransomware reaching clinical systems because the practice network was never segmented from guest Wi-Fi
- Imaging storage filling silently until studies fail to write, usually discovered mid-clinic
What constrains the work
These decide what can be changed and when. They are not obstacles to work around, they are the shape of the engagement.
Availability during consulting hours. A registration desk that cannot bill or a PACS that will not load an image stops clinical throughput immediately. Downtime here is measured in patients turned away.
Digital Personal Data Protection Act, 2023. Patient records are sensitive personal data. The Act requires purpose limitation, security safeguards and breach notification, which in practice means encryption, real access control and an audit trail rather than a shared login at reception.
What an engagement here involves
A Kolkata healthcare engagement starts with documentation rather than change, because these estates carry more history than the building suggests and the software has frequently been in place for a decade. Changing an undocumented clinical system is how outages happen, so we map first. After that the work is conventional and overdue: segmenting clinical systems from everything else, getting the image archive into backup rather than just the billing database, and replacing shared reception logins with named accounts. Patient volumes here are high relative to estate size, which means maintenance windows are genuinely narrow and have to be agreed against the clinic calendar.
The obvious question is what actually changes when the provider is in another city. For healthcare the honest answer depends on which part of the estate you mean, so here it is by category.
Imaging storage filling silently until studies fail to write, usually discovered mid-clinic. That is diagnosed and fixed remotely, and monitoring catches it rather than a user reporting it. Across Kolkata we see it often enough in healthcare that it is part of the standard onboarding audit rather than something we wait to be told about.
Backups configured for the billing database but never for the image archive, which is the larger and harder half. That is remote work: configuration, policy and monitoring, with nothing gained by being in the room. Across Kolkata we see it often enough in healthcare that it is part of the standard onboarding audit rather than something we wait to be told about.
Shared reception logins, so the audit trail cannot attribute a record access to a person. That one needs an engineer in the building, so it goes into a scheduled visit rather than waiting for a call-out. Across Kolkata we see it often enough in healthcare that it is part of the standard onboarding audit rather than something we wait to be told about.
Where healthcare sits in Kolkata
We work across Kolkata, and for hospitals, clinics and diagnostic centres the concentration is usually around Salt Lake Sector V, New Town and Rajarhat, Park Street and the EM Bypass corridor.
Because delivery is remote-first, the district matters less for support and more for the physical work: who controls the building services, what can be installed, and how much notice access requires.
How delivery to Kolkata actually works
Kolkata is served remote-first from Hyderabad. Support, monitoring and administration are delivered remotely, with engineers travelling for scheduled projects and reviews. That model suits the market: local providers are plentiful for break-fix, and what Kolkata businesses more often lack is depth in Microsoft 365, security and compliance.
In practice that means the majority of work, monitoring, patching, Microsoft 365 administration, security operations and helpdesk, happens remotely and continuously, and an engineer travels when the work genuinely needs hands in the building.
Managed clients have a 30-minute response target for critical issues. For a first enquiry, we reply within 4 business hours.
When we can touch your systems
Work happens between clinics or after the last appointment, agreed against your schedule in advance. Anything touching a clinical system carries a tested rollback before we begin.
Scheduling is agreed with you rather than assumed, and anything disruptive is planned into a window you have approved.
IT for healthcare in Kolkata, answered
Across Kolkata
More of what we do in Kolkata
- Manufacturing in Kolkata
- Pharmaceutical and life sciences in Kolkata
- Banking and financial services in Kolkata
- Education and training in Kolkata
- Retail and trading in Kolkata
- Logistics and warehousing in Kolkata
- Real estate and construction in Kolkata
- Legal and professional services in Kolkata
- Hotels and hospitality in Kolkata
- Startups and scale-ups in Kolkata
- Global capability centres in Kolkata
- Healthcare IT in Hyderabad
Get a fixed-scope quote for healthcare in Kolkata
Tell us what you run and how you operate, and we will come back within 4 business hours. Managed clients get a 30-minute response SLA.