Services
idataraya proves the system at one site, installs it in the provider's own environment, moves the open work across without closing the counter, and maintains it under one yearly agreement.
Rollout plan and proposal
Send the provider, the number of sites and the systems in use today. An engineer replies with a rollout plan, a migration plan and a proposal. It goes live at one clinic, branch or department first, before a group commits to it.
Installation and moving across
asasii health is installed in the provider's own data centre or cloud account and integrated with the clinical systems already in place. Outstanding balances, active episodes and open claims move with the data, and the previous path stays available until the new one is trusted. A provider cannot pause admissions for a cutover, so the plan assumes the counter keeps working throughout, and idataraya is present when it goes live.
Support and maintenance
One team looks after the system for the life of the agreement. A front desk that cannot bill is not a ticket that waits until Monday, and the people who set up how deposits net against the final bill are the people who answer when a discharge will not close.
- Severity-based response times, measured monthly
- Continuous monitoring from within the provider's environment
- A drilled backup and restore
- Releases, patches and incident response
- Changes as a growing group opens branches and adds panels
The yearly agreement
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.
Security and Malaysian compliance
Patient data carries obligations that ordinary business data does not. The questions IT and audit ask, answered in the system.
Security and data overview- PDPA 2010
- Patient data stays in the provider's own environment.
- Roles
- Access to patient records is scoped to role.
- Single sign-on and MFA
- On every console, with the provider's own identity provider.
- Audit trail
- Every change to a record is logged with who made it.
- Data residency
- Where the data lives is the provider's decision, not a condition of the product.
- The provider's records
- Owned by the provider, with the keys and the backups held by its own team.
See it at your own front desk
Send us the provider, the number of sites and the systems in use today. An engineer replies with a rollout plan, a migration plan and a proposal.