.svg)
Posos
Posos is a French medication-intelligence platform whose CE IIb-marked clinical APIs normalise raw patient data into SNOMED-CT, screen prescriptions for interactions and dosing risks, and ground AI agents in auditable, HAS-approved drug knowledge.
What is Posos?
Posos is a medication-intelligence platform built in Amiens, France, by a team of pharmacists and engineers. It sits between raw clinical data and the prescribing decision, and it is sold in two directions at once: as an infrastructure layer for medical software publishers and AI agent builders, and as a direct application for individual health professionals.
The technical core has three layers. Hybrid NLP models — named-entity recognition and linking, machine learning and computer vision — turn free-text record fields, discharge summaries, scanned paper prescriptions and voice transcriptions into structured data, expressed in SNOMED-CT, FHIR, ICD-10/11, ATC, EDQM, UCUM and UNII, with medicines modelled as IDMP-compatible international virtual products. A medical knowledge graph then links each drug to its indications, target patient profile, interactions, contraindications, dose adjustments and therapeutic alternatives, enriched with learned-society guidelines and hospital protocols. A deterministic reasoning engine finally produces recommendations whose every step a clinician can audit, down to the dose calculation itself.
What distinguishes the commercial offer is that the regulatory burden sits with the vendor. Posos declares itself Manufacturer under EU MDR 2017/745 and ships two CE class IIb medical devices, so an integrator becomes a Distributor instead of having to certify a clinical engine of its own. The platform holds an ISO 13485:2016 certificate and its drug database carries an HAS approval, which the company presents as a shortcut through LAP HAS V2 certification and the CNDA electronic-prescription approval that became mandatory in France in 2025.
Integration runs either through APIs — GraphQL, native FHIR and CDS Hooks, MCP compatibility, any LLM — or through ready-made prescription widgets. The pitch to AI teams is explicitly anti-hallucination: a deterministic engine that constrains and grounds a language model rather than replacing it.
For clinicians the same knowledge reaches iOS, Android and web applications covering interaction screening, adverse-effect lookup, renal and hepatic dose adaptation, prescription scanning, medication reconciliation and shared medication reviews. Drug coverage spans France, Belgium and Luxembourg. Allergy checking, duplicate-therapy detection and personalised care-plan generation are announced but not yet delivered.
What it does
- Structure prescriptions, discharge summaries and voice transcriptions into normalised clinical data
- Detect drug-drug interactions and contraindications against the full patient profile
- Adapt dosages to renal or hepatic impairment, age, pregnancy and comorbidities
- Propose therapeutic alternatives with dose equivalences
- Scan paper or PDF prescriptions and codify drugs, dosages and treatment durations
- Generate shared medication reviews and auditable care plans
- Expose the whole engine through GraphQL, FHIR and CDS Hooks APIs for AI agents
When to use Posos / When not to
A quick filter to help you decide if Posos is the right fit.
When to use Posos
- Health software publishers who must reach LAP HAS V2, CE marking or CNDA electronic-prescription approval without building a certified clinical engine in-house
- Engineering teams building clinical AI agents that need deterministic, auditable outputs instead of unverified LLM answers
- Community pharmacists running shared medication reviews, direct oral anticoagulant consultations and prevention check-ups
- Hospital physicians in anaesthesia, emergency and geriatrics, where medication reconciliation and dose adaptation carry the most risk
- Hospitals, clinics and nursing homes equipping prescribers across the whole medication circuit
When not to use Posos
- Members of the public looking for medication advice: the terms restrict access to health professionals and to medicine and pharmacy students
- Anyone practising outside France, Belgium or Luxembourg, since the drug database covers only those three markets
- Buyers who need a published DPA, a named subprocessor list or a documented position on model training before they can sign
- Teams wanting a self-service product with transparent enterprise pricing: hospital and group licences are quote-only
- Clinicians expecting the tool to decide for them, as the vendor states that medical liability remains entirely with the prescriber
How to use Posos
A typical end-to-end flow, from setup to results.
- Decide which route fits: APIs for full control, ready-made widgets for speed, or the end-user application for individual clinicians
- Request sandbox access or a product conversation through the demo page
- Read the public developer documentation in the help centre, covering connectors, formats, GAM/EHR data integration and exchange security protocols
- Call the clinical APIs over GraphQL, native FHIR or CDS Hooks, from any LLM or MCP-compatible agent
- Alternatively embed the prescription editing and analysis widgets directly into your software
- Work through the vendor's regulatory support: integration strategy assessment, technical integration, help with regulatory files, then post-certification follow-up
- As a health professional, register with your name, e-mail address and profession, which the terms make mandatory
- Install the iOS or Android app, or use the web application
- In a pharmacy running the Id practice-management system, click the "BPM Posos" button from the patient record to sync the file and the last three months of prescriptions
- Photograph any prescription that is not already in the system so it can be recognised and codified automatically
Pros & Cons
Pros
- The CE IIb marking is carried by Posos, so integrators inherit a certified clinical engine rather than certifying one
- ISO 13485:2016 certification and an HAS-approved drug database are supplied as audit evidence
- Deterministic, sourced and traceable output, in deliberate contrast to opaque LLM generation
- Native multi-terminology normalisation covering SNOMED-CT, FHIR, ICD-10/11 and ATC
- A permanently free plan for health professionals and students, alongside a free premium trial
- HDS certified hosting with data stated to be stored in Belgium
- Public developer documentation and sandbox access, with two integration routes from APIs to widgets
Cons
- Drug coverage is limited to France, Belgium and Luxembourg
- The privacy charter dates from October 2018, was written for posos.fr, and covers neither data-subject rights nor supervisory-authority complaints
- No DPA is published, no subprocessor list exists, and no position on training models with customer data is stated anywhere
- The site contradicts itself on price, showing €14.90, €25 and €29 per month for an individual subscription on different pages
- The Tarifs link present in every page's navigation returns a 404, and the help centre points at the same dead link
- Free-trial length is given as two months in the help centre and three months in the terms
- Several modules are announced but undelivered, including allergy checking, duplicate therapy detection and personalised care plans
Pricing & Plans
Yes, there is a permanent free plan: the Basique subscription costs €0 and is open to health professionals and to medicine and pharmacy students. The cheapest paid entry point is €29 excluding tax per month for the Flexibilité pharmacy plan with no commitment, falling to €26 excluding tax per month on an annual commitment; the help centre states the same figure as €313 excluding tax per year for the Premium Libéral licence. The Sérénité plan is €89 excluding tax per month, or €80 on an annual commitment. Medication reviews are billed at €5 excluding tax each on the Flexibilité plan, on a sliding scale down to €1.50 above fifty, and are unlimited at no extra cost on Sérénité. Hospital and group licences are quote-only. Note that the site displays two other individual prices elsewhere and that its own pricing link is broken, so figures should be confirmed with the vendor.
- Basique — €0 per month
- permanent
- for health professionals and students
- with limited features and access to more than 220 reference sources
- Flexibilité — €29 excluding tax per month with no commitment
- or €26 on an annual commitment
- medication reviews billed at €5 excluding tax each on a sliding scale
- Sérénité — €89 excluding tax per month with no commitment
- or €80 on an annual commitment
- with unlimited medication reviews included
- Premium Libéral — €313 excluding tax per year or €29 excluding tax per month
- no commitment
- licensed per user
- Premium Hôpital / Groupements — quote-only
- with configuration costs assessed case by case on top of a monthly or annual subscription
- Module commande EHPAD — optional add-on at €10 excluding tax per month
Data, GDPR & hosting
A consolidated view of how Posos handles your data.
GDPR overview
Compliance is claimed explicitly. Every page footer carries "En conformité RGPD", and the privacy charter invokes both French law 78-17 and Regulation (EU) 2016/679. A data protection officer is named — Benjamin Grelié, reachable at benjamin@posos.fr — and the controller is identified as POSOS SAS at its Amiens registered office. As a French company, Posos needs no Article 27 representative and designates none. HDS certified health-data hosting is claimed, with data stated to be stored in Belgium. The gaps are real, however. The charter is dated 8 October 2018, has never been revised, and names the posos.fr site rather than posos.co. It contains no article on data-subject rights — access, rectification, erasure, portability or restriction — and no mention of complaining to the CNIL. No DPA is published and no subprocessor list exists, although the terms confirm subcontractors are used.
Who owns the data?
The terms are unambiguous about the vendor's side. Article 18 places Posos' systems, software, infrastructure, databases and content under intellectual property and database-producer rights, and grants the user only a non-exclusive, personal, non-transferable SaaS licence that transfers no ownership whatsoever. POSOS SAS, registered in Amiens under number 833 942 030, is the declared data controller. The privacy charter rules out selling, renting or exchanging personal data with third parties, with one exception: a pharmaceutical laboratory the user has asked to be put in touch with. Anonymised data may be shared in statistical reports. Nothing in either document addresses who owns the clinical content a user creates.
Reuse rights
Users receive a SaaS licence to use the service, not a right to reuse what it contains: article 18 of the terms prohibits any disassembly, decompilation, extraction, reproduction or redistribution of Posos' databases and content without written authorisation, and points to database-producer rights as well as copyright. On the vendor's side, the privacy charter lists the purposes for which personal data is processed — service access, customer management, member and prospect files, newsletters and promotional messages, commercial statistics, review handling, personalised replies and legal obligations — resting on legitimate interest, consent for audience-measurement cookies, and contract performance. Recipients are limited to a pharmaceutical laboratory the user asks to be introduced to, public bodies, court officers and debt collectors. The API documentation states that only an anonymised patient profile is required and that no nominative data is needed. Notably, no document collected says anything about using customer data to train models.
Data retention & training
Hosting summary
Two claims sit side by side. The hospital and nursing-home offer pages state plainly that data is stored in Belgium on HDS certified servers, HDS being the French accreditation for hosting personal health data. The API and Id integration pages repeat the HDS claim without naming a country. The legal notice, separately, names Google Cloud at 8 rue de Londres, 75008 Paris as the hosting provider — the provider's French registered address, which is not in itself a statement about where data physically sits. Article 8 of the terms is looser still, committing Posos only to host accounts on its own servers or through a professional hosting provider working to current standards. Beyond that, nothing: no fallback region is named, no subprocessor list is published, and no data-transfer mechanism outside the European Union is described. Jurisdiction is French, since the controller is POSOS SAS in Amiens, and the stated storage country is within the European Union.
Where Posos works
Country-level availability.
Available in
Things to keep in mind
Risks and trade-offs to weigh before adopting Posos.
- The privacy charter is from October 2018, names the wrong domain, and omits data-subject rights and any route to complain to a supervisory authority
- Nothing states whether clinical or customer data feeds model training, and no opt-out is offered, which is a difficult gap to accept in health data
- No DPA and no subprocessor list are published, even though the terms confirm subcontractors are used
- Regulatory names on the compliance pages describe partly what the customer must obtain with Posos' help; only the CE IIb marking, the ISO 13485 certificate and the database's HAS approval belong to the vendor itself
- Automation bias is a real clinical risk: deterministic, well-sourced output invites trust, yet the vendor places medical liability squarely on the prescriber
- Pricing cannot be taken at face value, as three individual prices coexist and the site's own pricing link is broken
- Official contact addresses live on posos.fr rather than on the site's own posos.co domain, which is worth verifying before sending anything sensitive
Setup & Integrations
Technical difficulty
It depends entirely on who you are. For an individual clinician there is nothing to set up: create an account, install the iOS or Android app, and use it. For a software publisher, the vendor claims two to three weeks of technical integration and offers two routes — embeddable widgets, which are light, or GraphQL, FHIR and CDS Hooks APIs, which demand real engineering. Public developer documentation covers connectors, formats, EHR data integration and security protocols. Pharmacies running the Id system get a native integration for a one-off €170 excluding tax fee.
Deployment
Apps stores
Integrations
Supported languages
Behind Posos
Fundraising
Social
Resources
All the official URLs gathered for verification and reference.
Frequently asked questions
Who is Posos intended for?
Is there an API, and is it documented publicly?
Who carries the CE marking when I integrate Posos into my software?
Who is liable if a prescription error occurs?
Which countries does Posos cover?
Is there a free plan, and what does the cheapest paid plan cost?
How long does the free trial last?
Where is the data hosted?
Is customer data used to train AI models?
Is there a mobile application, and a data protection officer?
Should you pick Posos?
Posos occupies a position that is genuinely rare in clinical software: the vendor, not the customer, carries the regulatory weight. Two CE class IIb medical devices, an ISO 13485:2016 certificate and an HAS-approved drug database mean an integrator inherits a certified clinical engine rather than building one, and the company quantifies the saving as three to six months of LAP certification instead of twelve to eighteen. The clinical substance behind that claim looks solid too — a knowledge graph over 220 reference sources, native multi-terminology normalisation, and a deterministic engine whose reasoning a physician can follow step by step. For teams building prescribing agents, that auditability is the whole argument.
The reservations are of two kinds. The first is structural: the product is deeply wired into French healthcare — HAS, LAP, CNDA, DMP, the Id pharmacy system — which is an advantage at home and a limit elsewhere, with drug coverage confined to France, Belgium and Luxembourg. The second is simple neglect. The privacy charter dates from 8 October 2018, has never been revised, still names the posos.fr site rather than posos.co, and contains no article at all on data-subject rights or on complaints to the supervisory authority. No DPA is published, no subprocessor list exists, and nothing anywhere states whether customer data is used to train models.
The public surface is untidy in ways a buyer will notice: the Tarifs link in every page's navigation returns a 404, three different individual prices coexist across the site, the free-trial length is two months in the help centre and three in the terms, and the published sitemap points entirely at a staging domain. None of this touches the clinical engine, but all of it should be confirmed with the vendor before signing.
- Choosing a selection results in a full page refresh.
- Opens in a new window.