惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

T
Threatpost
CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
T
The Blog of Author Tim Ferriss
S
SegmentFault 最新的问题
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
博客园 - 司徒正美
T
Tailwind CSS Blog
The Cloudflare Blog
The Last Watchdog
The Last Watchdog
PCI Perspectives
PCI Perspectives
博客园 - 聂微东
Stack Overflow Blog
Stack Overflow Blog
TaoSecurity Blog
TaoSecurity Blog
云风的 BLOG
云风的 BLOG
C
Cybersecurity and Infrastructure Security Agency CISA
O
OpenAI News
Recorded Future
Recorded Future
GbyAI
GbyAI
www.infosecurity-magazine.com
www.infosecurity-magazine.com
Y
Y Combinator Blog
D
Darknet – Hacking Tools, Hacker News & Cyber Security
量子位
博客园 - 叶小钗
V
Vulnerabilities – Threatpost
F
Full Disclosure
Recent Announcements
Recent Announcements
Vercel News
Vercel News
S
Schneier on Security
H
Heimdal Security Blog
Cisco Talos Blog
Cisco Talos Blog
V2EX - 技术
V2EX - 技术
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
B
Blog RSS Feed
宝玉的分享
宝玉的分享
Exploit-DB.com RSS Feed
Exploit-DB.com RSS Feed
P
Privacy & Cybersecurity Law Blog
T
Threat Research - Cisco Blogs
G
Google Developers Blog
C
Cyber Attacks, Cyber Crime and Cyber Security
爱范儿
爱范儿
IT之家
IT之家
大猫的无限游戏
大猫的无限游戏
C
Check Point Blog
N
Netflix TechBlog - Medium
S
Security @ Cisco Blogs
cs.CV updates on arXiv.org
cs.CV updates on arXiv.org
Microsoft Azure Blog
Microsoft Azure Blog
H
Hackread – Cybersecurity News, Data Breaches, AI and More
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
Cyberwarzone
Cyberwarzone

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant Common SOC 2 Failures (Real World) Stop Vibe-Checking Your AI App: A Practical Guide to Evals How to Use SonarQube and SonarScanner Locally to Level Up Your Code Quality Your Next To-Do App Is Dead — I Replaced Mine with an OpenClaw AI Sign a Nostr event in 60 lines of Python using coincurve — no nostr-sdk, no nbxplorer, no rust toolchain ITGC Audit Explained Like You’re in Big 4 Patch Tuesday abril 2026: Microsoft parcha 163 vulnerabilidades y un zero-day en SharePoint Stop scraping everything: a better way to track competitor price changes Listing on MCPize + the Official MCP Registry while routing payments OUTSIDE the marketplace — how I kept 100% of my x402 revenue Building an AI-Powered Risk Intelligence System Using Serverless Architecture Why We Ripped Function Overloading Out of Our AI Toolchain Testing AI-Generated Code: How to Actually Know If It Works SaaS Churn Is Killing Your Business. Here Is What to Do About It (Without a Support Team) The Speed of AI Is No Longer Linear - And Self-Improving Models Are Why How to Implement RBAC for MCP Tools: A Practical Guide for Engineering Teams From Standard Quote to Persuasive Proposal: AI Automation for Arborists I built a CLI that scaffolds complete multi-tenant SaaS apps Axios CVE-2025–62718: The Silent SSRF Bug That Could Be Hiding in Your Node.js App Right Now The dashboard that ended our friendship Data Pipelines Explained Simply (and How to Build Them with Python) The Hidden Cost of AI Systems Nobody Talks About. undefined vs undeclared, and how typeof behaves Switching from file-based jobs to NATS/Kafka in Rust without changing code io_uring Adventures: Rust Servers That Love Syscalls Why Agentic AI is Killing the Traditional Database The POUR principles of web accessibility for developers and designers Quantum Neural Network 3D — A Deep Dive into Interactive WebGL Visualization How To Install Caveman In Codex On macOS And Windows Automation Pipeline Reliability: Why Your Workflow Breaks When Nobody Is Watching I Built an 'Open World' AI Coding Agent — It Works From ANY Folder From Freelancing to Product: A Tech Service Company's SaaS Transformation China's AI Giants: Adding Tencent Hunyuan & ByteDance Doubao to AI University (74 Providers) On the Vibe Coders and Their Lies clerk: Auto-Summarize Your Claude Code Sessions AI Weekly — 2026/04/10–04/17 | The Model Lockdown Is Here, but the Toolchain Is the Real Battleground AI 週報 — 2026/04/10–2026/04/17 模型封鎖潮來了,但工具鏈才是真戰場 Maybe this is how Open-Source apps are born... 🚀 Fine-Tune LLMs with LoRA and QLoRA: 2026 Guide tRPC v11 + Next.js App Router: End-to-End Type Safety Without the Boilerplate ShadCN UI in 2026: Why I Stopped Installing Component Libraries and Started Owning My Components SaaS Billing in React Server Components: Stripe + Supabase Without a Single `useEffect` Join our DEV Weekend Challenge — $1,000 in Prizes Across TEN winners! Submissions Due April 20 at 6:59 AM UTC. Implementing FSRS Spaced Repetition in Flutter + Supabase — Adding Memory Science to an AI Learning App "I Texted My Localhost From the Train — Claude Code Fixed the Bug Before I Got Home" I Built a Sales Prep AI and It Went Deeper Than Expected Design to Code #2: One JSON, Eleven Outputs Solving the 100M-Row Problem: A Summary Table Pattern for High-Volume Push Notification Logs Flutter Web With Wasm: What Actually Changes For Developers I Built 50 Royalty-Free Soundtracks for My Side Project in a Weekend Using AI Music Generation The Vibe Coding Security Checklist: 7 Things to Check Before You Ship Stop Letting Googlebot Guess Fix Your React App's SEO Right Desconstruindo o Streaming do LinkedIn: Como Criar um Engine de Extração de Vídeo de Alta Performance com HLS e FFmpeg (EDA Part-1) EDA (Exploratory Data Analysis) Explained With Real Life — Why Looking at Your Data Is the Most Important Step in Machine Learning Brand Relationship Management at Scale: Our 4-Touch Outreach System for 200+ Brands Why String.fromEnvironment() Might Return an Empty String in Dart JGuardrails 1.0.0 — Hardening Java LLM Apps Against Jailbreaks, Toxicity, and Prompt Injection Plan and Schedule a Full Week of Threads Content From One Claude Conversation Coding Cat Oran Ep3, Five Tables Changed Everything Updated: BFF Pattern I'm done watching freelancers get buried by 200 proposals. So I'm building the alternative. This is my first post BFS Algorithm in Java Step by Step Tutorial with Examples Tracking LLM Pricing Monthly: An Open Dataset for 22 AI Models How We Measure Content ROI on a Comparison Site: Revenue Attribution Without Perfect Data Introducing Nova AI Ops: The AI-Native Operating System for SRE Teams I built a free desktop video downloader for Windows — Grabbit How Talkie OCR Helps Vision-Impaired & Dyslexic Users Read the World Around Them VRCFaceTracking安装和iPhone面捕配置教程,有bug Even CrowdStrike Can't See Your Agents The Automation Gold Rush: What n8n Workflows and Claude Are Opening Up for Developers Right Now
Building a FHIR-Compliant ADT Database: Encounters, Polymorphism, and Facades
Yusdirman Lu · 2026-05-07 · via DEV Community

Building a FHIR-Compliant ADT Database: Encounters, Polymorphism, and Facades

If you are a software engineer building a healthcare application today, you're inevitably going to cross paths with HL7 FHIR (Fast Healthcare Interoperability Resources). FHIR is fantastic as a standardized API format for exchanging healthcare data. But when it comes time to actually store that data in a traditional relational database (SQL), things get complicated fast.

Today, we're going to look at how to design a database architecture for a core hospital workflow: ADT (Admission, Discharge, Transfer). We'll explore why standard SQL design patterns don't always apply, the headache of polymorphic relationships, and how real-world systems handle these challenges.

1. The End of Fragmented Visit Tables

In a legacy hospital system, you might expect to see a database schema that looks like this:

  • table_outpatient_visits
  • table_inpatient_admissions
  • table_er_logs

FHIR completely rejects this pattern. In FHIR, every type of patient visit is centralized into a single resource called an Encounter. To distinguish between an emergency visit and a routine checkup, we don't use different tables; we use state definitions—specifically, the class attribute (mapped to v3-ActEncounterCode) and the status attribute.

Here is how a single Encounter table handles the whole ADT spectrum:

  1. Walk-in (Service Undecided): class = AMB (Ambulatory), status = arrived. It's linked to a Patient and maybe a generic waiting room location, but no doctor is assigned yet.
  2. Outpatient: class = AMB. The encounter is linked to a specific Practitioner (doctor) and a consultation room.
  3. Inpatient: class = IMP (Inpatient), status = in-progress. This involves a complex history of Location relationships as the patient transfers from the Admission Ward -> Surgery -> Recovery Bed.
  4. Emergency: class = EMER. Often transitions into an IMP encounter if the patient is admitted (linked via Encounter.partOf).
  5. Daycare: class = SS (Short Stay). Mapped to a specific infusion chair or recovery bed for < 24 hours.

The ADT Entity-Relationship Diagram

Here is a simplified view of how these FHIR resources translate into relational tables:

erDiagram  
    PATIENT {  
        string id PK  
        string identifier  
        string name  
        date birthDate  
    }  

    ENCOUNTER {  
        string id PK  
        string patient\_id FK "Wait, is this a standard FK? See below\!"  
        string class\_code "AMB, IMP, EMER"  
        string status   
        datetime period\_start  
    }  

    LOCATION {  
        string id PK  
        string physical\_type "room, bed, ward"  
    }  

    ENCOUNTER\_LOCATION {  
        string encounter\_id FK  
        string location\_id FK  
        string status "planned, active, completed"  
    }

    PRACTITIONER {  
        string id PK  
    }

    ENCOUNTER\_PARTICIPANT {  
        string encounter\_id FK  
        string practitioner\_id FK   
        string type\_code "admitter, attender"  
    }

    PATIENT ||--o{ ENCOUNTER : "has"  
    ENCOUNTER ||--o{ ENCOUNTER\_LOCATION : "occupies"  
    LOCATION ||--o{ ENCOUNTER\_LOCATION : "houses"  
    ENCOUNTER ||--o{ ENCOUNTER\_PARTICIPANT : "involves"  
    PRACTITIONER ||--o{ ENCOUNTER\_PARTICIPANT : "acts as"

Enter fullscreen mode Exit fullscreen mode

2. The Elephant in the DB: Polymorphic Relationships

If you looked closely at the ERD above, you might have noticed a problem. I mapped patient_id as a standard Foreign Key on the ENCOUNTER table.

If you are building a strict, 100% compliant FHIR backend, that Foreign Key is illegal.

Why? Because FHIR relies heavily on a data type called a Reference. A Reference doesn't strictly point to a single table.

  • Look at the spec for Encounter.subject. It can be a reference to a Patient, OR a Group (e.g., for group therapy).
  • Look at Encounter.participant.individual. It can point to a Practitioner, a PractitionerRole, or a RelatedPerson.

How do you implement this in SQL?

Standard Foreign Keys (e.g., CONSTRAINT fk_patient FOREIGN KEY (subject_id) REFERENCES patients(id)) strictly enforce a link to one target table. To support FHIR, you must abandon strict DB-level referential integrity and embrace Polymorphic Associations.

Instead of a patient_id column, your schema needs two columns:

  1. subject_type (VARCHAR) - e.g., "Patient" or "Group"
  2. subject_id (VARCHAR) - e.g., "12345"

The Trade-off: Polymorphism gives you the flexibility FHIR demands, but you lose database-level Foreign Key constraints. Your application layer (or complex database triggers) is now solely responsible for ensuring that if subject_type="Patient" and subject_id="123", Patient 123 actually exists.

3. Real-World Case Study: The Frappe/Marley Healthcare Approach

Building a native FHIR document store from scratch is hard. Let's look at how a real-world system handles this using standard SQL.

Marley Healthcare (built on the Frappe/ERPNext framework using MariaDB) takes a very pragmatic approach. Rather than forcing MariaDB to act like a native FHIR document database, it uses a FHIR Facade pattern.

1. Operational ERP Tables First

Frappe prioritizes hospital operations (billing, inventory, UI). So, under the hood, MariaDB holds highly normalized, flat tables generated by Frappe's "DocTypes". You will actually find separate tables like tabPatient_Encounter (for OPD) and tabInpatient_Record (for IPD) because they trigger different billing and HR workflows.

2. The API Adapter

When a system requests FHIR data, Frappe's Python backend queries these disparate operational tables, merges them, and dynamically serializes the data into a compliant FHIR Encounter JSON payload. It’s an adapter pattern at the API boundary.

3. Solving Polymorphism with "Dynamic Links"

How does Frappe handle the FHIR Reference polymorphism in MariaDB? By using a built-in framework feature called Dynamic Links. Frappe uses exact two-column pairs:

  • link_doctype: Stores the target table name (e.g., "Patient").
  • link_name: Stores the target record ID.

This allows Marley Healthcare to support FHIR's polymorphic data structures perfectly within a standard MariaDB relational database without hardcoded schema limitations.

Conclusion

When building for FHIR on SQL, you have a choice to make. Do you build a strict, normalized schema that acts as a FHIR Facade (like Frappe), or do you build a native FHIR data store utilizing heavy polymorphism?

Understanding the unified Encounter paradigm and the necessity of polymorphic references is the first step to making the right architectural choice for your healthcare app.