Medical records summaries and ICD candidates: source, version and review design

Treat chart summaries, coding suggestions and quality checks as separate outputs. Summaries organize records, candidate codes propose options to validate, and quality queries identify gaps. None automatically establishes a diagnosis, final coding authority or submission permission.

This is integration planning, not a hospital delivery or outcome report. For a hypothetical inpatient record, establish intended use, approved data, the applicable code version and responsible reviewers before selecting a processing method. No fixed handling-time, adoption or reimbursement improvement is promised.

Summaries must lead back to the record

Organize records by event and time while retaining the source document, version, author, timestamp and passage. Retrieval is one way to gather relevant material; RAG is not mandatory for every chart task. Volume, document quality and existing interfaces influence the choice.

Separate recorded information, conflicts and missing material. Preserve documented diagnostic and procedural text rather than inferring undocumented diagnoses from medication, symptoms or fragments. Citations facilitate inspection but do not prove that a passage supports the summary.

If coding uses a summary, preserve access to complete source records so omitted conditions are not silently propagated. Reviewers need correction, return and stop options, not an obligation to choose one generated candidate.

Confirm the coding system, version and documentation

ICD-10-CM diagnosis coding and ICD-10-PCS procedure coding are different systems. Establish jurisdiction, date, setting, official version and approved review process. Separately verify that a candidate exists, its combination is valid and documentation supports it. Confidence and prompts do not replace these checks.

The CMS April 2026 ICD-10-PCS guidelines describe seven characters and valid table combinations. Their Medical/Surgical section example has this structure:

Approach and device are not the seventh axis. Check other sections against their own tables, and do not confuse PCS with ICD-10-CM seventh-character conventions. This dated US inpatient PCS source verifies structure; it is not Taiwan's current NHI coding, CC/MCC or payment authority.

Leave insufficient documentation as a query for authorized staff under applicable rules. Revenue is not a reason to prefer additional diagnosis suggestions. Historical human-assigned codes also require version and expert assessment before serving as evaluation references.

Quality queries do not rewrite the chart

Connect date conflicts, unsupported statements and missing documents to their sources for designated staff. A test, procedure or symptom does not authorize the system to add a diagnosis or alter a physician's record.

Agree who receives a query, who may correct it, how reasons are recorded and when summaries or candidates are regenerated. Documentation quality, coding errors and payment denials are separate outcomes; improvement in one does not establish another.

Keep evidence for the pilot

Separate development and held-out evaluation material. Record source, tool, model and code versions. Responsible owners establish use-specific acceptance criteria; changed sources or versions need impact assessment and stopping conditions. These are validation tasks to perform, not clinical validation achieved by this article.

Bound data and intended use

Before chart processing, establish purpose, medical-data conditions, recipients, access and retention under Taiwan's PDPA. On-premises deployment or de-identification does not automatically supply a lawful basis. Control sensitive content in operational and debugging records too.

For diagnostic or treatment functions, assess actual intended use, functions and risk through TFDA's scope guidance. Calling a function a summary, or having a reviewer, does not automatically exclude medical-device requirements.

Use the existing healthcare scope and RAG work assessment to establish sources and responsibilities. Agree inspectable outputs and interfaces before deciding whether to pilot.