Cardiac Aftercare
Cliniq Labs / Clinical research prototype

Research into structured cardiac recovery information.

An invite-only prototype exploring governed evidence retrieval, deterministic triage and on-device language models for clinician evaluation.

Invite-only research

Invite-only research. No claim of clinical approval or production readiness.

Product capabilities

Built around a defined research question.

Explore the features and their intended use before deciding whether this project fits your needs.

01

Invite-only testers

Cardiac specialists, cardiology trainees and junior doctors interested in reviewing triage behaviour, retrieval grounding and answer quality.

02

Not available to

Patients, carers, the general public, or any App Store / open distribution channel until Clinical Safety Officer sign-off and regulatory readiness.

03

Knowledge pipeline

Source register, ingestion, cleaning, clinical metadata, chunking, indexing and retrieval testing across a curated NHS/BHF/NICE-first corpus.

04

Safety layer first

Red / amber / yellow / green / blue triage rules, medication and safeguarding overlays, escalation wording and local audit before any generative path.

Research approach

Understand the research scope.

Review the documented research scope and contact the developer before considering participation. Public descriptions do not grant access or authorise clinical use.

Explore research details
  1. A cardiac specialist or junior doctor requests access and confirms they understand this is not for live patients.
  2. Invited testers exercise triage, clarification, retrieval grounding and answer quality on synthetic / non-patient scenarios.
  3. Feedback feeds clinician review workflows and CARE-RAG governance packages.
  4. Patient or public release remains blocked until Clinical Safety Officer sign-off and regulatory readiness.

Related internal review surface (unlisted): CARE-RAG governance review portal.

Product transparency

Understand the scope.
Know how information is handled.

01 / Intended use

Research boundaries

Not a public patient service. Not for live patient care, patient self-triage or public distribution. A project description is not clinical approval.

Our approach to product information
02 / Data & permissions

Privacy in context

Research access, permitted datasets and information handling depend on the project’s separate notices and approved arrangements. Do not submit identifiable patient information through this website.

Read the privacy information
Common questions

Make an informed choice.

Find answers about Cardiac Aftercare, its intended use and its limitations.

Get product support
Is Cardiac Aftercare available to patients?

No. The app is not available for patient or public distribution. Access is limited to invited cardiac specialists and junior doctors who want to evaluate the prototype.

What AI techniques does Cardiac Aftercare use?

It combines deterministic clinical triage rules, BM25 retrieval over a clinician-governed knowledge pack, escalate-only semantic similarity, and constrained on-device LLM roles for safety classification, clinical interpretation and grounded answer composition.

Does the app diagnose or prescribe?

No. It does not diagnose, prescribe, change medication, interpret ECGs or images, or replace emergency care or clinician judgement.

Who can request access?

Cardiac specialists, cardiology trainees and junior doctors interested in testing the governed RAG and on-device LLM prototype may request invite-only access.

Is this affiliated with the NHS?

No. Cardiac Aftercare is an independent development prototype. It is not affiliated with, endorsed by, or approved by the NHS, NICE, BHF or any hospital trust.

Independent development

A named developer.
A direct route to support.

Cardiac Aftercare is developed by Hassan Chizari and presented under Cliniq Labs. Earlier versions and notices may use the Random Mini Apps name.

For questions or corrections, include the app version and a description of the issue. Please leave out sensitive personal or patient information.

Contact the developer

Discuss the research scope.

Contact the developer about evaluation access and project limitations.

Enquire about research