RFS Tracker

Referrals whose next Request for Service is coming due (45 days before expiration) — live from your records. Click a row to set its RFS status; setting one makes it fall off the queue.

Get every visit's note into HSRM first, then draft and file the RFS. Tap a referral to open it.

· · expires — · sessions ? of ?

Notes in HSRM (checked before any RFS is filed)

Not checked yet. Open this referral in HSRM → Add/View Documents, then type below which session numbers have a signed note there. 0 visit(s) delivered so far.

RFS Submitted = you filed the Request for Service in HSRM. It stays locked until every visit on this referral has a signed note on its HSRM Documents list (box above). Approved / Denied = the VA's decision came back. Clear status puts the referral back in the due queue.

AI draft of the RFS

Shows only once every visit's note is on this referral's HSRM Documents list. Built only from this referral's finished notes, on the office AI computer. Nothing is filed, sent or signed. Read every line against the notes before you put it in HSRM.

PatientVA Auth #ExpirationRFS dueSessionsNotes in HSRMReferralRFS statusAction

Queue is clear — no referrals are inside their 45-day RFS window without a status.

Provider-requested referrals

Areas a provider flagged on a completed note as needing a separate referral (one request per area). Open a row, prepare and sign the 10-10172 packet, then mark it Filed.

· no auth # · · seen —

Provider reason: (none given)

Filed = you sent the 10-10172 for this area (fax to Biloxi or HSRM upload). Dismiss = no separate referral is needed. Both remove the request from this list.

PatientVA Auth #Date of serviceProviderAreaReasonStatusAction

No open provider requests — nothing flagged on completed notes is waiting for a referral.