← Arclight Readiness NavigatorCONTENT HISTORY

Update to Arclight Readiness Navigator

Snapshot Oct 8, 2026 · 18:03 UTC · version 0.3.0

Collection source: downloaded plugin package.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Build a de-identified wound-care evidence-readiness map for a Medicare audit or denial. Use for episode timelines, conservative-care history, wound measurements, product/application records, claim-line reconciliation, missing-evidence questions, and provider-validation lists. Do not use for a final appeal letter, legal conclusions, or invented clinical rationales.",
  "included_files": [
    {
      "relative_path": "references/evidence-schema.md",
      "size_in_bytes": 2848
    }
  ],
  "name": "wound-care-evidence-map",
  "skill_md_contents": "---\nname: wound-care-evidence-map\ndescription: Build a de-identified wound-care evidence-readiness map for a Medicare audit or denial. Use for episode timelines, conservative-care history, wound measurements, product/application records, claim-line reconciliation, missing-evidence questions, and provider-validation lists. Do not use for a final appeal letter, legal conclusions, or invented clinical rationales.\n---\n\n# Wound-Care Evidence Map\n\nBuild an auditable evidence map before drafting advocacy. Separate what the record says from what someone later explains.\n\n## Shared operating rules\n\nRead and apply [public-workflow.md](../../references/public-workflow.md) for proportionate answers, de-identified inputs, source verification, and user-requested support. Carry these rules across skill transitions; do not repeat the opening notice.\n\n## Workflow\n\n1. Identify the service, claim line, date or episode, stated denial issue, and controlling policy supplied by the user.\n2. Read [references/evidence-schema.md](references/evidence-schema.md).\n3. Build an episode timeline with one row per clinically or administratively meaningful event.\n4. Reconcile clinical notes, orders, product records, claim lines, remittances, submissions, and decisions. Never assume one record stands in for another.\n5. For each issue, cite the exact record location supplied by the user: document, date, page or section, and short neutral paraphrase.\n6. Label evidence as `contemporaneous`, `retrospective explanation`, `external clinical evidence`, `policy`, or `missing`.\n7. Identify contradictions and gaps as questions for the treating provider or records owner. Do not resolve them by inference.\n8. Identify the longitudinal core record that could proactively answer the current issue and foreseeable downstream theories, without treating a larger packet as automatically better.\n9. Produce the evidence map and provider-validation list. Do not draft the reviewer-facing narrative unless asked to use the focused appeal skill.\n\n## Required output\n\n### Episode overview\n\n- Services and dates at issue\n- Wound/site and episode boundaries\n- Denial issues to be answered\n- Records reviewed and records missing\n\n### Evidence matrix\n\n| Issue | Requirement or reviewer statement | Supporting record | Location | Evidence type | Strength | Gap/question |\n|---|---|---|---|---|---|---|\n\n### Episode timeline\n\nInclude wound status and measurements, standard/conservative care, response or failure, infection/vascular/offloading/nutrition factors when relevant, product selection, applications, quantities and wastage where relevant, outcomes, orders/signatures, and claim/submission events.\n\n### Claim-to-record reconciliation\n\n| Claim line/date | Code/product/units | Record support | Product or order support | Decision treatment | Reconciled? |\n|---|---|---|---|---|---|\n\n### Provider-validation questions\n\nList only questions that require clinical or firsthand confirmation. RCM personnel may collect the answers but must not supply clinical facts themselves.\n\n### Drafting readiness\n\nClassify the record as `ready`, `ready with stated limitations`, or `not ready`, with the specific reason.\n\n## Guardrails\n\n- Never convert an observational pattern, product label, barcode prefix, or later declaration into proof of a clinical fact not documented at the time.\n- Do not treat missing text as proof that care did not occur; call it a documentation gap.\n- Do not recommend altering an original record. Any lawful correction or delayed entry must be transparent, dated, attributed, and handled under applicable policy and organizational procedure.\n- Do not advise that an addendum automatically cures a gap. Preserve the original; any later entry must use the actual current date, identify its author, reflect firsthand knowledge or actual recollection, and be clearly labeled as retrospective.\n- Do not equate record imperfection with fraud or medical necessity failure.\n- Do not infer patient identity or re-identify a de-identified record.\n"
}

SHA-256 of public snapshot: 1fb34744ae9e327da377721eaa060c2eb416d53a261cbc3933d69fe90ed3b310