About

Built with a practice, not for a market

Katina Online is an Australian company making one thing: the software a psychology practice uses to turn a referral into a funded booking. We are small, and the product is specific, and both of those are deliberate.

Why it exists

It started as one practice's spreadsheet

The first version was built inside a multi-site practice, by the people who were doing the triage. That is why the vocabulary is a practice's vocabulary rather than a CRM's: the thing in the list is a referral, the person is a patient, the group of people is a practice, and the reason a booking cannot happen yet is a named document rather than a status code.

It also explains the shape of the product. The funding scheme is the first question Katina asks, because in an Australian practice the payer decides the paperwork, and the paperwork decides whether the appointment can happen at all. Software written without that experience treats funding as a field on a form.

The company

Who you are contracting with

Katina Online Pty Ltd

ACN 667 690 655. An Australian proprietary company.

Where the data sits

ap-southeast-2 — the AWS Asia Pacific (Sydney) region. Not replicated offshore.

How we are paid

By practices, monthly, at a published price. Patients are never charged and never asked to make an account.

How we work

Three things we have decided not to do

01

We do not publish testimonials

Advertising a regulated health service is constrained in Australia, and the line between endorsing software and endorsing a health service is one we would rather not test with somebody else's registration. Where a practice is willing, we write up what changed and attribute it to a role.

02

We do not claim features we have not built

Our own website advertised an integrated email service that does not exist. Rather than quietly remove the line, every page that could mention it now names it as missing, with a date. That is a more useful signal about how we work than any claim we could make instead.

03

We do not put patient data anywhere it can be read

No clinical field reaches a browser, a log, an analytics tool or a URL. It is the one constraint the architecture is organised around, and it is why some features are slower to arrive than they would otherwise be.

Next

Come and argue with it.

The most useful conversations we have are with practice managers who tell us the funding rule we got wrong. Bring yours.