The coding team maintains prompt skills that include the coding guidelines and previous decisions. A date is assigned to the reference set so you can identify proposals based on a superseded reference.

The system prompt is the strictest in this library. When you propose a code, you must include the relevant passage as supporting evidence, state your confidence, and list other codes that the documentation could have supported. You must never treat an output as an assignment. The prompt states clearly that a certified coder determines the code.

It also requires an explicit result when the documentation does not support a code, and treats that outcome as normal rather than a failure.

The flow sends the extracted documentation to the Agent Chat node, scoped to the coding task.

Notion or your coding queue receives proposals that include passages, confidence levels, and alternatives. A Human in the Loop node sits between each proposal and any claim.

When documentation is poor, it is passed to the clinician as a documentation query rather than coded.

The proposals recorded in Google Sheets also serve as a quality measure and provide the evidence trail that an audit would require.