Care experience, communication, access, or grievance issue
Start with the facility’s patient relations, grievance, records, or compliance lane when the issue belongs to the organization that provided care.
Compare route lanesOfficial route framework
Match the problem to the responsible lane before escalating.
A strong complaint or advocacy message depends on routing. Provider conduct, hospital grievance, pharmacy barrier, insurance issue, record access, civil-rights concern, and policy advocacy do not all belong in the same place.
Choose the right next step
Use the card that fits the barrier in front of you.
Medication, prior authorization, denial, or refill barrier
Separate pharmacy availability, prescriber policy, insurance authorization, shortage, taper pressure, and written-reason issues before escalating.
Build medication packetChart accuracy, source issue, or representative message
Use a records packet for chart concerns and a sourced policy message for broader system problems. Do not mix them into one unclear complaint.
Build records packetPacket standard
Before you choose an official route
Routing is not about sounding aggressive. It is about sending the right packet to the office that can actually review the issue.
- Decide whether the issue is medical care, records, insurance, pharmacy, civil rights, workplace, policy, or another lane.
- Collect dates, direct quotes, documents, and functional impact that support the request.
- Verify the recipient from an official source before sending anything sensitive.
- Ask for a written answer, explanation, review, correction, referral status, or next step.
- Keep public advocacy separate from private records unless a secure official process requires documents.
Safety boundary
Do not let routing become guesswork
Pain Care Rights can explain categories and prepare language, but official offices, deadlines, forms, and complaint requirements should be verified before use.
- verify official source
- review before sending
- no guaranteed response