decoded/interoperability/
Decoded #8: Why Doesn't Your Health App Already Know Your Meds?
The hard part was never teaching it medicine. It's getting it a seat at the table where your data already lives.
You get a new prescription. Your pharmacy app should already know. So should any AI tool built to help you.
Neither one does automatically, and here's why.
Every electronic health record stores medications, allergies, and conditions in its own format. Epic stores it one way, a different EHR stores it another. The old standard let each health organization customize it so heavily that two systems on the "same" standard still couldn't talk. Every connection got built by hand.
FHIR is the industry's attempt to fix that, and its acronym stands for Fast Healthcare Interoperability Resources. Think of it as a universal wall outlet. Before it, every system needed its own custom adapter. Now a compatible tool can ask for "this patient's active medications" the same way, no matter which EHR answers.
That fixes the format problem, but it does not fix the permission problem. Getting approved to even ask the question still takes vendor review, security checks, and real paperwork, system by system.
Useful frame: the hard part was never teaching it medicine. It's getting it a seat at the table where your data already lives.