In late 2003, when the idea of a Hospital Information System (HIS) first landed in Sevagram, it did not arrive with the fanfare of a revolution. It arrived as a stack of official letters, a collection of unfamiliar names, and a promise that sounded dangerously ambitious for our setting. At the time, MGIMS was a rural teaching hospital fueled by paper, collective memory, and raw human stamina. Our wards were perennially full, the OPDs overflowed with the desperate, and every department was its own sovereign state with its own secret language. Files moved between counters like tired, fraying messengers; lab reports traveled in envelopes like clandestine notes; and billing depended on slips of paper that could vanish into a pocket as easily as a forgotten coin. We weren\u2019t dreaming of “digital transformation.” We were simply trying to survive the daily load without losing our minds.<\/p>\n\n\n\n
The Center for Development of Advanced Computing (C-DAC) was the chosen architect. They had built systems for SGPGI Lucknow and stumbled through mixed results in Delhi, but the government decided that Sevagram would be the testing ground for their next great effort. The project was titled, with bureaucratic grandiosity, \u201cDesign and Development of Advanced Hospital Management System and Prototype Implementation for MGIMS.\u201d<\/em> That word\u2014prototype<\/em>\u2014was the most honest thing about the document. It meant we were to be the place where the system would learn to walk, likely by falling on its face several times first.<\/p>\n\n\n\n On 30 December 2003, Mr. R.K. Verma of C-DAC Noida identified the men who would lead us into this new era: Naveen Kumar Jain, Pradip Parida, and Praveen Srivastava. By February 2004, the Ministry formally tasked them with the implementation. The budget was \u20b9100 lakhs\u2014a king\u2019s ransom in 2004\u2014and the timeline was a optimistic twelve months. In reality, the project ignored “file time” and ran on “human time.” It would take four years, eventually reaching completion in June 2008.<\/p>\n\n\n\n ***<\/strong><\/p>\n\n\n On a PowerPoint slide, the C-DAC plan was a masterpiece of order. Phase 1 would build the clinical spine\u2014the very skeleton of the hospital. Phase 2 would handle the unglamorous machinery of laundry and security. Phase 3 was pure science fiction: digital radiology.<\/p>\n\n\n\n But in a hospital corridor, this neatness looked like impending chaos. Our staff hadn’t grown up with computers; many were nervous even touching a mouse. We didn\u2019t have a culture of “data entry”; we had a culture of “somehow manage.”<\/p>\n\n\n\n Then came the first heavy blow: the initial project manager left before the requirements were even gathered. It was the editorial equivalent of losing your star opening batsman for a duck. All the time spent by staff explaining registers and walking engineers through wards was evaporated. The document\u2014the very DNA of our workflow\u2014was lost. When the new team arrived, the energy had soured. People were polite, but the enthusiasm had been replaced by a quiet, cynical wait for the inevitable failure.<\/p>\n\n\n\n This is where Praveen Srivastava saved us. He stepped in as project manager with the calm of a mathematician who knew that progress rarely moves in a straight line. He didn’t offer speeches; he offered structure. He regrouped the team and began the grueling work of collecting requirements all over again. None of us knew then that this struggle would birth e-Sushrut<\/em>, a system now used across India. We were only thinking about how to survive the next morning\u2019s OPD.<\/p>\n\n\n\n ***<\/strong><\/p>\n\n\n A system is built by code, but it is implemented by people who take abuse with a smile. Sevagram became a colony for a steady stream of C-DAC engineers\u2014men like Rajeev Yadav, Ajay Gupta, Devendra Rao, and Ravi Sinha\u2014who sweated through our summers and learned our hospital\u2019s dialect.<\/p>\n\n\n\n There were the “House Officers” of the server room: Ashish Singh, Mantosh Kumar, and Amit Kumar Digaliya. Each left a mark. Ravikumar built the insurance module in a cramped pharmacy room; Ajay Gupta mastered the stores. Amit Kumar, however, became family. He was taken into local homes, tasted Maharashtrian meals with the curiosity of a student, and spent his weekends exploring Bordharan. These small human connections were the “grease” that allowed the digital gears to turn.<\/p>\n\n\n\n I remember Holi in 2005. Two young female engineers were warned to stay inside. They didn\u2019t listen. Sevagram Square on Holi does not deal in pastels; it deals in total immersion. They were drenched and startled, finding themselves in a crowd that meant no harm but looked like a riot. Our staff member Hemant had to rush out and rescue them, a small act of chivalry that reminded us that while technology is modern, implementation still rests on old-fashioned human decency.<\/p>\n\n\n\n ***<\/strong><\/p>\n\n\n In August 2004, I left for Berkeley for my MPH. I handed the HIS reins to Dr. Rajnish Joshi. He was thirty, a young lecturer in Medicine with a temperament for complexity. My brief to him was brutal: Get HIS on the desktops by August 2005.<\/em> Rajnish built a team of quiet revolutionaries. First was Bhavana, who had already been secretly writing FoxPro programs for discharge summaries in the Medicine department. Her work was “emotional labour”\u2014maintaining her composure while training staff who were terrified of the screen, all while managing a young family.<\/p>\n\n\n\n Then there was Yogesh Khond. Every great project has a hero who doesn’t appear in the official letterhead. Yogesh had endured more than his share of life’s cruelty\u2014losing his father to cancer, dropping out of his BSc to survive\u2014but he had a stubborn, innate love for machines. He became the “man who could fix anything.” When the system broke\u2014which was nearly every hour\u2014Yogesh was the one who answered the call. He wasn’t trained as an IT professional; he became one by necessity, learning faster than the system could fail.<\/p>\n\n\n\n ***<\/strong><\/p>\n\n\n The physical spine of the system was miles of cable. In 2004, networking felt like surgery on the earth itself. Digging up the campus roads to lay fiber optics was a bureaucratic nightmare, so the contractor did it “village heist” style\u2014quietly, overnight, while the campus slept. By dawn, the roads looked innocent again, but the cables beneath them were already carrying the future.<\/p>\n\n\n\n Training was a comedy of errors. Nearly 300 staff members were dragged to the computers. Some came with the fear of a child in a dark room; others came with a quiet, fierce pride.<\/p>\n\n\n\n But the “insurance module” launch in late 2004 nearly broke us. It went live under immense pressure, and it was a disaster. Mismatched cash, duplicate cards, and a discrepancy of \u20b92 lakhs. Worst of all, the source code was accidentally overwritten on a PC. It sounds farcical now, but we were learning the hard way that computerization doesn’t create discipline; it only shines a light on the lack of it.<\/p>\n\n\n\n ***<\/strong><\/p>\n\n\n By 2005, the Oracle servers had arrived, but they struggled. A busy teaching hospital is not a demo unit; it is a high-traffic monster. Transactions crawled. On 11 August 2006, I wrote to C-DAC with a line that came from the soul: \u201cWe look forward to a server that would run, not crawl.\u201d<\/em> It took years of upgrades\u2014more RAM, better processors, and the move to Tomcat in 2012\u2014to find stability. The HIS survived not because it was perfect, but because we were too stubborn to let it die.<\/p>\n\n\n\n When people ask me for the “hero” of the Sevagram HIS, I don’t give them a single name. I tell them about the engineers who took the heat, the clerks who overcame their fear, and the cables laid under the cover of darkness. It wasn’t a visionary moment; it was a thousand small persistences. The first time a patient\u2019s name appeared on a screen without a frantic search for a paper file, I didn’t feel pride. I felt relief\u2014the kind you feel when a long-standing headache finally eases. We didn’t become digital because we were advanced; we became digital because we were willing to learn, one mistake at a time.<\/p>\n","protected":false},"excerpt":{"rendered":"The PowerPoint and the Pavilion<\/strong><\/h2>\n\n\n
The Engineers in the Village<\/strong><\/h2>\n\n\n
The Quiet Heroes: Rajnish, Bhavana, and Yogesh<\/strong><\/h2>\n\n\n
The Midnight Heist<\/strong><\/h2>\n\n\n
The Server That Crawled<\/strong><\/h2>\n\n\n