Helios Casemix Engine

Know exactly why every contact lands in its DRG.

DK-DRG grouping in your browser or through an API, with the rule, route and codes behind every result. One logic per tariff year; every change has a reason and a second reviewer.

Illustration with example codes — not a real contact.

What it does

Grouping you can explain, change and trust.

Group any way you work

One contact, a whole forløb, an Excel workbook of thousands, or your own systems through the API. Every result shows the DRG, its name, tariff, trim point, length of stay and the rule that decided it.

See why, not just what

Atlas draws the rules as a diagram. Route a contact through it and every box tells you whether it said YES or NO — and exactly which of the codes you entered made it so.

Keep every rule accountable

Edit rules and group codes in Developer. Every change asks for a reason and lands in the change log; a second person approves it before the logic can become your API default or go to customers. Built-in checks flag codes no rule uses and groups no code carries.

One logic per tariff year

Import a DK-DRG release — the seven official table files — or build a logic by hand. Duplicate it to start next year’s version, export it back to the standard files, and publish a read-only page per year for your customers.

Your own SKS classification

Upload your own SKScomplete.txt for the years you work with — one file can cover several years. Years without a file of your own use the Helios standard catalog, and the SKS drilldown lets you search codes by code or text.

Made for teams and systems

A client portal with roles, team management and optional two-factor sign-in. API keys for your systems. The engine works in Danish and English, and grouping never needs a patient name or civil registration number.

Every result comes with its reasons

  • The DRG and its name
  • Tariff, trim point and length of stay
  • The rule that decided it
  • The codes that made each box say YES
Built for the Danish system

DK-DRG and SKS, the way your coders know them.

The engine works on the official DK-DRG table files and the Danish SKS classification, so a logic imported from a release behaves like the release — and a logic you build by hand uses the same rule columns.

How it works

From contact to DRG — and back to the rule.

01

Enter or upload

Type sex, age, diagnoses and procedures — searching the SKS catalog by code or text — or upload a workbook, or send contacts through the API.

02

Group

The engine applies the active logic for the right tariff year and returns the DRG with its tariff, trim point and length of stay.

03

Read the route

Open Atlas and follow the contact through the rules, with the deciding codes named at every step.

04

Change and approve

Fix a rule, give a reason, and let a second person approve it. Nothing reaches your API default or your customers until it is signed off.

Data and access

Your logics stay yours.

Users see only their own customer’s logics, keys and activity. Patient names and civil registration numbers are never needed. Read how the engine handles data before you decide what to send it.

How the engine handles data  ·  Read the API guide

See it on your own contacts.

A first conversation is a working session, not a pitch — bring a few real contacts and we will group them together.