Specialty EHR & IT

Allergy immunotherapy scheduling software and vial tracking

An allergy practice runs two schedules at once. One is the patient’s. The other belongs to a vial in a refrigerator, and almost no practice manages it with the same seriousness.

10 min read
September 8, 2026
Updated September 8, 2026
Allergy immunotherapy scheduling software and vial tracking
Quick answer
Allergy immunotherapy scheduling

Allergy immunotherapy scheduling software has to hold three things together: which patient is on which protocol and where in it, which vial and dilution their next dose comes from, and what happens when they miss. Most systems do the first well and the other two on paper.

Immunotherapy is the only treatment in most allergy practices that runs for years.

A patient starting build-up may come twice a week for months, then monthly for three more years. Across that time the protocol steps up through dilutions, the vials are remade, staff turn over, and the patient moves house. Nothing about that is clinically complicated. It is an administrative endurance test, and the record is what fails first.

The failure is rarely a wrong injection. It is far more often a patient who quietly stops coming and nobody notices, or a dose given from a vial that was remade last week by someone who wrote it on a different sheet.

Healthcare IT consulting perspective
The RealityThe vial and the appointment are one record
⚠️
The Problem
The schedule and the vial live apart.
The appointment is in the practice management system. The dilution, lot and expiry are on a card in the fridge. Reconciling them is a person’s memory.
🔧
The Solution
One record that carries both.
Tie each patient to a protocol step and to the specific vial their next dose comes from, in the chart, so the two cannot disagree.
✅
The Resolution
A schedule that shows what is actually due.
Nurses see the step, the vial and the last reaction on one screen, and the recall list contains people who are genuinely overdue.

The build-up phase and why the calendar is clinical

Build-up is the stretch where the dose climbs, and it is the stretch where scheduling stops being administrative. The interval between injections is part of the protocol, not a convenience. A patient who comes three days late is in a different clinical position from one who comes on time, and the person drawing the dose needs to know that before they draw it.

Which means the schedule has to expose the last injection date, the step reached, and any reaction recorded at that step, at the moment the appointment is booked and again at the moment the dose is prepared. Practices that keep this in a paper flow sheet manage it perfectly well right up until the person who knows the sheet is on leave.

This is worth designing rather than inheriting. The default configuration in most ambulatory platforms treats an injection visit as a nurse visit with no clinical state attached, which is how a four-year protocol ends up being tracked in the margin of a printout.

Extract preparation is a separate billable act

There is a coding distinction here that carries a documentation requirement with it, and getting it wrong is both a billing problem and a record problem. Medicare separates the professional administration of the injection from the preparation of the antigen vial.

The CMS billing and coding article for allergy immunotherapy sets out the split plainly: the injection codes cover “professional administration (injection) of the allergenic extract, when the extract is not included in the code descriptor,” while the preparation code covers preparation of the vial and not the injection. The same article states that a physician “may not bill this vial preparation code for more than 10 doses per vial.”

Read that last line as a data requirement rather than a billing rule. To bill preparation by the dose, the practice has to know how many doses came out of a specific vial. That is a count that lives in the vial record or nowhere.

Key takeaway
  • If your system cannot tell you how many doses have been drawn from a given vial, you do not have extract preparation documented — you have it estimated. Those are different things when somebody asks.

Vial tracking: the part the schedule depends on

A vial record that works holds the patient it belongs to, the antigens and dilution, the date it was made and by whom, the expiry, the lot numbers of the source extracts, and a running count of doses drawn. Six fields and a counter.

The source extracts themselves arrive as licensed biologics with their own controls. Federal regulation requires that “a sterility test shall be performed on each lot of each Allergenic Product” and that the potency of each lot be determined before release. FDA also draws a line practices should carry into their own records: for standardized extracts there is an established method to determine potency lot by lot, while non-standardized products have no such measure.

None of that governs what happens after the bottle reaches your refrigerator. That part is entirely your record, which is exactly why it deserves to be a structured one. Capturing source lot numbers on the vial record is the difference between a five-minute answer and a two-day search if a product is ever recalled.

Clinical team reviewing allergy immunotherapy scheduling software on a workstation
A recall list nobody owns behaves like an interface error queue. It fills quietly, and the first sign of trouble is a patient who stopped coming eight months ago.

Missed dose protocol, encoded rather than remembered

Every allergy practice has a rule for what happens when a patient misses. Most have it in a physician’s head, a laminated card, or both, in versions that differ slightly.

The rule is a lookup: how far past the interval, at which step, on which dilution, produces which adjustment. That is a table, and a table belongs in the system rather than on the wall. Encoding it does two things. It makes the decision consistent across nurses and across locations, and it creates a record showing why a dose was reduced, which is the documentation you want if a reaction follows.

Building it is not a large project. Writing the table down and getting the physicians to agree on it is usually the longer half, and it is worth doing at the same time as rebuilding the injection workflow around it rather than afterwards.

Qventive Healthcare

Not sure your vial record and your schedule agree?

We trace how a dose gets from the refrigerator to the patient in your practice, find where the two records diverge, and hand you written findings.

Patient recall and the three-year problem

Maintenance is where immunotherapy quietly fails. A patient on monthly injections for three years has thirty-six chances to drift away, and the schedule will not flag it because there is no appointment to miss — there is only one that was never booked.

Patient recall has to run off the clinical state rather than the calendar. The question is not who cancelled; it is who is on maintenance and has not had an injection in longer than their interval allows. That is a report, it takes minutes to build in any certified system, and it needs a named owner to work it. NIH has noted that achieving persistent relief requires at least three years of allergy shots, so a patient who drifts at month fourteen has spent the effort without reaching the benefit.

Where a check-in is about tolerance and adherence rather than the injection itself, a virtual visit is often the faster way to close the loop, and it gets the patient back on the schedule rather than onto a callback list.

What to fix first

  • Put the vial record in the chart. Patient, antigens, dilution, made-by, made-on, expiry, source lots, dose count. Not a card in the fridge.
  • Write the missed dose table down. One page, agreed by the physicians, then encoded.
  • Build the overdue-maintenance report before any new software. It is the cheapest thing on this list and it finds patients this month.
  • Name an owner for recall. By name, before the first list is generated.

In our experience practices that do those four find the scheduling product they were about to buy solves a problem they no longer have. Where a product is genuinely needed, the work sits inside our allergy and immunology EHR and IT support and a broader allergy immunology practice management engagement. Because a vial record identifies a patient by name alongside their treatment, it belongs in your HIPAA risk analysis as surely as the chart does.

Qventive provides allergy immunotherapy scheduling software help for medical practices across northern New Jersey, and the first conversation is usually about the vial record rather than the calendar.

Immunotherapy scheduling: common questions

Do we need dedicated immunotherapy software?
Often not, and it is worth finding out before you buy. The three things immunotherapy actually needs are a protocol step attached to the patient, a vial record with a dose count, and a report that finds people overdue on maintenance. Every certified ambulatory platform can express all three, though usually not out of the box and usually not in the place you would expect. Dedicated products add genuine convenience — protocol libraries, barcode scanning at the point of draw, reaction logging designed for the workflow — and for a high-volume practice that convenience is worth paying for. For a practice running a few dozen patients on maintenance, configuring what you own tends to get you most of the way. The honest test is to write down the five questions you want to answer on a Monday morning, then check whether your current system can answer them once somebody configures it properly.
How should we handle a patient who transfers in mid-protocol?
Treat it as a clinical handover rather than a data import, because the outside record will not contain everything you need. What you want before the first injection is the antigens and concentrations, the step reached, the date of the last dose, any systemic reactions and how they were managed, and whether the extracts came from the same manufacturer. That last one matters more than people expect, since potency is established lot by lot and a change in source is not a like-for-like continuation. Most practices have a written rule about restarting or stepping back when the outside information is incomplete, and the useful thing is to make that rule visible in the system rather than leaving it to whoever takes the call. Record the decision and its reason in the chart, because a year later nobody will remember why this patient started at that step.
What are the HIPAA implications of a vial refrigerator log?
A vial label with a patient name on it is protected health information sitting in a room that is often less controlled than the rest of the practice. So are the paper logs beside it, the spreadsheet somebody keeps of who is due, and the printed schedule left on the counter. The questions are the ordinary ones and they are rarely asked about this room. Who can enter it and is that access reviewed. Does the paper log leave the room, and where does it go when it is full. Is the temperature-monitoring device on your network, and is it on your device inventory. If vials are labelled with initials rather than full names, has anyone checked that the shorthand is not itself identifying in a small practice. In our engagements the injection room is very often absent from the risk analysis entirely, not because anyone excluded it but because the analysis was built around computers.
Can we bill for preparing vials and giving the injection on the same day?
Yes, and the mechanism is specific enough that it is worth reading the source rather than relying on memory. CMS separates administration from preparation: the injection codes cover giving the dose where the extract is not part of the code descriptor, and the separate preparation code covers making up the vial without the injection. When a practice does both on the same date, both are reported, with the preparation reported by the number of doses. What trips practices up is the dose count, since the preparation code cannot be billed for more than ten doses per vial and the count has to reflect what can actually be drawn. Get the vial record right and the billing follows from it. Get the billing right without the vial record and you are asserting a number you cannot evidence.
How long should we keep vial records after a course finishes?
Treat them as part of the medical record and retain them on the same schedule, because that is what they are. A vial record documents what was given to a named patient, which makes it clinical documentation rather than inventory paperwork, however much it looks like the latter. The temptation to discard the fridge cards once a course ends is understandable and it is how a practice ends up unable to answer a question about a reaction three years later. Source lot numbers deserve particular care, since a product recall or a safety communication is answered by searching those numbers, and a practice that recorded them can produce a patient list in minutes while one that did not cannot produce it at all. State retention requirements set the floor and they vary, so confirm yours rather than assuming a standard period.
Ready when you are

Let’s meet

Qventive works with allergy and immunology practices across New Jersey on protocol design, vial tracking and recall. Thirty years healthcare-exclusive, from our office in Hackensack.

Sources
  1. Injection codes cover administration, 95165 covers vial preparation, and preparation may not be billed for more than 10 doses per vial. cms.gov
  2. Sterility and potency testing required on each lot of each allergenic product. ecfr.gov
  3. Standardized extracts have an established lot-by-lot potency method; non-standardized products do not. fda.gov
  4. Persistent symptom relief requires at least three years of allergy shots. nih.gov
Qventive Healthcare
Healthcare IT consulting and managed services, healthcare-exclusive since 1994. 200 Passaic Street, Hackensack, New Jersey. We serve as a business associate to the practices we support.
AI Assistant Online

Schedule a Consultation

Fill out the form below and we'll get back to you within 24 hours.

Request Sent!

We've received your request and will be in touch within 24 hours.

Something went wrong