Workflow
The medication that changes an injection plan is usually knowable weeks before anyone asks about it. An AI receptionist asks at intake, records the named agent and what actually happened during a reported reaction, and puts it in front of your provider while there is still time to arrange labs or a hold.
A patient on warfarin or dabigatran presenting for a facet block may need pre-procedure coagulation labs and a medication hold. Identifying anticoagulation at intake gives your staff the interval they need to arrange labs and instructions before the procedure date.
Some patients report a steroid allergy that was a reaction to the vehicle, the preservative or the local anaesthetic rather than the steroid. Capturing the specific reaction, rash against anaphylaxis against nausea, is what lets your provider make an informed drug choice.
Chronic oral steroids and frequent steroid injections are captured with dose and frequency as the patient reports them, so your provider is reading that history when they plan, rather than hearing it for the first time in the room.
Medication and allergy data come back as a single structured checklist rather than scattered through a call note, which is what makes it realistic for a provider to review it before the procedure rather than during it.
Medication and allergy history captured on intake
Anticoagulants, steroids, NSAIDs, and allergies documented before procedure date
Drug interaction flags
AI alerts your staff to hold anticoagulants, verify lab values, or adjust procedure timing
Provider pre-procedure checklist
Structured summary ready for provider review hours before the scheduled block
New patient medications and updated findings
Captured during intake and returned as a structured, EMR-pasteable summary for staff review and filing
It is captured during the intake call, flagged in the structured summary, and returned to your staff with the rest of the medication list. Because that happens at booking rather than at the pre-procedure call, your team has the interval to arrange labs, a hold, or a conversation with the prescriber.
Exactly that, plus whatever detail they can give: when they started it, who prescribes it, what it is for. The summary shows an unidentified anticoagulant rather than an empty field, so your staff know to confirm the agent with the pharmacy or prescriber.
It does not try to. It asks what happened when the patient took the medication and records the answer as given — rash, difficulty breathing, nausea. Your provider uses that detail to decide whether it is an allergy, a side effect or an intolerance.
Neither. It recognises the high-risk categories your protocol names — anticoagulants such as warfarin, apixaban, rivaroxaban and dabigatran, antiplatelet agents such as clopidogrel and ticagrelor, NSAIDs and high-dose corticosteroids — and flags them for review. It does not perform pharmacological interaction checking and does not instruct a patient to stop anything.
The intake summary is a snapshot at booking. Your staff confirm current medications with the patient closer to the date, on your standard pre-procedure call, and any change is noted and passed to the provider.
Capability
Patient intake
Structured AI intake for medications, allergies, imaging, and clinical history across all specialties.
Next step
Booking new patients on the first call
How a first-time caller becomes a booked appointment on one call.
Next step
Pain management practices
How call handling differs for pain management practices.
See how MedReception AI handles after-hours calls, scheduling, intake, and patient communication for medical practices like yours.
Want the numbers first? See plans and pricing