Who lands
Healthtech / digital-MCO / TPA product or IT, payor claims/formulary lead, clinic-network or pharmacy-ops IT, a hospital-group digital lead asked to put models on claims and e-Rx data that cannot leave Malaysia.
Health
On-prem AI for drug pricing, claims integrity, and outpatient ops.
A public chatbot is the wrong architecture for claims, e-prescriptions, and formulary files. We put open-weight models on infrastructure the healthtech or hospital group controls — a data platform you can point to in Malaysia — and write into the auditor queue, sheet, or API the desk already uses.
Who this page is for
Payor, provider, and pharmacy data that cannot leave
Who buys
Healthtech or payor IT + compliance (PDPA), with an ops sponsor on pricing, claims, or outpatient routing. Architecture sale plus one bounded workflow. Not an EHR replacement, not a diagnostic device, not a patient-facing chatbot.
What we do
The same three services, on the healthtech’s wall
On-premise & private AI
Open-weight models on infrastructure the healthtech or hospital group controls. Claims, e-Rx, and formulary files do not go to a public API.
- Model selection and serving (vLLM, Ollama, or your stack)
- Private retrieval over approved claims, e-Rx, and formulary sources only
- Access control, audit logs, encryption in transit and at rest
- Air-gapped or default-deny outbound when policy requires it. Malaysian residency when that is the requirement.
Custom models
SKU / formulary language, payor rules, Bahasa correspondence — if you designate a corpus. We do not train a third-party model on your corpus.
- Fine-tuning only on data you designate, on infrastructure you control
- RAG evaluated on real pricing/claims/ops prompts
- English and Bahasa Malaysia
- Quantisation to the hardware you have
LLM automation workflows
Control-tower jobs, not a diagnostic product.
- Private retrieval / data platform over approved sources
- Claims / FWA copilot into an auditor queue — human in the loop, not a denial bot
- Clinic/ops document and price-list workflows into the sheet/inbox/API already in use
- Guardrails: we do not replace the HIS, the TPA, or the clinician
First workflows
What we would scope first
Example scope
Private retrieval / data platform
Over approved claims, e-Rx, and formulary sources on infrastructure the healthtech or hospital group controls.
Example scope
Claims / FWA copilot
Duplicate/phantom flags and substitution notes into an auditor queue the payor already uses — human in the loop, not a denial bot.
Example scope
Clinic / ops documents
Itemised billing and approved-source copilots that write into the sheet, inbox, or API already in use.
These are first workflows we would scope. They are not case studies. Do not send patient or claims files to hello@. Discovery is a call, under NDA.
Data & security
Constraints we design for
Where it runs
On-prem, private cloud, or air-gapped on infrastructure the healthtech or hospital group controls. We do not require a public model API. Malaysian residency when that is the requirement.
How we handle data
Encrypted in transit and at rest. Access scoped by role. We do not train a third-party model on your corpus, and we do not pool client data. Not a PDPA certificate, not HIPAA, not “PHI never leaves” as a legal warranty.
How we integrate
Read existing systems first. Write-back only where you approve it — a sheet, an inbox, an auditor queue, an API you already have. We do not rip out the HIS, EMR, or TPA. We do not claim a named HIS connector.
Who it belongs to
Weights, prompts, evaluations, and logs stay yours. A mutual NDA is ready before any deeper scoping call.
We do not offer a diagnostic product, a medical device, or a patient-facing chatbot. We do not train third-party models on patient, claims, or e-Rx corpora. We do not replace the HIS / EMR / TPA. PDPA and data residency are constraints we design for — not a certification claim.
Built in Malaysia · data residency as a design constraint · English and Bahasa. Why Malaysia
Get in touch
If this is healthtech or payor IT, write to us
Do not send patient or claims files to this address. Discovery is a call, under NDA.
[email protected]Public contact for projects, partnerships, research, and investor conversations.