---
title: "Discussion on \"Why my clinical RAG is mostly SQL\" | Hashnode"
description: "Discussion on \"Why my clinical RAG is mostly SQL\". In the previous post I built a RAG system over my One Piece notes. At the end, I said I'd tackle something more real next: RAG for the healthcare industry. So here we are.\nThe anime version was fun, a"
url: "https://hashnode.com/posts/why-my-clinical-rag-is-mostly-sql/6a23a4b48f8be6022c79687c"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Why my clinical RAG is mostly SQL](https://codeanding.com/why-my-clinical-rag-is-mostly-sql?utm_source=hashnode&utm_medium=feed)

In the previous post I built a RAG system over my One Piece notes. At the end, I said I'd tackle something more real next: RAG for the healthcare industry. So here we are. The anime version was fun, a

Jun 6 · 8 min read · codeanding.com  
Read the article

-   [#aws](https://hashnode.com/tag/aws)
-   [#rag](https://hashnode.com/tag/rag)
-   [#hybrid-rag-systems](https://hashnode.com/tag/hybrid-rag-systems)
-   [#healthcare](https://hashnode.com/tag/healthcare)

## Written by

[Julissa Rodriguez](https://hashnode.com/@julissarparco)

@julissarparco · Santiago, Chile

  
[View profile](https://hashnode.com/@julissarparco)

Bug Slayer

## Responses 1

Markdown supported · ⌘↵ to post

[Hayrullah Kar](https://hashnode.com/@magesheet)

[Jun 7](https://hashnode.com/posts/why-my-clinical-rag-is-mostly-sql/6a23a4b48f8be6022c79687c/comment/6a25af1a7829edb31110aa3b)

Splitting structured clinical facts into SQL and freeform text into pgvector is pure architectural maturity. Relying on evals rather than unit tests for confident wrong answers is spot on.
