Kenya’s first DHA-certified claims system. The fourth company certified by DHA.
Submit through Ginja AI’s certified claims layer without separately certifying your existing HMIS for that connection. Your facility keeps its own registrations, data protection and other applicable obligations.
- Certified entity
- Eden Care Proactive Ltd (Ginja AI)
- Scope
- Claims system
- Registry
- CERT-2026-992OE5NR
Less to build. Faster to connect.
| What matters | Build / HMIS vendor | With Ginja AI |
|---|---|---|
| Time to connect | Build, test and secure approvals. | 1–2 weeks once prerequisites are ready. |
| Changes & maintenance | Your team or vendor maintains it. | Ginja AI manages connection updates. |
| Assurance | Assemble the integration’s evidence. | Certified claims system; security evidence available for review. |
Agree the connection scope before you start.
Security and governanceGet connected.
Get more claims paid.
Lamu catches errors before submission and helps resolve rejections and follow up payments. One connection. Less repeat work.
See how Lamu worksFive things we need.
Ginja AI leads configuration, testing and onboarding.
- 01
SHA registration
Provider registration and required approvals.
- 02
ODPC registration
Your facility’s data-controller certificate.
- 03
Technical contact
An available HMIS vendor or IT lead.
- 04
System access
Permissions and information to connect and test.
- 05
Claims through Ginja AI
Use SHA Connect for the agreed submissions.
Before you connect.
Do we need to replace our HMIS?
No. We check compatibility with your vendor or IT team, then connect to your existing system.
What does Ginja AI’s certification cover?
Our certified claims layer lets you keep your existing HMIS without a separate HMIS certification for that connection. Your facility still needs its own registrations and approvals, and must submit the agreed claims through Ginja AI.
Who handles implementation and go-live?
Ginja AI configures the connection, tests submissions and responses with your IT team, and provides focused staff onboarding. Your team confirms readiness and approvals before go-live.
How long does implementation take?
SHA integration takes 1–2 weeks once registrations, payer credentials, access and technical support are ready. The wider platform rollout takes another 2–3 weeks; CDS is available in early access.
Can we connect one facility first?
Yes. Start with SHA Connect at one facility, then expand across your group or add Lamu, Aria and Clinical Decision Support.
What about private insurers?
SHA Connect handles SHA submissions. Lamu also supports claims checks and follow-up for connected private insurers.
Ready to connect?
Tell us your hospital and HMIS. We’ll confirm what you need and when you can go live.