Theronix

Healthcare software that reaches the machine in the room.

Revenue cycle, clinical records, human resources and finance, built for hospitals and polyclinics. Connected to the analysers, the imaging suites, the card terminals and the payer rails that most systems leave to somebody else.

Enterprise healthcare systems Sixteen years of practice Saudi Arabia and the Gulf
16
years building systems clinics run on
4
domains under one record: revenue, clinical, people, finance
9
standards spoken natively, from HL7 to DICOM to NPHIES
1
rule engine, governed as data rather than written into code
What we build

Four systems that agree with each other

Most clinics run a billing system that has never met the clinical record, and a payroll that has never met the rota. The reconciliation happens in a spreadsheet, once a month, by somebody who is good at it. We build the four as one record so the reconciliation is not a job.

Revenue cycle

RCM

Eligibility, prior approval, coding, claims, batches, remittances and the appeal. Every claim traceable back to the visit that produced it, and every rejection to the field that caused it.

Clinical

EMR

The visit end to end: chart, consultation, orders, results, consent and discharge. Coded as it is written, so the claim is a consequence of the record rather than a retyping of it.

People

HR & workforce

Employment, credentials and licence expiry, monthly rosters that have to add up, leave, and attendance taken from the building itself rather than from a machine at the door.

Money

Finance

Cash control that is counted and verified by two people, tax documents that satisfy the authority, and figures a finance officer can defend line by line.

What we connect

The part other vendors quote separately

A hospital's real cost is not the software licence. It is the six months of interface work nobody quoted for: the analyser that speaks a thirty-year-old protocol, the panoramic machine that wants a worklist, the card terminal that will not tell the ledger what it took. We do that work, and we have been doing it long enough to know which parts are hard.

Laboratory analysers

Results filed against the accession number on the tube, and worklists sent back so nobody programs a rack by hand. Instrument results arrive as preliminary: a machine is not a second person.

HL7 v2MLLPASTM E1394ORU^R01LOINCUCUM

Radiology and imaging

Modality worklist so the patient is never retyped at the machine and no study is filed against the wrong person, images to a proper store, and the dose read from the machine instead of guessed.

DICOM MWLC-STOREMPPSRDSR doseDICOMweb

Payment terminals

The amount pushed to the terminal, the approval and retrieval reference read back automatically. The card never passes through the application, so the clinic stays out of card-industry scope.

SPAN / madaECRsettlement reconciliation

Attendance over wifi

Presence taken from the network the staff already carry a phone onto, rather than a queue at a fingerprint reader at seven in the morning. It feeds the roster and the payslip, not a separate report.

WPA2 EnterpriseRADIUSgeofence

Payer and national rails

Eligibility, approvals and claims on the national exchange, with the code systems each field is required to carry rather than the ones that happened to be handy.

NPHIESFHIR R4ICD-10-AMSBSSNOMED CT

Tax authority

Phase-two e-invoicing: a signed UBL document per invoice, an unbroken hash chain, clearance for standard invoices and reporting for simplified ones. Onboarding is a screen, not a project.

ZATCA FatooraUBL 2.1XAdESsecp256k1
IN THE CLINIC Analysers Imaging and CBCT Card terminals Wifi attendance One record revenue · clinical · people · finance rules held as data, not as code every figure traceable to its visit OUTSIDE IT Payers, NPHIES Tax authority Banks and acquirers
The whole path, owned end to end: a value leaves an analyser and arrives on a claim without being retyped, and without a second vendor in the middle of it.
The insurance cycle

Rules the clinic can change without calling us

Every payer wants something different asked, coded and attached, and every one of them changes its mind. A system that holds those rules in code needs a release each time a circular is issued, which means the clinic waits, and in the meantime somebody just remembers.

So we hold them as governed data. What needs approval before it is done, which limit a charge counts against, what a claim is checked for before it may go, which codes are valid for a diagnosis: each is a row somebody in the clinic can read, change and switch off, with the circular it came from recorded beside it.

The rules are also honest about what they are for. They stop paperwork. They never stop treatment.

Approval
Ask the payer first. By service, category, diagnosis or substance, per agreement, with the clause it came from.
Limits
Per visit or per episode. Which threshold a charge counts against, and how the window is measured.
Coding
Checked as written. Billable level, one code per family, sex and age edits, each citing its standard.
Claims
Before it goes. Blocking and advisory checks, each naming the field and the reason a payer would reject it.
Terms
The clock. Submission windows counted from the visit or the accounting period, per contract.
Documentation
CDI. Queries raised while the patient is still there, worded so they lead nobody to an answer.
In production

Chairside

A platform for polyclinics and hospitals. One patient record across every clinic in the building: dentistry, obstetrics and gynaecology, paediatrics, general practice, with the department that dentistry actually needs. a tooth chart, periodontal charting, treatment plans and estimates, sitting beside the antenatal record and the growth chart rather than in a second system.

Registration and the appointment board, the clinical note, consent in two languages, laboratory and radiology worklists, invoicing, insurance claims, the roster and the cash drawer. Multi-branch from the first day, because a group that opens a second site should not be buying software again.

It is the same argument as the rest of this page, made concrete. Every refusal is a sentence in plain words. Every rule is a row somebody can edit. A physician is never blocked from treating. Sixteen chapters of the guide are inside the product, beside the screens they explain.

See the live demonstration chairside.theronix.app
How we work

Four commitments, and they are testable

  1. Care is never blocked

    Consent, approval and payment checks stop paperwork. A clinician is never held up by one, and every gate has a person who can waive it on the record.

  2. The system says what it means

    A refusal names the rule, why it exists and where the fix is, in a sentence. Silence and error codes are how software loses the room.

  3. Nothing is deleted

    Corrections supersede, credit or withdraw with a reason attached. A record has to explain itself to an auditor two years later.

  4. The rules belong to the clinic

    Held as data with their source cited, so the people who answer to the regulator are the people who can change them.

Enquiries

Tell us what the current system will not do

The useful first conversation is usually about the part that is presently done by hand: the month-end reconciliation, the rejections nobody can explain, the interface that was quoted and never delivered.

Leave a message and a person reads it. There is no queue and no sales sequence.

  • A walkthrough of the live system, on your own terms
  • An honest answer on whether a machine you own can be connected
  • A written scope before anybody is quoted

We use what you write here to answer you, and for nothing else.