Skip to content

Frequently asked questions

The questions hospitals, clinics and pharmacies ask about the patient record, claims, moving across and the agreement, before a proposal.

The patient record and billing

How does one patient record work?

Registration, billing, claims and the pharmacy counter read one record rather than keeping their own. A returning patient is found rather than re-created, so the same person does not exist three times with three balances. A bill, a deposit and a guarantee letter refer to the same episode.

Do we have to replace our clinical systems?

No. Clinical systems stay where they are. asasii health covers the administrative work around care, and idataraya integrates it with the systems the provider already runs rather than replacing working clinical software.

How do deposits and the final bill work?

Deposits at admission, interim bills during a stay and the final bill at discharge are built against the same episode rather than assembled at the end, and the deposit nets against the final bill. What has been paid, what is estimated and what is outstanding are on screen while the patient is still at the desk.

Claims and the pharmacy

How are panel and insurer claims followed up?

Guarantee letters, claim submission and the follow-up when a claim is queried or short-paid are tracked against the episode the claim belongs to. The desk can say where a claim has reached without calling the insurer. Finance sees which claims are ageing before they become write-offs.

How does the pharmacy work with the rest?

The pharmacy dispenses at the counter against the prescription and the patient record, and stock is drawn down as it is dispensed. Reordering works from the actual position rather than a count at month end. Payment at the pharmacy counter posts against the bill.

Moving across and the agreement

How do we move across without closing the counter?

It goes live at one clinic, branch or department first, before a group commits to it. Outstanding balances, active episodes and open claims move with the data, and the previous path stays available until the new one is trusted. The plan assumes the counter keeps working throughout, and idataraya is present when it goes live.

Where does it run, and who holds the data?

In the provider's own data centre or cloud account, where its data policy requires. idataraya installs it and keeps it current, and the provider's team holds the keys, the backups and the data. Where the data lives is the provider's decision, not a condition of the product.

What does the yearly agreement cover?

Software updates and patches, the customisations made for you, monitoring and incident response, severity-based response and restoration targets, and the changes a growing group needs as it opens branches and adds panels. Hosting stays with you. It is a fee, not a subscription.

Still have a question?

Send it with the provider and the number of sites, and an engineer replies within one working day.