ORtelligence · Mobile
ORtelligence: Instrument Preparation 75% Faster and Operations 40% Shorter
Designed mobile scanning flows that showed instrument-count status, missing items and preparation work in the operating room.
- Role
- Senior UX Designer
- Scope
- Surgical instrument scanning and count workflow
- Focus
- Mobile

My contribution · ORtelligence
Surgical instrument scanning and count workflow
The case study covers the interface work, which made count status, missing items, and recovery steps visible in a fast-moving operating-room workflow.
- 400+ to 200
- components consolidated
- 18,000+
- customers in 60 countries
- UI Relay
- Figma plugin
What I owned
- 01Mapped OR count workflows and failure points around missing instruments.
- 02Designed mobile scanning, confirmation, and recovery states for surgical teams.
- 03Brought count status and missing items into one mobile view.
Clickable prototype
Open the redesigned sORT app
Scan a tray with the camera or the RFID reader, resolve the instruments sORT couldn't read, and confirm the count. You can also record a missing instrument with a second person's check, and send a problem report with a drawing on the tray photo.
Overview
About the project
- Role: Senior UX Designer at Digica, an AI and machine-learning product development agency.
- Client: ORtelligence, a mobile product for scanning and tracking surgical instruments in the operating room.
- What it is: The app is called sORT, and it runs on Android phones in the operating room. A scrub nurse scans an instrument tray with the phone camera or an RFID reader, and sORT reads the QR code or RFID tag on each instrument and compares it with the tray's count sheet. The nurse then checks the instruments sORT couldn't read, which come back as missing or to check, instead of counting the whole tray by hand.
- Objective: Help operating-room teams identify instruments, track count status, and resolve a missing item with less manual checking.
- Outcome: Preparation became 75% faster, against a target of 25%, and overall operation time dropped by 40%, against a target of 15%. This case study documents my interface contribution and does not attribute operational outcomes to the design alone. In 2026, I went back to my original designs and rebuilt sORT as a clickable coded prototype, with a more modern interface in the same brand.
Prototype
- Interactive prototype: Open the prototype. You can go through the tutorial, scan a tray with the camera or the RFID reader, resolve the instruments sORT couldn't read, and send a problem report with a drawing on the tray photo. After the set-up count, you can switch the case to the closing count and sign it off with a second person.
- Try this: Open the 08:30 case in Theatre 3 and scan the small fragment set with the camera. Press Confirm tray before you've resolved anything, and you'll find it stays off until every instrument has a state. Then record 21-813 as missing and confirm the tray. You'll have to choose what you did about the missing instrument and add a second person's initials.


The product problem
Surgical teams were tracking instruments by hand, on top of an already demanding operating-room workflow. A missing or unaccounted-for instrument could delay the work and put patient safety at risk.
The way it worked before sORT is that the team counted every instrument against the tray's count sheet, one by one, before every surgery and again after it. The instruments can number in the hundreds, and a case can need several trays. The closing count also happens while the surgeon is closing, which is when the pressure to finish is highest. In usability engineering terms, a miscount at closing is a hazard-related use scenario, because it can leave an instrument inside the patient.
ORtelligence asked Digica to design a mobile app that could manage surgical instruments through scanning. Operating-room teams work quickly, so the app had to fit into the count workflow they already had and show the count status at a glance.
The original brief had two goals. The app had to shorten the check-in and check-out time for trays, and it had to take human factors errors into account, so the person doing the count could make the right decision at a glance.



Goals and success metrics
- Missing instruments: Make an unaccounted-for item easier to identify and resolve.
- Preparation: Test if the workflow could improve preparation speed by 25%.
- Procedure time: Explore if better instrument tracking could contribute to a 15% reduction in overall operation time.
- Results: Preparation became 75% faster, against a target of 25%, and overall operation time dropped by 40%, against a target of 15%.
Research
- Observation: I attended mock surgical sessions to see how instruments were tracked, labelled, and transferred. I sat in on 6 mock sessions across two theatres and timed the manual tray check. A tray took a median of 6 minutes to count by hand, and in 4 of the 6 sessions, someone lost their place and the count was restarted at least once.
- Workshops: Nurses, surgeons, and IT administrators mapped out the problems they had with misplaced instruments and supply gaps. We ran 3 workshops with 14 participants in total. In a 5 Why analysis, the group traced inefficiency and inaccuracy back to the same chain: the count was manual, so it depended on people not making mistakes, it took a long time, it was done differently from one team to the next, and the technology the hospitals had didn't help.
- Interviews: I ran 20 interviews with medical staff. What they needed most was speed, reliability, and clear scanning feedback. The 20 were 8 scrub nurses, 5 circulating nurses, 4 surgeons, and 3 sterile services technicians, and 17 of them described a count discrepancy in the past month that took more than 5 minutes to resolve.
- Survey: 30 surgeons and their assistants filled in a survey. 90% believed the app could improve the safety and efficacy of surgeries, 65% agreed it would reduce the risk of surgical errors, and 75% were willing to bring it into their workflow. 55% agreed it would make their job more enjoyable, and 50% of the assistants said it could help them manage their tools and equipment better.
- Usability rounds: I ran 3 rounds of formative evaluation with 6 participants in each round, using a tray on a mock back table. In round 1, 61% of participants found and resolved the missing instruments. The main use error was a close call: 4 of the 6 participants pressed Next while an undetected instrument was still on the list, and they only noticed when I asked them for the count. By round 3, after the changes to the results screen, task success was 94%.
- Surgeons: They needed to identify instruments quickly and reliably without taking their attention off the procedure.
- Nurses and attending staff: They needed a shorter way to track instruments and resolve a count.
- IT staff: They needed the app to exchange data with hospital records and inventory systems, so staff didn’t have to keep entering it by hand.
- Persona: I worked from a persona, a general surgeon called Jane with 10 years' experience, who starts her rounds at 6:00 am and is back in theatre by 3:00 pm. Her pain point was the time-consuming manual process of checking her surgical tools, and she was worried about surgical errors caused by human error in tool management.
What I designed
With the Digica product team, I mapped the main workflows for surgeons, nurses, and IT administrators. We prioritised:
- Scanning: Identify instruments through QR codes or RFID tags with as few steps as possible.
- Live status: Update the operating-room dashboard with each instrument’s location, availability, and usage history.
- Inventory alerts: Show low inventory or a missing instrument as soon as the system detects it.
At first, we considered voice-activated commands, but background noise in the OR made them inaccurate. That confirmed our choice to put the effort into scanning instead.
- Navigation: I kept the main scanning and count actions visible, so nurses and surgeons didn’t have to search through the app for them.
- Core tasks: The wireframes prioritised scanning, live count status and quick instrument search.
- Tray scanning: The nurse picks the picture type, lines the tray up with an overlay in the camera, and takes one photo. If sORT can't find a tray in the photo, the error screen lists the two usual causes, a photo that wasn't taken from directly above or a tray that isn't supported yet, with links to the tutorial and the list of supported trays.
- Results: Each instrument came back as detected, undetected, or inconclusive. I split inconclusive into three groups, because each group needs a different check from the nurse: two possible matches for one instrument, instruments sORT can't read at all, and instruments hidden underneath other instruments.
- Feedback reports: The nurse can mark any result as wrong, choose an error category, describe the problem, and draw on the photo to show the instrument. Several instruments can go into one report.
- Tutorial: A five-step tutorial covers the camera technique and how to mark an instrument. The tutorial has two versions, one for press and hold and one for swipe, because I designed both gestures for marking an instrument.
- Feedback sessions: I held weekly reviews with a small group of operating-room nurses and used their feedback to revise the interface.
- Design and engineering: As the design changed, I went through real-time data syncing and hospital-database integration with the developers.









Beta testing
The beta ran in two pilot hospitals. We held focused sessions with surgical teams to find problems and decide what to change next. Over 6 weeks, 41 staff scanned 1,180 trays. sORT found the tray on the first photo 91% of the time, and 7.8% of instruments came back as inconclusive.
Nurses found the scanning flow fast but asked for a simpler way to find rarely used instruments.
Some surgeons asked for offline support in case the network went down.
IT staff required encryption for patient and hospital information.
Changes after testing: I made frequently used tools easier to reach, added an offline scanning cache, and revised the security requirements with the team.
The design work focused on the mobile count workflow: identify the kit, review what’s missing, confirm the count, and recover from an interrupted scan.
The main interface decision was to keep the count status and recovery actions on screen, so the team didn’t have to switch between tools.
My contribution: I designed the mobile workflow so the operating-room team could see kit identification, missing-item review, confirmation, and recovery states.



How I redesigned it
In 2026, I rebuilt sORT as a coded prototype. I kept the brand: the navy app bar, Raleway, the light blue from the tutorial illustrations, and red for missing instruments. Recognition works the way the product was specified, through QR codes or RFID tags, and the camera view from the original screens is still the scanning interface. I framed the changes in IEC 62366-1 terms, because a count app is part of how the team controls the risk of a retained instrument.
- Count summary first: In the original results screen, you'd see the tray name and the photo first, and you had to read two lists to know if the tray was complete. In the redesign, the screen opens on four counts: expected, found, to check, and missing. Each count is also a filter for the list underneath, so the nurse can go straight to the instruments that need a decision.
- One state for each instrument: The original went through three versions of the status lists. The first scan had detected and undetected, and the later version added three inconclusive groups, each with its own header colour. In the redesign, every instrument has one state, Found, To check, Missing, or Confirmed, and the reason sORT couldn't read it is a line of text on the row. This way the nurse reads the same row layout everywhere and only has to learn four states.
- A prevention gate on Confirm tray: In the original, you could press Skip or Next and leave a tray with an undetected instrument still on the list, which was the close call from the usability rounds. In the redesign, Confirm tray stays off until every instrument has a state. If the nurse presses it early, the app lists what's still open, for example 3 missing and 3 to check, and scrolls to the first one.
- Recording a missing instrument: Before an instrument is recorded as missing, the nurse confirms it in a dialog. Then, before the tray can be confirmed, they choose what they did about it: found it outside the tray, asked sterile services for a replacement, or escalated it to the surgeon and the team lead. A second person types their initials on the phone, and the initials have to match the person chosen in the list. Theatre teams already use two-person verification for a count discrepancy, so the count record now has both names.
- Closing count: At closing, sORT compares each tray with the set-up count as well as the count sheet. An instrument that was counted at set-up and isn't read at closing goes to the top of the results with a warning, because that's the case where an instrument could still be inside the patient. The closing count always needs a second person to sign it off.
- Visible actions instead of gestures: The original relied on press and hold or a swipe to mark an instrument, and it took two tutorial steps to teach them. With surgical gloves on, it's easy to trigger a swipe by accident. In the redesign, each row opens a sheet with the actions written out, like Rescan this slot and I can see it in the tray, and the Select button starts a problem report. Long press is still there as a shortcut.
- Partial code reads: When sORT only reads part of a code, the nurse picks between the two possible instruments, which are shown with their colour band and value. If they pick the one that isn't on the count sheet, a dialog explains that the slot is for the other instrument, and they can report it and record the right one as missing.
- Confirmation and undo: Checking an instrument by eye needs a tick in a box that names the instrument. After that, every change to an instrument, a confirmed tray, a cleared drawing, and a removed report item can be undone for a few seconds from the message at the bottom of the screen.
- RFID reads: With the reader, the tags are read through other instruments, so an instrument that was covered in the photo comes back as found. Instruments without a tag still come back as to check, and the nurse checks them by eye.
- Status that doesn't depend on colour: The face icons at the end of each row looked like a satisfaction rating, and the inconclusive rows used white text on mauve at 4.1:1. In the redesign, every state has an icon and a text label, the to check rows have an amber tint with dark text, and the light-blue Skip and Cancel buttons, which were at 2.3:1, are now outlined navy buttons.
- Numbers you can compare: Raleway's default old-style figures made catalogue numbers hard to compare at a glance. Every number now uses lining tabular figures, and instrument names wrap onto a second line instead of being cut off.
- Error copy that explains the fix: The original No tray detected screen started with "This is because: the background picture was taken", which is hard to read in a hurry. The new copy explains what happened, then the steps to fix it: hold the phone flat above the tray, about 50 cm away, and fit the whole tray and its label inside the frame. Retake the photo is the main button.
- A specific review dialog: The original review dialog only read "Make sure you have provided feedback for all of them." The new dialog lists each instrument that still needs a category or a description, and each one links straight to its form.
- States the original didn't have: The redesign adds a progress bar while sORT checks the tray, an offline banner with a queue for scans made without a connection, and a warning before a confirmed tray is scanned again. It also has states for an RFID reader that isn't connected and for camera access that's turned off.
- Case list and search: The case list has a feed of the other theatres, a low stock alert, and an instrument search with the frequently used instruments as shortcuts, which follows the beta change that made frequently used tools easier to reach.











Impact
Preparation became 75% faster, against a target of 25%, and overall operation time dropped by 40%, against a target of 15%.
In the beta, the median tray check went from 6 minutes by hand to 1 minute 30 seconds with sORT.
This case study documents my interface contribution and does not attribute operational outcomes to the design alone.
The 2026 prototype is my own redesign. ORtelligence and Digica didn't commission it, and it runs on sample data, with invented trays, catalogue numbers, and people.
Need this level of detail in your product?
Work through the hard product decisions early.
If you’re a product team, that can mean a focused design, system, or prototype project. If you’re hiring, it’s a chance to look closer at how I work across research, interfaces, and code.
Gideon Awolesi

