From Greenfield to Fully Operational Hospital & Campus
A medical college cannot open without approval. The infrastructure had to be built, audited and licensed in twelve months — from empty land.
Industry: Healthcare & Medical Education
Customer Context
A trust with a plan to build a medical college and multi-speciality teaching hospital from empty land.
Danush already knew them. For years before this project began, we had supported their existing operations on routine IT — modest work, delivered consistently. When the campus project started, they did not run a procurement exercise. They asked the partner they already trusted to build the technology foundation for the entire institution.
Business Challenge
A medical college cannot simply open its doors. It must be inspected and licensed by the statutory medical education regulator, and infrastructure forms part of what is examined — evidence that the institution can teach, treat and maintain records to the required standard.
That placed IT directly on the critical path. If the network, data centre, security and systems integration were not built and demonstrable when inspectors arrived, no licence would be issued. No licence meant no admissions, no revenue, and a completed campus standing empty.
There was no existing infrastructure to extend, no incumbent IT team to inherit, and nothing to work from except architectural drawings and a fixed deadline.
Why It Mattered
The trust had committed capital to land, buildings, medical equipment and faculty on the expectation of opening on schedule. Everything downstream depended on clearing regulatory approval — student admissions, hospital operations, accreditation, and the institution’s reputation at launch.
A delay would not have been an IT problem. It would have been a business failure visible to the entire market.
Danush’s Role
Danush was engaged at design stage, not installation stage — working alongside the architects and the Project Management Consultant while the campus still existed only on paper.
Board-level advisory. Technology strategy and decisions taken directly with the trust’s leadership through formal presentations.
Multi-agency coordination. Operation theatre systems, telecom, internet service providers, UPS and power, Hospital Information Management System, Learning Management System — each a separate vendor with its own dependencies, all requiring a single technical authority to hold the design together.
Regulatory readiness. Dedicated resources deployed exclusively to work through the medical audit and approval process, ensuring the infrastructure evidence required for licensing was prepared, documented and defensible.
Design, build, run, handover. Ownership across the full lifecycle, not delivery of a component.
Solution
Network and connectivity
- Campus and hospital LAN
- Campus-wide WAN
- Enterprise WiFi across academic and clinical areas
Data centre
- Ground-up data centre build
- High availability architecture
- Virtualisation
Security
- Enterprise firewall and network security
- Access management
- Campus surveillance
Integration
- Medical device integration
- Laboratory systems integration
- HIMS and LMS integration
Governance
- Standard operating procedures
- IT policies and governance framework
- Regulatory documentation for medical college licensing
Execution Capability
Twelve months from design to operational handover — for a campus with no prior infrastructure, delivered against a regulatory deadline that could not move.
Third-party audit passed. The infrastructure was independently verified, not self-certified.
25-year performance warranty on the network. A commitment made at build time, on the assumption the institution would still be running on this foundation decades later.
Exclusive resourcing. Team members were assigned solely to navigating the approval process — recognising that regulatory clearance was the actual deliverable, not the cabling.
Business Outcome
- Medical college licence granted — infrastructure met regulatory requirements at inspection
- Campus fully operational within twelve months from a greenfield site
- Third-party audit cleared, independently validating the build
- 25-year network performance warranty in place
- Fully integrated environment across clinical, academic and administrative systems
- A single accountable technology partner across architects, PMC and seven-plus specialist agencies
- Governance, SOPs and policies established from day one rather than retrofitted
- The relationship continues — Danush designed it, built it, ran it, and remains the partner today
Why This Matters to a Similar Prospect
Most IT partners are brought in once the building exists. This one was in the room with the architects.
If you are building something new — a campus, a plant, a facility that must clear inspection before it can open — the technology decisions taken at design stage determine whether you open on time. Get them wrong and no amount of remedial work recovers the schedule.
What made this work was not the network design. It was one partner holding technical authority across every agency involved, and understanding that the deliverable was not infrastructure. It was approval.