Notes on health interoperability
Ideas, product and real cases on how to connect what was fragmented without moving data from its source.
Federate, don't centralize: why clinical data should stay where it originates
Centralizing medical records in a single repository looks simple until the first audit. FHIR federation offers another path: query the data where it lives.
The facade from the inside: what you have to build and when it is worth it
A facade looks like a thin layer until you build one. We walk through what the platforms solve, what stays with your team, and the cases where it is still the right decision.
Read article →
Facade or repository: how to choose your path to FHIR
For most institutions the question is no longer whether to adopt FHIR, but how. We compare the two available paths, what each one costs and what recently changed between them.
Read article →Mapping HL7 v2 to FHIR without rewriting your system
Most hospitals in LATAM still emit HL7 v2 messages. This is how Harmony translates them into FHIR resources with versioned, auditable rules.
Read article →Health data sovereignty: the LATAM regulatory map in 2026
Chile, Colombia, Mexico and Brazil are advancing interoperability laws with different approaches. A summary of what each framework requires.
Read article →How a network of 14 clinics cut patient history lookups down to seconds
Gathering the history of a referred patient used to take days of emails and faxes. With Acordia, the federated query answers while the patient is still in the room.
Read article →FHIR explained for CIOs: what you need to know before issuing an RFP
No unnecessary acronyms: what FHIR is, what to ask a vendor, and the warning signs that a solution is not truly interoperable.
Read article →Traceability by design: auditing every query at the source
Every federated query leaves a trail in the institution that holds the data. This is how we designed the audit log to be useful, not just mandatory.
Read article →