Master Prompts for ICD-10 Coding and Medical Billing: Structured Output for Revenue Cycle Teams

Medical coding is not a text-generation task. It is an evidence, classification, and review workflow governed by current code sets, official guidance, payer rules, and accountable professionals.

A master prompt can help organize documented facts, identify missing specificity, and return coding candidates in a stable schema. It should not invent support, treat model memory as the current code book, or submit a final claim without the organization's approved review and validation.

The Source Record Comes First

The model should work only from documentation authorized for the coding workflow.

Use only supplied documentation. Do not infer a diagnosis, condition, service,
laterality, encounter status, causal relationship, or other specificity that is
not supported by the source. Identify missing or conflicting documentation for
qualified reviewer resolution.

An output that sounds clinically plausible is not enough. The candidate must be traceable to documented evidence.

Use the Current Authoritative References

CMS and the National Center for Health Statistics publish official ICD-10-CM coding guidelines by fiscal year. The FY 2026 ICD-10-CM Official Guidelines cover October 1, 2025 through September 30, 2026.

Do not embed a code set in a prompt and assume it remains current. Supply the approved version through a controlled reference or retrieval system, preserve its identity, and require review when the needed authority is unavailable.

ICD-10-CM diagnosis coding, ICD-10-PCS inpatient procedure coding, CPT, HCPCS, payer policy, coverage, and claim edits are related but distinct. One prompt should not blur them into a generic "billing code" task.

Define the Workflow Narrowly

A useful coding-support master prompt might perform one job:

• extract documented diagnoses and relevant qualifiers;
• identify candidate ICD-10-CM codes from an approved reference set;
• flag missing specificity;
• compare documentation with a defined code requirement;
• organize a denial reason for human follow-up;
• produce a pre-bill documentation-completeness review.

It should not perform all revenue-cycle operations in one call.

A Review-Oriented Output Schema

The schema should make evidence and uncertainty visible:

{
  "type": "object",
  "required": ["reference_version", "candidates", "missing_information", "review_required"],
  "additionalProperties": false,
  "properties": {
    "reference_version": { "type": "string" },
    "candidates": {
      "type": "array",
      "items": {
        "type": "object",
        "required": ["candidate_code", "documented_text", "source_location", "status"],
        "additionalProperties": false,
        "properties": {
          "candidate_code": { "type": "string" },
          "documented_text": { "type": "string" },
          "source_location": { "type": "string" },
          "status": {
            "type": "string",
            "enum": ["supported_candidate", "insufficient_documentation", "conflicting_documentation"]
          }
        }
      }
    },
    "missing_information": { "type": "array", "items": { "type": "string" } },
    "review_required": { "type": "boolean" }
  }
}

The label candidate_code is intentional. The output becomes a review queue, not a silent final determination.

Preserve Exact Evidence

For every candidate, require:

• the documented term or statement;
• source document and location;
• relevant qualifiers present in the source;
• required specificity that is absent;
• reference version used;
• reason for escalation.

Do not let the model rewrite weak documentation into stronger documentation. The original wording should remain visible to the reviewer.

Separate Coding From Coverage and Payment

A valid code does not establish coverage, medical necessity, or payment.

CMS notes that standardized coding supports orderly claims processing and that code assignment is distinct from coverage. Medicare also uses separate National Correct Coding Initiative edits to prevent improper payment from certain code combinations. See the CMS coding overview and NCCI program.

Keep those checks in their authoritative systems or controlled rule services. The master prompt can structure inputs and findings; deterministic edits should stay deterministic.

Handle Missing Specificity Correctly

When required documentation is missing, the output should say so.

{
  "candidate_code": null,
  "status": "insufficient_documentation",
  "missing_information": ["required specificity absent from supplied source"],
  "review_required": true
}

Do not ask the model to produce the "most likely" code from contextual hints. That creates unsupported precision.

Protect PHI Throughout the Workflow

Coding data can contain protected health information. User authorization, vendor approval, business associate agreements where applicable, data minimization, encryption, logging, retention, and incident response must be handled outside the prompt.

Read HIPAA-Compliant Master Prompts before connecting a coding-support prompt to real records.

Test With Coding Failure Cases

Use approved, de-identified, or synthetic records that include:

• complete documented specificity;
• missing laterality or encounter detail where relevant;
• uncertain or rule-out language;
• contradictory documentation;
• copied-forward text;
• a code from an outdated reference version;
• a condition absent from the source;
• a valid code that fails a separate payer edit;
• a malformed output object;
• content that should route to a qualified reviewer.

Reviewers should verify both the candidate and the model's use of evidence. A schema-valid unsupported code is a failed output.

The Revenue-Cycle Developer Rule

Developers own a safe evidence pipeline, current reference selection, validation, version traceability, and controlled failure. Coding and billing professionals own final interpretation and submission under applicable guidance and payer requirements. Clinicians own the documentation and clarification processes defined by the organization.

The master prompt should make those handoffs visible instead of hiding them behind one recommended_code field.

Read the Healthcare Master Prompts guide, then browse healthcare workflow structures in the CyWire marketplace.

This article is technical information, not medical, coding, billing, reimbursement, compliance, or legal advice.