medical-invoice-consolidator-audit

Consolidate administrative, medical, and financial audit outputs into a canonical output.json.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/arkangelai/skills --skill medical-invoice-consolidator-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: medical-invoice-consolidator-audit
Source: https://github.com/arkangelai/skills/tree/main/medical-insurance-audit/medical-invoice-consolidator-audit
Command: npx skills add https://github.com/arkangelai/skills --skill medical-invoice-consolidator-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates the outputs of administrative, medical, and financial audits into a single canonical output.json to drive glosa generation and payer communications.

Core Features & Use Cases

  • Unifies admin, medical, and financial audit results into a single consolidated artifact.
  • Assigns Anexo 6 causales and computes concepto_final, en_devolucion, and summary metrics for downstream workflows.
  • Generates the canonical output.json consumed by the glosa generator and email notifier, and handles case-level observations.
  • Validates presence of required inputs (admin_checklist_output.json, medical_checklist_output.json, financial_checklist_output.json) and propagates audit_perspective.

Quick Start

Run this skill after the three audit outputs are present to produce a consolidated output.json ready for dashboard and billing workflows.

Frequently Asked Questions about medical-invoice-consolidator-audit

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

FAQPage Schema
How do I consolidate medical invoice audit outputs into a single glosa case?

A canonical glosa output requires validation of instrument fields, propagation of audit perspectives, and computation of totals across all invoice items before generating the final JSON.

What inputs are required to generate a consolidated Anexo 6 glosa output?

The consolidation process unifies these three audit outputs, assigns Anexo 6 causales, and computes final concepts and summary metrics for downstream billing workflows.

How does audit perspective propagation work during medical invoice consolidation?

This process validates instrument fields and structures case-level observations and findings across all invoice items to maintain data integrity for downstream systems.

Can I generate glosa payer communications without all three audit checklists?

Without the complete administrative, medical, and financial audit results, the canonical output.json cannot be reliably generated for downstream dashboards.

What downstream systems consume the consolidated medical invoice audit output?

It structures case-level observations, computes en_devolucion amounts, and assigns Anexo 6 causales for seamless downstream integration.