# Hls Identify Government Subpoena Issues > Reviews a government healthcare subpoena and supporting materials to identify potential temporal scope objections, relator indicators, audit privilege risks, retaliation exposure, successor-liability issues, parallel-state-investigation coordination needs, and spoliation concerns. - Skill: `finchipaiorg/hls-identify-government-subpoena-issues` (Agent Skill) - Install (CLI): `npx skillmds@latest add finchipaiorg/hls-identify-government-subpoena-issues` - Raw SKILL.md: https://api.skillmd.com/api/skills/finchipaiorg/hls-identify-government-subpoena-issues/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Security - Author: FinchipAIOrg (https://skillmd.com/u/finchipaiorg) - Updated: 2026-09-22 - Page: https://skillmd.com/skills/finchipaiorg/hls-identify-government-subpoena-issues --- # Skill: Identify Issues in Government Subpoena — Healthcare Provider ## 1. Subject-matter triage - Treat the subpoena packet as an investigative issue-spotting exercise, not a merits brief. - First map the document set: subpoena terms, definitions, return date, supporting exhibits, internal complaints, audit materials, personnel actions, and any acquisition or state-agency materials. - Identify whether the record reflects one investigation or several overlapping inquiries; if multiple matters exist, analyze each separately rather than blending them. ## 2. Failure modes the skill is correcting - Missing temporal-scope objections when the requested period predates entity formation, operational control, or acquisition of the relevant business. - Failing to connect whistleblower indicators, complaint timing, and personnel actions into a coherent relator-risk assessment. - Overlooking privilege-waiver risk where audit materials move between counsel-directed and management-directed tracks. - Understating retaliation exposure tied to terminations, discipline, credentialing actions, restrictive covenants, or other adverse actions near the investigative trigger. - Ignoring successor-liability questions when the business was bought, integrated, or billed under inherited identifiers. - Failing to coordinate federal, state, and internal responses when parallel investigations are underway. - Missing preservation problems where the litigation hold came late or collection gaps suggest spoliation. ## 3. Legal frameworks / domain conventions that apply - Temporal scope objections depend on the entity’s actual operational and recordkeeping period, the subpoena’s date range, and any acquisition date; analyze whether the demand reaches beyond the period in which the recipient held the relevant records or conducted the relevant business. - Relator analysis in healthcare fraud matters should account for sealed qui tam structure and the indicia commonly associated with whistleblower activity; cite the governing statutory and procedural authorities implicated by the source materials, including False Claims Act provisions and any referenced sealing or retaliation framework. - Audit privilege analysis should distinguish attorney-client privilege, work-product protection, and business-record status; assess whether dissemination to non-legal personnel or mixing of tracks undermines protection under the applicable privilege doctrines. - Retaliation exposure should be analyzed under the anti-retaliation statute or regulation implicated by the facts, with attention to whether the adverse action followed protected complaint activity, cooperation, or refusal conduct. - Restrictive covenant enforcement against a likely relator can compound retaliation risk even if framed as contract enforcement; evaluate the restraint in light of the applicable employment and retaliation authorities. - Successor-liability analysis should test whether transaction language, assumed operations, inherited billing identifiers, continuity of workforce, or continuity of claims creates exposure notwithstanding internal allocation provisions. - Parallel-state coordination requires aligning responses across agencies to avoid inconsistent testimony, selective production, or privilege waiver. - Preservation analysis should apply the litigation-hold and spoliation framework tied to the first reasonable anticipation of investigation or litigation. ## 4. Analytical scaffolds 1. Build a source map: enumerate the subpoena demand categories, time periods, custodians, and any referenced incidents, then analyze each category on its own terms. 2. Temporal-scope review: compare the requested date range to formation, licensure, acquisition, integration, and operational milestones; flag overreach where the demand reaches earlier than the relevant business period. 3. Relator indicator review: examine complaint logs, exit timing, internal escalations, protected disclosures, and personnel changes; infer whether a sealed whistleblower filing is a plausible driver of the subpoena. 4. Privilege review: identify whether the audit was counsel-directed, management-directed, or hybrid; determine whether sharing, forwarding, or mixed circulation may have waived protection. 5. Retaliation review: assess disciplinary measures, terminations, schedule changes, non-renewals, credentialing actions, or covenant enforcement occurring near complaint or investigation onset. 6. Successor-liability review: analyze acquisition documents, assumed operations, inherited identifiers, continuity of services, and any liability allocation language that may not bind the government. 7. Parallel-investigation review: identify state, federal, payer, or licensing inquiries and reconcile the response strategy to avoid inconsistency. 8. Preservation review: determine when the duty to preserve likely attached, compare it to hold issuance and collection steps, and identify any destruction or loss after that point. 9. Return-date review: assess whether the production window is workable and whether an extension or staged production request is warranted. ## 5. Vertical / structural / temporal relationships - Always analyze the timeline vertically: pre-investigation events, complaint activity, audit activity, personnel actions, subpoena service, hold issuance, and production deadlines. - Tie each issue to the source-set relationship that creates it: subpoena term to record custodian, audit finding to complaint, adverse action to protected activity, acquisition to liability allocation, and preservation duty to data destruction. - If the documents reveal multiple business units, facilities, or billing streams, separate the analysis by unit and period instead of treating them as a single enterprise. - When a subpoena references both federal and state matters, identify the overlap and any sequencing problem in responding to one forum while preserving defenses in another. ## 6. Output structure conventions - Write a memo organized by severity, with a clear ordinal scale defined once at the top and applied uniformly to every issue. - For each issue, use a compact four-part structure: issue, controlling authority, source-based analysis, and recommended action. - Every issue discussion should include the relevant scale or scope drawn from the source materials, the document or clause that interacts with it, and the downstream consequence for the client. - Use legal authorities by name and citation style when the source set identifies them, and otherwise cite the governing statute, regulation, rule, or doctrine supporting the proposition. - End with a discrete Recommended Actions block that assigns each step to a role and ties it to a concrete deadline or urgency marker grounded in the subpoena response process. - Keep the memo practical and prioritized; the purpose is to surface issues and response actions, not to argue them exhaustively.