For mobile phlebotomy and specimen-collection operations
The run is the business. Schedule it as one thing
Mobile phlebotomy software schedules a route, not a building: the same facility stops in driving order, each arrival time computed from the first stop plus the minutes at and between stops, the whole run handed to one phlebotomist in one act — with geofenced clock-in as proof of presence and mileage captured at clock-out into the payroll export.
From $99/month per location · No sales call · No card to start
At a glance
- A mobile phlebotomy operation is not a building with shifts; it is a route with a clock. The unit of work is the run — the same stops, in driving order, with the timetable falling out of the first arrival time plus the minutes at and between each stop.
- Mornings are the business. Fasting draws and lab courier cutoffs push nearly all the work into a window that starts before 6 a.m., so a timetable that slips fifteen minutes at stop two is late everywhere after it.
- Proof of presence is part of the service. A geofenced clock-in at the facility, with scheduled-versus-actual times on every visit, is the difference between an invoice and an argument.
- Mileage is money. It should be captured at clock-out, on the visit it belongs to, and land in the payroll export in its own column — not reconstructed from memory on the last day of the month.
- Phlebotomy certification is a real credential with a real expiry, and in the states that license it, an expired certificate on a draw is not a paperwork problem. The roster is where an expiry can actually block work.
What does mobile phlebotomy software actually schedule?
Runs. A run is a named, ordered round of client stops — the Monday-Wednesday-Friday nursing-home circuit — built once, generated forward as one thing, and assigned to one phlebotomist in one act.
The tools most mobile operations start with treat every visit as its own island: a calendar entry here, a spreadsheet row there, each with a hand-typed time. That works until anything changes. Add a facility mid-route and every later time is wrong; retime the first draw and you are editing a dozen entries before six in the morning, which is exactly when this work gets edited.
In MedAligna the run is one object. Each stop carries the minutes spent there and the drive to reach it, and every arrival time is computed from everything before it — change one number and the whole morning re-times itself, previewed before it is saved. Each facility is a client record with an address and coordinates; the phlebotomist sees her stops, in order, with the address and the task list, on her phone.
Why is the morning window the whole game?
Because fasting draws and courier cutoffs compress nearly all the work into the hours before mid-morning, so a timetable that slips at stop two is late everywhere after it.
A patient fasting since midnight cannot reasonably wait past mid-morning, and the specimens have to make the courier pickup or the lab's own stability windows. The result is a business where the productive day is a few compressed hours, the sequencing inside those hours is everything, and the difference between a six-stop morning and a five-stop morning is real revenue.
That is an arithmetic problem before it is a scheduling one, and the arithmetic should not live in anyone's head at 5 a.m. The run's timetable is computed; the drive times are yours, because you know the roads; and the board's own travel check still warns when a hop between geocoded stops looks impossible in the time budgeted. What the software deliberately does not do is pretend to know your specimens: courier cutoffs and stability windows are constraints you build the run around, not data we hold.
How do you prove the draw happened, where and when?
Clock-in and clock-out happen on the visit itself, optionally inside a geofence around the facility's coordinates, and every visit keeps its scheduled time beside its actual one.
A standing contract with a skilled-nursing facility is a relationship of record: somebody at the facility will eventually ask whether the 14th's draw happened at 6:40 or 7:20, and the operator who answers from a record wins the conversation that the operator who answers from memory loses. Scheduled-versus-actual times, kept per visit, are that record.
The geofence is optional and belongs to you: set a radius around the facility's coordinates and a clock-in outside it is refused, with the distance recorded. The floor is 25 metres, because tighter than that is inside a phone's own GPS error and would turn honest arrivals away. Each day's round also exports as a collection manifest — stops in run order, scheduled against clocked, tasks done, mileage — and, where the work is Medicaid-funded, as EVV visit records carrying the six federal data elements. The FAQ below is precise about what that is and is not.
What reaches payroll, and what reaches the invoice argument?
Hours from the clock, computed on real elapsed time, with mileage in its own column and every visit marked as a visit — one file your payroll system imports.
Mileage reconstructed from a notebook at month end is a negotiation; mileage entered at clock-out, on the visit it belongs to, is a record. The payroll hours export carries visit hours beside shift hours, with mileage in its own column, in a layout Gusto imports directly and any other system takes after a one-time column mapping.
Certifications ride the same rails as everything else in the product: define phlebotomy certification as a required credential and an expired card refuses the assignment — checked against the end of the visit — with warnings to the phlebotomist and the operator at sixty, thirty, fourteen and seven days. In the states that license phlebotomists, that refusal is the difference between a paperwork lapse and work that should not have happened.
Three mornings that did not go to plan
The new nursing-home contract
A facility signs on for Monday-Wednesday-Friday draws. It has to slot into an existing morning run without wrecking the timetable, and every tool the operator has used treats each visit as its own island.
The facility is added as a stop, in driving order, with its minutes and the drive to reach it — and every later arrival time re-computes itself. Save, regenerate, and the new timetable is on everyone's phone.
The phlebotomist out sick at 05:10
The Tuesday run has six stops and the person who drives it is not driving anywhere. Reassigning six visits one at a time, before six in the morning, is how stops get missed.
The whole run is handed to another phlebotomist in one act — with every stop still checked individually against her certification, her exclusions and her day, and anything the rules refuse left visibly open rather than silently dropped.
The mileage dispute
Reimbursement is reconstructed from a notebook at month end, the number does not match anyone's expectation, and the argument costs more goodwill than the miles cost money.
Mileage is entered at clock-out on the visit it belongs to, and the payroll export carries it in its own column beside the hours — a record made at the moment, not a memory made at month end.
How to choose mobile phlebotomy scheduling software
Six questions worth asking any vendor here, including us. The first one is the one that decides whether the tool fits the work.
01Is the route one object, or a pile of independent visits?
A run is a thing you name, reorder, and hand to one person. If the tool only has individual visits, every schedule change is a dozen edits and every handover is a dozen chances to drop a stop.
Where MedAligna lands: A run is first-class: ordered stops, a computed timetable, generated as one thing and assigned to one phlebotomist in one act.
02When a stop's time changes, does the rest of the morning re-time itself?
The timetable is arithmetic — first arrival plus minutes at and between stops. A tool that stores each time separately makes you redo the arithmetic by hand, and the morning you get it wrong is the morning of the dispute.
Where MedAligna lands: Each stop's arrival is computed from everything before it. Change one duration and the whole run re-times, with the change previewed before it is saved.
03Can you prove the draw happened at the facility, at the time?
Standing contracts get audited, informally or otherwise. Scheduled-versus-actual times, recorded where the work happened, settle questions before they become disputes.
Where MedAligna lands: Clock-in and clock-out happen on the visit itself, optionally inside a geofence around the client's coordinates, with the distance recorded.
04Where does mileage live?
If mileage lives in a notebook, month end is a negotiation. It belongs on the visit, captured at clock-out, and in the export beside the hours.
Where MedAligna lands: Mileage is captured at clock-out and lands in the payroll hours file in its own column, with the visit marked as a visit rather than a shift.
05Does an expired certification actually stop an assignment?
Certification renewals live on personal calendars. A tool that emails a warning has not prevented anything; a tool that refuses the assignment has.
Where MedAligna lands: Credentials are checked against the end of the visit and the assignment is refused with the reason stated. Expiry warnings go out at sixty, thirty, fourteen and seven days.
06Is the price published, and can you start without a sales call?
A two-van operation does not have a procurement department. If the price takes a phone call, the product was not built for you.
Where MedAligna lands: $99–$249 per location per month, published. The 14-day trial takes no card and includes everything, runs included.
Runs, stops, draw windows — the vocabulary
- Run
- A named, ordered round of client stops driven by one person — the Monday morning nursing-home circuit. In MedAligna it is one object: built once, generated as one thing, assigned in one act.
- Stop
- One client site on a run, with the minutes spent there and the drive time to reach it from the previous stop. Its arrival time is computed, not typed.
- Draw window
- The span in which a collection is usable — bounded by fasting on one side and courier cutoffs or specimen stability on the other. The reason mobile phlebotomy is a morning business.
- Geofenced clock-in
- A clock-in accepted only within a set distance of the client's coordinates, with the distance recorded. Proof of presence, not surveillance: the radius is the operator's own setting, floor 25 m.
- Scheduled versus actual
- The planned visit time beside the clocked one, kept per visit. The record that turns a late-on-the-14th accusation into a checkable statement instead of a memory contest.
Questions people actually ask
- What does mobile phlebotomy scheduling software cost?
- MedAligna is $149 per month per location for the Pro tier, which is where runs, client records, geofenced clock-in and mileage capture sit. A mobile operation dispatching from one base is one location, however many facilities it drives to. The 14-day trial takes no card and includes everything, runs included.
- Does it track specimens, requisitions or results?
- No, and it is worth being blunt: we schedule the people, not the tubes. Requisitions, specimen tracking, chain of custody and results stay with the ordering provider and the testing laboratory. If you need a laboratory information system, we are not it — we are the reason the right phlebotomist is at the right facility at the right time.
- Does it integrate with the lab's LIS or courier system?
- Not today. Courier cutoffs and lab requirements are constraints you build the run around — the timetable is fully in your control — rather than data we import. The REST API on the Enterprise tier can push the schedule outward if your lab wants visibility.
- How do phlebotomists see their run?
- On their phone: today's stops in order, each with the address, the tasks, and the clock. They can also subscribe to their schedule from their own calendar app. There is no app store download — it is a responsive web app that installs to the home screen.
- What about one-off home draws between the standing runs?
- Ad-hoc visits exist alongside runs: add a single visit for a client at a time, assign it, and it appears in the same day board with the same travel checks. The run covers the standing circuit; one-offs cover everything else.
- Is the geofenced clock-in EVV?
- It is the location half of it. Every visit captures the six federal EVV data elements — service and code, client with Medicaid ID, date, geofenced location, worker, actual start and end — and the EVV export hands you those records as CSV or JSON. What we are not is a state-certified alt-EVV system: certification is a per-state registration and testing process, and claiming it before passing it would be selling you a compliance outcome we have not earned yet.
Related
Six stops, one timetable, one tap to hand over
Build the run once. It generates forward, re-times itself when anything changes, and lands on the payroll export with the mileage attached.