Building a Home Lab-Testing System with Rust

Hello readers, I am a backend engineer currently building an application that connects patients with medical laboratories for home sample collections. The workflow begins when a user books a laboratory test appointment. Instead of visiting a clinic, a phlebotomist travels to the patient's home, collects the sample, and flags the task as completed, leaving the laboratory to handle the test results.

This is a significant step for me. A friend persuaded me to take on this project, and my initial hesitation wasn't about Rust's reputation for being difficult to learn. Rather, I have spent recent years comfortable with Python and Node, languages where memory management, data ownership, and concurrency handling are either invisible or managed by someone else. Choosing Rust for a project dealing with real data—such as in-app patient payments, laboratory payouts upon sample collection, and sensitive patient details—felt like an unusual time to learn a new language.

Choosing Rust for applications handling sensitive healthcare data and financial transactions is a strategic decision. Its compile-time memory safety guarantees and strict ownership model eliminate entire classes of bugs common in languages like Python or Node, ensuring high reliability for mission-critical backend systems.

Nevertheless, this is precisely why I chose it. This is a serious project with complex states to manage, such as an appointment moving through booked, confirmed, collected, and paid-out statuses, along with real consequences if financial transactions fail. Rust's type system makes it difficult to represent an invalid state, while its compiler ensures that error paths cannot be easily ignored.

This article marks the beginning of a new series documenting my journey through building this software with Rust. If you want to follow along with the language itself, you can explore the official Rust programming language website.

Source: Dev.to