By 2007, the Hospital Information System had graduated from a fragile experiment into a stubborn reality. It had survived the sceptics, the slow servers, and the endless, exhausting phone calls that accompany any attempt to drag a traditional institution into the digital age. It was still imperfect—temperamental on bad days and sluggish on others—but it had achieved the most important quality of all: inevitability. People no longer asked, “Why are we doing this?” They merely asked, “Why is it not working faster?”
Then came the news that made the entire campus sit up straight. Dr. A.P.J. Abdul Kalam, the President of India, was coming to Sevagram on June 15, 2007.
For a rural teaching hospital, a presidential visit is not merely an honour; it is a logistical storm warning. The Special Protection Group arrived first, with their walkie-talkies and faces that revealed nothing. Routes were mapped, corridors sterilized, doors sealed, and the forgiving, fluid routine of the institute was suddenly placed in a corset. Every movement was planned; every minute had a price.
In the middle of this tightening grid, I was handed a task that sounded simple but felt terrifying. I had to demonstrate the HIS to the President.
I had five minutes.
***
The 85,000 Rupee Question
Five minutes is a breath. It is nothing when you are trying to explain the nervous system of a hospital to a rocket scientist.
In those days, the HIS was a work in progress. It was registering patients, generating bills, and beginning to knit the laboratories into the wards. It allowed residents to order tests without chasing peons, but on bad days, it would freeze mid-transaction, provoking the specific, helpless rage that only a tired doctor at 2 a.m. can feel. I knew Dr. Kalam would not be seduced by PowerPoint slides or jargon. He was not a politician who smiled politely at buzzwords; he was a man who understood how machines failed. He would want to see if the logic held.
Security decided that the demonstration could not happen in the crowded OPD. Instead, we were banished to the corridor of the Radiotherapy department—a narrow, controllable space. A corridor is an odd place to showcase a digital revolution. A laptop screen was too small for a delegation, and a projector would wash out under the harsh tube lights. We needed something bold.
So, the hospital bought a 36-inch high-resolution colour screen for ₹85,000.
Writing that figure today makes me pause. In 2007, that amount could run a village household for a year. It was the kind of money that made you question your own sanity. But the decision was made instantly, because when the President is coming, hesitation is a luxury you cannot afford.
***
The Invisible Labour
In the days leading up to the visit, my mind ran on two parallel tracks. One was clinical: patients would not stop falling ill just because a VIP convoy was approaching. The other was digital: we had to make the software behave.
I rehearsed my script until I could say it in my sleep. I stripped away the adjectives and the self-congratulation. The HIS was not a trophy to be polished; it was a tool to be used. I wanted to show the journey of a patient—Registration, Insurance, OPD, Lab, Discharge—without a single wasted word.
Mr. S.R. Halbe and Mr. Dhirubhai Mehta watched these preparations with the quiet intensity of men who had gambled on this project. Mr. Halbe, practical as ever, asked the only question that mattered: “What if it crashes?”
It was not a threat. It was the question of a man who respected the law of averages.
“We will keep backups,” I said, sounding more confident than I felt. “And we will pray.” Technology, I had learned, is much like medicine. You can prepare, anticipate, and mitigate, but you can never guarantee the outcome. There is always a small, silent space where fate sits.
What the President would not see, however, was the invisible labour that made the screen light up. For months, our residents—specifically the postgraduate batch of 1998—had served as unwilling test pilots. Residents like Udit Narang and Namita Jajoo did what residents always do: they complained about the extra work, they rolled their eyes at the “green button” that loaded too slowly, and then they did the work anyway. The system survived not because the code was perfect, but because the juniors absorbed the pain of the transition.
***
The Scientist’s Smile
On the evening of June 15, Sevagram felt scrubbed and held its breath. The humidity was heavy, but the usual chaos of the hospital had been hushed.
When Dr. Kalam walked into the corridor, the space suddenly felt smaller. He moved with that famous, springy energy that belied his age, his eyes darting around with genuine curiosity rather than ceremonial boredom. He didn’t look like he was inspecting a guard of honour; he looked like he was about to debug a circuit.
I stood by the expensive screen, my mouth dry. I began.
I walked him through the registration, the unique ID that prevented duplication, the lab orders, the retrieval of reports. I showed him how a system-generated report was valid without a signature because the integrity came from the process, not the ink.
The moment I feared—the spinning hourglass, the frozen screen—never came. The server behaved beautifully. The pages loaded with a snap. The data appeared cleanly.
Dr. Kalam did not just watch; he engaged. He asked questions about the logic and the utility, treating the software not as a magic trick but as a working model. When I finished, he smiled. It was not the practiced smile of a dignitary on a schedule. It was the smile of a teacher who has just seen a student solve a difficult problem.
That smile travelled down the corridor like a quiet blessing. I felt my shoulders loosen for the first time in a week.
***
A Quiet Exhale
After the convoy left and the security detail packed up their radios, the campus exhaled. People began speaking at normal volumes again. The tension dissolved into the familiar, comforting noise of a working hospital.
But for me, the victory wasn’t the successful demo. It was what that success signalled to the people who kept the hospital running. Somewhere that night, a clerk at the registration desk might have felt a little more important. A cynical resident might have felt the system was worth the trouble. And Bhavana, who had poured her life into the code, must have felt that the long nights were not in vain.
In a hospital, the most fragile thing is not a server or a patient’s pulse. It is morale. And that evening, without speeches or slogans, the morale rose.