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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Chairside
Chairside brings the front desk, the clinic, insurance, contracts, billing and your team into one system, so nothing gets typed twice and the end of the month stops being a hunt through spreadsheets. It started in dentistry, where it goes deep, and it grows with you: one branch or ten, in Arabic or English.
We built it around one promise. The system never stands between a doctor and a patient, and when it does have to say no, it tells you why in plain words.
See the live demonstration chairside.theronix.app Book a guided walkthroughWhat your team gets
All of it is running in the live demonstration. Come and try it.
Built by listening to dentists
- A chart that grows with the patient, from a child's first teeth to a full adult smile.
- Mark up an X-ray or a photo in seconds, while the original stays exactly as it was taken.
- Gum charting that shows at a glance what has changed since the last visit.
- Treatment plans and estimates your patients understand before they say yes.
- Consent forms in Arabic and English, signed on the screen, for the patient or a parent.
The whole visit in one place
- Notes, diagnoses, orders and results together, so nobody goes looking.
- Laboratory and radiology in the same flow, even for tests sent to another lab.
- Prescriptions, sick notes and referrals printed on your own letterhead.
Fewer rejections, less chasing
- Know what each insurer will ask for before anything is sent, and have it ready.
- Your team sets the rules for each insurer, without waiting for us.
- What is already on file is gathered for you.
Every agreement you sign, on both sides of the ledger
The money coming in and the money going out, managed in one place.
- Insurers and corporate clients sit beside suppliers, landlords and maintenance providers.
- Renewals and changes that never lose what was agreed before.
- A clear view of what is coming up for review, before anything quietly expires.
- Built for the agreements you actually have, not only the ones software usually expects.
Money that adds up
- Patient and insurer shares worked out for you, visit by visit.
- A cash drawer that is counted, checked and explained every time it closes.
- Tax invoices with the ZATCA QR code on them.
Your team, looked after
- Staff records and licences, with a heads-up well before a licence runs out.
- Rosters, leave and overtime in one place, ready for payroll.
- Everyone sees what their role needs, and nothing more.
A calmer front desk
- One file for each patient, whichever branch they walk into.
- A diary that shows at a glance who is waiting, who is in the chair and who has gone home.
- No bookings with a doctor who is off that day.
Clinical documentation and coding
The physician speaks or types the note the way they always have. While the patient is still in the room, the codes the note supports appear beside it, each with its reason, and a short, fair question comes up when the note leaves something unclear. Nothing enters the record until the clinician agrees.
- Speak in Arabic or English and read the note in English.
- ICD-10-AM codes in well under a second, each showing why it was suggested and the standard behind it.
- The questions a good coder would ask, asked at the right moment and worded so they lead nobody to an answer.
- It reads like a clinician: what the patient has, what was ruled out, and what belongs to a relative are kept apart.
- Investigations and medicines from published guidelines, offered for the clinician to accept or ignore.
- Built to sit inside the record system a hospital already runs.
Four commitments, and they are testable
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.
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.
Nothing is deleted
Corrections supersede, credit or withdraw with a reason attached. A record has to explain itself to an auditor two years later.
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.
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