After Her Surgeon Son-in-Law Assaulted Her Daughter, Causing Premature Birth, A Retired Archivist Uncovered His Twisted Medical Cover-Up
Armed with Dr. Petrova’s timestamp, my next step was clear: delve deeper into the hospital’s digital archives. I knew the labyrinthine corridors of medical records better than anyone, or so I thought. I headed back to the Medical Records Department, a place that had been my domain for decades.
The department itself felt foreign, cleaner, quieter, filled with unfamiliar faces glued to glowing screens. My old office was now occupied by a young woman with a stern expression and a headset. It was a cold, hard dose of reality, a painful reminder of how much had changed since my retirement.
“Evelyn Reed,” I introduced myself to a fresh-faced supervisor named Ms. Jenkins, who looked barely old enough to vote. “I used to run this department.”
Her smile was polite but distant.
“Ah, yes. We have your file in the archives. A legend.” She said it with a hint of irony, as if referring to a historical figure.
I tried to use my old connections, mentioning names of colleagues who had been like family. “Is Janet still handling CPT coding audits? Or Mark in system integrity?”
Ms. Jenkins frowned slightly.
“Janet retired two years ago. Mark moved to corporate IT. We’ve had a lot of restructuring,” she explained, her voice devoid of emotion. “Everything’s centralized now. Different protocols.”
I felt a pang of frustration. My network, once so vital, was slowly unraveling.
I pressed on, explaining the CPT code discrepancy for Amelia and the 2:17 AM timestamp from Dr. Petrova. I expected at least a flicker of recognition, a familiar understanding of the gravity of such an alteration. Instead, Ms. Jenkins looked at me with polite bewilderment.
“All coding changes are logged and approved,” she recited, as if reading from a manual. “If there was an override, it would be documented. Our system is robust.”
I could almost hear Arthur’s influence in her robotic assurances. The new protocols, the centralized system—it was all designed to obscure, not illuminate. This was his turf now, secured and defended by layers of bureaucracy.
“I need to see the audit trail for that specific code change,” I insisted, “and cross-reference it with system access logs for Amelia’s records around 2:17 AM on the night of the incident.”
She tapped her keyboard, her eyes scanning her screen.
“I see the CPT code was updated on that date,” she confirmed, “but the system shows it as a standard, authorized revision by Dr. Finch. No flags.”
“And the access log for the terminal on Amelia’s floor at 2:17 AM?” I pressed, my voice unwavering.
She typed again, then paused. Her brow furrowed, a genuine crack in her professional facade.
“That’s… odd,” she murmured, more to herself than to me. “The system reports a brief, localized network anomaly in that wing around that time. It might have affected logging capabilities.”
“An anomaly?” I repeated, seizing on the word. “What kind of anomaly?”
She shrugged, a gesture of helplessness.
“It just says ‘temporary data integrity issue.’ It wouldn’t show who accessed what, or what changes were made, if the log itself was corrupted for that brief window.”
This was a classic gaslighting technique: blame the system, the invisible machine. It made me doubt my own deep knowledge of how such systems usually worked. True data integrity issues were rare, usually flagged instantly, and easily traceable. This felt too convenient, too specific to Arthur.
“So you’re saying there’s no way to tell who was on that terminal, or what they did?” I asked, my voice edged with disbelief.
“Not from our department’s access,” she replied, shaking her head. “You’d need to go to IT for anything related to network anomalies or system-level logs. They handle all ‘data integrity issues’ now.”
She handed me a printed slip of paper with a generic IT department number, a clear dismissal. It was a brick wall, built with the very foundations of the system I once helped to create. The old network of favors and shared knowledge was gone, replaced by a rigid, unfeeling hierarchy.
I left the department feeling a profound sense of isolation. My expertise, once my greatest strength, felt useless against this new, opaque system. Arthur had not just manipulated records; he had exploited the changes in the hospital’s infrastructure, hiding in plain sight behind bureaucratic language and digital firewalls. The ghost in the machine was very real, and it was protecting him.
I walked the familiar hallways, feeling like a stranger in my own former home. The fluorescent lights hummed, indifferent to my growing despair. I glanced at the IT department number on the slip of paper, a new battleground emerging. Arthur had insulated himself well, but I knew his weaknesses. His arrogance would make him overlook small details, just like this timestamp. My job was to find those details, to make the ghost visible.
This wasn’t just about finding the truth; it was about proving it to a system that seemed intent on denying it at every turn. Ms. Jenkins’s bland, almost rehearsed answers had left a bitter taste in my mouth. She was either genuinely ignorant or, more likely, too intimidated to look closely. That was Arthur’s power, his ability to silence through influence, to make people look away. I wouldn’t.
More Stories
+ There are no comments
Add yours