News

The Fire Chief Watched Her Work and Asked, “Where Exactly Did You Train?”

PART 2

The young woman was twenty-three.

Name:

Kayla Jenkins.

Passenger.

Eight months pregnant.

No major visible injury.

She had been walking after the crash.

Now pale.

Dizzy.

Complaining of abdominal tightness.

Ruth stopped before touching her.

An EMT already there.

Good.

“What happened?”

EMT said:

“Possible pregnancy complication.”

Kayla whispered:

“My baby’s moving.”

Good.

Not definitive.

Ruth noticed something.

Seatbelt mark.

Low across abdomen.

Tenderness.

But again, Ruth was not an obstetric trauma specialist.

She did not pretend.

She told the EMT:

“She needs obstetric-capable trauma evaluation.”

Already planned.

No revelation.

No miracle.

Then Kayla asked:

“Can I lie flat?”

Ruth said:

“Let EMS position you.”

Why?

Late pregnancy, trauma, circulation concerns.

But the roadside was not the place for improvised care outside team coordination.

Ruth stepped back.

That became the pattern.

She noticed.

Communicated.

Did not take over.

By midnight:

four ambulances.

Fire department.

Highway patrol.

Bus passengers triaged.

Most minor.

Three transported urgently.

Mr. Harris.

Kayla.

Pickup driver with significant chest pain after impact.

Ruth helped only where asked.

Names.

Medications.

Medical histories.

Keeping patients seated.

Finding luggage containing prescription bottles.

Telling one volunteer:

“Please don’t give him water until EMS clears it.”

Small things.

Then paramedic supervisor Jake Morrison approached.

“You the dialysis nurse?”

“That sounds accusatory.”

He smiled.

“Mr. Harris is moving.”

“Good.”

“We treated presumed severe hyperkalemic conduction changes. Rhythm narrowed.”

“Good.”

“Hospital’s ready.”

Ruth nodded.

Jake continued:

“His sister says you saved him.”

“No.”

“You caught the dialysis history.”

“The bracelet caught it.”

“You read it.”

Ruth looked at him.

“That’s what it’s for.”

Jake laughed.

Fair.

But the night produced another question.

Why had Mr. Harris boarded a three-hour bus trip after missing scheduled dialysis?

His sister explained.

Treatment had not simply been skipped casually.

His dialysis clinic canceled his Friday session because of a water-system problem.

They tried transferring patients to another center.

Mr. Harris was told someone would call with an alternate appointment.

No one called before the family left.

He felt fine.

He planned to dialyze Saturday at a center near the wedding.

Reasonable?

Risky.

But not absurd.

Ruth asked:

“Did he have confirmed appointment?”

“No.”

That bothered her.

Not because of the crash.

Because dialysis care transitions were fragile.

Patients depended on scheduling systems most people never saw.

One missed communication could become a medical event hours later.

At 1:20 a.m., Ruth finally returned to her car.

Coffee frozen.

She threw it away.

Drove home.

Slept three hours.

Then woke thinking about Mr. Harris.

Not heroic.

Annoyed.

Something about the sequence bothered her.

Clinic canceled.

Alternate treatment promised.

No confirmation.

Patient traveled.

Then collapse.

She told herself:

Not your patient.

Not your clinic.

Let it go.

At 9:15, her phone rang.

Unknown number.

She answered.

“Ruth Caldwell?”

“Yes.”

“This is Jake Morrison from county EMS.”

She sat up.

“Mr. Harris?”

“Stable.”

Good.

“Potassium was 7.2.”

High.

Dangerous.

Hospital treated, then emergency dialysis.

He was awake.

Talking.

No major crash injury.

Ruth exhaled.

Jake continued:

“He wants to thank you.”

“No.”

“Apparently that’s your favorite word.”

“He should thank the paramedics.”

“He is.”

“And emergency department.”

“He is.”

“And dialysis team.”

“Ruth.”

She stopped.

“Fine.”

Jake laughed.

Then his tone changed.

“There’s another reason I called.”

“What?”

“The hospital asked whether you knew anything about the canceled dialysis session.”

“No.”

“His sister told them the clinic’s water problem affected multiple patients.”

That got Ruth’s attention.

“How many?”

“Don’t know.”

“Were all rescheduled?”

“Don’t know.”

There.

A system question.

Much more dangerous than a dramatic roadside one.

PART 3

Ruth worked for Meridian Dialysis Network.

Different company from Mr. Harris’s clinic.

Still, dialysis was a small professional world.

Water-system failures were serious.

Dialysis used enormous amounts of specially treated water.

If a clinic could not ensure water quality, treatments might need to stop or relocate.

That was appropriate.

The question was:

what happened afterward?

Mr. Harris’s center belonged to RiverPoint Renal Care.

Ruth did not call pretending to investigate.

She had no authority.

Instead, Mr. Harris—now awake—asked the hospital social worker to help review his missed treatment and future scheduling.

His sister also filed a complaint.

That triggered RiverPoint’s own quality process.

Two weeks later Ruth received another call.

This time from Mr. Harris himself.

“Ms. Caldwell?”

“Ruth.”

“Then I’m Walter.”

Good.

He thanked her.

She accepted.

Then Walter said:

“They told me I was marked as transferred.”

Ruth frowned.

“What does that mean?”

“Apparently their computer said I had a Saturday appointment at another clinic.”

“Did you?”

“No.”

“Why did it say you did?”

“That’s what they’re checking.”

Now Ruth was interested.

Not personally involved.

Interested.

RiverPoint discovered Friday’s water-system problem at one location forced cancellation of thirty-eight treatments.

Staff attempted to redistribute patients among four nearby centers.

Most successfully.

But the scheduling software had a workflow flaw.

A coordinator could select:

TRANSFER REQUESTED.

Then another center could mark:

RECEIVED.

System dashboard converted that to:

TRANSFER COMPLETE.

But “received” meant:

request received.

Not:

patient appointment accepted.

For Walter:

home clinic sent request.

Receiving clinic opened request.

System displayed:

COMPLETE.

Nobody actually assigned a chair time.

Home clinic assumed transferred.

Receiving clinic assumed waiting for home clinic to confirm.

Walter’s name disappeared from the unresolved list.

The system had not lost him.

Worse.

It had falsely told everyone he was finished.

Ruth heard this later through Walter, then through a regional dialysis safety meeting where the case was discussed anonymously.

The screen used one word:

COMPLETE.

But the process contained at least three different states:

REQUEST SENT.

REQUEST ACKNOWLEDGED.

TREATMENT SCHEDULED.

Only the third mattered to the patient.

Yet the dashboard collapsed all three into something that looked final.

Ruth nearly laughed when she saw the slide.

Not because it was funny.

Because healthcare loved words that pretended uncertainty did not exist.

“Complete.”

“Cleared.”

“Stable.”

“Reviewed.”

“Discharged.”

Every word required:

complete what?

Cleared for what?

Stable compared with when?

Reviewed by whom?

Discharged with which plan?

RiverPoint changed workflow.

No transfer marked complete without:

receiving clinic,

date,

chair time,

patient notified,

transportation needs assessed when applicable.

Canceled treatments remained on exception dashboard until actual treatment occurred or medical director documented alternate plan.

No disappearing because somebody clicked acknowledgment.

Ruth’s own company reviewed its process too.

They found something embarrassing.

Their software used almost the same terminology.

Not identical.

Same vulnerability.

Ruth attended a staff meeting.

Regional manager said:

“This was another company’s incident.”

Ruth raised her hand.

“Same workflow problem.”

“We haven’t had an event.”

“That we know of.”

Silence.

Manager looked at her.

“What do you recommend?”

Ruth said:

“Search recent canceled treatments.”

“Look for patients marked transferred.”

“Confirm actual completed sessions.”

They did.

Six-month review.

Most correct.

Three documentation discrepancies.

One patient had treatment six hours later than recorded.

No harm.

One transferred appointment changed locations without updated transportation note.

Family solved it themselves.

One patient had skipped treatment entirely but was marked “rescheduled” because scheduler entered proposed date before patient declined.

No hospitalization.

But the record implied care happened when it had not.

The company changed system wording.

Not because Ruth was extraordinary.

Because another organization’s near miss showed where to look.

Disclaimer: This story is fictional and created for entertainment purposes only. Any names, characters, places, or events are fictitious or used fictitiously. No real person or organization is intended to be portrayed.

You Might Also Enjoy