Aimedis Whitepaper

Aimedis develops applications for patients, healthcare professionals, practice teams, rehabilitation teams and organizations. Each application has a defined role. Connections between them support particular workflows and depend on configured interfaces, appropriate permissions and the receiving service.

Aimedis Care organizes a patient’s own health record. Pro is the workspace for professionals who work with records that patients have shared. Aimedis Onboard prepares a visit with a structured intake, Booking finds and manages appointments, Connect carries secure messaging, video calls and information events, Aimedis Decision provides remote consultation led by a physician, and Rehab supports rehabilitation between patients and their therapy teams. Aimedis Support is the help and feedback service for every platform, and Aimedis XR covers immersive education.

Between late October and early November 2026, seven applications (Care, Pro, Booking, Onboard, Connect, Decision and Rehab) were rebuilt in one shared look with AVA, the Aimedis assistant, at the centre, and Aimedis Support was rebuilt on 7 November 2026. Since 8 November 2026 one Aimedis sign-in covers seven applications: Care, Pro, Booking, Onboard, Connect, Decision and Support. Rehab keeps its own accounts, and the Wiki has its own administrator sign-in. Video in Connect, Decision and Rehab runs on Aimedis’ own server with end-to-end encryption, and every medical AVA takes its evidence through the Aimedis Wiki.

Aimedis Wiki is a separate, private library of reviewed medical reference material for administrators and authorized AI applications, and the terminology server for clinical codes. It does not inherit patient-record access merely because it belongs to the same product family.

The following applications support care-related workflows. They are separate products with their own data, roles and integrations, which must be checked individually. Since their v2 releases they share one look, one Aimedis sign-in and AVA as the assistant on their main screens.

Aimedis Insur, an application for insurers’ health programmes, is being reworked and is not offered at present.

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. Beside the reviewed library, the Aimedis RAG collection holds documents that become searchable as soon as they are processed, without that review; its passages are always labelled “Aimedis RAG”, never presented as library sources.

There is no public sign-up: administrators of approved organizations sign in, and the public sees the landing page and the machine-readable reference API. Administrators can organize material by medical specialty and other catalogue fields, inspect extraction results, compare evidence and prepare cited research briefs with AVA. OCR and transcription require the relevant processors. A PubMed bibliography import does not itself grant access to licensed full-text evidence. The landing page and the workspace are available in 18 languages.

Since 8 November 2026 every medical AVA, in Care, Pro, Booking, Onboard, Connect, Decision, Rehab and the Wiki itself, takes its evidence only through the Wiki, in a fixed order: the reviewed Aimedis Wiki library, Aimedis RAG, PubMed and a public medical library (MedlinePlus, joined by trusted public-health websites only when the other stages find too little). The Wiki is the only place where medical knowledge is uploaded; the platforms’ own uploads were removed. Each passage carries its stage, source, version and licence, and a stage that cannot be reached is reported as unavailable while the answer goes on without it. For visitors who are not signed in, only openly licensed Wiki and RAG passages (CC BY, CC BY-SA and CC0) are quoted. The calling application is responsible for keeping each excerpt’s source, version and licence with the answer. The reference API does not authorize access to patient records. Patient-data processing in Wiki has separate controls and approval requirements.

The Wiki is also the terminology server of the Aimedis platforms. It holds the WHO’s ICD-10 (2019 edition) and ICD-11 (MMS, January 2026 release), used in a wide range of countries, and national editions such as Germany’s ICD-10-GM 2026, each with its publisher’s licence and attribution. Platforms look codes up, validate and expand them over the reference API with their own credential; nothing is served anonymously. SNOMED CT, LOINC, ICF and ATC are not loaded; each needs its licence or written permission first. The Wiki also hosts Aimedis Media, the films that platforms show, such as Rehab’s exercise films, delivered through short-lived signed links.

Consent to platform terms or processing at signup, permission to receive an intake, and a grant to read medical-record categories are distinct decisions. They should not be described as one consent that automatically applies everywhere.

Care workflows use service-specific authorization, scopes and expiry. Intake and record sharing have different PIN contracts. Revocation must be enforced on subsequent access; it does not erase information already received by an authorized recipient.

Applications record access and operational activity. Care, Connect and Decision link their audit entries with hashes to support integrity checks. Retention, independent protection and inspection capabilities depend on the service and its deployment; these records should not be described as universally immutable or tamper-proof.

One Aimedis account serves Care, Pro, Booking, Onboard, Connect, Decision and Support. Since 8 November 2026 signing in to one of them signs the person in to all of them on that device, through a shared session cookie for aimedis.com that expires after seven days without use; signing out ends them all. Pro, the practice side of Booking and Support create their own session from the verified shared one and end it when the shared session ends. Aimedis Rehab keeps its own accounts, which Support also accepts, and the Wiki has its own administrator accounts.

People sign in with a password or with Google. Two-step sign-in with an authenticator app is available; once a person has set it up, the applications ask for it, and administrators in Pro and support staff in Support must use it.

Roles decide what a person may see, and each application checks them on its own server. In Pro a record module appears only when the professional’s role allows it and the patient’s grant covers it, and administrators of Pro, Booking and Decision see no patient data. In Aimedis Decision a physician reads only the cases they have taken on. In Rehab a professional sees a patient’s record only after the patient gives them the Aimedis ID and PIN or accepts their invitation.

Every Aimedis site, this website included, sends a strict content-security policy with a new nonce for each page, so that a script injected into a page without that nonce does not run; this matters because the shared sign-in cookie is valid for every aimedis.com site. Forms that carry a password, PIN or code send it in the body of the request, never in the web address.

The table shows where the platforms store data today, as their repositories, privacy texts and deployment records state it. Providers outside the EU process what they receive for their function, among them Anthropic for AVA’s answers, ElevenLabs for voice, Resend for e-mail and, only in a fallback call, Zoom, all in the United States.

AVA is the Aimedis assistant in every application. It explains, summarizes, finds information, drafts entries and reminds. A draft becomes part of a record only after the person confirms it. AVA never diagnoses, never prescribes and does not replace the judgment of a qualified professional.

Its tools, data context and permissions differ by product, and a conversation in one application does not create a shared memory or unlock another application’s records. In Aimedis Care, with the patient’s consent to AI processing, AVA answers from the patient’s own record with sources. In Pro, the briefing and the attention list are computed from the record’s entries without an AI model, and AVA answers general and reference questions. In Booking, AVA finds times and drafts watches from booking facts; a clinical word filter keeps health details out of its requests, although a word list can miss a word. In Aimedis Onboard, AVA interviews the patient and keeps their own words. In Aimedis Decision, AVA is decision support for the physician, with identifying details removed before a case reaches the model, and explains care information to the patient. In Rehab, it coaches the session and drafts entries that the person confirms. In Connect, AVA’s home brief uses metadata only (counts, times, states and names), never message content; AVA inside chats works on the participant’s device with consent per chat, so end-to-end encryption stays intact, and was first released to a test group. In Support, AVA answers product questions, hands over to a person on request and never acts on accounts. On the public website, AVA searches public site content and helps visitors navigate; it has no patient-record access.

At the time of writing, AVA’s answers in every application, the Wiki and this website are written by Anthropic’s Claude Sonnet 5, a model fixed in each application’s code. Read-aloud and dictation use ElevenLabs, with the Eleven v4 Turbo voice played while it is generated, and Rehab adds a live video face from D-ID for patients. A medical answer names the stage of every source: Aimedis Wiki, Aimedis RAG, PubMed or Public Medical Library. Where no source is sufficient, AVA in the platforms answers from the model’s general knowledge and labels that answer “General medical knowledge”; the Wiki’s own AVA does not answer without a source.

In Care, Pro, Booking, Onboard, Connect, Decision and Rehab, a message that reads like an emergency gets the emergency notice first, before any answer. The notice comes from a fixed multilingual check that runs before any model call and does not depend on budgets or on the AI service being available.

AI output needs the review appropriate to the workflow. Clinical suggestions are decision support for a qualified professional. Retrieval similarity and model-reported confidence are not measures of clinical certainty. Missing evidence or a failed dependency must be surfaced rather than disguised as a complete answer.

Aimedis Decision (since 1 November 2026), Aimedis Connect and Aimedis Rehab (both since 3 November 2026) run video calls on Aimedis’ own LiveKit server at video.aimedis.com. LiveKit is open-source video software that Aimedis hosts itself, so call media does not pass through a third-party video service.

Calls are end-to-end encrypted. Aimedis Decision makes a fresh key for each meeting; in Connect the key is made on a participant’s device and shared through the encrypted conversation, so the server holds no call key; Rehab uses the call kit taken from Connect. Calls offer a device check, a lobby and waiting room, screen sharing, background blur, picture-in-picture and quality settings up to a 4K detail mode.

Zoom remains only as a fallback for a single call: in Aimedis Decision with the patient’s consent, in Connect and Rehab with every participant’s consent. A Zoom fallback call is not end-to-end encrypted by Aimedis; Zoom processes its audio and video.

The table lists the external services that the applications call in their current versions. Each depends on its provider’s availability and on configuration in each environment; an integration listed here is not a commitment for a particular deployment.

The website, Care, Pro, Booking, Onboard, Connect, Decision, Rehab, the Wiki and Support offer the same 18 interface languages: Arabic, Bengali, Chinese, Dutch, English, French, German, Hindi, Japanese, Korean, Portuguese, Russian, Spanish, Urdu, Turkish, Slovenian, Thai and Hebrew, with right-to-left layouts for Arabic, Urdu and Hebrew. Each starts in the language a person chose before; without one, in a supported language of the browser, else in a language suggested by the country, else in English, and keeps that language for later visits. Many newly written texts were machine-translated and await review by native speakers. Voice services, documents and reference catalogues may support a different set.

Where Aimedis sells something, the price is shown in the buyer’s market currency: euros in the EU and EEA, US dollars in the United States, pounds sterling in the United Kingdom, Swiss francs in Switzerland, and the local currency in the United Arab Emirates, Saudi Arabia, Qatar, Kuwait, Bahrain, Oman, India, Bangladesh, Pakistan and Turkey. Every other country pays in US dollars, which makes 14 currencies. A professional’s own sessions in Connect are priced in the currency of the professional’s market.

The patient core is free. Patients pay Aimedis nothing for the health record in Aimedis Care, for finding and booking appointments, for preparing an intake or for taking part in Connect. Rehab has no paid plan today. In Aimedis Decision, Aimedis prices nothing; where a practice charges a private or self-pay fee, the patient sees its cost information first.

Aimedis itself charges for two things. AVA Plus is a monthly plan for patients in Aimedis Care. Without it, five AI uses a day are free: an AVA question, Insights, an AI document import or a diary improvement each count as one, while read-aloud, dictation and emergency notices never count. AVA Plus raises the allowance to up to 300 a day; at the time of writing its list price is EUR 29 a month, shown in the buyer’s currency before purchase. It starts with a 7-day free trial once per account, for which a payment method is needed up front, runs until cancelled, can be cancelled at any time to the end of the paid month and comes with a 14-day right of withdrawal, set out in the app before purchase.

Professionals subscribe in Aimedis Pro, each for themselves, monthly. At the time of writing the list prices are EUR 49 per month for each of Booking, Radiology & Imaging and Connect, and EUR 129 per month for the Practice package of all three. Decision, for physicians, is EUR 149 per month and includes Booking. Each plan offers a 7-day free trial, once per plan for each professional, and the rest of the Pro workspace is free. Where the paid modules have not been switched on, professionals keep their current access without a subscription.

In Connect, professionals set their own prices for sessions, packages and tickets to their information events. Payments go to the professional’s own Stripe account, and at the time of writing Aimedis takes no commission on them. Organizations agree implementation, integration, support and specialist programmes with Aimedis individually.

Further integration is a development and acceptance process. A feature present in a local application, a green demonstration dashboard or a contract labelled live is not proof that an entire patient journey has succeeded in a hosted environment.

Planned and not available today: storage of data in the region the law requires (EU data in the EU, US data in the US, UAE data in the UAE); an Aimedis interface gateway that gives hospitals and practice software one address for HL7 v2 over MLLP, FHIR with SMART Backend Services and national e-health profiles, to be built only with a concrete partner; SNOMED CT, LOINC, ICF and ATC in the Wiki’s terminology server once their licences or permissions are in place; Aimedis Onboard intakes handed to Booking, and Booking video visits; phone dial-in to video calls.

The product family consists of separate web applications and service integrations. Care, Pro, Booking, Onboard, Connect, Decision and Support share one Aimedis account and one database project, in which each application owns its own tables; Rehab and the Wiki run their own. Data ownership and access checks reside in the service that owns the data. There is no central gateway for clinical traffic and no universal identity provider beyond the shared account.

Since 8 November 2026 Care, Pro, Decision and Rehab exchange data through one shared library for FHIR R4, HL7 v2 and GDT, a practice-software format that is one example of many. Aimedis Care offers scoped, read-only FHIR R4 reads, a patient summary in the structure of the International Patient Summary, and an inbox in which the patient reviews records sent by Aimedis Decision, by a connected practice or from a file they import. Pro connects practice software with its own credentials. Rehab accepts FHIR referrals and exports a rehabilitation record and a discharge report as FHIR R4. The Wiki provides FHIR R4 reference resources and the terminology operations for clinical codes.

Clinical codes follow the WHO’s ICD, used in a wide range of countries, with national editions such as ICD-10-GM where a country uses one. In their FHIR output, Care, Pro and Rehab code a diagnosis only when the Wiki confirms the code in the edition concerned; otherwise its text is kept. Care and Pro include 2D and 3D DICOM viewers that open files locally in the browser. None of this establishes a family-wide FHIR-native clinical database, conformance to a certified profile or a ready-made hospital, PACS or national e-health integration.

Start with the person’s task and the product that owns it. Identify the information needed, the required approval and the receiving workflow. Add integrations after their access, failure handling and delivery have been confirmed.

For a product overview, use the application pages. For Wiki retrieval, use the concrete API guide. For a care-platform integration, agree the owning service’s current contract and acceptance process with Aimedis.