PFS Analyzer
Extracts structured data from PI plaintiff fact sheets and initial disclosures, reconciles against draft builder responses, and produces an issues memo with variance flags and full source traceability.
All output requires attorney review before service or filing.
Quick Start
- Gather source documents (PFS, provider lists, wage docs, insurance disclosures, builder draft)
- Extract providers, employers, and insurance/lien entities with source citations
- Reconcile extractions against builder draft — flag all variances
- Deliver builder-ready output + lawyer-facing issues memo
Intake Checklist
Ask every time unless user says "use defaults" or "just draft":
- PFS / Initial Disclosures — executed PFS, FRCP 26(a)(1) packet, or MDL CMO form
- Medical provider list — specials spreadsheet, treatment chronology, HIPAA auth list
- Wage loss package — employer verification, pay stubs, W-2s, tax returns
- Insurance disclosures — EOBs, PIP/MedPay, lien letters, subrogation notices, Medicare/Medicaid status
- Client intake notes — internal questionnaires with details possibly omitted from PFS
- Draft builder responses — discovery responses to validate
- Forum/jurisdiction — federal vs. state court
- Key context — DOI, prior injury history, date range, cash-pay/LOP/workers' comp, pharmacy list, employment gaps >6 months
Defaults (if user doesn't respond): federal court, FRCP 26(a)(1) framework, all available docs, partial output if incomplete.
If any source is missing, label output "Partial" and identify what is absent.
Core Workflow
1. Build Extraction Map
Every extracted data point must include:
| Field |
Format |
| Source document |
"Doc 1, p. 4" or Bates range |
| Verbatim text |
Exact wording from source |
| Confidence |
High (explicit with address + dates) / Medium (listed, missing details) / Low (inferred, needs verification) |
Rules:
- Untraceable facts must not be presented as extracted data
- Preserve spelling in
verbatim_name; create separate normalized_name
- Never silently correct spelling, expand abbreviations, or merge duplicate-looking entities
- Distinguish treatment facility from billing entity
2. Extract Medical Providers
Per provider, capture: name (verbatim + normalized), type (hospital/clinic/physician/PT/imaging/pharmacy/lab/ambulance), address/phone/fax, service dates, NPI, records/bills status, category (injury-related / pre-existing / billing-lien), source citation.
Rules:
- Pre-DOI treatment → "Prior/Pre-existing" (never omit)
- Separate radiology reads, pathology, facility fees as distinct billing entities
- Referrals are not treatment encounters
- Do not collapse multiple locations of a provider network
- Flag potential non-retained treating experts
- Include pharmacies, PTs, imaging, labs — not only physicians
3. Extract Employment & Wage Loss
Per employer, capture: legal name (+ DBA), address/contacts, job title/schedule/pay rate (exact phrasing), start/end dates, wage documentation, injury impact (first missed date, total days, PTO, return status), benefits applied for (STD/LTD/SSDI/workers' comp).
Rules:
- Preserve vague references as "reported estimate per disclosure"
- Distinguish employer from worksite (staffing agencies)
- Capture self-employment separately
- Flag mitigation issues and employment gaps
4. Extract Insurance, Liens & Prior Claims
Per entity, capture: insurer/lienholder name (verbatim), plan type, member/group/claim/policy IDs (distinguish each), named insured, contact info, lien status (asserted/pending/final + amount), source citation.
Rules:
- Extract only what documents contain — never guess limits, coverage, or validity
- Letter of protection is not an insurance lien
- Silent on Medicare → flag: "Confirm Medicare beneficiary status and SSDI; may trigger MSP reporting"
- Capture prior accidents/claims/settlements; flag for builder consistency
5. Reconcile Against Builder Draft
Three-dimension diff:
| Dimension |
Check |
Flag |
| Completeness |
Entity-by-entity |
"Missing in builder" / "New — confirm supplementation" |
| Consistency |
Names, dates, amounts |
"Spelling mismatch" / "Date conflict" / "Amount discrepancy" |
| Characterization |
Builder vs. disclosure |
"Overstates" / "Understates" |
Priority levels:
- RED ALERT — Document contradictions (e.g., PFS says not working but records reference work). Requires attorney intervention before service.
- HIGH — Undisclosed prior accidents, missing providers, inconsistent injury mechanism
- MEDIUM — Spelling variations, missing addresses, incomplete date ranges
- LOW — Formatting issues, optional fields unpopulated
Rules:
- Never silently overwrite builder data
- Distinguish "disclosed but not produced" from "entirely undisclosed"
- Do not override intentional attorney scope narrowing — flag and defer
- Note FRCP 26(e) supplementation timing (state analogs may be stricter)
6. Deliver Output
A. Builder-Ready Output: Separate verbatim_name/normalized_name, include source_citation and confidence per record, match builder schema, include reservation language.
B. Issues Memo (label: DRAFT — Attorney Work Product / For Counsel Review Only):
- Client follow-up questions
- Supplementation needs with timing
- Defense focus areas and impeachment vectors
- Red flags with recommended action
- Entity verification results (NPI checks)
- Privilege flags — exclude attorney-client communications from extraction
Post-Draft Check
Ask after delivering initial output:
- Are RED ALERT/HIGH flags accurate — known explanations to incorporate?
- Providers/employers client mentioned but absent from disclosures?
- Generate supplementation timeline from identified gaps?
- Builder schema match confirmed?
Default: address RED ALERT items first.
Quality Checklist
Compliance Guardrails
- ABA 1.1/1.3: Attorney must verify; LLM extraction does not satisfy competence/diligence
- Model Rule 1.6: Mask identifiers in memo (last four only); full values in secure builder fields
- Model Rules 3.3/3.4/4.1: Distinguish documented facts from reported estimates; never assert completeness if record is incomplete
- FRCP 37: Incomplete provider lists are common sanctions targets
- HIPAA: All extracted data is PHI; handle per firm protocols
- Conflicts: Multiple potential claimants → flag for Model Rule 1.7 screening
- Anti-hallucination: Every data point traceable to source; never invent names, dates, identifiers; unverified citations must be flagged
Jurisdiction Notes
- Federal MDL: Follow CMO-mandated PFS headers exactly; non-compliance risks dismissal
- California: CCP governs; plaintiff verification form required
- Florida: Align with Form 1.977 interrogatories (10-year history) [VERIFY]
- Texas: Map to Rule 194 Required Disclosure categories [VERIFY]
- State auth forms: Flag "state-specific medical authorization — attorney to confirm"
1---2name: pfs-analyzer3description: Extracts and reconciles medical provider, wage-loss, and insurance/lien data from personal injury plaintiff fact sheets and initial disclosures against builder draft responses. Use when the user mentions PFS analysis, medical provider reconciliation, wage loss audit, insurance lien tracking, PI discovery reconciliation, builder response validation, MDL plaintiff data extraction, FRCP 26(a)(1) disclosures, treatment chronologies, or specials spreadsheets.4---56# PFS Analyzer78Extracts structured data from PI plaintiff fact sheets and initial disclosures, reconciles against draft builder responses, and produces an issues memo with variance flags and full source traceability.910All output requires attorney review before service or filing.1112## Quick Start13141. Gather source documents (PFS, provider lists, wage docs, insurance disclosures, builder draft)152. Extract providers, employers, and insurance/lien entities with source citations163. Reconcile extractions against builder draft — flag all variances174. Deliver builder-ready output + lawyer-facing issues memo1819## Intake Checklist2021Ask every time unless user says "use defaults" or "just draft":22231. **PFS / Initial Disclosures** — executed PFS, FRCP 26(a)(1) packet, or MDL CMO form242. **Medical provider list** — specials spreadsheet, treatment chronology, HIPAA auth list253. **Wage loss package** — employer verification, pay stubs, W-2s, tax returns264. **Insurance disclosures** — EOBs, PIP/MedPay, lien letters, subrogation notices, Medicare/Medicaid status275. **Client intake notes** — internal questionnaires with details possibly omitted from PFS286. **Draft builder responses** — discovery responses to validate297. **Forum/jurisdiction** — federal vs. state court308. **Key context** — DOI, prior injury history, date range, cash-pay/LOP/workers' comp, pharmacy list, employment gaps >6 months3132**Defaults** (if user doesn't respond): federal court, FRCP 26(a)(1) framework, all available docs, partial output if incomplete.3334If any source is missing, label output **"Partial"** and identify what is absent.3536## Core Workflow3738### 1. Build Extraction Map3940Every extracted data point must include:4142| Field | Format |43|---|---|44| Source document | "Doc 1, p. 4" or Bates range |45| Verbatim text | Exact wording from source |46| Confidence | **High** (explicit with address + dates) / **Medium** (listed, missing details) / **Low** (inferred, needs verification) |4748Rules:49- Untraceable facts must not be presented as extracted data50- Preserve spelling in `verbatim_name`; create separate `normalized_name`51- Never silently correct spelling, expand abbreviations, or merge duplicate-looking entities52- Distinguish treatment facility from billing entity5354### 2. Extract Medical Providers5556Per provider, capture: name (verbatim + normalized), type (hospital/clinic/physician/PT/imaging/pharmacy/lab/ambulance), address/phone/fax, service dates, NPI, records/bills status, category (injury-related / pre-existing / billing-lien), source citation.5758Rules:59- Pre-DOI treatment → "Prior/Pre-existing" (never omit)60- Separate radiology reads, pathology, facility fees as distinct billing entities61- Referrals are not treatment encounters62- Do not collapse multiple locations of a provider network63- Flag potential non-retained treating experts64- Include pharmacies, PTs, imaging, labs — not only physicians6566### 3. Extract Employment & Wage Loss6768Per employer, capture: legal name (+ DBA), address/contacts, job title/schedule/pay rate (exact phrasing), start/end dates, wage documentation, injury impact (first missed date, total days, PTO, return status), benefits applied for (STD/LTD/SSDI/workers' comp).6970Rules:71- Preserve vague references as "reported estimate per disclosure"72- Distinguish employer from worksite (staffing agencies)73- Capture self-employment separately74- Flag mitigation issues and employment gaps7576### 4. Extract Insurance, Liens & Prior Claims7778Per entity, capture: insurer/lienholder name (verbatim), plan type, member/group/claim/policy IDs (distinguish each), named insured, contact info, lien status (asserted/pending/final + amount), source citation.7980Rules:81- Extract only what documents contain — never guess limits, coverage, or validity82- Letter of protection is not an insurance lien83- Silent on Medicare → flag: "Confirm Medicare beneficiary status and SSDI; may trigger MSP reporting"84- Capture prior accidents/claims/settlements; flag for builder consistency8586### 5. Reconcile Against Builder Draft8788Three-dimension diff:8990| Dimension | Check | Flag |91|---|---|---|92| Completeness | Entity-by-entity | "Missing in builder" / "New — confirm supplementation" |93| Consistency | Names, dates, amounts | "Spelling mismatch" / "Date conflict" / "Amount discrepancy" |94| Characterization | Builder vs. disclosure | "Overstates" / "Understates" |9596Priority levels:97- **RED ALERT** — Document contradictions (e.g., PFS says not working but records reference work). Requires attorney intervention before service.98- **HIGH** — Undisclosed prior accidents, missing providers, inconsistent injury mechanism99- **MEDIUM** — Spelling variations, missing addresses, incomplete date ranges100- **LOW** — Formatting issues, optional fields unpopulated101102Rules:103- Never silently overwrite builder data104- Distinguish "disclosed but not produced" from "entirely undisclosed"105- Do not override intentional attorney scope narrowing — flag and defer106- Note FRCP 26(e) supplementation timing (state analogs may be stricter)107108### 6. Deliver Output109110**A. Builder-Ready Output**: Separate `verbatim_name`/`normalized_name`, include `source_citation` and `confidence` per record, match builder schema, include reservation language.111112**B. Issues Memo** (label: DRAFT — Attorney Work Product / For Counsel Review Only):1131. Client follow-up questions1142. Supplementation needs with timing1153. Defense focus areas and impeachment vectors1164. Red flags with recommended action1175. Entity verification results (NPI checks)1186. Privilege flags — exclude attorney-client communications from extraction119120## Post-Draft Check121122Ask after delivering initial output:1231. Are RED ALERT/HIGH flags accurate — known explanations to incorporate?1242. Providers/employers client mentioned but absent from disclosures?1253. Generate supplementation timeline from identified gaps?1264. Builder schema match confirmed?127128Default: address RED ALERT items first.129130## Quality Checklist131132- [ ] Every field has source citation or labeled "client to confirm"133- [ ] Forum-specific law references match actual jurisdiction134- [ ] Provider names checked against CMS NPI Registry; unverifiable names flagged135- [ ] Treatment dates consistent with DOI; pre-DOI marked "Prior"136- [ ] Date formats consistent; no false precision from estimates137- [ ] Identifiers transcribed accurately; OCR-sourced values flagged138- [ ] All provider types included (pharmacies, PTs, imaging, labs)139- [ ] No omission construable as concealment (adversarial review)140- [ ] Builder output matches schema constraints141- [ ] All variances shown — nothing silently overwritten142143## Compliance Guardrails144145- **ABA 1.1/1.3**: Attorney must verify; LLM extraction does not satisfy competence/diligence146- **Model Rule 1.6**: Mask identifiers in memo (last four only); full values in secure builder fields147- **Model Rules 3.3/3.4/4.1**: Distinguish documented facts from reported estimates; never assert completeness if record is incomplete148- **FRCP 37**: Incomplete provider lists are common sanctions targets149- **HIPAA**: All extracted data is PHI; handle per firm protocols150- **Conflicts**: Multiple potential claimants → flag for Model Rule 1.7 screening151- **Anti-hallucination**: Every data point traceable to source; never invent names, dates, identifiers; unverified citations must be flagged152153## Jurisdiction Notes154155- **Federal MDL**: Follow CMO-mandated PFS headers exactly; non-compliance risks dismissal156- **California**: CCP governs; plaintiff verification form required157- **Florida**: Align with Form 1.977 interrogatories (10-year history) [VERIFY]158- **Texas**: Map to Rule 194 Required Disclosure categories [VERIFY]159- **State auth forms**: Flag "state-specific medical authorization — attorney to confirm"