Care agents that remember the patient between visits
Enhance patient care with memory-powered AI that understands context, history and individual needs. Without memory, every conversation asks the patient to start again from the intake form.
The mixture
- 01 · Persistent memory
- Leads
- 02 · Current context
- Uses
- 03 · Traceable decisions
- Uses
- 04 · Shared context
- Light
- 05 · Scoped retrieval
- Uses
Every visit starts from the intake form
Current AI healthcare solutions struggle with context retention and personalization, leading to poor patient experiences. Patients feel it first.
- 01
Very generic suggestions
Agents cannot retain the context of previous conversations, so what they suggest is generic, and generic suggestions are not a reliable basis for a care plan.
- 02
No connection for patients
Patients have to give their details again for every query. The agent never feels like it knows them.
- 03
No progress retention
Sessions are not stored, so past conversations and the progress made in them are lost between visits.
Intelligent healthcare features
Transform patient care with memory-powered AI that understands each patient's unique journey.
Full context awareness of the patient
Retains history, medications and preferences across all sessions.
Patient-tailored suggestions, at scale
Suggestions are custom-suited to the patient in front of it, not the average patient.
Remembers each patient's quirks
Tracks past conversations, so answers stay consistent with each patient's earlier questions.
Plans ahead
Remembers what is next in line in the patient's treatment.
Mostly persistent memory. Then three others.
Every application on Alchemyst is a different mixture of the same five jobs. That mixture is what makes this a different piece of software from the one next to it, even though the API underneath is identical.
What the user told you once stays told
Each patient has a durable memory of history, medications, preferences and where they are in their care plan. It is written as conversations happen and read before the next one, so the patient never has to repeat themselves.
- Patients do not repeat their history.
- Progress carries from visit to visit.
- The next step in the plan is remembered.
Uses · Current context
The medication list in force
Discontinued medications and superseded plans are subtracted before the agent answers.
Uses · Scoped retrieval
This patient, this care team
Patient and care-team scopes are intersected, so an agent only sees what it is entitled to see.
Uses · Traceable decisions
Where the answer came from
Every answer carries the notes and guidelines it drew on, for a clinician to verify.
That is four of the five. The fifth, shared context (what one agent learns, the next one already knows, on the same definitions), is what leads in Sales agents, Customer success and Enterprise operations instead. Same API, different mixture.
The sources you already have
Bring sources in through the data-source integrations (PostgreSQL, MongoDB, Google Docs, Google Sheets, Amazon S3), an n8n workflow, or a direct context.add call. Each one lands scoped, so retrieval can intersect it with everything else.
01 · Ingest
Scope what you ingest
Every document lands with a groupName: the sets it belongs to. Those sets are what retrieval intersects later, so the structure you choose here is the precision you get there.
context.addimport AlchemystAI from "@alchemystai/sdk";const client = new AlchemystAI(); // reads ALCHEMYST_AI_API_KEYawait client.v1.context.add({ context_type: "resource", scope: "internal", source: "care-guidelines", documents: [{ content: "Post-operative knee recovery: weight-bearing as tolerated from day 2. Physiotherapy three times a week for six weeks.", }], metadata: { fileName: "post-op-knee-recovery.md", groupName: ["clinic", "ortho", "guidelines"], // the sets this belongs to },});02 · Write
Write where the patient is in their plan
The next conversation needs to know what happened in the last one. Write progress against the patient, not into a transcript nobody reads.
context.memory.add// De-identified reference, never a name or record number.await client.v1.context.memory.add({ sessionId: "patient_ref_20931", contents: [{ role: "assistant", content: "Week 3 of physiotherapy. Reported pain 3/10, down from 6/10. Next review due in two weeks.", }], metadata: { groupName: ["clinic", "ortho", "patient_ref_20931"] },});03 · Search
Search before responding
Search intersects the scopes, subtracts superseded and duplicate content, and ranks what survives. Only that reaches the model, and the whole decision is recorded as a Context Trace.
context.searchconst { contexts } = await client.v1.context.search({ query: "Patient asks whether they can start cycling again", scope: "internal", similarity_threshold: 0.8, minimum_similarity_threshold: 0.5, metadata: { groupName: ["clinic", "ortho"] }, // ∩ narrow scope});// − superseded, deduplicated → ranked → into the window// Every search is recorded as a Context Trace.const reply = await llm.respond(message, { context: contexts });
npm install @alchemystai/sdk or pip install alchemystai, both ship the same client. Full reference in the docs.
Cost optimized. Out of the box.
Run agents with more power, at lower cost.
- Does the heavy lifting of memory offloading by itself.
- Optimizes token expenditure with efficient prompts.
- Highly capable of handling longer tasks.
Standard agent
3M tokensHigh token usage, short context window
Alchemyst-enhanced agent
1.8M tokensShorter prompt optimized with Alchemyst
Patient data needs an agreement before it needs a feature
Support for Protected Health Information is on our roadmap. Until a Business Associate Agreement is in place, do not send PHI to Alchemyst: start with guidelines, care pathways and de-identified data, and talk to us about dedicated or self-hosted deployment.
Security & complianceManaged cloud
Encrypted in transit and at rest, isolated per organization, and scoped at write time.
Dedicated infrastructure
EnterpriseSingle-tenant, with VPC peering when your data cannot share a network boundary.
Self-hosted
On-premiseRun the context layer on your own infrastructure, with OpenTelemetry for observability.
The same API, a different mixture
Each of these leads with a different job, pulls from a different set of sources and needs a different call. All of them, by job.
Bring the conversation that starts from zero.
The one where the patient had to explain their history again.