Linda Virtue

MyRekord · Healthcare product design

What happens after a lab result?

Lead Product Designer and Strategist · Proposed healthcare platform · Interactive Figma prototype

I led discovery and independently designed MyRekord, a proposed healthcare platform for patients and care teams in Nigeria. I took the project from research and concept through role-based workflows, high-fidelity mobile and desktop interfaces, and interactive Figma prototyping.

I found that a patient’s information didn’t reliably follow them through care. I used the lab report to show how the design could help at one of those handoffs. A patient can ask the ordering physician a question directly from the report. A clinician can open the follow-up calendar from the test details.

Presented
June 2025
Platforms
Mobile and desktop
Roles designed
Patient, clinician, lab technician, hospital administrator
Tools
Figma
MyRekord splash screen between the patient and clinician dashboards.

The system

How one lab result moves

I mapped a proposed workflow for how a lab result moves between roles, in three stages. The patient, clinician, lab technician, and hospital administrator examples below are views into this proposed workflow.

  1. 01

    Request lab work

    Doctor

    • Log in
    • Look up the patient
    • Select tests
    • Provide clinical notes
    • Choose lab and method
    • Review and submit
  2. 02

    Process the request

    Lab technician or admin

    • Log in to the lab portal
    • Receive new request
    • Review request details
    • Schedule sample collection
  3. 03

    Return results

    Lab

    • Verify results
    • Generate report
    • Send to doctor
    • Notify patient (optional)
    • Track delivery

Handoff between roles Optional step

View the original workflow map
Original workflow map in three columns. Doctor requesting lab work: log in, look up the patient, select tests, provide clinical notes, choose the lab and method, review and submit. Lab receiving request, by a lab technician or admin: log in to the lab portal, receive the new request, review request details, schedule sample collection. Lab sending results digitally: verify results, generate the report, send to the doctor, notify the patient (optional), track delivery.

Patient

Ask about a result

Patients described difficulty reaching their care teams. I put Message Physician on the report and prefilled the physician, facility, and test-related subject. The patient can go straight to writing their question. The simulated confirmation identifies the recipient and sets expectations for a reply.

Swipe to see each step

  1. My Test Results list showing CBC (Complete Blood Count) and pelvic ultrasound results, each with the date, the ordering physician, and a See Details button.
    01Results list
  2. CBC test details with the order, collection, received, and report dates, the requesting physician, a Message Physician button, and a results table with a flagged white blood cell count.
    02CBC report
  3. Message Center composer with the To, Facility, and Subject fields already filled in and an empty message field.
    03Prefilled message
  4. Success screen confirming the message was sent to the physician, with a note that messages are reviewed during business hours and may take 2 to 3 business days.
    04Send confirmation

Message Physician sits on the report itself and opens the prefilled message in step 03.

Clinician

Move from review to follow-up

I placed Make Appointment with Patient on the test detail screen so clinicians could move directly from reviewing a result to the next scheduling step. The prototype walkthrough ends at the follow-up calendar.

Swipe to see each step

  1. Test Results Just In list for the clinician showing CBC, pelvic ultrasound, and basic metabolic panel results, each with the date, patient, ordering physician, and a See Details button.
    01Results list
  2. Clinician view of CBC test details with a Make Appointment with Patient button above the final result and test details table.
    02CBC report with Make Appointment with Patient
  3. Your Calendar month view with an Add Event button, followed by the start of a daily view of appointment slots.
    03Opening the follow-up calendar

Make Appointment with Patient sits on the test details and opens the follow-up calendar in step 03.

Desktop operations

Lab delays also surfaced in discovery. I designed two desktop workspaces around different responsibilities. Lab technicians need the details of an individual request. Hospital administrators need to see which tests are still in progress and whether results have come back across labs.

Lab technician

Review an incoming order

The lab technician home, with New Orders Received highlighted in orange alongside Pending Collections, Tests in Progress, Recently Completed Tests, Submit Results, and Results Archive and Reports.
Starts from New Orders Received on the lab home.

QueueOrders Received

The Orders Received queue cropped to the Patient Name column, listing Adeyemi, Tunde; Bello, Amina; Fatima, Yusef; and Faruk, Umar. The Bello, Amina row is highlighted.

Order detailAmina Bello · Order #10003

The order detail for Amina Bello: order reference and date, a patient ID panel, the lab partner, the ordering physician and facility, a table of requested tests, and the Accept Request button.

Technicians open an order from the queue and accept it from the detail view.

View full lab home
Full lab technician home for LASUTH Labs.
View full queue
Full Orders Received screen.
View full order detail
Full Order Detail screen.

The lab home leads with new orders. The incoming queue helps technicians find an order. The detail view brings patient information, the ordering physician, lab partner, and requested tests together around the Accept Request action.

Hospital administrator

Monitor lab activity

Lab Activity
Detail of the Lab Activity table: lab name, status (Completed or In Progress), results received (Yes or No), and flags for High Cholesterol and Elevated Enzymes.

Full table · scroll sideways

Lab Activity table listing test ID, test name, patient, ordering physician, date collected, lab name, status (Completed or In Progress), whether results were received, and flags, with a lipid panel flagged High Cholesterol and a liver function test flagged Elevated Enzymes.
View full screen
Full Lab Activity screen under Operational Management.

I separated test status, result receipt, and flags so administrators could scan which tests were still in progress, which results had arrived, and which results needed attention.

How administrators get there
Focused crop of the administrator home: the Operational Management column with Billing and Payments, Inventory Management, and Lab Activity.

From the home screen: Operational Management → Lab Activity.

View full screen
Full administrator home, titled Choose Your Focus, with Patient Management, Staff Management, and Operational Management.

Validation

From wireframe to tested design

I ran two rounds of usability testing. Round one used low-fidelity wireframes, and round two used the high-fidelity prototype. Seven participants across several roles took part in testing.

WireframeResults list, low fidelity
Low-fidelity wireframe of My Test Results in grayscale: filters and search, then cards for a CBC dated May 15, 2025 and a pelvic ultrasound, each with the date, the physician’s name, and a small black See Details button at the right.
FinalResults list, high fidelity
High-fidelity My Test Results in MyRekord’s purple and orange: a filter bar and search, then result cards with the date, an Ordered by line, and a wide orange See Details button.
  1. The physician’s name gains an “Ordered by” label.
  2. See Details moves from a small black button at the right to a wider, centered orange button.

Outcome

From prototype to build

I presented MyRekord as a proposed platform in June 2025, with an interactive prototype tested across patient, clinician, lab, and administrator roles. It showed the moments that matter most after a lab result: a patient asking a question from the report, a clinician moving to follow-up, a lab accepting an order, and an administrator seeing what’s still outstanding.

After the presentation, I previewed the design with engineers and, acting as product strategist, helped determine what was needed to start the build. When MyRekord was revisited in 2026, the question shifted from what the platform should do to what it would take to build it. I helped develop estimates to guide the search for a development team, using the prototype and workflows to give that conversation a concrete starting point.