Patient data deserves plain answers.
A hospital system holds the most sensitive information people share. TibaIQ puts access control, audit and encryption at the core of the platform, and this page explains how.
Two questions, answered separately.
- Privacy
- What TibaIQ records about a patient, why, who can see it and for how long. Your organisation decides; the platform enforces it.
- Security
- Keeping records confidential, accurate and available: only the right people see them, every change is traceable, and care continues through an outage.
Security controls in the platform.
Built into every module, not sold as an add-on.
Role-based access
Access scoped to role, facility and department, so each person sees what their work requires and nothing else.
Audit trail
Every read and write recorded with who, what and when, and kept for 20 years.
Sign-in and break-glass
Multi-factor sign-in for staff. Emergency access to a restricted record requires a reason and is reviewed afterwards.
Encryption
Records are encrypted in transit and at rest, and so are backups.
Continuity and offline
An encrypted offline queue on each device, an optional on-site server, and a clear outage banner. Records sync when the connection returns.
Backups and restore
Daily backups, with restores tested on a schedule rather than assumed.
Built to Kenyan law.
Built to the Kenya Data Protection Act 2019 and the Digital Health Act 2023, and the regulations made under them.
Ownership
Your organisation is the data controller and owns its records. TibaIQ processes them on your instructions.
Purpose and consent
Records are used for care, billing and the reporting the law requires, with consent captured where it is needed.
Retention
Retention periods follow the Health Information Management Procedures and your own policy.
Export on exit
Existing records stay available read-only, with a full export, whatever happens to the subscription.
Hosting and transfers
Hosting and backup arrangements are set out in each customer’s contract. Any transfer outside Kenya follows the Act’s consent and safeguard rules.
Payers and tax
Built for SHA and KRA eTIMS inside the platform, so claims and receipts never pass through separate middleware.
How we build and change TibaIQ.
Tested before release
Every module ships with acceptance tests, and counts as done only when they pass.
Approved configuration
A second person approves each change to a care journey before it goes live, and the change applies only to new visits.
Traceable administration
Changes to users, roles and settings are written to the same audit trail as clinical records.
What tibaiq.com collects.
This website does not collect patient or clinical information. The demo request form asks only for business contact details. It is protected by Cloudflare Turnstile, and repeated submissions are limited. We keep a one-way hash of your IP address for rate limiting, never the address itself, and use no advertising or analytics cookies.
Reporting a security concern
If you believe you have found a security issue in TibaIQ or this website, send it through the request form with “Security report” at the start of the message. Do not include patient information or data that is not yours.
Documents
- Privacy noticeHow tibaiq.com handles demo requests. Updated 22 October 2026.
- Terms of useTerms for using tibaiq.com. Updated 22 October 2026.
Questions security teams ask.
Who can see our patients’ records?
Only your staff, within the roles, facilities and departments you assign. Emergency access outside those limits needs a recorded reason and is reviewed.
What happens if the internet goes down?
Care continues. Devices queue work in encrypted storage, an optional on-site server keeps the whole facility running, and records sync when the connection returns.
Where is our data hosted?
The hosting and backup arrangements for each customer are set out in its contract. Any transfer of personal data outside Kenya follows the Data Protection Act 2019.
How does Digital Health Agency certification work?
Under the Digital Health Act 2023, the Digital Health Agency assesses each health information system, including data exchange and the SHA claim process. Approval lasts two years, each hospital also needs its own go-live approval, and the Agency lists approved systems in a public registry. This answer explains the process only and is not a statement of TibaIQ’s certification. Check the registry for every vendor you evaluate, and ask us for TibaIQ’s position during your evaluation.
Can we export our data?
Yes. Your organisation owns its records and can export them in full, during the subscription or after it ends.
What happens when someone leaves?
Their access ends when their account is deactivated. Their audit history stays, so you can still see everything they did.
Talk to us about security.
Bring your IT lead and your data protection officer, and your security questionnaire. We walk through access, audit, encryption and continuity on the working product.