IndustriesHealthcare Operations

Lab problems get written down in more than one place. Rarely in the same words.

The huddle records what faulted overnight, the bench messages a workaround, the service system closes a ticket, and the morning report shows turnaround over target. AOI connects those records into one operational history for the instrument or workflow involved. This is operations: equipment, workflow, facilities, and handoffs. Not clinical care.

Walk through a core lab example Talk to us

What came before the ticket

Day 1 · 06:45Huddle note

Decapper on the automation line faulted twice overnight. Nights cleared it both times.

Day 1 · 09:30Internal message

Decapper stopping again. Moving chemistry tubes to manual decap to hold turnaround.

What the service system records

Service system · SR-2291

Closed

Core lab · Automation line decapper

Intermittent gripper fault

Opened: Day 1 · 10:10
Closed: Day 1 · 15:40

11 days later

What came after it closed

Day 12 · 07:00Huddle note

Decapper faulting again on nights. Manual decap for most of the shift.

Day 12 · 08:15Daily turnaround · Chemistry

Chemistry turnaround over target between 03:00 and 06:00. Manual decap noted.

“A service record can tell you the instrument was fixed. The huddle notes around it usually tell you what the bench was working around, for how long, and whether the fault came back.”

Where an equipment problem gets recorded

A fault on one module is written down by the people it reached: the bench, the huddle, the service system, the morning report. Each entry is accurate and partial.

Source	Who writes it	What it tends to hold
Operational huddles	Shift and section leads	What faulted overnight, what is down, and what to watch today.
Internal messages	Bench staff and supervisors	The first report, the workaround, and who was told.
Service records	The equipment or service system	The ticket, the instrument, and when it was closed.
Technician and vendor notes	Biomedical and field service	What was adjusted or replaced, and what was left unchecked.
Workflow reports	Lab and department operations	Turnaround against target, backlogs, and manual steps taken.
Facilities requests	Facilities teams	Rooms, power, temperature, and building systems.

Operational huddles: Shift and section leads; What faulted overnight, what is down, and what to watch today.
Internal messages: Bench staff and supervisors; The first report, the workaround, and who was told.
Service records: The equipment or service system; The ticket, the instrument, and when it was closed.
Technician and vendor notes: Biomedical and field service; What was adjusted or replaced, and what was left unchecked.
Workflow reports: Lab and department operations; Turnaround against target, backlogs, and manual steps taken.
Facilities requests: Facilities teams; Rooms, power, temperature, and building systems.

Your lab and service systems stay the systems of record. AOI adds the operational history around them, and stays scoped to operations.

The service record says resolved. The huddle notes say otherwise.

Seven records in five places across twelve days, with ordinary lab traffic in between. Read one at a time, each one looks handled.

Core lab · Automation line decapper

Illustrative example. Synthetic data. No patient information.

Day 1
06:45Huddle note · Core lab01
Decapper on the automation line faulted twice overnight. Nights cleared it both times.
09:30Internal message · Lab operations02
Decapper stopping again. Moving chemistry tubes to manual decap to hold turnaround.
10:10Service system · SR-2291
Opened03
Automation line decapper: intermittent gripper fault.
15:20Field service note · Vendor04
Realigned the gripper sensor, ran 200 tubes clean. Cap waste bin was overfull, emptied it.
15:40Service system · SR-2291
Closed05
Resolved on site.
Day 4
+3 days
13:05Facilities message · Building
Walk-in refrigerator 2 door gasket replaced. Temperatures normal.
Day 8
+4 days
16:20Huddle note · Core lab
Analyzer 3 QC rerun on second shift. Back in service by 16:00.
Day 12
+4 days
07:00Huddle note · Core lab06
Decapper faulting again on nights. Manual decap for most of the shift.
08:15Daily turnaround · Chemistry
07
Chemistry turnaround over target between 03:00 and 06:00. Manual decap noted.

Day 8 is the same lab and the same shift, but a different instrument. Sharing a room is not enough to connect two records.

One module, one history

The seven records grouped around the instrument they describe: two episodes, a service ticket closed in between, and every line traced back to where it was written.

AOI / Histories / H-1106

Illustrative

Core lab · Automation line

Recurring decapper gripper fault

Recurring

Status

Fault reported
D1 06:45
Manual workaround
D1 09:30
Ticket opened
D1 10:10
Ticket closed
D1 15:40
Faulting again
D12 07:00

Episode 1 · Day 1

Two overnight faults, chemistry tubes moved to manual decap on day shift, and a field service visit that realigned the gripper sensor. SR-2291 closed the same afternoon.

11 days after SR-2291 closed

Episode 2 · Day 12

Faulting again overnight, another shift of manual decapping, and chemistry turnaround over target in the morning report.

How the AOI demo works · Illustrative

The same two stages as the live demo, on an automation line.

The interactive AOI demo runs on a synthetic clinical laboratory, North Valley Medical Center, which is a fictional organization. It works in two stages: first it turns each record into a structured event, then it connects related events into one history. Here are the same two stages applied to the decapper above.

01Structured events

One record, structured

As written

Day 1 · 09:30Internal message · Lab operations02

Decapper stopping again. Moving chemistry tubes to manual decap to hold turnaround.

Automation line decapper stopping again. Chemistry tubes moved to manual decap.

Workaround

Entity: Automation line
Department: Lab operations
Date: Day 1 · 09:30
Source: Internal message

Explicitly stated“Moving chemistry tubes to manual decap to hold turnaround.”
InferredNot the first stop: the message says “again”.
UncertainWhat is causing the decapper to fault.

Source kept · Internal message · Day 1 · 09:30

02Operational memory

Related events, one history

Entity history

Core lab · Automation line

Recurring
7 events
2 episodes
5 sources

Episode 1 · Day 15 events
- 01Huddle note
- 02Internal message
- 03Service ticket
- 04Field service note
- 05Service ticket
Quiet 11 days, then activity resumed
Episode 2 · Day 122 events
- 06Huddle note
- 07Workflow report

Linked by entity and timing · each event keeps its source

Lab Operations demo · Synthetic data

See AOI applied to lab operations.

The AOI demo runs on a synthetic laboratory operation. Huddle notes, service records, and workflow reports become structured events, then connect into the history of each instrument and workflow, with the evidence behind every step. Everything in it is synthetic.

Explore the Lab Operations demo

All demo information is synthetic.

What the records state, and what they don’t.

Explicitly stated

The decapper faulted in both episodes.

Written in the huddle notes on both days, and in a message on the first.

Inferred

Day 12 is the same fault SR-2291 was opened for.

Same module, same symptom, eleven days after the ticket closed.

Uncertain

Whether the overfull cap waste bin has anything to do with it.

Noted once by field service. Never mentioned again.

AOI puts that last line in front of the team with the records attached. Whether it matters is a question for the lab.

What is your lab working around this month?

We’re looking for a small number of healthcare operations teams to test AOI against real equipment, workflow, and handoff history.

Explore the Lab Operations demo Talk to us