fhir-migration
CommunityMigrate to HAPI FHIR with FHIR mappers.
Authorbtall
Version1.0.0
Installs0
System Documentation
What problem does it solve?
This Skill guides the migration of demographic data storage to a hybrid architecture where HAPI FHIR becomes the source of truth for Patient and Practitioner data, while PostgreSQL stores GDPR metadata and Keycloak handles authentication and RBAC.
Core Features & Use Cases
- FHIR integration & mappings: Implement Pydantic ↔ FHIR mappers for Patient and Practitioner to enable bidirectional sync with HAPI FHIR.
- GDPR metadata layer: Introduce GDPR metadata tables in PostgreSQL to track verification, anonymization, soft deletes, and correlation hashes.
- Orchestration pattern: A service-layer workflow that creates/updates FHIR resources, persists GDPR metadata, and publishes events.
- Use case: Modernize a platform by consolidating identity data in HAPI FHIR while preserving GDPR controls in PostgreSQL and keeping authentication in Keycloak.
Quick Start
- Install required dependencies (e.g., fhir.resources, httpx) and set up environment for HAPI FHIR.
- Implement the FHIR mappers as described (PatientMapper, ProfessionalMapper) and wire them to the service layer.
- Create GDPR metadata models and a migration script, then run the migration to move existing data and enable sync with FHIR.
Dependency Matrix
Required Modules
None requiredComponents
Standard package💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: fhir-migration Download link: https://github.com/btall/core-africare-identity/archive/main.zip#fhir-migration Please download this .zip file, extract it, and install it in the .claude/skills/ directory.