Namespace adas_core.Infrastructure.Repositories

Classes

AdmissionRepository: Repositorio para gestionar las operaciones de la entidad Admission en MongoDB. Proporciona métodos para insertar, actualizar, eliminar y buscar admisiones, así como para manejar opciones de listas maestras relacionadas con las admisiones. Utiliza Serilog para el registro de errores y eventos importantes durante las operaciones de la base de datos.

AlarmRepository: Repository for managing patient observation alarms in MongoDB. Provides methods to retrieve aggregated patient observations based on specified fields and expiration status. Implements the IAlarmRepository interface and extends the MongoRepository base class for common MongoDB operations.

AppointmentArchiveRepository: Repository for managing archived patient appointments in MongoDB. This repository provides methods to insert, delete, and manage archived appointments, ensuring efficient storage and retrieval of historical appointment data.

AppointmentRepository: Repository for managing patient appointments in a MongoDB database. This class provides methods to perform CRUD operations and queries related to patient appointments, such as retrieving appointments by patient ID, finding appointments by point of care, and updating or deleting appointments. It utilizes the MongoDB driver for database interactions and is configured using application settings for collection names and other parameters.

ArchivePatientCarePlanRepository: Repository for managing archived patient care plans in a MongoDB database. This class provides methods to perform CRUD operations and queries related to archived patient care plans, such as retrieving care plans by patient ID, inserting new care plans, and creating indexes. It utilizes the MongoDB driver for database interactions and is configured using application settings for collection names and other parameters.

AuthorityRepository: Repository for managing user authorities and permissions in the system. This repository provides methods to create, retrieve, and delete authorities based on user and unit identifiers. It also includes logging for debugging purposes and ensures that initial data is loaded when necessary.

CameraRepository: Repository for managing camera entities in the MongoDB database. This repository provides methods to create, retrieve, update, and search for cameras based on various criteria. It also includes error handling and logging for debugging purposes.

ConfigObservationRepository: Repositorio para manejar las operaciones CRUD de ConfigObservation en MongoDB.

ConfigPumpsRepository: Repository for managing ConfigPumps in MongoDB. Provides methods to retrieve, update, and delete pump configurations.

ConfigUnitsRepository: Repository for managing ConfigUnits in MongoDB. Provides methods to retrieve and manipulate ConfigUnits data.

DeviceRepository: Repository for managing Device entities in MongoDB. Provides methods for finding devices by various attributes and updating device statistics.

DiagnosisArchiveRepository: Repository for managing archived patient diagnoses in MongoDB. This repository provides methods for inserting, deleting, and indexing patient diagnosis records in the archive collection.

DiagnosisRepository: Repository for managing patient diagnoses in a MongoDB collection. Provides methods for CRUD operations and querying diagnoses by patient ID and code.

DischargeRepository: Repository for managing Discharge entities in MongoDB. Provides methods for CRUD operations and specific queries related to discharges.

DisplayCardConfigRepository: Repository for managing display card configurations in MongoDB. Provides methods to perform CRUD operations on CardConfig documents.

DisplayChartConfigRepository: Repository for managing ChartConfig in MongoDB. Provides methods to retrieve and manipulate ChartConfig data.

DisplayConfigRepository: Repository implementation for managing DisplayConfig entities in MongoDB. Provides CRUD operations and specialized queries for display configurations.

DisplayDetailConfigRepository: Repository implementation for managing CardDetailsConfig entities in MongoDB. Provides CRUD operations for display detail configurations used in nurse and smart displays.

DisplayRepository: Repository implementation for managing Display entities in MongoDB. Provides CRUD operations and specialized queries for display devices.

HistoricalConfigChangesRepository: Repository implementation for managing HistoricalConfigChanges entities in MongoDB. Provides CRUD operations and specialized queries for tracking configuration changes over time.

LightBeaconRepository: Repository implementation for managing LightBeacon entities in MongoDB. Provides CRUD operations and query capabilities specific to light beacons.

MasterListRepository<T>: Generic repository implementation for managing MasterList entities in MongoDB. Provides CRUD operations and specialized queries for various master list types including options lists, diagnoses, allergies, procedures, treatments, and other reference data.

MedicineRepository: Repository implementation for managing Medicine entities in MongoDB. Provides CRUD operations, search, pagination, and aggregation capabilities specific to medicines.

MongoRepository<T>: Abstract base repository providing common MongoDB persistence operations for a given document type T. Concrete repositories must implement GetCollectionName() to identify the target collection, and may override CreateIndexes(), InsertInitialLoad(), and InsertOneAsync(T) to customize schema setup, seeding, and insertion behavior.

NoticeRepository: Repository implementation for managing Notice entities in MongoDB. Provides CRUD operations for notices/notifications that can be displayed on screens.

ObservationArchiveRepository: Repository implementation for managing PatientObservation archive entities in MongoDB. Provides operations for storing and retrieving historical patient observations.

ObservationRepository: Repository implementation for managing PatientObservation entities in MongoDB. Provides specialized query, aggregation, retention, and expiration operations for patient clinical observations.

PatientArchiveRepository: Repository implementation for managing Patient archive entities in MongoDB. Provides CRUD operations for historical/archived patient data.

PatientCarePlanRepository: Represents a MongoDB-backed repository for managing PatientCarePlan entities, providing concrete persistence operations defined by the IPatientCarePlanRepository contract.

PatientRepository: Provides a MongoDB-backed repository implementation for managing patient data, exposing patient-specific data access operations defined by the IPatientRepository contract.

PoCMappingRepository: Provides a MongoDB-backed repository implementation for PoCMapping entities.

PoCSettingsRepository: Represents a MongoDB-backed repository for PoCSettings entities, implementing the IPoCSettingsRepository contract to provide data access operations.

PointOfCareRepository: Represents a MongoDB-backed repository for PointOfCare entities, providing the persistence operations defined by the IPointOfCareRepository interface.

PumpAlarmEventRepository: Represents a MongoDB-backed repository for PumpAlarmEvent documents, exposing pump alarm event-specific data access through the IPumpAlarmEventRepository contract.

PumpAlarmStateRepository: Represents a MongoDB-based repository for PumpAlarmState entities, providing concrete data access functionality defined by the IPumpAlarmStateRepository contract.

PumpArchiveRepository: Repositorio de archivo para observaciones de bombas. Colección: archive_pumpobservations (configurable por ApiSettings.ArchivePumpObservations).

PumpObservationRepository: A repository for managing PumpObservation entities in a MongoDB data store. This class extends the generic MongoRepository<T> base class and implements the IPumpObservationRepository contract to provide persistence operations for pump observation data.

PumpStateRepository: Provides a repository implementation for PumpState entities backed by a MongoDB data store.

RecordingAlertArchiveRepository: Represents a MongoDB repository responsible for managing archived patient recording alerts, exposing archive-specific data access operations through the recording alert archive repository contract.

RecordingAlertRepository: Provides a MongoDB-backed repository implementation for PatientRecordingAlert entities, exposing data access operations defined by the IRecordingAlertRepository contract.

RelayRepository: Represents a repository for managing Relay entities, providing MongoDB-backed data access through the MongoRepository<T> base class and exposing the contract defined by IRelayRepository.

SectionRepository: Represents a MongoDB repository for Section entities, implementing the contract defined by ISectionRepository.

ServiceConfigRepository: Represents a MongoDB repository for ServiceConfig entities, implementing the IServiceConfigRepository contract to provide data access operations.

TreatmentArchiveRepository: Provides a MongoDB-backed repository for persisting and retrieving archived patient treatment records. Inherits from MongoRepository<T> and implements the ITreatmentArchiveRepository contract.

TreatmentRepository: Represents a MongoDB-backed repository for PatientTreatment entities, inheriting common data access functionality from MongoRepository<T> and implementing the ITreatmentRepository contract.

UnitRepository: Represents a MongoDB-backed repository for Unit entities, inheriting persistence functionality from MongoRepository<T> and implementing the IUnitRepository contract.

UserRepository: Represents a MongoDB-backed repository for managing User entities.

Table of Contents

Namespace adas_core.Infrastructure.Repositories

Classes