How openmrs/openmrs-esm-patient-chart works
Main Components
a. Core Application Layer:
• Patient Chart Core (esm-patient-chart-app)
• Common Library (esm-patient-common-lib)
• Form Engine & Entry System (esm-form-engine-app, esm-form-entry-app)
b. Feature Modules Layer:
• Clinical Modules (Allergies, Conditions, Immunizations)
• Documentation Modules (Notes, Forms, Attachments)
• Monitoring Modules (Vitals, Tests, Medications)
• Administrative Modules (Programs, Lists)
c. UI Components Layer:
• Patient Banner
• Navigation Menu
• Workspace Components
• Dashboard Widgets
Relationships
a. Data Flow:
• API interactions with backend services
• Form submission flows
• Patient data access patterns
b. Dependencies:
• Common library usage by feature modules
• Form engine integration points
• Shared service utilization
Architectural Patterns to Highlight
a. Microfrontend Architecture:
• Module isolation
• Dynamic loading boundaries
• Shared state management
b. Component Communication:
• Event-based communication channels
• Shared state mechanisms
• Extension points
• Browser/Client |
• ↓
• OpenMRS 3.0 SPA Framework |
• ↓
• Core Layer | Feature Layer |
• Chart Core | - Clinical Modules |
• Common Lib | - Doc Modules |
• Form Engine | - Monitoring Modules|
• ↓
• UI Components Layer |
• Banner - Navigation - Workspace |
• ↓
• Backend Services |
Implementation Details
a. Technical elements:
• Translation support (i18n)
• Testing infrastructure
• Configuration management
• Offline capabilities
b. Integration points:
• REST API connections
• FHIR resource handling
• External system interfaces
Notes
Annotations for:
• Key configuration points
• Scalability considerations
• Security boundaries
• Performance optimization points