Jengu Visit Assistant

Jengu Visit Assistant is the clinical-encounter capture module of the Jengu platform: it turns the spoken consultation between a clinician and a patient — in-person, remote, on a ward round, or in a team meeting — into a structured clinical record, a list of follow-up actions, and a take-home note for the patient, with proper audited consent and no clinician hand-typing the result afterwards.

What Jengu Visit Assistant gives a clinician

A working visit-capture surface, in customer terms:

• The clinician keeps eye contact with the patient. The consultation is recorded once consent is captured; the documentation that used to follow it does not need to happen at the keyboard while the patient watches.
• A draft clinical note appears as soon as the visit ends. A structured note — history, examination findings, assessment, plan — is generated from the transcript in the FHIR shape the patient's record expects. The clinician reviews, edits, signs. Hours of typing become minutes of review.
• Help arrives during the conversation, not after. Live clinical assists surface lab-order suggestions, drug-interaction warnings, and role labelling sub-second — before the moment passes. The clinician decides whether to act; the platform surfaces, does not direct.
• Actions get captured at the bedside. Referrals, slot bookings, on-the-spot follow-ups — the things that have to be completed while the patient is there — are detected from the conversation and surfaced as one-click forms. No "I'll do that after" lists; the action happens while the patient is in the room.
• The patient leaves with something they can read. A lay-language take-home summary in the patient's language with structured follow-up: medications to take, appointments to keep, things to watch for, when to call. Closes the gap between what the clinician said and what the patient remembers.
• Remote consultations use the same pipeline. Televisit recordings, transcripts, assists, and notes are produced the same way as in-person — there is no second product for remote care, no separate compliance story.
• Team meetings are captured properly. MDT discussions, tumour boards, complex-case reviews capture per-participant identity from the meeting setup; the resulting structured note attributes decisions and rationales to the right speaker, not to a single anonymous voice.
• Walking rounds, too. A nurse on inpatient rounds dictates bed-by-bed; each observation is tied to the patient selected at that bed and to the speaker derived from their login.
• Consent is captured in-flow, not as a side process. A patient who declines recording gets the same clinical care; the platform records the consent decision either way. Every recording action — start, pause, raw-data access, retention deletion — is on the audit trail.

The full inventory of testable features is on the Features page.

How Jengu Visit Assistant fits a clinical setting that already runs encounters

Clinicians currently document visits one of three ways: typing into an EMR during or after the visit, dictating to a transcription service with a turn-around lag, or scribbling notes that turn into typed records later. Jengu Visit Assistant doesn't ask anyone to change how visits happen — it changes what happens after the words are spoken.

Stage 1 — Pilot in one specialty. A small group of clinicians (typically one specialty in one location) turn recording on for their consenting patients. The platform produces transcripts and note drafts; the clinician's existing documentation tool remains the record-of-truth. Value shows up as time saved on documentation and as fewer "what was I going to write?" moments.

Stage 2 — Note drafting becomes routine for the pilot group. The clinical note generated from the visit feeds the patient's chart directly. Live clinical assists turn on; smart-action capture opens at the bedside for slot bookings and same-visit referrals. The pilot group's documentation backlog drops sharply.

Stage 3 — Expand to other specialties and contexts. Remote consultations move onto Televisit using the same pipeline; ward rounds use the inpatient-rounds workflow; MDT meetings adopt the multi-participant capture. The clinical-encounter surface is unified across in-person, remote, team, and rounds settings.

Stage 4 — Patient-facing summary at every encounter. The lay-language take-home note is delivered to the patient at the end of every visit, in their language, with structured follow-up actions. Patient adherence and recall improve measurably.

Each stage delivers value on its own. Customers can stop at stage 1, 2, or 3 indefinitely if that's what fits their workflow; we're not selling a forced rollout.

What changes for the clinical organisation once Visit Assistant is fully in place

• Clinicians spend less time on documentation. The note is a review-and-sign job, not a re-creation job.
• Visit data is structured from the start. Lab orders, referrals, prescriptions, follow-ups become discrete records, not free-text notes someone parses later.
• The patient leaves better informed. A take-home summary they can actually read closes the recall gap that medical literature has measured for decades.
• Compliance is on the audit trail, not in a binder. Consent decisions, recording actions, raw-data access — every step is queryable, regulator-readable, attributable.
• One module covers every encounter type. Visits, televisits, team meetings, rounds — same recording, same assists, same anonymisation pipeline. Not four separate apps with four compliance stories.
• The clinician's attention returns to the patient. This is the change most clinicians notice first and value most.

Where Jengu Visit Assistant fits in the broader Jengu platform

Visit Assistant is a module on the Jengu platform. The platform underneath provides the secure recording service that captures audio with audited consent, the AI routing layer that picks the right model per task and per jurisdiction, the anonymisation pipeline that strips identifiers before any LLM call, and the multi-tenant isolation, encryption, and audit trail that make the whole thing legal. Reading the platform principles and the platform features explains the substrate Visit Assistant is built on.

Other modules built on the same platform — Lab today, future Insurance and Billing modules — share that substrate. A Lab order detected during a visit lands in the same shared clinical record both modules read; no integration code between them.

Talk to us

For a demo or to discuss a pilot, write to jengu@jengu.cloud.