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: >4 Extracts and reconciles medical provider, wage-loss, and insurance/lien data5 from personal injury plaintiff fact sheets and initial disclosures against6 builder draft responses. Use when the user mentions PFS analysis, medical7 provider reconciliation, wage loss audit, insurance lien tracking, PI8 discovery reconciliation, builder response validation, MDL plaintiff data9 extraction, FRCP 26(a)(1) disclosures, treatment chronologies, or specials10 spreadsheets.11---1213# PFS Analyzer1415Extracts 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.1617All output requires attorney review before service or filing.1819## Quick Start20211. Gather source documents (PFS, provider lists, wage docs, insurance disclosures, builder draft)222. Extract providers, employers, and insurance/lien entities with source citations233. Reconcile extractions against builder draft — flag all variances244. Deliver builder-ready output + lawyer-facing issues memo2526## Intake Checklist2728Ask every time unless user says "use defaults" or "just draft":29301. **PFS / Initial Disclosures** — executed PFS, FRCP 26(a)(1) packet, or MDL CMO form312. **Medical provider list** — specials spreadsheet, treatment chronology, HIPAA auth list323. **Wage loss package** — employer verification, pay stubs, W-2s, tax returns334. **Insurance disclosures** — EOBs, PIP/MedPay, lien letters, subrogation notices, Medicare/Medicaid status345. **Client intake notes** — internal questionnaires with details possibly omitted from PFS356. **Draft builder responses** — discovery responses to validate367. **Forum/jurisdiction** — federal vs. state court378. **Key context** — DOI, prior injury history, date range, cash-pay/LOP/workers' comp, pharmacy list, employment gaps >6 months3839**Defaults** (if user doesn't respond): federal court, FRCP 26(a)(1) framework, all available docs, partial output if incomplete.4041If any source is missing, label output **"Partial"** and identify what is absent.4243## Core Workflow4445### 1. Build Extraction Map4647Every extracted data point must include:4849| Field | Format |50|---|---|51| Source document | "Doc 1, p. 4" or Bates range |52| Verbatim text | Exact wording from source |53| Confidence | **High** (explicit with address + dates) / **Medium** (listed, missing details) / **Low** (inferred, needs verification) |5455Rules:56- Untraceable facts must not be presented as extracted data57- Preserve spelling in `verbatim_name`; create separate `normalized_name`58- Never silently correct spelling, expand abbreviations, or merge duplicate-looking entities59- Distinguish treatment facility from billing entity6061### 2. Extract Medical Providers6263Per 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.6465Rules:66- Pre-DOI treatment → "Prior/Pre-existing" (never omit)67- Separate radiology reads, pathology, facility fees as distinct billing entities68- Referrals are not treatment encounters69- Do not collapse multiple locations of a provider network70- Flag potential non-retained treating experts71- Include pharmacies, PTs, imaging, labs — not only physicians7273### 3. Extract Employment & Wage Loss7475Per 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).7677Rules:78- Preserve vague references as "reported estimate per disclosure"79- Distinguish employer from worksite (staffing agencies)80- Capture self-employment separately81- Flag mitigation issues and employment gaps8283### 4. Extract Insurance, Liens & Prior Claims8485Per 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.8687Rules:88- Extract only what documents contain — never guess limits, coverage, or validity89- Letter of protection is not an insurance lien90- Silent on Medicare → flag: "Confirm Medicare beneficiary status and SSDI; may trigger MSP reporting"91- Capture prior accidents/claims/settlements; flag for builder consistency9293### 5. Reconcile Against Builder Draft9495Three-dimension diff:9697| Dimension | Check | Flag |98|---|---|---|99| Completeness | Entity-by-entity | "Missing in builder" / "New — confirm supplementation" |100| Consistency | Names, dates, amounts | "Spelling mismatch" / "Date conflict" / "Amount discrepancy" |101| Characterization | Builder vs. disclosure | "Overstates" / "Understates" |102103Priority levels:104- **RED ALERT** — Document contradictions (e.g., PFS says not working but records reference work). Requires attorney intervention before service.105- **HIGH** — Undisclosed prior accidents, missing providers, inconsistent injury mechanism106- **MEDIUM** — Spelling variations, missing addresses, incomplete date ranges107- **LOW** — Formatting issues, optional fields unpopulated108109Rules:110- Never silently overwrite builder data111- Distinguish "disclosed but not produced" from "entirely undisclosed"112- Do not override intentional attorney scope narrowing — flag and defer113- Note FRCP 26(e) supplementation timing (state analogs may be stricter)114115### 6. Deliver Output116117**A. Builder-Ready Output**: Separate `verbatim_name`/`normalized_name`, include `source_citation` and `confidence` per record, match builder schema, include reservation language.118119**B. Issues Memo** (label: DRAFT — Attorney Work Product / For Counsel Review Only):1201. Client follow-up questions1212. Supplementation needs with timing1223. Defense focus areas and impeachment vectors1234. Red flags with recommended action1245. Entity verification results (NPI checks)1256. Privilege flags — exclude attorney-client communications from extraction126127## Post-Draft Check128129Ask after delivering initial output:1301. Are RED ALERT/HIGH flags accurate — known explanations to incorporate?1312. Providers/employers client mentioned but absent from disclosures?1323. Generate supplementation timeline from identified gaps?1334. Builder schema match confirmed?134135Default: address RED ALERT items first.136137## Quality Checklist138139- [ ] Every field has source citation or labeled "client to confirm"140- [ ] Forum-specific law references match actual jurisdiction141- [ ] Provider names checked against CMS NPI Registry; unverifiable names flagged142- [ ] Treatment dates consistent with DOI; pre-DOI marked "Prior"143- [ ] Date formats consistent; no false precision from estimates144- [ ] Identifiers transcribed accurately; OCR-sourced values flagged145- [ ] All provider types included (pharmacies, PTs, imaging, labs)146- [ ] No omission construable as concealment (adversarial review)147- [ ] Builder output matches schema constraints148- [ ] All variances shown — nothing silently overwritten149150## Compliance Guardrails151152- **ABA 1.1/1.3**: Attorney must verify; LLM extraction does not satisfy competence/diligence153- **Model Rule 1.6**: Mask identifiers in memo (last four only); full values in secure builder fields154- **Model Rules 3.3/3.4/4.1**: Distinguish documented facts from reported estimates; never assert completeness if record is incomplete155- **FRCP 37**: Incomplete provider lists are common sanctions targets156- **HIPAA**: All extracted data is PHI; handle per firm protocols157- **Conflicts**: Multiple potential claimants → flag for Model Rule 1.7 screening158- **Anti-hallucination**: Every data point traceable to source; never invent names, dates, identifiers; unverified citations must be flagged159160## Jurisdiction Notes161162- **Federal MDL**: Follow CMO-mandated PFS headers exactly; non-compliance risks dismissal163- **California**: CCP governs; plaintiff verification form required164- **Florida**: Align with Form 1.977 interrogatories (10-year history) [VERIFY]165- **Texas**: Map to Rule 194 Required Disclosure categories [VERIFY]166- **State auth forms**: Flag "state-specific medical authorization — attorney to confirm"