iMed

Institution-first care operations

iMed

When a care recipient asks for help, iMed turns the moment into owned staff work across care queues, mobile handoffs, and audit trails.

Live operationsHadassah Home Care

active tenant

1
Voice chat
2
CRM request open
3
Notification to staff
4
Care
Care queue

urgent

Knee pain

Forwarded to Omri

09:18
Medication

Assigned to Yael

open
One login

The right workspace opens.

Owned care work

Voice and device requests enter the queue.

Audited handoffs

Mobile handoffs stay tied to the request.

From help request to accountable staff work.

Institution operating loop

One tenant-scoped path across intake, queue, phone handoff, and audit.

Voice intake

request opened

CRM queue

staff assigned

Audit trail

institution ledger

Institutions are the unit of delivery

Every account, request, voice session, and alert belongs to one institution before work begins.

Voice becomes accountable work

Realtime LLM sessions create staff-visible CRM records, notes, and escalation paths.

Forwarded care reaches phones

Staff handoffs carry request context, delivery status, acknowledgement, and audit history.

Authority is resolved server-side

Each account opens only the workspace and actions it is allowed to use.

One account entry

Sign in once. The right workspace opens.

After sign-in, iMed opens the workspaces and actions your account can use, including multi-institution teams and institution-specific roles.

Credentials

Username and password only.

Workspace

Authority resolves server-side.

Action

Only allowed tools appear.

Talk to iMed

Bring iMed into your care operation.

Tell us about the care setting, the teams involved, and the workflow you want iMed to support.

Full name
Organization
Work email
Phone
What should we help with?