Revenue recovery
Surfaces underpayments, unbilled procedures, copay rate errors, lab bundling gaps, and missed DRG packages.
Recover the SGK revenue already in your claims
Bilun checks claim exports against the Sağlık Uygulama Tebliği: underbilling, pre-submit risk, and the clause behind each finding. It sits beside MEDULA — it does not replace it.
4,757
In-force SUT paragraphs indexed today
3,250+
Numbered rule clauses in the database
47
Registered executable rule engines
/ Capabilities
What Bilun does
A layer over claim data that connects invoice lines to the official tariff — so finance and coding see where money is at risk and why.
Pre-submission compliance
Flags surcharge prohibitions (EK-2G, §1.9.3), copay exemptions (EK-1A), and EK-2C-1 rate mismatches before claims leave — not after MEDULA rejects them.
MEDULA rejection follow-up
Maps rejection codes to the offending claim line and a SUT-anchored fix list so teams know what to correct before they rebill.
Inspectable rule coverage
Indexed SUT clauses, bundling rules, and engine coverage are displayed in the app alongside source gazette text.
Compliance · Pre-submit
Pre-submission compliance that stops rejections
Flags unbundled materials, missing pre-authorizations (EK-3C-1), and required medical justifications before claims leave — not after MEDULA rejects them.
Revenue · Source text
Instant claim validation with quantified savings
Calculates recoverable potential savings in real time, checks EK-3/C procedure pairings, and pins rule violations to exact SUT articles like §3.1.1(10).
Rules · Source text
3,250 indexed clauses, verified against the gazette
47 executable rule engines with transparent tracking of automated rules and reference-only gaps — with published legal text attached.
/ Process
How it works
Three steps from claim export to actions your team can defend.
01
Upload claim data
CSV or HBYS export — Bilun reads the fields; the file stays under your control.
02
Apply the rulebook
Lines are checked against SUT clauses and tariffs. Findings that fire are tied back to source text.
03
Act on findings
Revenue gaps, compliance flags, and rejection follow-ups — ready for finance and coding.
When the inputs are missing, Bilun says unavailable — it never invents a number that won't survive an audit.
That distinction is the product. Precise-looking estimates that cannot be defended cost hospitals more than the gaps they pretend to close.
/ Trust
Built for audit, not theater
Hospital buyers need defensibility. Bilun is built so findings can be checked against the gazette — and so claim files stay under your control.
Source-traced findings
Recommendations are pinned to published SUT article text — an audit trail you can open, not a score you have to trust.
Exactness first
When claim lines or tariff inputs are missing, Bilun says unavailable. It does not invent a TRY amount that will not survive review.
Your claim data, your control
CSV / HBYS exports stay under hospital control. The SUT layer is public tebliğ data and needs no patient file to run the rulebook.
Made for hospital teams
Finance, coding, and clinical reviewers share the same rule-backed view — ranked actions, not another vanity dashboard.
/ About
What does Bilun mean?
Our first project, which won first place at the Acıbadem Hackathon, was named İlay—meaning full moon. At the Harvard Hackathon, we expanded the system to unite clinical triage with SUT reimbursement intelligence under one roof.
Yet we quickly realized where the deepest friction in healthcare finance truly lay: billing. Every month, hospitals lose millions in legitimate SGK revenue to unbilled procedures and tariff mismatches without ever noticing.
Bilun means half-moon—the half of İlay dedicated entirely to billing integrity. We are not a full moon; we are intentionally half. Because we chose laser focus over breadth: recovering the revenue already sitting in your claims.
Safa Oksuz — Founder & CEO · LinkedIn ↗
/ Demo
Book a demo
Pick a preferred date and time (Europe/Istanbul). We will confirm by email and walk through Bilun on a claim set that matches your workflow.