Documentation Chasing
The US therapeutic shoe benefit needs a certifying physician, a recent visit and tight dating. Capture where each patient sits in the chain, on the call.
The patient, your practice, and the physician managing the diabetes all have to act inside overlapping windows, and only one of those parties is thinking about the deadline. Every status call captured with the missing item named turns a vague follow-up into a specific chase with a named recipient.
"I got my shoes last November, can I get another pair now?" is a question about a calendar year, a previous dispense date and your own policy. Where a read integration exists that history is checked on the call. Where it does not, the question is captured with everything needed, instead of the patient being told to call back.
The staff member who fits shoes is usually the staff member who answers the phone about shoes. Every status call pulls them out of a fitting. Moving the routine "where is my paperwork" call off that person is a direct return of clinical time, not a theoretical efficiency.
Coverage language is where practices get hurt. The call never states that a patient qualifies, that certification has been accepted, or that a claim will pay. It reports recorded status, states your policy, and routes anything else to a human, which is the only defensible posture on a documentation-dependent benefit.
24/7 coverage
Status enquiries and referring-office calls are captured outside clinic hours
HIPAA BAA included
Diabetes context, identifiers and document status encrypted with AES-256 at rest and TLS in transit
Under 1 second to answer
The dispensing staff member is not pulled out of a fitting to take a status call
No. Certification is a physician act with specific content and dating requirements. The system captures which documents are outstanding, records what the caller reports, and routes the chase to your staff. It never generates, completes or attests to clinical documentation.
No. Qualification depends on a diabetes diagnosis, specific qualifying foot conditions, and a certifying physician's judgement, all documented clinically. The call books the evaluation and captures the request. It does not assess eligibility or predict a coverage outcome.
From your record where a read integration is live or available through API or FHIR. Where no read path exists, it captures the patient's own account, flags it as unverified, and routes it, which is materially safer than answering a calendar-year question from a guess.
The therapeutic shoe benefit described here is a United States Medicare programme and does not apply outside it. Footwear and orthotic coverage in Canada and Australia varies by province, state, scheme and private insurer, so those callers follow whichever rule set your practice configures.
Provider-to-provider calls are captured with the practice, caller, callback number and fax destination, and routed as a task rather than a message. That is usually the call that unblocks the file, so it should not land in the same queue as general patient voicemail.
Your practice does. The policy statements, timing language and escalation paths are configuration you control, which matters on a benefit where the requirements are updated by policy rather than by us.
Related
Custom Orthotics Calls: Fitting, Pickup and Refits
The adjacent supply workflow, where lab turnaround and pickup generate their own call volume.
Related
Foot Surgery Scheduling and Clearance Coordination
The same pattern in a different key: a date that waits on documents held by other offices.
Related
Podiatry Referral Intake from Diabetes and Vascular
How the co-managing offices that hold this paperwork reach you in the first place.
Pillar guide
AI Receptionist for Podiatry Practices
The full podiatry front-desk picture: at-risk foot care, wound follow-up, orthotics, surgery and multi-site access.
See how MedReception AI handles after-hours calls, scheduling, intake, and patient communication for medical practices like yours.