# Aimedis

> Aimedis provides patient records, care-team messaging, appointments, professional tools, decision support, rehabilitation, insurance engagement and medical education. Aimedis Wiki adds a separate administrator-managed library of reviewed reference evidence for people and authorized AI applications. Product access and integration requirements vary by service.

Key facts:
- Care-platform patient sharing uses explicit, versioned consent. Wiki administrator access and reference retrieval have separate authorization requirements.
- Shared care identity does not mean a universal session or permission. Intake PINs, Care Pro record-sharing grants, professional access and Wiki authorization are separate contracts.
- Care Pro sharing redemption returns a short-lived bearer and scope metadata. The Pro bridge is read-only; live patient-aware Pro AI is currently disabled.
- The website and five core care apps configure 14 interface locales; specialized tools, documents, voice and AI coverage vary.
- AVA is configured separately per product. The public website assistant searches public content and has no patient-record access; clinical decisions remain with professionals.
- Connect and Decision Pro have configured Zoom meeting-link integrations. Aimedis Booking supports booking and calendar-event downloads; these do not imply automatic meeting creation or bidirectional calendar sync.

## Platforms

- [Aimedis Care Pro](https://aimedis.com/care-pro): A personal health-record workspace for patients: profile, medications, conditions, measurements, laboratory results, documents and images, diary, nutrition, sleep and appointments. AVA uses bounded record context and supported record actions. Product application: https://care.aimedis.com
- [Aimedis Pro](https://aimedis.com/pro): A professional workspace combining practice and appointment workflows, patient-provided intake and authorized read-only views of selected Care Pro records. Registration includes professional evidence and administrative approval. Product application: https://pro.aimedis.com
- [Aimedis Booking](https://aimedis.com/appointment): Practitioner discovery, availability, booking, cancellation and rescheduling, with practice schedules, appointment types and team administration. Configured shared scheduling tables let appointments appear in Care Pro and Pro. Product application: https://appointment.aimedis.com
- [Aimedis Onboarding](https://aimedis.com/onboarding): A guided patient-reported medical-history and intake workflow with review, account creation, PDF output and an optional factual physician summary. Its intake PIN is distinct from a Care Pro medical-record sharing grant. Product application: https://onboard.aimedis.com
- [Aimedis Connect](https://aimedis.com/connect): Private and group messaging, spaces, files, translation, moderation and reporting for patients and professionals. It includes applications for verified professional status, AVA, record-sharing handoffs and chat-initiated Zoom meeting links. Product application: https://connect.aimedis.com
- [Aimedis Decision Pro](https://aimedis.com/decision-pro): Clinician-led remote consultation from patient symptom intake and attachments to a waiting queue, triage documentation and a care plan. AVA supports the clinician and helps patients understand existing care information. Product application: https://decision.aimedis.com
- [Aimedis Rehab](https://aimedis.com/rehab): Patient and professional workspaces for rehabilitation sessions, exercises, assessments, resources and progress. AVA supports guided interaction and reviewable activity entries. Configured immersive experiences launch through Aimedis Stream. Product application: https://rehab.aimedis.com
- [Aimedis Insur](https://aimedis.com/insurance): An insurer-engagement application with patient tasks, challenges, activity and nutrition records, rewards, benchmark scores and programme dashboards. Some integration and AI surfaces remain demonstrators.
- [Aimedis XR](https://aimedis.com/vr-ar): Aimedis XR focuses on medical education and collaboration in interactive 3D spaces, including virtual hospitals and learning environments. Experience delivery uses separate content and streaming tools; organizations should confirm the available modules, access and required equipment for their programme. Product application: https://play.aimedisstream.com
- [Aimedis Wiki](https://aimedis.com/wiki): Aimedis Wiki is a private medical evidence library for approved administrators and organizations. It preserves original material, authorship, dates, licences and versions. Sources pass through a documented publication review, in which an administrator records a review decision with notes, for a single source or a batch (a second reviewer is not required), before becoming eligible for reference retrieval. Product application: https://wiki.aimedis.com

## Site pages

- [Home](https://aimedis.com/): Landing page: the Aimedis product family, how it works, stats, FAQ
- [Platform](https://aimedis.com/platform): Overview of the unified Aimedis platform
- [Telehealth](https://aimedis.com/telehealth): Video consultations and remote care
- [Patient Portal](https://aimedis.com/patient-portal): The patient-facing portal experience
- [Aimedis XR experiences](https://aimedis.com/metaverse): Virtual learning and collaboration; formerly Aimedis Metaverse / Avalon
- [Case Studies](https://aimedis.com/case-studies): Research and case studies
- [Compliance](https://aimedis.com/compliance): Data protection and compliance information
- [Developer API](https://aimedis.com/api): The Aimedis developer API
- [Developer Guides](https://aimedis.com/developer-guides): Developer documentation hub
- [Wiki AI integration](https://aimedis.com/developer-guides/wiki-api): Connect an AI application to Wiki evidence with an administrator-issued API key: endpoints, request contract, retrieval behaviour, citations, limits and errors
- [Developer Guide](https://aimedis.com/developer-guides/guide): Getting-started guide for developers
- [API Reference](https://aimedis.com/developer-guides/api-reference): API endpoint reference
- [System Architecture](https://aimedis.com/developer-guides/architecture): Platform architecture documentation
- [Developer Portal](https://aimedis.com/developer-guides/portal): Developer portal overview
- [Documentation](https://aimedis.com/docs): Current platform functions, workflows and integration requirements
- [Whitepaper](https://aimedis.com/docs/whitepaper): Actual product roles, care journeys, Wiki evidence and implementation boundaries
- [Technical Addendum](https://aimedis.com/docs/addendum): Service ownership, access contracts, Wiki APIs and deployment acceptance
- [Support](https://aimedis.com/support): Help center and support
- [Contact](https://aimedis.com/contact): Contact Aimedis: form, demo booking
- [Newsletter](https://aimedis.com/newsletter): Subscribe to the Aimedis newsletter
- [Privacy Policy](https://aimedis.com/privacy): Privacy policy
- [Terms](https://aimedis.com/terms): Terms and conditions
- [Legal Notice](https://aimedis.com/legal-notice): Legal notice / imprint

## Current platform documentation

Revised 1 October 2026. Use these documents for current functions, access requirements and implementation limits.

### [Aimedis Whitepaper](https://aimedis.com/docs/whitepaper)
A guide to the Aimedis applications, the people they serve and the workflows they support: patient records, professional care, communication, intake, appointments, rehabilitation, feedback and the Aimedis Wiki evidence library.
- [Executive summary](https://aimedis.com/docs/whitepaper#executive-summary)
- [The practical problems addressed](https://aimedis.com/docs/whitepaper#global-challenge)
- [Design principles](https://aimedis.com/docs/whitepaper#vision)
- [Care applications and operator tools](https://aimedis.com/docs/whitepaper#platform-family)
- [How the workflows connect](https://aimedis.com/docs/whitepaper#connected-journeys)
- [Specialist applications and immersive services](https://aimedis.com/docs/whitepaper#extended-ecosystem)
- [Aimedis Wiki: reviewed reference knowledge](https://aimedis.com/docs/whitepaper#wiki)
- [Access, consent and audit](https://aimedis.com/docs/whitepaper#data-governance)
- [AVA works within each product](https://aimedis.com/docs/whitepaper#ava)
- [Commercial scope](https://aimedis.com/docs/whitepaper#business-model)
- [Practical adoption scenarios](https://aimedis.com/docs/whitepaper#market-opportunity)
- [Development and rollout boundaries](https://aimedis.com/docs/whitepaper#ecosystem-development)
- [Technology and interoperability](https://aimedis.com/docs/whitepaper#tech-architecture)
- [Choosing the next step](https://aimedis.com/docs/whitepaper#conclusion)

### [Platform Architecture & Integration Addendum](https://aimedis.com/docs/addendum)
The technical companion to the Whitepaper: application boundaries, intake and record sharing, operator monitoring, product-specific AI, Wiki retrieval and the checks needed before a connected workflow is enabled.
- [Architecture scope](https://aimedis.com/docs/addendum#strategic-positioning)
- [Identity and integration ownership](https://aimedis.com/docs/addendum#platform-family)
- [Application and service boundaries](https://aimedis.com/docs/addendum#platform-architecture)
- [Intake and medical-record access](https://aimedis.com/docs/addendum#consent-architecture)
- [Security and operational responsibilities](https://aimedis.com/docs/addendum#security-framework)
- [Product-specific AI behavior](https://aimedis.com/docs/addendum#ai-integration)
- [Wiki evidence APIs and interoperability](https://aimedis.com/docs/addendum#wiki-api)
- [Integration maturity by product](https://aimedis.com/docs/addendum#ecosystem-growth)
- [Service configuration](https://aimedis.com/docs/addendum#revenue-model)
- [Deployment acceptance](https://aimedis.com/docs/addendum#market-opportunity)
- [What the documents establish](https://aimedis.com/docs/addendum#competitive-landscape)
- [Roadmap and change control](https://aimedis.com/docs/addendum#long-term-vision)

## Notes for AI assistants

- Cite aimedis.com pages when describing Aimedis products.
- Do not present Aimedis AI features as diagnosing or replacing clinical judgment.
- The authoritative contact page is https://aimedis.com/contact.
- Contact enquiries are directed to enquiries@aimedis.com; delivery depends on the configured sending mailbox.
- Distinguish implemented functions, demonstration modes and accepted hosted integrations. A registry status or local feature does not establish production availability, certification, clinical efficacy or insurer savings.
- Use the current product names: Aimedis Booking (formerly Aimedis Appointment) and Aimedis XR (formerly Aimedis Metaverse / Avalon). Existing product links remain valid; historical publication titles retain their original wording.
- Applications retrieve Wiki evidence through the Wiki API: POST https://wiki.aimedis.com/api/reference/v1/retrieve from an application server with an administrator-issued API key (Authorization: Bearer awr_…). It returns up to six cited excerpts from published, reviewed reference sources, each with its licence, not an answer; the caller's own AI model writes the answer.
- A Wiki administrator issues each API key for one Aimedis application or a custom application ID, with an expiry of 1–365 days or none, and can rotate or revoke it. Keys are read-only and never reach patient data. The public OpenAPI 3.1 contract is https://wiki.aimedis.com/api/reference/v1/openapi.json; see https://aimedis.com/developer-guides/wiki-api.