FHIR Implementation Architecture: Comparing Native vs. Façade and Managing Risk
FHIR 風險評估及最佳實務(2):Native 跟Façade 架構的十字路口 - CIO Taiwan
Summary
This article analyzes the critical architectural choice (Native vs. Façade) for FHIR implementation in hospitals. The decision profoundly impacts data synchronization, system integration, and long-term maintenance, emphasizing that defining the Source of Truth and responsibility boundaries is crucial to prevent accumulating technical debt.
Details
The most critical decision in FHIR implementation is selecting the underlying architecture. Native FHIR stores data directly as FHIR Resources, promoting standardization, but faces high costs and risks associated with migrating data from legacy HIS. Conversely, Façade FHIR wraps the existing HIS, providing an external FHIR interface, which lowers initial costs but introduces complexity in data write-back. Regarding data synchronization, it is crucial to define the required level of 'real-time' rather than simply aiming for it. For a Native FHIR approach, event-driven synchronization using CDC (Change Data Capture) and messaging platforms (like Kafka) is recommended. To avoid technical debt, the principle of clearly defining a Single Source of Truth (SoT) must be maintained. Utilizing the Façade layer as a read-only 'bridge' is presented as a practical method that supports long-term system maintenance and eventual transition to Native FHIR.
Original content copyright by respective publishers