KastHunt PoC Lab

Deployable healthcare AI

Healthcare AI products, customised to your clinic.

The KastHunt PoC Lab is where our working healthcare AI products live — including an ambient AI scribe, adaptive patient intake, referral and no-show recovery, a patient companion, clinical reasoning support, with new products added regularly. We customise it to your workflows, systems and rules, then deploy it in your own environment.

  • Working end to end
  • Customised to your clinic
  • Clinician review built in
PoC Lab workspace Review-first
PHI data Human review
EveStella Clinician

Structured note from live consultation

Turns the visit into a structured note in the clinician's own voice, with codes flagged before signing.

Draft output Review ready
Consultation → structured note
VoiceClinician phrasing retained Visit noteStructured for review CodesFlagged before sign-off
01Capture the consultation signal 02Draft in the clinician’s voice 03Flag codes before sign-off

Explore the workflow

Start with a concrete clinical or patient journey, not a vague AI promise.

Understand the handoff

See what is captured, what is produced, and what still needs review.

Keep people in control

Every concept is framed as a decision-support workflow, not an autopilot.

The Products

Healthcare AI products, ready to customise.

Start with one, or connect several into a single flow from intake to insight.

How we work

How long does it take to deploy a KastHunt product?

We take a working product and shape it to your clinic in four steps. Your first site is typically live within 3-4 weeks, and each further site on the same EHR takes about a week.

Book a free Discovery Workshop
What happens in this step
  • Map each roleWe map how each role works today — front desk, nurses, doctors, specialists and admin.
  • Review your settingWe review your EHR, data rules, consent needs and the regions you operate in.
  • Set a clear scopeYou leave with a clear scope, the product to start with and how we will measure success.
AssemblyAI Deepgram Claude OpenAI FHIR Gemini Groq Docker AWS MedGemma Qwen PostgreSQL MongoDB Redis GitHub

Frequently asked questions

Questions about KastHunt’s healthcare AI products.

Clear answers on cost, timelines, data, EHR integration and how we customise each product for your clinic. Can’t find what you need? Ask us directly.

What is the KastHunt PoC Lab?

The PoC Lab is where KastHunt’s healthcare AI products live. Every product already works end to end. We call it a lab because no two clinics work the same way: each product becomes your full product only after we customise it to your roles, templates, EHR, data rules and region. Your first deployment is your proof of concept — real software, shaped to you.

What comes with every KastHunt product?
  • Your environment: deployed inside your boundary, so patient data stays with you.
  • Clinician review: AI drafts; people approve. Every output has a sign-off point.
  • Audit trail: access logs and decision logs.
  • Privacy controls: PHI masking, de-identification, configurable consent and retention per site.
  • Regional compliance mapping: HIPAA, UK GDPR and NHS standards, Australian Privacy Principles, PIPEDA and provincial law, GDPR, UAE and India rules.
  • Fallbacks: if a model or service fails, work is queued securely or routed to an approved backup.
  • One licence: organisation-wide licensing, not per-seat fees.
Why do healthcare AI tools fail to scale — and how does customisation help?

Most healthcare AI stalls between pilot and full rollout because the tool does not fit local workflows. In one US survey, every responding health system had piloted ambient documentation, but only 14% had fully deployed it. At Providence, voluntary adoption of an ambient AI tool reached only about 8% of eligible clinicians. Customising roles, templates and integrations before rollout is how adoption grows.

  • Fit drives adoption: tools that match how each role already works get used.
  • Accuracy needs review: Ontario’s assessment found incorrect medical information in all 20 AI scribe products it tested — governance must be built in.
  • Rules differ by region: a tool built for one country rarely fits another without change.
Three routes to a healthcare AI product
Comparison Off-the-shelf SaaS Built from scratch KastHunt product, customised
Time to live Days to weeks Months to years About 4–8 weeks
Fits your workflows Partly Fully Fully, after customisation
Where data goes Vendor’s cloud Your choice Your environment
Covers every role Usually the doctor only If you build it Front desk, nurse, doctor, specialist, admin
Cost model Per seat, ongoing Large build plus team One organisation-wide licence
Who maintains it Vendor You Us during support, then you or us
Where is our patient data stored? Do your AI products make clinical decisions?

Inside your own environment. Each product is deployed on your servers or in your own AWS or Azure account, so audio, notes and records never leave your boundary. Audio is deleted after use (24 hours by default), and retention can be set to match your local rules.

No. Our products draft, organise and surface information. A clinician or staff member reviews and approves every output before it becomes part of the record. Each product has a clear sign-off point, and every action is logged so you can see who approved what.

Can we use more than one product together? Can we see a product before we commit? Can our own team maintain the product after handover?

Yes. Our products are built to connect. Patient intake can feed the AI scribe, which can feed referral and no-show recovery. Information is captured once and reused at every step, from the front desk to the admin dashboard.

Yes. Each product page has a demo using synthetic patients. To see it applied to your own workflow, book a free Discovery Workshop: we map your roles and systems, then show how the product would work in your clinic before you sign anything.

Yes. After the 3–6 month support period, your team can run and maintain it under your licence, or you can keep us on for ongoing maintenance. Updates and new features are available through a maintenance plan.

Do your products work across multiple sites and regions? Are your products compliant with HIPAA, UK GDPR and other privacy laws?

Yes. Each product supports many sites under one organisation. Head office sets standards, and each site keeps its own templates, consent wording and data rules. That makes it suitable for groups operating across states, provinces or countries.

Who can use it? Multi-location clinic groups, hospitals and health-tech companies that want AI shaped to how they actually work — across general practice, cardiology, ophthalmology, dental, mental health and women’s health — in the UK, US, Australia, Canada, New Zealand, the EU, the UAE and India.

Each product is built with safeguards for HIPAA, UK GDPR, the Australian Privacy Principles, PIPEDA, GDPR, UAE and India rules, including PHI masking, audit logs and configurable consent. We sign Business Associate Agreements in the US. Each product is ISO 9001 and ISO 27001 compliant.

Start with your workflow

Pick a product. We’ll shape it to your clinic.

Tell us how your clinics work today. In a free Discovery Workshop we map your roles, systems and rules, and show you which product to start with.