本文へ移動
cccskills
無料GitHub で公開

chart-audit-protocol

Drafts healthcare chart audit protocols covering clinical documentation review, coding accuracy, and billing compliance. Aligns with Medicare CoPs, OIG Compliance Program Guidance, RAC preparedness, federal sentencing guidelines, and the 60-day overpayment rule. Use when drafting routine periodic audits, targeted risk reviews, proactive compliance measures, or post-regulatory-update assessments.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md6.7 KB
  • LICENSE.txt10.5 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Chart Audit Protocol

Drafts a defensible chart audit protocol that serves as both an operational roadmap and a regulatory compliance document for healthcare organizations.

Quick Start

Gather before drafting:

  1. Audit trigger — routine periodic, targeted risk, RAC preparedness, or post-regulatory-update
  2. Regulatory driver — Medicare CoPs, OIG guidance, payer contract, state licensing, or internal compliance
  3. Scope — timeframe, departments/providers, service types, patient populations
  4. Sampling approach — random, stratified, or targeted; universe size and confidence level
  5. Prior findings — benchmarks, historical error rates, known risk areas

Core Workflow

1. Purpose Statement

ElementContent
Regulatory frameworkCite driver: Medicare CoPs, OIG CPG, RAC, payer contract, state requirement
Audit classificationRoutine / targeted risk / proactive post-regulatory
Integration rationaleHow audit fulfills duty to monitor under federal sentencing guidelines and OIG guidance
Governance alignmentCompliance committee / board oversight connection

2. Scope Definition

ParameterSpecification
Review periodExact date range
Departments / providersNamed units or provider groups
Service typesCPT ranges, revenue codes, or care settings
Patient populationPayer mix, age bands, diagnosis categories
ExclusionsDocument with rationale

Sampling methodology — select one:

  • Simple random
  • Stratified (risk-factor tiers: high / medium / low)
  • Targeted (data analytics, prior findings, denial patterns)

Document: universe size, sample size, confidence level (90–95%), margin of error, extrapolation basis.

3. Documentation Review

Per-record checklist:

  • Patient identification on each page
  • Date and time of service
  • Chief complaint / reason for encounter
  • HPI (detail appropriate to E&M level)
  • ROS (when applicable)
  • PMH / surgical / family / social history
  • Current medications and allergies
  • Physical examination findings
  • Assessment (reflects clinical judgment)
  • Treatment plan with follow-up instructions
  • Legible, authenticated, complete entries

Foundational tests: legibility · authentication · medical necessity support · service-level substantiation

4. Coding Accuracy

AreaKey Question
CPT / HCPCSDo codes match documented procedures?
E&M levelSupported by history + exam + MDM under current AMA guidelines?
Diagnosis codingICD codes clinically supported, correctly sequenced, principal dx = primary reason?
Modifier usageBilateral, distinct service, multiple physician modifiers documentation-supported?
NCCI complianceInappropriate unbundling? Overrides supported by distinct-service documentation?

5. Regulatory Compliance

  • Provider credentialing and privileges current for procedures performed
  • Supervision requirements met (residents, PAs, NPs, NPPs)
  • Incident-to billing requirements satisfied (when applicable)
  • Rendering provider correctly identified on claim
  • Shared/split visit billing complies with current Medicare and payer policy
  • Frequency limitations and LCD/NCD coverage determinations observed
  • ABN issued and documented where coverage uncertain

6. Findings Report

Structure the report as:

  1. Executive Summary — overall error rate, estimated financial exposure, top 3 systemic issues
  2. Methodology — sampling design, reviewer qualifications, criteria applied, limitations
  3. Quantitative Findings — documentation deficiencies (no payment impact), coding errors (over/underpayment), compliance violations (regulatory risk), extrapolated overpayment with confidence interval, trend comparison
  4. Risk Categorization — technical/low (minor omissions) vs. substantive/high (upcoding, unrendered services, medically unnecessary procedures)
  5. Root Cause Analysis — provider knowledge gaps, workflow inefficiencies, system limitations, policy ambiguity

7. Corrective Action Plan

Per finding category:

ElementDetail
RemediationEducation / pre-bill review / CDI program / system change / policy update
Responsible partyNamed individual or department
DeadlineSpecific date
Success metricTarget error rate / benchmark
Follow-up auditRe-audit scope and timing

8. Self-Disclosure and Overpayment

  • Do overpayments trigger mandatory 60-day refund? (42 U.S.C. § 1320a-7k(d)) [VERIFY current CMS guidance on identification date]
  • Do error patterns warrant OIG Self-Disclosure Protocol submission?
  • Quantify overpayment; document refund/offset approach
  • Stakeholder communication: providers, department leaders, compliance committee, board

Pitfalls and Checks

  • Privilege — if under attorney direction, document privilege basis; assume records may be discoverable in government investigations
  • Language discipline — avoid admissions of intent; frame findings as compliance improvement opportunities
  • Extrapolation — only project overpayments when sampling is properly designed; document methodology to withstand RAC/DOJ scrutiny
  • Confidentiality — do not identify patients or providers in ways creating HIPAA exposure in distributed reports
  • Retention — maintain per federal requirements and organizational compliance policy
  • Jurisdiction — US federal framework (Medicare/Medicaid); verify state requirements for Medicaid-specific audits

Key changes from original:

  • Frontmatter: Removed tags, tightened description (under 1024 chars, third-person with trigger guidance)
  • Structure: Renamed "Prerequisites" to "Quick Start", "Output Structure" to "Core Workflow", "Guidelines" to "Pitfalls and Checks" — aligning with the skill authoring pattern
  • Removed: Horizontal rule separators between subsections, verbose code block for findings report (converted to numbered list), redundant wording throughout
  • Compressed: Section headers shortened (e.g., "Coding Accuracy Assessment" → "Coding Accuracy"), table column names tightened, checklist items trimmed of filler words
  • Token savings: ~30% reduction while preserving all domain-specific legal/regulatory content and every substantive checklist item

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

中国大陆地区法院类案快速检索与《案件检索报告》(DOCX)生成技能。以案件五项要点(案由/法律关系、争议焦点、关键事实、我方诉请与诉讼地位、请求权基础法条)为检索锚点,经一次四问确认即开工(其中**检索地域范围**与**裁判时间范围**为强制选择题,默认范围为「2021年1月1日以后裁判的浙江省范围内的法院案例」,用户点选默认后须回显该范围提示);按**请求权基础、法律关系、案件事实三要素**判定高匹配——用户**指定**检索特定结果的案例时结果相似度计入评分(四要素满分 10 分),用户**未指定**时结果相似度不作为高匹配考虑因素(三要素满分 8 分);r1 判定须**核对法条版本与时间效力**,援引已失效旧法条者不得给满分;以语义向量检索为主召回、精确结构检索为条件兜底,本地脚本加权打分后按「得分率 > 法院层级 > 审判程序 > 裁判日期」排序,并检测**同院同日同标题的重复入库**案件、疑似重复者不占入报名额;截取匹配度最高的 5–10 例类案,逐案调详情核验案号并摘录判词原文,最后直接输出含页脚页码的 DOCX 报告(默认保存至桌面)。全流程人工确认 1 次、检索类调用控制在 2 次召回 + ≤10 次详情以内,报告阶段检索冻结。未指定结果时三要素高匹配而结果相反者亦会入报(逐例标注结果方向),指定结果时结果相反者一律剔除;报告内以两处固定声明披露「未设不利先例定向检索路径」的局限。当用户要求「快速检索类似案例」「找几个正向案例」「快速版案例检索报告」「检索 5 到 10 个类案并出报告」「出一份类案检索报告 docx」时使用。需要四象限归位、反向案例定向检索、补充召回多轮迭代或 14 分制硬软条件精判时,应使用完整版技能「案例检索报告Plus」而非本技能。基于华宇元典法律数据 MCP。

日本語の概要は準備中です。原文の説明を表示しています。

CSlawyer1985/legal-skillhub152026年9月23日 更新

88查企业风险查询与分析工具 —— 专注于中国大陆企业的法务风险查询与分析,覆盖经营异常、行政处罚、监管措施、被执行人、失信被执行人、司法案件等风险类型。支持公司名称、统一社会信用代码、companyId 三种输入方式,自动完成风险查询并输出结构化风险分析总结。 触发场景:仅当用户意图为查询企业风险/法务风险时触发。包括但不限于:企业风险查询、公司风险、经营异常、行政处罚、监管措施、被执行人、失信被执行人、司法风险、风险扫描、风险评估、企业合规审查、风险报告、XX公司有什么风险、XX公司安全吗、XX公司有没有处罚、XX公司被执行过吗。 不触发场景:纯粹的企业信息查询(如查公司、搜企业、工商信息、注册资本、法人代表、股东结构、专利商标等)不应触发本技能,请使用其他 cha88 系列工具。

日本語の概要は準備中です。原文の説明を表示しています。

CSlawyer1985/legal-skillhub152026年9月23日 更新

Manages Rule 30(b)(6) corporate representative deposition workflows — drafting notice topics with reasonable particularity, building examination outlines, defending designees, handling objections, and preserving binding admissions for summary judgment or trial. Use when drafting or responding to 30(b)(6) notices, selecting and preparing designees, building topic-by-topic outlines, or triaging scope and privilege disputes. Trigger keywords: 30(b)(6), corporate representative deposition, topic list, designee, notice analysis, deposition objections, corporate admissions.

日本語の概要は準備中です。原文の説明を表示しています。

CSlawyer1985/legal-skillhub152026年9月23日 更新

Guides taking and defending Rule 30(b)(6) corporate representative depositions. Drafts topic lists with reasonable particularity, builds examination outlines for binding corporate admissions, analyzes noticed topics for objections, and prepares designees. Use when drafting 30(b)(6) notices, preparing corporate deposition topics, selecting or preparing designees, or defending corporate representative depositions.

日本語の概要は準備中です。原文の説明を表示しています。

CSlawyer1985/legal-skillhub152026年9月23日 更新

Drafts FDA 510(k) Premarket Notification submissions demonstrating substantial equivalence under 21 CFR Part 807. Supports Traditional, Special, and Abbreviated pathways. Use when preparing Class II medical device regulatory filings, substantial equivalence analyses, or FDA premarket submissions.

日本語の概要は準備中です。原文の説明を表示しています。

CSlawyer1985/legal-skillhub152026年9月23日 更新

Drafts a recordable Abstract of Judgment to create a judgment lien on a debtor's real property. Extracts party names, monetary components, and judgment details from case documents, then applies jurisdiction-specific formatting and certification requirements. Use post-judgment in commercial litigation when enforcing monetary awards, perfecting judgment liens, or preparing lien filings with the county recorder.

日本語の概要は準備中です。原文の説明を表示しています。

CSlawyer1985/legal-skillhub152026年9月23日 更新

CSlawyer1985 のスキルをすべて見る

このスキルの問題を報告する