FHIR Challenges and Advanced Usage for Technical Architects
FHIR for Technical Architects - Darren Devitt Darren Devitt FHIR
Summary
This article provides technical architects using FHIR with key design considerations and 'hidden features' not found in standard documentation. It focuses on solving practical issues, such as determining proper usage for data sharing, building proxy layers, and utilizing the Task resource for workflows.
Details
This is an explanatory guide aimed at technical architects implementing FHIR (Fast Healthcare Interoperability Resources), providing advanced knowledge beyond what is covered in standard documentation. The article first addresses the fundamental decision of whether a project should use FHIR at all, based on whether data sharing outside the organization is required. It then highlights that FHIR servers are not production-ready and necessitate building a proxy layer (Intercept Layer) to intercept requests and responses. Furthermore, it covers practical pitfalls such as early adoption of workflow design using the 'Task resource'—which becomes critical later in development—and the difficulty of running heavy analytical queries against a FHIR API. Regarding security, it emphasizes the importance of Provenance for identifying data ownership and AuditEvent for tracking who did what and when. Other topics include guidance on proper implementation of patient consent management (following HL7 groups' work), and how to correctly create custom Extensions. It serves as a comprehensive checklist designed to help streamline FHIR projects by addressing common real-world challenges.
Technology Note
FHIR（Fast Healthcare Interoperability Resources）は医療データ交換の国際標準。このエントリの関連技術: FHIR
Original content copyright by respective publishers