INDUSTRY FIELD GUIDE
Pharmacy benefit formulary version records for AI
A formulary can change between two dates, and a product entry can look alike across plans.
NAICS 524292 · Pharmacy Benefit Management and Other Third Party Administration of Insurance and Pension Funds
A formulary can change between two dates, and a product entry can look alike across plans. CMS’s public formulary guidance and coverage determination overview show why plan, version, and administrative status matter. A benefits administrator can evaluate record matching with dummy codes and no member information. CMS formulary guidance · CMS coverage determination overview
Invent two plans, two versions of a product list, and a change record with an effective date. Add a question from before the change and a second case where a plan identifier is missing. Ask which document supports each response. Require the assistant to flag the incomplete record and route it for review. Do not test treatment advice, drug selection, or approval of a benefit.
Keep real member, prescription, provider, manufacturer pricing, and contract information private. Use artificial product names and confirm that no row originated in a production claims system.
Describe a synthetic formulary evaluation
Original Fiund exercise
Plan identity is required before selecting a dated product-list entry
Two imaginary plans list a wholly artificial product named DEMO-P. The task concerns document matching, with no medication, patient, prescription or treatment recommendation.
| Record | Source | What it records |
|---|---|---|
| FV1 | Plan A list versions | A-v1 lists DEMO-P in practice category C1. A-v2 changes it to C2, effective day 15; approval record links the change to Plan A only. |
| FV2 | Plan B list | B-v1 keeps DEMO-P in C1 throughout the practice period. No A-to-B equivalence rule supplied. |
| FV3 | Questions | Q1: Plan A, date day 12. Q2: DEMO-P, date day 20, plan identifier missing. No member determination records included. |
Question for the model
Which document supports Q1, and can Q2 be answered from the product name and date alone?
Show the reference answer and checks
FV1's A-v1 supports Q1 because day 12 precedes A-v2's day-15 change. Q2 lacks a plan identifier: FV1 and FV2 supply different day-20 categories for the same fictional product. Report the missing plan and route the incomplete question for review instead of selecting the most recent list across all plans. A list-category match does not constitute a member-specific coverage or benefit approval.
- Applying a future list revision to an earlier question.
- Assuming that identical product names make two plans' lists interchangeable.
Fields to preserve
- Plan and artificial product ID
- Defines the applicable list.
- Version and effective interval
- Supports date-specific retrieval.
- Question completeness and review state
- Marks missing scope before responding.
Test another case
Add Plan B to Q2. Require B-v1/C1 even though A-v2 is a newer document.
Use synthetic product codes and original lists. Exclude member, prescription, pricing and contract information; no drug-selection or coverage decision is requested.
Discuss a contribution
Describe the sources you control, the task they could support and what has already been checked. Use the existing-data assessment for an archive or the collection brief for a new recording project. The contributor agreement defines Fiund’s licensing authority and compensation. A guide or fictional exercise does not establish an accepted collection or a sale.