Catalogs

The catalogs contain base information that other modules consume: system modules, submodules, tags, study types, staff types, medical groups, medications, templates, presentations, active components, cash box concepts and system actions.

This page is the entry to the catalog system. Each catalog is described below with its purpose, route and dedicated page.

System catalogs

Catalog	Route	Purpose	Dedicated page
Modules	/manage-modules/modules	Functionally group the submodules of the system.	System modules
Submodules	/manage-subModules/subModules	Define submodules assigned to modules and used for permissions.	System submodules
Actions	/manage-hcpsTypes/hcpTypes/actions	Define system actions (SHOW_LOGS, AGENDA_PARAMETERS, etc.) and their availability.	System actions
Tags	/manage-tags/tag	Classify records (appointments, patients, etc.) by module.	Tags
Study types	/manage-study-types/studyTypes	Maintain the available study types.	Study types
Staff types and actions	/manage-hcpsTypes/hcpTypes	Define HCP types and their allowed actions.	Staff types
Medical groups	/manage-medical-groups/medGroups	Maintain medical groups that group services and availability.	Medical groups
Medications and families	/manage-meds/meds	Maintain medications, active components and families.	Medications and families
Templates	/manage-templates/templates	Reuse formats for prescriptions and other flows.	Templates
Presentations	/manage-presentations/presentations	Configure presentation containers (box, bottle, ampule).	Presentations
Active components	/manage-active-components/active-components	Maintain active components used in medications.	Active components
Resources (cash box concepts)	/manage-resources/cashBoxConcept	Maintain entry and exit cash box concepts.	Resources and cash box concepts

Roles and permissions

Each catalog has its own permission. Most require WRITE level to create or edit and ADMIN level to delete. See each dedicated page.

Good practices

• Define base catalogs first (medical groups, staff types, branches) before creating services or HCPs.
• Document catalogs internally so the operations team knows where to find each value.
• Avoid duplicates. If a value already exists, reuse it.
• Deactivate before deleting when the catalog keeps historical references.
• Periodically review unused catalogs and deactivate them.

Relation with other modules

• Catalogs are the source of truth for selectors and validations throughout the system.
• Catalog changes impact immediately in the flows that consume them (Schedule, Cash box, Patients, etc.).
• The modules and submodules of the system feed the dynamic sidebar and the permissions.