Why keeping up with SUT changes became a full-time job

SUT (Turkey's national health payment regulation) is not a fixed document — it is a living body of rules. Payment lists, points, package definitions and exceptions change regularly. For a billing team, that means reading every change, interpreting it, and reflecting it into existing processes — often without formal training or tooling.

The problem is not only how often the rules change, but how scattered the changes are. One update touches a line item while another circular changes the documentation requirement for the same item. The intersection of two separate changes is invisible when you look at each in isolation.

The result: institutions either carry a constant "reading SUT" workload, or ignore the risk. Neither is sustainable.

In this post we look at why change-tracking does not scale, and how rule knowledge can be made executable.