How cardio-ai/fl-multi-modal-dataset-creation works
Main Components
a) Data Input Layer:
• DICOM Files (Images, Waveforms)
• Annotations (Segmentations)
• Structured Reports (ECG Reports, Basic Diagnostic Reports)
b) Processing Components:
• highdicom Extension Module
• SR Template Processors (TID 2000, TID 3700, TID 3802)
• DICOM SR to FHIR Converter
c) Kaapana Integration Layer:
• Airflow DAGs Components
• Metadata Collection Workflows
• Installation/Uninstallation Workflows
• Docker Container Environment
d) Storage and Indexing:
• Metadata Index
• Dashboard Data Storage
• Backup Systems
Component Relationships
• Data input → Processing Components
• Processing Components → Kaapana Integration Layer
• Kaapana Integration Layer → Storage and Indexing
• Storage and Indexing → Dashboard/UI Layer
Specific Implementation Details
• Blue: Core DICOM processing components
• Green: Kaapana extension components
• Yellow: Storage/database components
• Purple: User interface/dashboard components
Architectural Patterns to Highlight
• Workflow-based Architecture (evidenced by DAG files)
• Modular Design (separate operators for different functions)
• Plugin Architecture (extension-based design)
Key Technical Elements
• Annotation Collectors
• Metadata Operators
• Dcm2JsonOperator
• Json2MetaOperator
• MetaBackupOperator
• MetaInstallOperator
• Dashboard Integration
Data Flow Patterns
Following flows:
Integration Points
Highlight:
• Kaapana Platform Integration
• FHIR Conversion Capabilities
• Dashboard Data Export/Import
Special Considerations:
A separate section showing the template structure
• TID 2000 (Basic Diagnostic Imaging Report)
• TID 3700 (ECG Report)
• TID 3802 (Cardiovascular Patient History)