How the FRx lookup tool and the guide library work together
A walkthrough of the public content layer and the professional lookup tool.
FRx has two layers. The guide library explains common pharmacy billing workflows in ordinary language. The lookup tool is a faster interface for carrier entries, rejection codes, program notes, patient assistance programs, forms, and price-ratio data. Both layers should remain available because they serve different tasks.
The guide library is intended for reading and onboarding. It gives context to decisions that are easy to oversimplify in a table. The tool is intended for the moment when staff already understand the problem and need a quick lookup. Moving every explanation into the tool would make the tool slower. Moving every table into the guide library would make the articles unreadable.
Start with a guide when the concept is unclear
If the issue is coordination of benefits, vacation supply, authorization type, or intervention-code documentation, the guide should be read first. The guide explains what to check before the claim is submitted. This reduces trial-and-error behaviour.
Use the tool when the task is specific
If the task is to find a carrier entry, compare a rejection code, print a form, search a patient assistance program, or identify a meter pseudo-DIN, the tool is faster. Its global search and panel navigation are built for point-of-care reference.
- Guides explain the reasoning behind workflows.
- The tool shortens lookup time for specific entries.
- Source pages show where rules came from.
- Contact and correction pages provide a feedback path.
- The sitemap and source pages make the public reference structure easier to navigate.
Why this structure was chosen
A JavaScript-heavy lookup tool can be useful at the pharmacy counter, but it is not the best way to teach a workflow. The static guide layer explains the reasoning behind common billing problems without making the professional tool slower.
The public pages should therefore stay linked and maintained. The tool should remain prominent, but it should not be the only way a new reader learns what the site does.
Maintenance responsibilities
The two-layer structure only works if both layers are maintained. When a guide explains a workflow, the related tool entry should point in the same direction. When a carrier field changes, the tool should be updated first because it affects counter workflow. When the reason behind a rule changes, the guide should be updated so readers understand the context.
For pharmacy users, the tool prevents the editorial pages from becoming too slow for real counter use. For new readers, the guides prevent the tool from becoming an unexplained data dump. The value comes from the combination.
FRx guide page · Static editorial reference · Last reviewed 2026-05-02