DEV Community: michael fabien

The 2 Questions Every ManyChat Agency Client Asks (Answered)

michael fabien — Sat, 27 Jun 2026 09:30:44 +0000

Every ManyChat agency hits the same wall at the same time.

You've built the flow. You've set the triggers. You've delivered open rates your clients haven't seen since 2018. Then the product team leans in: "Can the bot actually sell things?"

Not broadcast a discount code. Not send a generic "check out our store" link. Actually sell — recommend a specific product, match it to what the customer just said, and drop a checkout button right inside the DM.

That question leads directly to a second one.

"How Does It Know What's In Stock?"

This is the question that exposes the real problem with every rule-based product recommendation bot: catalog drift.

Your client updates a price on Friday afternoon. The bot still quotes Thursday's price on Saturday morning. A SKU goes out of stock. The bot keeps recommending it. A variant gets discontinued. The bot generates cart errors.

You end up maintaining a product list inside ManyChat that is always slightly wrong and always your problem.

SmartBrain solves this at the architecture level. The engine connects directly to the live Shopify catalog — real SKUs, real prices, real stock counts, real variants. It does not copy the catalog into a bot flow. It queries it in real time.

When a customer types "I need a moisturizer under $40 for sensitive skin," SmartBrain pulls qualifying products from the actual store, checks current inventory, respects the stated budget, and surfaces a checkout-ready card with a real Buy button. The AI only writes the sentence that frames the product. It cannot invent a price or a discount that does not exist in the store, because it never touches those fields — the deterministic engine does.

Your client's catalog can change a hundred times a week. The recommendation is always accurate.

"Can We Put Our Name On It?"

The second question arrives about three weeks later, usually over a screen share.

The client has seen the engine work. Add-to-cart events are firing from DMs for the first time. Now they want to know if they can show this to their own network — and whether you can sell it as your product.

SmartBrain is built for white-label deployment. You install it inside your client's existing ManyChat account. No rebuild, no migration, no separate platform to explain or support. Your agency name stays on the relationship. You set the margin. You own the upsell path.

The typical ManyChat agency that adds SmartBrain to a client's account unlocks a new recurring revenue line — not a one-time setup fee — because the engine keeps working autonomously after handoff. Flows that used to end at "click here to browse" now close transactions inside the conversation.

Your client gets a bot that knows the catalog cold and never quotes a wrong price in front of a shopper. You get a differentiated product in a market where hundreds of agencies are running identical ManyChat playbooks.

Both questions answered. One integration, no rebuild, full white-label.

See how SmartBrain works for agencies at askamelie.com

Sell in Any Language Without Rebuilding Your ManyChat Flow

michael fabien — Fri, 26 Jun 2026 09:31:01 +0000

Your Shopify store ships to Lyon, São Paulo, and Mexico City. Your ManyChat flow was built in English. What happens when a customer DMs you in French?

Most bots either ignore the language entirely or try to translate on the fly — and then confidently quote a price that doesn't match the product page. That's a trust kill. One wrong number in a DM and the sale is gone.

SmartBrain solves this at the architecture level, not the copy level.

The Engine Picks the Product. The AI Speaks the Language.

SmartBrain is a deterministic commerce engine: it queries your live Shopify catalog — real SKUs, real stock levels, real variant prices — and selects the right product based on what the customer asked for and what budget they stated. No inference, no estimation. The engine either finds a matching product or it doesn't.

Once the product is chosen, the AI copywriter steps in. Its only job is to phrase that already-selected product in the customer's language. It can't change the price, invent a discount, or swap the SKU. The product is locked. The language is flexible.

So when Ana writes "busco algo para el dolor de espalda, menos de 40 euros", SmartBrain reads the budget, queries your catalog for back-pain products under €40, picks the best match, and replies in Spanish — with the correct euro price pulled directly from Shopify. No hallucination. No mismatch.

Inside the DM: A Checkout Card That Actually Converts

The customer doesn't get a link to browse. They get a product card delivered inside the conversation: product name, variant, stock availability, and price — all live from your Shopify catalog — plus a direct Buy button that opens checkout with the item pre-loaded.

The entire path from "I want X" to purchase happens without leaving the DM thread. No redirect friction. No language barrier. No price confusion.

And because SmartBrain plugs into your existing ManyChat setup, there's no rebuild. You connect your Shopify store, and the multilingual engine activates on top of what you already have. Your current automations keep running exactly as before.

Who This Actually Helps

If you're selling across borders — or even serving a bilingual domestic market — you're leaving money on the table every time a customer gets an English reply to a French question and quietly bounces.

The economics are straightforward: SmartBrain respects the budget the customer states. A shopper who says "under $50" won't be shown a $70 product. Pair that with replies in their own language, and you're removing the two biggest friction points in cross-border DM commerce at once — without adding a single new workflow to manage.

There's no smarter move for a Shopify brand running ManyChat at scale than closing the language gap without adding operational complexity.

Ready to sell in every language your customers speak? Explore SmartBrain at askamelie.com.

SmartBrain Never Recommends a Product Above Your Customer's Budget

michael fabien — Tue, 23 Jun 2026 09:31:15 +0000

When a shopper tells your ManyChat bot "I have about $40 to spend," what happens next determines whether you close the sale or lose them forever. Most chatbot setups ignore budget signals entirely — same product carousel for everyone, hope something sticks. SmartBrain is built differently.

The Budget Signal Is a Hard Filter, Not a Hint

Every time a customer mentions a price ceiling — "something under $50," "a gift around $30," "nothing over $80" — SmartBrain treats it as a strict query parameter against your live Shopify catalog.

Not an approximation. Not "roughly similar." The engine queries real product data — actual prices, current stock, active variants — and returns only items priced at or below the stated ceiling. A product priced at $51 when the customer said $50 never appears. Full stop.

This works because SmartBrain's recommendation logic is deterministic: a rule-based commerce engine selects products first, then an AI copywriter phrases the recommendation in natural language. The AI cannot invent prices, manufacture discounts, or hallucinate SKUs. It only writes about what the engine already selected from real catalog data. Catalog integrity is structural, not a policy.

What a Budget-Filtered Recommendation Looks Like in Practice

A customer messages your store: "Looking for a moisturizer, budget around $35."

SmartBrain queries your catalog, filters by category and max price $35, checks live stock, then delivers — inside the DM — a checkout-ready product card: real product photo, exact price, active variant selector, and a live Buy Now button routing directly to Shopify checkout.

No link to a product listing page. No "here are some options." One card, one click, one purchase path.

The customer never sees a product they can't afford. You never lose a sale to sticker shock. Merchants running SmartBrain consistently report that budget-filtered recommendations outperform generic carousels on both click-through and conversion — not because the AI writes better copy, but because showing the right product at the right price removes the friction that kills DM commerce.

A shopper who says "$40" and receives a $65 recommendation buys nothing. A shopper who receives a $37 option with a Buy button in the same message often closes in under 90 seconds.

No Rebuild — Installs on Top of Your Existing ManyChat Flows

SmartBrain isn't a replacement for your current ManyChat setup. It installs as an intelligence layer on top of what you've already built. Your sequences, keyword triggers, opt-in flows — unchanged.

What changes: at the product recommendation moment, SmartBrain intercepts with catalog-aware, budget-filtered logic instead of a static carousel. You configure budget detection once — quick-reply prompt, free-text extraction, or both — and every subsequent conversation respects it automatically.

For Shopify stores with active ManyChat setups, integration typically takes under two hours. No new platform to learn, no migration, no downtime.

Budget respect isn't a nice-to-have feature. It's the mechanical reason DM commerce converts — and the reason SmartBrain's architecture makes it structurally impossible to embarrass a customer with the wrong price.

Ready to turn budget signals into closed sales? See SmartBrain at askamelie.com.

How SmartBrain Turns Dead DMs Into Checkout-Ready Sales

michael fabien — Mon, 22 Jun 2026 09:30:52 +0000

The Menu-Bot Problem Nobody Talks About

Every Shopify store that plugs ManyChat in eventually builds the same thing: a menu. "Tap 1 for shoes. Tap 2 for bags." It feels like automation. It isn't — it's a digital phone tree from 2003.

Here's what actually happens when a customer DMs your store at 11 PM:

Customer: "I'm looking for a birthday gift for my sister, around $60, she's into skincare."

Menu-bot: "Please choose a category: 👟 Footwear / 👜 Accessories / 💄 Beauty"

The customer taps Beauty. Gets a link to your full catalog. Leaves. You lost a $60 sale to decision fatigue.

That's not a traffic problem. That's a conversation problem.

What SmartBrain Does Instead (The After)

SmartBrain plugs into your existing ManyChat flow — no rebuild, no new platform — and replaces the dead-end menu with a deterministic commerce engine.

When the same customer sends that message, SmartBrain does four things in under two seconds:

Reads the intent — "birthday gift, sister, skincare, ~$60"
Queries your live Shopify catalog — real products, real prices, real stock levels
Selects the best match — a $58 Vitamin C serum set, in stock, variant confirmed
Phrases it conversationally — "This Vitamin C Brightening Set is a popular gifting pick — it's $58, ships in a gift-ready box, and we have 14 left. Want me to send you the checkout link?"

The customer gets a product card with a real Buy button, right inside the DM. One tap. Checkout open.

No hallucinated price. No "sorry, that item is sold out" after they click. No AI-invented discount your POS has to honor later. SmartBrain cannot fabricate product data because it never writes it — it reads from Shopify first, then the AI copywriter phrases what the engine already found.

Why Stores Running This Don't Go Back to Menus

Three things happen when you replace a menu-bot with SmartBrain:

Recovered sales from budget-constrained shoppers. SmartBrain respects the budget a customer states. A $60 ceiling means it will never surface a $90 product and create friction. The recommendation fits the conversation.

Zero merchant risk on pricing. Your flash sale ends at midnight. Shopify updates the price. SmartBrain reads the updated price at the exact moment of the DM. No sync lag, no stale cache, no awkward "sorry, that price expired" email to write.

No rip-and-replace. If you've spent months building your ManyChat subscriber list and flows, they stay. SmartBrain drops in as a node. Your subscribers won't notice a rebuild — they'll just notice the bot actually answers them now.

The before-and-after isn't about technology. It's about whether your DM channel converts or just exists. A menu-bot is a filing cabinet. SmartBrain is a salesperson who knows your entire catalog cold, never sleeps, and never quotes a price that isn't live in Shopify.

If your store runs ManyChat and your DM conversion rate is a rounding error, that's the gap.

Turn your DMs into a revenue channel → https://askamelie.com

Turn ManyChat Buying Intent Into Checkout-Ready Cards With SmartBrain

michael fabien — Sun, 21 Jun 2026 09:31:23 +0000

Your ManyChat flows capture buying intent every single day. Someone types "do you have this in blue?" or "I need a gift under $50" — and the conversation stalls. No friction-free path to checkout. No sale. The drop-off is invisible, but it adds up to real lost revenue.

SmartBrain closes that gap. It plugs into your existing ManyChat setup and converts those DM intent signals into checkout-ready product cards — complete with a real Buy button — without rebuilding a single flow.

Why Buying Intent Dies in the DM

Most Shopify brands treat ManyChat as a top-of-funnel tool: capture the lead, send the broadcast, hope they click through to the store. But the moment a customer types a specific buying signal — a budget ceiling, a variant question, a product category — there's no friction-free path to purchase inside the thread. The best most bots can offer is a storefront link: two more clicks, a context switch, and a measurable conversion drop.

The deeper problem is accuracy. Any bot that attempts to match products in real time risks surfacing stale data — wrong prices, out-of-stock variants, invented discounts. One incorrect price shown in a DM is a customer service incident waiting to happen.

The Deterministic Engine Behind the Card

SmartBrain is built on a deterministic commerce engine. When a customer says "something for dry skin under $40," SmartBrain queries your live Shopify catalog — real current prices, real stock levels, real available variants — and selects the right match based on rules you define. Budget caps, inventory status, collection logic: all enforced by the engine before any AI touches the response.

The AI layer has one job: write the recommendation. It phrases a sentence around a product that already exists in your store. It cannot hallucinate a price, invent a SKU, or suggest a size that's sold out. The output is a structured product card — image, name, price, variant selector, and a native Buy button — delivered directly inside the DM thread.

The customer taps Buy and completes the purchase without leaving the conversation.

From Intent Signal to Completed Order

A customer messages your bot at 11pm looking for a coffee-related gift under $60. SmartBrain reads the intent, queries your catalog, picks the strongest match by your rules, writes a two-sentence recommendation, and returns a product card with a live checkout link embedded in the Buy button. The whole exchange takes seconds. Your team sees a completed order in the morning.

No redirect. No abandoned cart follow-up sequence. No manual intervention required.

Because SmartBrain attaches to your existing ManyChat setup, your flows, keywords, and audience segments stay untouched. It activates at the moments where buying intent is highest and handles the close.

If your ManyChat DMs are generating intent signals that currently go nowhere, SmartBrain converts them into revenue.

See SmartBrain in action at https://askamelie.com

Why Shopify Stores Need a Deterministic Engine, Not an LLM Chatbot

michael fabien — Sat, 20 Jun 2026 10:09:15 +0000

Every Shopify merchant chasing conversational commerce has heard the pitch: "Just plug in an AI chatbot and watch sales roll in." Then the chargebacks start. A customer screenshots a price the bot invented. Another orders a variant that went out of stock six weeks ago. The bot was confident. The bot was wrong.

This is the structural flaw of deploying a pure large-language model directly against your catalog. LLMs are probability engines — they predict plausible text. A plausible-sounding price is not the same as the price in your Shopify admin.

Why Pure-LLM Chatbots Break in E-Commerce

When a customer asks "what's the cheapest blue hoodie under $60?", a general-purpose LLM has two options: hallucinate from training data, or run a fuzzy retrieval that still leaves room for interpretation errors. Neither is acceptable when money changes hands.

The consequences are concrete:

Invented discounts customers demand at checkout, forcing manual overrides or refunds
Discontinued SKUs confidently recommended, leading to failed checkouts and support tickets
Wrong variant pricing — XL costs more than S, and the model simply doesn't know that
Out-of-stock promises that destroy trust the moment they surface

One bad DM experience costs you not just the sale, but the customer's lifetime value — and the public review that follows.

How a Deterministic Engine Fixes This at the Root

SmartBrain doesn't ask an LLM which product to recommend. It uses a deterministic commerce engine that queries your live Shopify catalog directly: real prices, real stock levels, real variant availability, real SKUs. The engine applies your rules — budget filters, category constraints, margin floors — and selects the correct product programmatically.

Only after a product is selected does the AI enter the picture. The AI copywriter's single job is to phrase that already-chosen product in a way that fits the customer's context and tone. It cannot hallucinate a price because the price is already locked. It cannot suggest an out-of-stock variant because the engine already filtered it out at query time.

The output is a checkout-ready product card delivered directly inside the DM — real product image, real price, real Buy button. The customer clicks and lands on a pre-filled checkout. Zero friction, zero surprises, zero chargebacks from invented discounts.

Plugs Into Your Existing ManyChat — No Rebuild Required

If you're already running ManyChat flows, SmartBrain connects without replacing what you've built. It adds a deterministic product recommendation layer on top of your existing automations. No flow rebuilds, no migrating conversation logic, no retraining period.

The integration also respects customer-stated budgets as a hard constraint, not a suggestion. When someone says "I'm looking for something around $40," that filter runs against the live catalog at query time. The product returned is always within budget. Always in stock. Always a real SKU your fulfillment team can actually ship.

For Shopify merchants driving volume through DMs, this isn't an incremental improvement — it's the difference between a chatbot that entertains and a revenue engine that converts without blowing up your support queue.

Turn your ManyChat DMs into a zero-hallucination checkout lane at askamelie.com.

Before & After: What Happens When a Dumb Shopify Chatbot Gets a Brain

michael fabien — Sat, 20 Jun 2026 10:09:11 +0000

Every Shopify store with a ManyChat bot has the same quiet leak: DMs full of buying intent, answered by a bot that can only send menus. The customer is ready. The bot is busy asking them to press 1, 2, or 3.

Here is the same conversation, before and after you give that bot a brain.

Before: the menu machine

Customer: hey do you have something for dry skin? budget around $40

Bot: Welcome! 👋 Please choose an option:
1️⃣ Shop all products
2️⃣ Track my order
3️⃣ Talk to support

Customer: …
(left, opened a competitor's tab)

The bot had everything it needed to make a sale and instead handed the customer a directory. This is not a content problem you fix with better copy. The bot literally cannot see your catalog, your prices, or your stock. It is a switchboard, not a salesperson.

After: the conversation closes

Customer: hey do you have something for dry skin? budget around $40

SmartBrain: Yes — our Hydrating Repair Serum is made exactly for dry skin, and it's $39. Want me to send it over?
🧴 Hydrating Repair Serum — $39 [ Buy now ]

Customer: yes please

(checkout link tapped — sale recovered in the DM)

Same customer, same DM, same two seconds. One version sends them to a menu. The other sends them a product card with a real buy button.

What changed under the hood

SmartBrain did not "get smarter at chatting." It got connected to reality:

It read the intent — dry skin, ~$40 ceiling — instead of pattern-matching to a menu.
A deterministic engine queried the real Shopify catalog — filtering by need, price, and live stock. The recommended serum is a real product at a real price, not an LLM guess.
The AI wrote one clean line to present it, in the customer's language.
It returned a checkout-ready card, not a paragraph telling them to "browse the site."

Crucially, SmartBrain never invents a product or a price. The engine picks from your actual catalog; the AI only phrases the pick. Worst case is a slightly plain sentence — never a fake discount you have to honor.

Why this is an upgrade, not a rebuild

You do not throw away your ManyChat setup to get this. SmartBrain plugs into the bot you already run:

Keep your flows, your audience, your DM volume.
Add memory, catalog-aware recommendations, and in-chat buy buttons.
Live in minutes, not a migration project.

The leak was never that customers were not interested. It was that your bot answered interested customers with a menu. Give it a brain and the same conversations start ending in carts.

Turn DM intent into checkouts → https://askamelie.com

SmartBrain: A Deterministic Commerce Engine for Shopify, Not Another Chatbot

michael fabien — Sat, 20 Jun 2026 10:09:07 +0000

Most "AI for commerce" tools are a language model in a trench coat. You ask for a product, the model improvises an answer, and sometimes it invents a SKU, a price, or a discount that does not exist. That is fine for a demo and a disaster for a store.

SmartBrain is built the other way around. It is a deterministic commerce engine with an AI copywriter bolted on top — never the reverse.

The split that makes it safe

SmartBrain separates two jobs that most chatbots dangerously merge:

Deciding what to sell. This is done by a deterministic product engine that queries your actual Shopify catalog: real inventory, real prices, real variants, real availability. The model does not get a vote here. If a product is out of stock or over budget, it is simply not eligible.
Deciding how to say it. This is the only place the LLM is allowed to act — turning the chosen product into a warm, on-brand sentence in the customer's language.

Because the engine picks the product and the AI only phrases it, SmartBrain cannot hallucinate a price, a discount, or a product that does not exist. The worst case is a slightly awkward sentence, not a fake $20 coupon honored at checkout.

Why "deterministic" is the whole pitch

When a merchant connects a store, three things become non-negotiable guarantees rather than hopes:

Catalog truth. Every recommendation maps to a real product ID. No phantom SKUs.
Budget respect. Tell it a customer's ceiling and it will never surface something above it. The constraint lives in the engine, not in a prompt the model might ignore.
Checkout-ready output. A recommendation is not a paragraph of prose — it is a product card with a real buy URL. The conversation ends in a cart, not a "you can find it on our site somewhere."

A pure-LLM bot can do none of these reliably, because every answer is a fresh roll of the dice.

Where it lives: inside the conversation you already have

SmartBrain plugs into ManyChat + Shopify. You keep your existing flows, your existing audience, your existing DM volume. SmartBrain adds the brain:

It reads what the customer actually wants ("something gentle for dry skin, under $40").
The engine filters your catalog deterministically against intent + budget + stock.
The AI writes one clean recommendation in the customer's language.
The customer gets a product card with a Buy button, right in the DM.

No rebuild, no migration, no 500-branch flow tree to maintain.

The mental model

Think of a great in-store associate. They do not invent products — they know the shelf cold (that is the deterministic engine). What makes them good is how they read you and talk to you (that is the LLM). You would never hire an associate who confidently sells things the store does not carry. So why ship a bot that does?

SmartBrain gives your ManyChat + Shopify setup an associate that knows the shelf cold and talks like a human — and never makes up the shelf.

Give your store a brain → https://askamelie.com

Méthode KFP pour les EDN : décision clinique chronométrée

michael fabien — Mon, 08 Jun 2026 07:32:29 +0000

Le KFP (Key Feature Problem) est devenu central depuis la réforme R2C 2022 — c'est 30% du score EDN. Voici la méthode.

Format KFP

Un cas clinique court (5-15 lignes) avec 3-5 questions de décision. Chaque question = un point clé du raisonnement (= un "feature").

Pas de question piège, mais des décisions impliquant un GRADE de connaissance précis.

La méthode en 4 minutes

Minute 1 : Lecture active

Surligner l'âge, antécédents, terrain
Identifier le motif principal et les drapeaux rouges

Minute 2 : Décision diagnostique

Hypothèse principale + 1-2 différentiels
Critère discriminant

Minute 3 : Décision thérapeutique

Urgence ? Prise en charge en ambulatoire vs hospitalisation ?
Quel traitement de première ligne ?

Minute 4 : Communication et suivi

Annonce, surveillance, éducation
Critères d'alerte pour le patient

Exemple — IDM inaugural (item 232)

Patient de 62 ans, diabétique. Douleur thoracique rétrosternale depuis 2h.

KFP-1 : examen immédiat → ECG en 10 min + troponine ultra-sensible.
KFP-2 : ECG = sus-décalage ST V2-V4. Décision → coronarographie d'urgence < 90 min.
KFP-3 : traitement pré-hospitalier → MONA + double antiagrégation + héparine.
KFP-4 : suivi → réadaptation cardiaque + éducation thérapeutique.

Ressources

Contenu pédagogique IA-assisté basé sur référentiels officiels (CNG, SIDES UNESS, collèges nationaux).

Originally published on Ask Amelie

Items EDN par spécialité — guide 15 spécialités prioritaires

michael fabien — Mon, 08 Jun 2026 07:16:47 +0000

L'EDN (Examen Dématérialisé National) format R2C 2022 = 360 items à connaître pour le second cycle médecine en France. Voici comment les attaquer par spécialité.

Méthode KFP + QI

KFP (Key Feature Problem, 30%) : décision clinique chronométrée 4 min.
QI (Question Isolée, 40%) : connaissance pure 30 sec.
ECOS (30%) : 10 stations × 10 min en mai.

Items prioritaires par spécialité

Cardiologie

224 — Hypertension artérielle (rang A)
232 — Infarctus myocardique (rang A)
234 — Insuffisance cardiaque (rang A)
339 — Arrêt cardio-respiratoire (rang A) Détails complets

Pneumologie

188 — Asthme aigu grave (rang A)
200 — Toux chronique (rang B)
207 — BPCO (rang A)
351 — Embolie pulmonaire (rang A)

Neurologie

104 — AVC ischémique (rang A — délai thrombolyse)
89 — Épilepsie
106 — Méningite

Gastro

280 — RGO
285 — Pancréatite aiguë
287 — Ictère

Infectiologie

154 — Méningite bactérienne
159 — Sepsis
173 — Antibiothérapie

Psychiatrie

64 — Dépression majeure
68 — Troubles anxieux
73 — Schizophrénie

Méthode rotative 12 semaines

Cardio + pneumo (sem 1-2)
Gastro + uro (sem 3-4)
Gynéco + pédia (sem 5-6)
Neuro + psy (sem 7-8)
Infectio + rhumato (sem 9-10)
Transversal + ECOS (sem 11-12)

Pour s'entraîner

15 fiches détaillées : askamelie.com/items-edn/
Annales 2025 corrigées : askamelie.com/blog/annales-edn-2025-corriges
Coach IA dans tes DM : askamelie.com/chat-amelie/

Contenu pédagogique IA-assisté, basé sur les référentiels officiels (CNG, SIDES UNESS, collèges nationaux).

Originally published on Ask Amelie

EDN 2025 : ce qui est tombé et ce qu'il faut anticiper pour 2026

michael fabien — Fri, 05 Jun 2026 12:08:37 +0000

L'EDN (Examen Dématérialisé National) a remplacé l'ECN en 2023 avec le format R2C 2022. Décortiquer 2025 permet d'anticiper 2026.

Spécialités tombées en 2025

Cardio (item 232 — IDM, item 224 — HTA) : KFP sur un infarctus inaugural chez un patient diabétique. QI sur l'hypertension résistante.

Pneumo (item 188 — asthme, item 200 — toux chronique) : asthme aigu grave en ambulatoire avec décision d'orientation.

Gastroentérologie (item 280 — RGO, item 285 — pancréatite) : pancréatite aiguë biliaire, conduite à tenir en urgence.

Neurologie (item 104 — AVC, item 89 — épilepsie) : prise en charge AVC ischémique en thrombolyse.

Infectiologie (item 154 — méningite, item 159 — sepsis) : sepsis à point de départ urinaire chez un sujet âgé.

Méthode KFP + QI

Le KFP (Key Feature Problem) cible la décision — pas la connaissance.
Le QI (Question Isolée) cible la connaissance pure.

Stratégie d'entraînement :

KFP : se chronométrer 4 min/cas, forcer une décision claire
QI : passer en mode rapid-fire 30 sec/question
Rotation hebdo par cluster d'items

Pour 2026 — axes prioritaires

Sur la base des évolutions et des items rang A non couverts en 2025 :

Endocrinologie (item 245 — diabète T2, item 253 — obésité)
Néphrologie (item 263 — IRA, item 264 — IRC)
Rhumatologie (item 197 — PR)
Hématologie (item 296 — anémie)
Pédiatrie (item 109 — convulsions, item 144 — fièvre)

Ressources

Pour t'entraîner : ton tuteur IA dans tes DM — askamelie.com/chat-amelie/

Sources : SIDES UNESS, collèges nationaux. Contenu pédagogique sans valeur de remplacement des recommandations officielles.

Originally published on Ask Amelie

5 cas cliniques EDN incontournables (cardio, uro, pneumo, neuro, hémato) avec corrigés et pièges classiques

michael fabien — Thu, 04 Jun 2026 07:36:37 +0000

5 cas cliniques EDN incontournables — corrigés détaillés

Tu prépares les Épreuves Dématérialisées Nationales (EDN) ? Voici 5 cas cliniques courts par spécialité, avec corrigés structurés et pièges classiques. Tous les cas sont travaillables sur Ask Amélie ECN en mode interactif (l'IA te corrige en temps réel et planifie ta révision en répétition espacée).

Pourquoi ces 5 cas ?

Cardio, uro, pneumo, neuro, hémato : ce sont les 5 spécialités qui pèsent le plus dans l'EDN (en termes de items LiSA mobilisés ET de dossiers progressifs). Si tu maîtrises les pièges classiques de ces 5 cas, tu sécurises déjà 30-40% des points de la session.

Cas — cas-cardio-01

Cas clinique express EDN. Homme 68 ans, HTA + tabac 40 PA. Douleur thoracique constrictive type 'barre' à la marche rapide, cède en 3 min au repos. ECG de repos normal. Troponine négative.

Ton diagnostic le plus probable ? Ton examen de seconde intention ?

La moitié des étudiants oublient la 1re étape avant l'épreuve d'effort. Réponse complète + piège item 334 sur Ask Amélie.
ecn.askamelie.com #EDN #cardio #ECN

Cas — cas-uro-01

Cas clinique EDN urologie. Femme 32 ans, sans antcd, dysurie + pollakiurie depuis 48h, fièvre 39,2°C, douleur lombaire droite + Giordano +. BU : leuco +++, nitrites +.

Diagnostic ?
Simple ou à risque de complication ?
Quel ATB en probabiliste ?

80% des candidats EDN se trompent sur le critère 'à risque de complication'. Pose la question à Amélie, elle déroule l'algo HAS.
ecn.askamelie.com #EDN #uro #item161

Cas — cas-pneumo-01

Cas clinique pneumo/cardio EDN. Homme 55 ans, dyspnée d'effort NYHA III depuis 3 mois. Crépitants bilatéraux base + OMI bilatéraux + turgescence jugulaire. BNP 1850. ETT : FEVG 55%.

ICFEp ou ICFEa ?
Mécanisme physiopathologique ?
Traitement de fond ?

Le piège item 232 : la FEVG normale n'exclut PAS l'insuffisance cardiaque. Amélie te liste les 4 critères ESC.
ecn.askamelie.com #EDN #cardio

Cas — cas-neuro-01

Cas clinique neuro EDN. Femme 28 ans, paresthésies des deux MI depuis 3 semaines. Antcd : épisode de baisse d'AV œil gauche régressif il y a 14 mois. IRM cérébrale : 4 hypersignaux T2 péri-ventriculaires + 1 juxta-cortical.

Diagnostic le plus probable ?
Critères diag à appliquer ?
Quel exam complémentaire ?

Critères de McDonald 2017 : dissémination temporelle + spatiale. Amélie te fait l'arbre déroulé.
ecn.askamelie.com #EDN #neuro #SEP #item104

Cas — cas-hemato-01

Cas clinique hémato EDN. Homme 65 ans, asthénie depuis 6 mois. Examen : ADP cervicales bilatérales fermes, indolores, splénomégalie modérée. NFS : Hb 12, plaquettes 180, leucocytes 28, dont lymphocytes 25 G/L.

Diagnostic le + probable ?
Examen clé pour le confirmer ?
Classification de Binet ?

LLC = lymphocytose absolue > 5 G/L PERSISTANTE + immunophénotypage. Amélie te déroule Binet A/B/C en 30s.
ecn.askamelie.com #EDN #hemato #LLC #item217

Mnémo à connaître par cœur

mnemo-cha2ds2

Mnémo cardio EDN incontournable : CHA₂DS₂-VASc (risque thromboembolique en FA non valvulaire).

C = Cardiac failure (IC) → 1pt
H = HTA → 1pt
A₂ = Age ≥ 75 → 2pts
D = Diabète → 1pt
S₂ = Stroke / AIT / embolie → 2pts
V = Vasculaire (IDM, AOMI) → 1pt
A = Age 65-74 → 1pt
Sc = Sex catégorie féminin → 1pt (si ≥1 autre facteur)

Décision : ≥2 chez ♂ / ≥3 chez ♀ → anticoagulation orale (AOD en 1re intention).
Item 232, 232bis. Amélie te pose la question en QI et corrige direct.
ecn.askamelie.com #EDN #cardio #FA

mnemo-abcde

Mnémo URG/réa absolu pour les stations ECOS : ABCDE (prise en charge initiale).

A = Airway (libération VAS + protection rachis)
B = Breathing (FR, SpO₂, ausculation, O₂)
C = Circulation (FC, TA, perfusion, VVP, remplissage)
D = Disability (Glasgow, pupilles, glycémie capillaire)
E = Exposure (déshabiller, T°, examen complet, rechauffement)

Règle d'or station ECOS : on ne passe JAMAIS à la lettre suivante tant que la précédente n'est pas sécurisée. 60% des candidats se font sanctionner sur ce point.
ecos.askamelie.com #ECOS #urgences #DUMA

mnemo-face-fa

Mnémo neuro AVC : F.A.S.T. (à connaître pour le grand public ET pour l'item 100).

F = Face : asymétrie faciale (faire sourire le patient)
A = Arm : déficit moteur d'un bras (lever les 2 bras 10s)
S = Speech : trouble du langage (faire répéter une phrase simple)
T = Time : noter l'heure de début → fenêtre thrombolyse 4h30 / thrombectomie 6h (jusqu'à 24h sur sélection IRM/CT-perf)

Un signe positif = appel 15 immédiat. Item 100 EDN.
ecn.askamelie.com #EDN #neuro #AVC

3 pièges classiques à éviter

piege-uvee

Piège EDN typique item 81 — uvéite antérieure.

La faute classique : « patient jeune, uvéite, on met corticoïdes locaux + cycloplégique, c'est bon ».

NON. Toute uvéite (surtout récidivante / bilatérale / chez le jeune) impose un bilan étiologique :

HLA-B27 (SPA, Behçet)
Sérologies (syphilis, Lyme, tuberculose, HSV/VZV)
Rx thorax / TDM thx (sarcoïdose)
Bilan MICI si signes digestifs

Les correcteurs adorent ce piège. 70% des candidats oublient le bilan étio. Amélie te liste les 6 examens à demander.
ecn.askamelie.com #EDN #ophtalmo

piege-bpco

Piège EDN item 209 — exacerbation de BPCO.

Les 2 fautes classiques :

Mettre des ATB d'emblée : NON. Critères d'Anthonisen = augmentation volume + purulence expectorations + dyspnée. Au moins 2/3 → ATB. Pas systématique.
Oublier la VNI : indication formelle dès pH < 7,35 + PaCO₂ > 45 mmHg (acidose respiratoire). C'est la principale erreur d'orientation.

O₂ titré pour SpO₂ 88-92% (PAS 95-100% = aggrave hypercapnie). Aérosols bronchodilatateurs + corticothérapie PO 5j.

Amélie te déroule l'arbre HAS en 1 min.
ecn.askamelie.com #EDN #pneumo

piege-stt

Piège EDN cardio item 334 — SCA ST non sus.

L'erreur typique : « troponine négative à H0 + ECG normal → on rentre à la maison ». FAUX.

Devant DT évocatrice + ECG non sus :

Tropo Hs-cTn à H0 + H1 (algo rapide ESC 2020) OU H0 + H3
Si delta < 5 ng/L et tropo < seuil → exclusion possible
Si delta ≥ 5 ng/L ou tropo > 99e percentile → rule-in

Ne JAMAIS sortir un patient sur 1 seule troponine. Le piège fait perdre l'épreuve clinique. Amélie te fait la grille de lecture.
ecn.askamelie.com #EDN #cardio #SCA

Pour aller plus loin

Tu peux travailler ces cas en mode interactif avec Ask Amélie ECN : tu poses ton diagnostic, l'IA te corrige, te liste les items LiSA touchés et planifie ta révision en répétition espacée (J+1, J+3, J+7, J+15, J+30).

Tu peux aussi simuler les ECOS oraux à voix haute sur ecos.askamelie.com (1 station gratuite par semaine, Premium illimité à 24,99€/mois).

Bon courage et bonne révision.

Cet article fait partie d'une série de contenus de révision EDN/ECOS produits par l'équipe Ask Amélie.