medical-invoice-fix-review

To apply auditor comments to a medical invoice JSON file, this skill reads comments.json chronologically, classifies intents like modify_finding or approve, and patches the output.json accordingly. It updates hallazgos and resumen fields while appending detailed audit-log entries for traceability.

Managing a claim-denial workflow requires processing auditor feedback chronologically until final approval is achieved. This skill classifies comment intents, applies JSON patches to output.json, enforces safety invariants like total_glosado limits, and supports escalation flows when edits cannot be resolved immediately.

Classifying structured intents from auditor feedback involves parsing comments.json to identify actions such as modify_finding, add_finding, approve, or escalate. This skill automatically categorizes each comment, applies the corresponding JSON patch to output.json, and logs the change to maintain a strict audit trail.

Yes, you can signal PDF regeneration automatically after applying JSON patches to invoice findings. This skill sets the pdf_regeneration_needed flag whenever changes affect hallazgos or resumen, ensuring the PDF output reflects the latest auditor corrections while leaving the actual regeneration to a separate step.

Safety invariants enforced when applying auditor edits to medical invoice claims include preventing negative valor_glosado values and ensuring total_glosado never exceeds total_facturado. These guards protect the output.json integrity during the JSON patch application process across all processed auditor comments.

Yes, you need a separate comments.json file containing new auditor entries to process medical invoice fixes. The skill watches this file for new comments, applies them chronologically to output.json, updates resumen and hallazgos, and logs every change to maintain full audit traceability before final approval.