Sources and verification

FRx separates primary public documents, provider manuals, carrier pages, representative confirmations, and community field notes. Public and provider documents are preferred for published billing rules. Field notes may explain a workflow, but they should not be treated as authority unless a stronger source supports them.

Each guide page lists the source family used for that topic. The lookup tool also stores source keys for carrier facts and visible source pills for static references. When a source is outdated, contradicted, or unavailable, the published content should be softened or removed rather than guessed.

Other source families

Correction standard

Corrections should identify the affected page, the claim or rule, the source that supports the correction, and the date of verification. Unsourced corrections are useful leads, but they are not automatically published as facts.

How dates are used

Dates are used to show when a rule, table, or program page was last checked. A date does not guarantee that the rule is still current; it tells the reader how stale the verification might be. High-risk sections should be rechecked more often than background glossary pages.

How unpublished knowledge is handled

Pharmacists often learn useful workflows from rejected claims, successful calls, and repeated plan responses. Those observations can be valuable, but they are not the same as published policy. FRx can use them to guide what should be verified, but public wording should make the uncertainty visible unless a stronger source confirms the rule.

Why source pages are linked

External source links are included so readers can leave FRx and verify a point at the primary location. The purpose is not to make FRx appear authoritative; the purpose is to make the path back to authority easier.