Inky HealthFounder experience
A clinical retrieval platform, taken beyond the pilot.
Before Inky Health was formed, its founder built a clinical question-answering platform for a large Australian public health service and helped move it towards production in a restricted environment.
This is previous founder experience. The system and its intellectual property belong to the health service. It is not an Inky Health product or client engagement.
Answers clinicians could trace back to source.
Clinical guidance was spread across documents and systems. The platform searched a governed corpus and returned a direct answer with citations, while making it clear when the source material did not cover the question.
It ran as a pilot in a clinical setting and moved towards production under the controls required by a restricted public health environment.
What the work required.
Clinical retrieval
Hybrid search and reranking over curated clinical documents, with citations back to the source passage.
Measured quality
Human-graded questions, automated evaluation, and regression checks for retrieval and answer quality.
Safety controls
Explicit scope limits, refusal conditions, and versioned rules for how the system is allowed to answer.
Restricted delivery
Self-hosted models and reproducible deployment into a network with no public internet access.
The demo was the easy part.
The hard work was measuring retrieval, controlling unsafe behaviour, governing change, and delivering every required artefact into an isolated network.
That experience shapes how Inky Health scopes new work: prove quality early and design for the real production boundary from the start.
Start a conversation.
Ask how evaluated retrieval, self-hosted models, or restricted-network delivery could apply in your environment.
Enquiries are typically answered within one business day.