Back to proposalCleveland Clinic Abu Dhabi

Interactive demonstration · fictional patient data

CCAD AI platform — interactive demonstration workspace

Shared patient context

Khalid — fictional demonstration patient

AI-generated image · fictional person

Next appointment

No upcoming appointment

Next appointment
No upcoming appointment
Journey checklist
0 of 10 steps

Pro · Clinical team

Clinical overview

Neurology and neurorehabilitation · worklist and patient chart

The fictional demo rehabilitation physician

Demo rehabilitation physician

Rehabilitation medicine

AI-generated image · fictional person

Worklist dayFriday, 23 October 2026Abu Dhabi time

Today

Worklist

  • Khalid

    62 years · follow-up after stroke

    Task: Intake requested — awaiting Khalid

    Responsible discipline: Rehabilitation medicine

    Status: Awaiting patient
  • A. R.

    Epilepsy follow-up

    Task: Seizure diary reviewed

    Responsible discipline: Neurology

    Status: Nothing due
  • S. M.

    Migraine

    Task: New headache questionnaire

    Responsible discipline: Neurology

    Status: Needs review
  • H. K.

    Parkinson's disease

    Task: Therapy goals updated

    Responsible discipline: Physiotherapy

    Status: Nothing due

Only Khalid's entry is interactive. The other entries are fictional context.

Cohort overview

Fictional demonstration data

Onboard

Latest intake

Draft

Not submitted yet. Khalid completes the intake in Onboard; it appears here once submitted and shared with the care team.

Patient-reported

Home readings

Shared by Khalid for this visit

  • Intake not submitted yet
  • No questions for the visit shared yet
  • 14 home readings, 10–⁠23 Oct

Blood pressure, morning readings

mmHg · documented target: below 130/80

  • Systolic
  • Diastolic
  • Above target
  • Within target
  • Target line

Self-rated fatigue

Out of 10, as reported by Khalid

Shared with Khalid once approved

Care plan and goals

Draft — not yet approved

Current plan

A clinician reviews and approves the plan in Decision before Khalid sees it.

1. Secondary prevention: continue the medicines in the discharge letter; review home blood-pressure readings at each visit (target below 130/80 mmHg). 2. Rehabilitation referral: physiotherapy (walking endurance and balance), occupational therapy (hand function, dressing, kitchen safety), speech and language therapy (word-finding). 3. Fatigue: pacing and energy-conservation education for Khalid and Fatima. 4. Mood and cognition: screening at the next in-person visit. 5. Goals agreed with Khalid: dressing including buttons; walking 300 metres outdoors with the cane, to the neighbourhood mosque; preparing a simple breakfast safely. 6. Follow-up: neurology clinic review as in the discharge plan (within six weeks); next rehabilitation physician review after the first therapy sessions; reviewed rehabilitation progress shared in Care.

Shared goals

Proposed in the draft plan — not yet approved.

  • Dress independently, including buttons

  • Walk 300 metres outdoors with the cane — to the neighbourhood mosque

  • Prepare a simple breakfast safely

Khalid's priorities: Greater independence at home and clear instructions for the family

Clinical view

Timeline

  1. Discharged home after a stroke

    September 2026 · before this scenario

New entries appear here as Khalid and the care team move through the journey.

Shows only what Khalid has shared with the care team.

Clinical background

Patient summary

Discharge summary — synthetic preview

  • Acute ischaemic stroke in the left middle cerebral artery territory on 14 September 2026; treated on the stroke unit; discharged home on 23 September 2026.
  • At discharge: mild right-sided weakness (arm more than leg), reduced right-hand dexterity and mild word-finding difficulty when tired. NIHSS 3; modified Rankin Scale 2.
  • Secondary prevention: continue the medicines listed in the discharge letter (antiplatelet, statin, blood-pressure and diabetes medicines); home blood-pressure target below 130/80 mmHg.
  • Follow-up: outpatient neurology and rehabilitation physician review within six weeks; outpatient physiotherapy, occupational therapy and speech and language therapy to be arranged.
Medical history
Type 2 diabetes, high blood pressure and high cholesterol, managed under the existing clinician-approved plan; former smoker (stopped in 2015). No known allergies (fictional).
Existing plan notes
  • Discharge plan: outpatient neurology follow-up and rehabilitation physician review within six weeks.
  • Continue the existing clinician-approved medication plan; no changes in this demonstration.
Care team (fictional, role-based)
  • Demo rehabilitation physician
  • Demo neurologist
  • Demo physiotherapist
  • Demo occupational therapist
  • Demo speech therapist
  • Demo nurse
Family contact
Fatima — daughter, authorised family contact (fictional)Family sharing on

Abu Dhabi time

Appointments

No follow-up booked yet. Khalid books it in Booking.

Aimedis Rehab

Rehabilitation

No referral sent

No referral yet. Once the care plan is approved, a referral to Aimedis Rehab is prepared in Decision.

Integration concept

Simulated exchange — no external clinical connection.

Connections

  • Aimedis Rehab

    Demo adapter

    A local adapter behind a proposed interface, not an existing Aimedis Rehab API.

  • Hospital / HIE connection

    To be scoped

    Malaffi, the Abu Dhabi health information exchange, is an integration consideration to be scoped. This demonstration does not connect to it, and a FHIR adapter does not by itself provide access.

Exchange events

Newest first · times in Abu Dhabi time

No exchanges yet

Events appear here as the journey runs: an intake is submitted, home readings and visit questions are shared, an appointment is booked, a video visit is held and its note signed, a plan is published, a referral is sent and Rehab progress is returned.

Proposed FHIR R4 mapping

FHIR R4 is the reference version for this demonstration mapping. It is an interoperability specification, not a certification; the production version and the customer's profiles are confirmed during integration discovery.

Select an event above to highlight its resources here.

Demonstration information and the illustrative FHIR R4 resources proposed for it
Demonstration informationIllustrative FHIR R4 resources
Patient and linked caregiverPatientRelatedPerson
Clinical professionals and disciplinesPractitionerPractitionerRoleCareTeam
Sharing preferencesConsent
Intake form and submitted answersQuestionnaireQuestionnaireResponse
Appointment and consultationAppointmentEncounter
Video follow-up (virtual consultation)An encounter of class virtual, started and finished as two events.Eventsencounter.startedencounter.finishedEncounterProposed codingclass VR (virtual)
Condition and relevant historyCondition
Approved care or rehabilitation planCarePlanGoal
Rehabilitation referralServiceRequest
Referral execution and work trackingTask
Patient- or clinician-reported measurementWhen the relevant meaning and coding are definedObservation
Home readings: blood pressure and self-rated fatigueBlood pressure panel. The demonstration payload keeps text only; fatigue is noted as text.Eventsobservation.recordedObservationProposed codingLOINC 85354-9
Reviewed summary or reportDocumentReference
Signed visit noteDrafted by CCAD AI; it enters the record only when the physician signs it.Eventsvisit-note.signedDocumentReference
Clinical communication recordWhere appropriate to the agreed profileCommunication
Questions for the visit, prepared with CCAD AIShared with the care team only while clinical-team sharing is on.Eventsvisit-questions.sharedCommunication
Attribution and access-event representationAs appropriateProvenanceAuditEvent
  • Aimedis XR interaction data stays application session data: it is not mapped to a clinically validated Observation, and its factual summary enters the therapist-reviewed report.
  • Payloads are synthetic and mostly text-only. The published codes named here (LOINC 85354-9 for the blood pressure panel, class VR for a virtual encounter) are proposed for confirmation during integration discovery; no other medical codes are invented, and local references stay consistent.

Future production connection — design only

Not part of this demonstration; noted for integration discovery.

  1. Reconcile these interfaces with the actual Aimedis Rehab API and identity model before implementation.
  2. Agree patient-identifier mapping, organisation boundaries, FHIR profiles, terminology, consent scope and data ownership.
  3. Route real traffic through authenticated server-side adapters; never expose service credentials in browser code.
  4. Use server-validated identity and consent checks, delivery acknowledgements, idempotency, version and conflict handling, and auditable updates.
  5. Prefer negotiated event or webhook delivery, or a supported pull mechanism, according to the real API contract.
  6. Show explicit pending, failed and retried exchanges; never fabricate successful delivery.