compliance-review

Verify provider prior authorization documentation against a 10-item completeness checklist.

Updated Apr 29, 2026
One-click install
npx skills add https://github.com/otey247/Multi-Agent-Provider-Prior-Auth --skill compliance-review-otey247
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compliance-review
Source: https://github.com/otey247/Multi-Agent-Provider-Prior-Auth/tree/main/agents/compliance/skills/compliance-review
Command: npx skills add https://github.com/otey247/Multi-Agent-Provider-Prior-Auth --skill compliance-review-otey247

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates the completeness of provider prior authorization submissions to prevent payer rejections due to missing patient data, credentials, or required documentation.

Core Features & Use Cases

  • 10-item completeness checklist covering patient information, provider credentials, insurance details, diagnosis codes, procedure codes, clinical notes quality, NCCI awareness, and service type classification.
  • Flags missing or incomplete documentation before submission to ensure auditability and smoother payer review.
  • Use Case: A clinic packages a prior authorization and runs this skill to surface gaps (e.g., missing ICD-10 codes, missing NPI, nonspecific notes) before sending to the payer.

Quick Start

Inspect the PA package and surface any missing or incomplete items on the 10-item checklist.

Frequently Asked Questions about compliance-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a prior authorization documentation review checklist?

A prior authorization documentation review checklist validates patient information, provider credentials, insurance details, ICD-10 codes, procedure codes, clinical notes, NCCI risk, and service type before submission to prevent payer rejections.

How do I check a prior authorization package for missing ICD-10 or NPI data?

Run an automated compliance review on the prior authorization package to surface gaps like missing ICD-10 codes or NPI data, verifying completeness against a 10-item checklist before sending it to the payer.

How does NCCI awareness affect prior auth submission approval?

NCCI awareness flags potential procedural edits or risks in the prior authorization package, ensuring the documentation meets payer review standards and auditability requirements before submission.

What fields are non-blocking when validating prior authorization documentation?

Non-blocking fields for prior authorization documentation validation include Insurance ID, Insurance Plan Type, NCCI awareness, and Service Type, allowing submission even if these specific items are incomplete.

Can I verify clinical notes quality before sending a prior auth package?

Yes, you can verify clinical notes quality by running an automated compliance review that checks for nonspecific or incomplete notes within the prior authorization package before submission.

Why does my prior authorization submission get rejected by the payer?

Prior authorization submissions are rejected by payers due to missing patient data, incomplete provider credentials, or missing required documentation like ICD-10 codes and clinical notes, which a review checklist prevents.