SHA CONNECT · KENYA

Keep your HMIS. Get SHA-ready in 1–2 weeks.

See SHA Connect
Ginja AI
See a demo
Clinical Decision SupportEarly access

Smarter decisions. Better care.
Backed by evidence.

Bring patient history, relevant guidance and safety checks into the HMIS your clinicians already use. See what matters, review the evidence and document the decision.

Ginja AI suggests. Your clinicians decide.

Inside your existing HMIS
01Context02Prompt03Decision
PATIENT CONTEXT
EncounterMedication review
Order in progressAmoxicillin 500mg · 3× daily
Allergy statusNot yet confirmed
GUIDANCE
Context for clinician review Confirm the missing detail before completing the order.

The allergy field is incomplete. Review the patient’s history and update the record.

Source: facility protocol · Allergy documentation
Clinician reviews, decides and documents.
The gap we close

Clinical knowledge has to reach the decision.

Busy shifts leave little time to search guidelines or piece together a patient’s history. Ginja AI brings relevant context and guidance into the workflow, while there is still time to act.

Guidance that fits the patient.

Bring relevant care pathways into view alongside symptoms, history and existing conditions. Clinicians assess what applies.

More consistent care

Safety concerns, surfaced earlier.

Flag potential drug interactions, allergy conflicts and dosage concerns for clinical review before an order is finalised.

Earlier review of risks

Protocols grounded in your practice.

Use agreed Kenyan Ministry of Health guidance, facility protocols and formularies that reflect your resources and care setting.

Locally relevant decisions
Responsible by design

Useful guidance.
Fewer interruptions.

Decision support should make the next action clearer. Keep the reasoning visible and clinical judgement with the people delivering care.

  1. 01

    Relevant, not relentless.

    Prompts are prioritised by severity and clinical relevance. Configured thresholds help keep routine noise out of the consultation.

  2. 02

    Show the reason. Open the source.

    Review why an insight appeared, the patient context behind it and the cited evidence. Assess its relevance before acting.

  3. 03

    Your standards. Your control.

    Clinical leads agree alert thresholds, supported protocols and updates to guidance. Clinicians retain control of decisions, orders and the final record.

CDS + Aria + Lamu

Better decisions. Stronger records.
Cleaner claims.

CDS informs the decision. Aria captures the clinician’s reasoning. Lamu checks the claim against that reviewed record. The evidence stays with the care, reducing the need to reconstruct it when a payer asks a question.

See how the three fit together

Clinical decisions follow patient needs. Payer requirements are handled in the claims workflow.

  1. Decide

    Clinical Decision Support

    Review context and evidence.

  2. Document

    Aria

    Capture the reviewed reasoning.

  3. Claim

    Lamu

    Check the claim against the record.

  4. Learn

    Clinical leadership

    Review feedback. Refine workflows.

Learning means clinician-led review and approved workflow changes.
Early access

Start with your clinical leads.

Agree the care setting, test the guidance and measure what changes before a wider rollout.

  • Source relevance and clinical accuracy
  • Time spent finding guidance
  • Useful prompts and clinician acceptance
Security and governance
Does Ginja AI make the clinical decision?

No. It brings context and evidence to qualified clinicians. They assess the recommendation and remain responsible for decisions, orders and the final record.

Can we use our own protocols and formularies?

Yes, within the agreed deployment scope. Your clinical leads select supported sources, tune alert thresholds and agree how guideline and formulary updates are reviewed.

What if information is missing or no alert appears?

Clinicians must resolve missing or conflicting information and review the underlying sources. No alert is not confirmation that a treatment is safe; CDS supplements clinical judgement and existing safety procedures.

Does this guarantee compliance or claim payment?

No. CDS supports clinical review and documentation. Facility compliance obligations remain with your organisation, and payer acceptance depends on the claim and applicable terms.

How is patient information handled?

Role-based access and audit trails support oversight. Your governance team reviews permitted data uses, including any model-improvement uses, in the agreement before implementation.

What do we need to get started?

Start with one care setting, a clinical lead and an IT contact. Your team provides system access, protocols and formularies; Ginja AI configures the agreed sources and checks alongside your HMIS.

How long does rollout take?

For a combined rollout, SHA integration takes 1–2 weeks once prerequisites are ready; wider products take another 2–3 weeks. Your clinical leads agree the CDS early-access scope before rollout.

How do we prepare staff and approve go-live?

Ginja AI trains clinicians to review prompts, sources and recommendations in their existing workflow. Your clinical leads test relevance and accuracy, resolve launch-critical issues and approve the care setting before wider use.

See Ginja AI in action

Give every decision stronger support.

See the patient context, the prompt and the evidence in a workflow your clinicians recognise.

Speak to our medical team

Start with a conversation.

Tell us your hospital and what you’d like to see. No claims or patient information are needed.

Prefer email? support@ginja.ai