prior-auth-packet-builder

Compile prior authorization packets from case files and payer policy documents.

Updated Dec 6, 2016
One-click install
npx skills add https://github.com/majunbao/learn --skill prior-auth-packet-builder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prior-auth-packet-builder
Source: https://github.com/majunbao/learn/tree/main/openai-agents-python_tags/openai-agents-python-0.14.6/examples/sandbox/healthcare_support/skills/prior-auth-packet-builder
Command: npx skills add https://github.com/majunbao/learn --skill prior-auth-packet-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prior authorization workflows are often manual, slow, and error-prone. This skill automates assembling a concise PA packet from local case files and payer policy documents, reducing turnaround time and increasing accuracy.

Core Features & Use Cases

  • Inspect case/scenario.json and case/transcript.txt to extract relevant case details.
  • Use targeted searches against the policies directory to identify payer requirements, prior auth criteria, referrals, and imaging guidelines.
  • Generate output/policy_findings.md with a concise case summary, matched policy files, prior auth determinations, referral status, and missing information; also create output/human_review_checklist.md for reviewer guidance.

Quick Start

Provide the required files in the workspace and run the skill to produce output/policy_findings.md and output/human_review_checklist.md.

Frequently Asked Questions about prior-auth-packet-builder

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

FAQPage Schema
How do I compile a prior authorization packet from case files and payer policy documents?

Prior authorization packet compilation extracts case details from scenario.json and transcript.txt, searches payer policy documents for matching criteria, and outputs policy findings with a human review checklist.

What is the process for checking payer-specific prior auth criteria against a patient case?

Payer-specific prior auth checks extract case details from local files, query the policies directory for matching guidelines, and produce a policy findings report detailing determinations and missing information.

When do I need to perform a prior auth review or referral validation for healthcare cases?

A prior auth review or referral validation is needed when a healthcare case requires payer-specific policy checks, imaging review, or referral validation before treatment approval. This skill identifies the necessary guidance from local policy documents.

Can I automate generating a human review checklist for prior authorization determinations?

Yes, you can automate generating a human review checklist. The skill outputs a human_review_checklist.md file alongside a policy findings report to guide reviewers through prior authorization determinations and missing case information.

What file formats do I need to provide to start the prior authorization workflow?

To start the prior authorization workflow, provide local case files specifically named case/scenario.json and case/transcript.txt, along with a policies directory containing payer policy documents for targeted searching.

What are the limitations of automating prior authorization packet assembly?

Automating prior authorization packet assembly requires structured local case files and a policies directory. It generates findings and a checklist for human review, meaning a human must still validate the final prior auth determination and handle missing information.