How animalost/zamenishealth works
Zamenis2024 is a healthcare operations suite: a Windows desktop application for reception and clinical workflows, alongside controller/API projects and persistence/domain libraries. The user-facing path starts in the desktop shell, enters a role-specific workflow such as reception, then uses controllers and services to retrieve or update operational data. Scheduling, patient records, billing, reporting, and interoperability are distinct product areas. The README provides no capability detail; the graph uses the supplied source index and excerpts, so links to unsampled subsystems are conservative.
Main entry points: Metodos Persistence methods · Recepcion.cs Reception menu · Services Email and images · Program.cs Desktop shell
Components 24
Desktop application
- Desktop shell
ZamenisH/ZamenisHealth/Program.cs - Role workspace
ZamenisH/ZamenisHealth/Comunes/Contenedor.cs
Care operations
- Reception menu
ZamenisH/ZamenisHealth/Comunes/ConfigContenedor/Recepcion.cs - Appointment workflow
ZamenisH/ZamenisHealth/Recepcion/AgendaDiaria - Patient workflow
ZamenisH/ZamenisHealth/Recepcion - Create client
ZamenisH/ZamenisHealth/Recepcion/Extras/CrearCliente.cs
Controllers and services
- Admissions controller
ZamenisH/Controlador/Controlador/Controllers/AdmisionesController.cs - Agenda service
ZamenisH/Controlador/Controlador/Services/AgendaService.cs - HTTP API client
ZamenisH/Controlador/Controlador/APIController.cs - Patient services
ZamenisH/Controlador/Controlador/Services - Management reports
ZamenisH/Controlador/Controlador/Controllers/Gerencial/GerencialController.cs - Electronic invoices
ZamenisH/APIFacturaElectronica/DocumentosElectronicos - Email and images
ZamenisH/APIController/APIController/Services
Domain and persistence
- Healthcare models
ZamenisH/Domain - Persistence methods
ZamenisH/Persistence/CXN/Metodos - Persistence contracts
ZamenisH/Persistence/CXN/Interfaces - Connection config
ZamenisH/Persistence/Conexion.cs - SQL data store
External integrations
- FHIR exchange
ZamenisH/APIIHCE/APIFhir - ICD-11 lookup
ZamenisH/ICD11/ServiceICD11/ICD11ApiService.cs - RIPS reporting
ZamenisH/MinSalud/APIRips/Methods.cs - Email provider
- Image storage
Other components
- Staff user
Connections 21
- Staff user → Desktop shell: uses
- Desktop shell → Role workspace: launches
- Role workspace → Reception menu: opens
ZamenisH/ZamenisHealth/Comunes/Contenedor.cs - Reception menu → Appointment workflow: opens
ZamenisH/ZamenisHealth/Comunes/ConfigContenedor/Recepcion.cs - Reception menu → Patient workflow: opens
ZamenisH/ZamenisHealth/Comunes/ConfigContenedor/Recepcion.cs - Reception menu → Create client: opens
ZamenisH/ZamenisHealth/Recepcion/Extras/CrearCliente.cs - Create client → Persistence methods: creates patient
ZamenisH/ZamenisHealth/Recepcion/Extras/CrearCliente.cs - Persistence methods → Persistence contracts: implements
ZamenisH/Persistence/CXN/Metodos/MReportes.cs - Persistence methods → Healthcare models: uses models
- Persistence methods → SQL data store: reads and writes
- Admissions controller → Agenda service: calls
ZamenisH/Controlador/Controlador/Controllers/AdmisionesController.cs - Agenda service → HTTP API client: sends requests
ZamenisH/Controlador/Controlador/Services/AgendaService.cs - HTTP API client → Healthcare models: serializes data
- Management reports → Patient services: calls
ZamenisH/Controlador/Controlador/Controllers/Gerencial/GerencialController.cs - Connection config → Persistence methods: configures
ZamenisH/Persistence/Conexion.cs - Electronic invoices → Persistence methods: uses data access
ZamenisH/APIFacturaElectronica/DocumentosElectronicos/Servicio/ExportarPDF.cs - FHIR exchange → SQL data store: exchanges records
- ICD-11 lookup → SQL data store: uses connection
ZamenisH/ICD11/ServiceICD11/ICD11ApiService.cs - RIPS reporting → SQL data store: submits reports
- Email and images → Email provider: sends email
- Email and images → Image storage: handles images