Official route directory
Find the right complaint or appeal lane before your packet goes out.
Browse reviewed official pathways for medical board, pharmacy board, insurance, Medicaid fair-hearing, attorney-general, records, and federal complaint routes. The directory keeps state routes and federal routes separate so patients can prepare a focused packet without turning agency names, deadlines, or legal claims into guesswork.
Start with the state tied to the provider, pharmacy, insurer, Medicaid office, or record holder.
Choose the issue that best fits the paper trail: records, pharmacy access, insurance, Medicaid, delay, or rights concern.
Open the official source, confirm current instructions, and keep your packet narrow, dated, and factual.
Find the right lane
Filter by state, issue, route type, or agency keyword.
North Carolina routes are shown first, with federal fallbacks separated below when they may matter.
State routes
Use these first when the problem belongs to a state board, state insurance office, Medicaid office, or attorney-general route.
North Carolina medical board complaint
North Carolina Medical Board
Use this route when the concern involves possible unprofessional, unethical, incompetent, or board-regulated conduct by a North Carolina medical licensee.
North Carolina pharmacy board complaint
North Carolina Board of Pharmacy
Use this route for evidence-based concerns involving a North Carolina pharmacy, pharmacist, pharmacy technician, or DME facility within the Board of Pharmacy’s authority.
North Carolina health insurance complaint or claim denial help
North Carolina Department of Insurance
Use this route when the barrier is an insurance coverage problem, denied health claim, appeal question, or insurance-company complaint within NC DOI consumer assistance.
North Carolina Medicaid member help, appeal, or grievance route
NC Medicaid Division of Health Benefits
Use this route when the issue involves North Carolina Medicaid care access, a notice, a health-plan problem, an appeal or grievance question, or help understanding the next Medicaid step.
North Carolina attorney general consumer complaint
North Carolina Department of Justice Consumer Protection
Use this route when the concern is a consumer-protection issue and another specialized health, insurance, Medicaid, pharmacy, or board route does not clearly fit first.
Federal fallback routes
Review these separately. A federal route may matter, but it does not replace state-specific verification.
Medicare complaint or grievance route
Centers for Medicare & Medicaid Services - Medicare
Use this route for Medicare-related complaints or grievances about care quality, services, plan issues, or other Medicare concerns.
Original Medicare first-level appeal: redetermination
Centers for Medicare & Medicaid Services - Medicare
Use this route when Original Medicare made an initial claim determination and you need to request the first level of appeal.
Coverage by issue
Start with the problem you can document, then choose the office that fits it.
These counts show how the reviewed source set is organized while keeping the limits clear. A route count is not a legal conclusion or a promise that an agency will act.
Safe use
Use the directory to route a packet, not to guess your rights.
Results come from the reviewed Pain Care Rights route directory. Use them to organize the next responsible step, then confirm the current instructions on the official page before filing, sending, uploading records, or relying on a deadline.
- Verify every official page before relying on instructions, deadlines, mailing addresses, phone numbers, forms, or upload steps.
- Do not include unnecessary medical details when a narrow records, pharmacy, insurance, Medicaid, or board issue is enough.
- Use the free tools to prepare dates, functional impact, written requests, attachments, and a short packet summary before escalating.
Contact path planner
Choose where the packet should go before the wording gets louder.
Patients are often forced to explain the same harm to the wrong office again and again. This planner keeps the first contact practical: match the barrier, verify the official route, prepare only the proof that belongs, and keep the request readable for a real person reviewing it.
A records office can review chart access. A pharmacy board can review pharmacy conduct. A lawmaker can hear policy harm. Mixing those readers makes a packet harder to process.
The strongest first packet is not the longest one. It names the barrier, gives dated proof, explains impact, and asks for a specific written response.
Forms, portals, addresses, phone numbers, categories, and appeal instructions can change. The user should open the official source before sending anything.
A provider message, records request, board complaint, insurer appeal, Medicaid hearing request, and policy letter should not sound the same.
Where this belongs
Use the contact path that matches the barrier, not the one that sounds the most forceful.
A clean route gives the recipient less room to dodge the issue. Each card below separates the first ask, the proof to prepare, and the wording to avoid.
Records or damaging chart notes
Use first when: the problem is an inaccurate note, missing record access, a correction request, or a paper trail that is hurting later care.
- the exact note, visit date, author, portal message, or record request
- why the entry is incomplete, inaccurate, or harmful in plain terms
- the narrow correction or attachment request, not a full life story
Do not send a broad accusation packet before identifying the record holder and the exact record action being requested.
Provider, facility, or patient-relations issue
Use first when: the treating office, facility, referral team, or patient-relations department still needs a clear written chance to answer.
- the visit, referral, refill, denial, or portal thread involved
- what was requested and what written response is still missing
- functional impact: what the delay is doing to daily life, work, caregiving, sleep, or mobility
Do not make every first message sound like a licensing complaint when a narrow office answer may create the cleanest record.
Medication or pharmacy barrier
Use first when: the barrier involves a refill, stock explanation, refusal, forced taper documentation, prior authorization, or unclear pharmacy communication.
- prescription date, pharmacy name, plan or Medicaid detail, and the words used to deny or delay
- provider instructions, prior authorization history, refill history, or written denial notice
- the practical harm without threatening language or unnecessary private detail
Do not let the draft read like a demand for a medication outcome from the website. Keep it to documentation, review, and written explanation.
Insurance, Medicare, Medicaid, or appeal route
Use first when: the issue is a plan denial, prior authorization barrier, grievance route, Medicaid fair-hearing problem, or coverage runaround.
- denial notice, plan name, member ID removed where not needed, dates, and service or medication at issue
- provider support, functional impact, and prior steps already tried
- the official notice language before relying on a deadline or appeal category
Do not calculate deadlines from memory or present the site as an appeal-filing service.
Board, licensing, or professional-conduct concern
Use first when: there is a documented pattern, unsafe dismissal, abandonment concern, refusal-to-document issue, or pharmacy conduct problem that belongs with a licensing reviewer.
- names, dates, locations, and the specific conduct concern
- messages, records, denial language, or screenshots that prove the issue without oversharing
- the office-level step already attempted, if one was safe and reasonable
Do not frame a board packet as a treatment order, lawsuit, or guarantee that discipline will happen.
Civil-rights, attorney-general, or policy contact
Use first when: the problem involves privacy access, disability access, consumer-protection routing, or broader policy harm that needs a public office rather than a treating provider.
- the official route category and why this office is the right reader
- a short timeline with dated facts and one clear request
- private medical details removed unless they are necessary to explain the barrier
Do not write a policy contact like a private medical order or send a medical chart dump when a short public-facing packet is enough.
Send-safe boundaries
The helper should reduce panic, not create risky shortcuts.
Pain Care Rights can help a user prepare a focused packet and find a reviewed route. The user still verifies the official page, reviews every word, removes unnecessary private detail, and sends only from their own account when they choose to act.
- The helper does not file, submit, email, calculate deadlines, or contact an office for the user.
- The helper does not decide that a law was violated, a provider is required to prescribe, or an agency must grant relief.
- The helper should never invent contact details, staff names, complaint categories, forms, or appeal rights.
- The user should remove private identifiers and unnecessary medical detail before copying or sending any packet.
Official contact helper
Turn a route result into the right contact path before anyone sends a packet.
A complaint route is only useful when the contact path fits the problem. This helper framework keeps provider offices, records teams, boards, pharmacies, insurers, Medicaid offices, federal routes, and policy contacts separated so a user can prepare the right packet for the right reader.
Contact lanes
Choose the contact by what the office can responsibly review.
The safest contact path starts with the documented barrier, then narrows the reader. A pharmacy barrier, records correction request, Medicaid hearing issue, insurance appeal, provider delay, and policy letter should not all use the same wording.
Provider, facility, and patient relations contacts
a missed follow-up, referral loop, inaccurate visit summary, pain-care access problem, or a request that needs the treating office to answer in writing first
- the exact visit, portal message, refill issue, denial, or delay
- the short functional impact in daily-life terms
- the specific written action being requested
Do not turn the first office message into a board complaint when a narrow written answer from the provider or patient relations team may create the clearest record.
Medical board and licensing contacts
documented professional conduct, refusal-to-document concerns, abandonment, unsafe dismissal, record accuracy harm, or a pattern that belongs with a licensing reviewer
- provider names, dates, visit locations, and the narrow conduct concern
- records or messages that show the issue without extra private detail
- what was requested, what was refused, delayed, or documented inaccurately
A board contact is not a treatment request, medication shortcut, malpractice lawsuit, or promise that the board will discipline anyone.
Pharmacy board, pharmacy, and medication-barrier contacts
refill barriers, refusal explanations, stock confusion, pharmacy documentation gaps, or a medication-access paper trail that needs dates and source verification
- prescription date, pharmacy name, denial or barrier language, and who said what
- provider instructions, insurer or Medicaid information, and any written pharmacy response
- the practical harm: missed dose risk, travel burden, withdrawal concern, or worsening function
The contact path should document the barrier and ask for a written explanation. It should not demand a specific medication outcome from the site.
Insurance, Medicaid, Medicare, and appeal contacts
coverage denials, prior authorization barriers, plan grievance routes, Medicaid fair-hearing preparation, or insurer runaround that needs a dated packet
- denial letter, plan name, dates, deadlines shown on the official notice, and appeal route
- provider support records, functional impact, and the narrow service or medication issue
- what has already been tried through the plan or Medicaid office
Coverage contacts require official deadline verification. The site should help organize facts, not calculate deadlines or promise appeal rights.
Records, privacy, civil-rights, and policy contacts
record amendment requests, damaging chart-note concerns, access delays, privacy complaints, disability-access concerns, or broader policy advocacy
- the exact note, record request, access problem, or public policy harm
- the correction requested or the statement of disagreement the user wants attached
- only the private details needed for that route and nothing more
Records and policy contacts should stay narrow. A lawmaker or civil-rights route should not be written like a private treatment order.
Review sequence
Before a contact is used, the packet should pass four plain checks.
Identify the reader before drafting
A provider, records office, pharmacy board, insurer, Medicaid office, civil-rights office, and representative need different language. The helper should make the reader clear before the packet is copied or sent.
Separate route from emotion
The lived harm matters, but the contact path needs dated facts, documents, functional impact, and one written ask so the recipient knows what response is being requested.
Verify the source before using a contact
Phone numbers, forms, portals, addresses, complaint categories, and appeal instructions can change. The official page must be opened and checked before the user relies on a contact method.
Keep the user in control
The tool can help organize the contact path, but the user decides what is accurate, what is private, what gets copied, and whether anything is sent from their own account.
Proof before escalation
A contact packet needs enough evidence to be understandable, not every private detail.
The goal is a narrow packet a real office can process: dates, the specific barrier, the impact, the request, and the records that support it.
- date, office, agency, pharmacy, plan, or record holder
- what happened, what was requested, and what written answer is missing
- functional impact in plain daily-life terms
- records, messages, denial letters, refill history, or portal screenshots that support the issue
- private details removed unless they are needed for the route
No-guess boundaries
The contact helper must stay useful without pretending to be an official office.
A stronger contact path is still only preparation. The user verifies the official page, reviews the wording, removes unnecessary private information, and chooses whether to copy, print, download, or send anything from their own account.
- No invented phone numbers, email addresses, forms, agencies, offices, laws, staff names, deadlines, or complaint categories.
- No automatic filing, automatic sending, automatic storage, or hidden account action.
- No promise that a board, agency, insurer, Medicaid office, pharmacy, provider, or lawmaker will act.
- No legal conclusion, diagnosis, prescribing instruction, medication demand, or promise about care access.
- No supporter wording that makes credibility, dignity, or basic organization depend on payment.
Route-to-packet bridge
A route is only useful if the packet matches what that office can answer.
State boards, pharmacy boards, insurers, Medicaid offices, federal routes, privacy offices, and representatives do not all handle the same problem. Use the directory to verify the lane, then keep the facts and requested action inside that lane.
Sort the pressure point
Name the barrier first: medical dismissal, records problem, pharmacy delay, medication access, care delay, insurance, Medicaid, or official complaint route.
Build the usable facts
Capture dates, names, exact wording, stated reasons, functional impact, and the one written answer being requested.
Verify the responsible lane
Check whether the issue belongs with a provider office, records department, board, insurer, Medicaid office, federal route, or representative.
Carry only what belongs
Trim private details, match attachments to the route, and keep a copy before using a portal, email, fax, mail, or outside form.
What should carry forward from page to page?
The site should not make a sick patient rebuild the same story from scratch. These are the facts that usually travel safely from a free tool into a records request, route check, appeal packet, or official complaint draft.
- One sentence naming the barrier and the responsible reader.
- Dates, names, exact wording, and the stated reason for any denial, delay, or dismissal.
- Functional impact written in daily-life terms instead of only diagnosis labels.
- One clear requested action and a request for a written response.
- Only the private details or attachments that the route actually needs.
