Clinical Reference Data Endpoints — Lookup Tables

The Gestión Clínica API exposes a collection of small, stable lookup tables that power dropdown controls, validation rules, and reporting classifiers throughout every clinical module. These catalogs — covering demographic attributes (gender, civil status, blood type, identity documents), administrative classifications (patient types, hospitalisation types, discharge types, affiliation, filiation), geographic codes (ubigeo), and workflow statuses — are typically populated once during system setup and updated only when regulatory requirements change. Frontend applications should load these catalogs at startup or cache them per session to avoid redundant network calls. All endpoints use HTTP POST and require a valid Authorization bearer token.

Most reference-data controllers expose only a GetAllActives action — a no-body POST that returns every active record in the table. The exceptions are ADM_OCUPACION and ADM_UBIGEO, which additionally support filtering, and TIPO_ESTADO, which exposes only a GetAllFilters action (no GetAllActives); those actions are documented within their respective accordions below.

Because these catalogs are rarely updated, consider caching them in your application’s session store or a client-side state manager (Redux, Pinia, Zustand, etc.) right after login. This eliminates dozens of redundant API round-trips during a user’s session.

Standard Response Envelope

Every endpoint documented on this page returns responses wrapped in the same JsonResponse structure:

Field	Type	Description
`Success`	boolean	`true` when the request completed without a server exception.
`Data`	array / null	Array of DTO objects on success; `null` on error.
`Message`	string / null	Human-readable message, populated on warning or error conditions.
`Warning`	boolean	`true` when a business-rule condition is met but no hard exception occurred.

Reference Catalog Endpoints

ADM_GENERO — Gender Catalog

The gender catalog provides the list of gender options available when registering patients and professionals. Extends EntityAuditableDTO.DTO fields — ADM_GENERODTO

Field	Type	Description
`id_genero`	integer	Unique primary key.
`c_codigo`	string	Short code (e.g., `"M"`, `"F"`).
`t_descripcion`	string	Full description (e.g., `"Masculino"`, `"Femenino"`).
`FechaCreacion`	datetime?	Audit: creation timestamp.
`FechaModificacion`	datetime?	Audit: last modification timestamp.
`UsuarioCreacion`	string	Audit: creating username.
`UsuarioModificacion`	string	Audit: last modifying username.

POST /api/ADM_GENERO/GetAllActives — returns all active gender options. No request body required.

curl -s -X POST \
  https://{base_url}/api/ADM_GENERO/GetAllActives \
  -H "Authorization: Bearer {token}" \
  -H "Content-Type: application/json"

Example response

{
  "Success": true,
  "Data": [
    { "id_genero": 1, "c_codigo": "M", "t_descripcion": "Masculino" },
    { "id_genero": 2, "c_codigo": "F", "t_descripcion": "Femenino" }
  ],
  "Message": null,
  "Warning": false
}

ADM_ESTADO_CIVIL — Civil Status Catalog

Provides the list of marital/civil status options required for patient registration and used in SUSALUD statistical reports. Extends EntityAuditableDTO.DTO fields — ADM_ESTADO_CIVILDTO

Field	Type	Description
`id_estado_civil`	integer	Unique primary key.
`c_codigo`	string	Short code (e.g., `"S"` = Soltero, `"C"` = Casado).
`t_descripcion`	string	Full description (e.g., `"Soltero(a)"`, `"Casado(a)"`, `"Divorciado(a)"`).
`FechaCreacion`	datetime?	Audit: creation timestamp.
`FechaModificacion`	datetime?	Audit: last modification timestamp.
`UsuarioCreacion`	string	Audit: creating username.
`UsuarioModificacion`	string	Audit: last modifying username.

POST /api/ADM_ESTADO_CIVIL/GetAllActives — returns all active civil status options. No request body required.

curl -s -X POST \
  https://{base_url}/api/ADM_ESTADO_CIVIL/GetAllActives \
  -H "Authorization: Bearer {token}" \
  -H "Content-Type: application/json"

Example response

{
  "Success": true,
  "Data": [
    { "id_estado_civil": 1, "c_codigo": "S", "t_descripcion": "Soltero(a)" },
    { "id_estado_civil": 2, "c_codigo": "C", "t_descripcion": "Casado(a)" },
    { "id_estado_civil": 3, "c_codigo": "D", "t_descripcion": "Divorciado(a)" },
    { "id_estado_civil": 4, "c_codigo": "V", "t_descripcion": "Viudo(a)" }
  ],
  "Message": null,
  "Warning": false
}

ADM_DOCUMENTO_IDENTIDAD — Identity Document Types

Enumerates the types of identity documents accepted when registering patients and professionals in Peru (DNI, passport, carnet de extranjería, etc.). Extends EntityAuditableDTO.DTO fields — ADM_DOCUMENTO_IDENTIDADDTO

Field	Type	Description
`id_documento_identidad`	integer	Unique primary key.
`c_codigo`	string	Short code (e.g., `"DNI"`, `"PAS"`, `"CE"`).
`t_descripcion`	string	Full document name (e.g., `"Documento Nacional de Identidad"`, `"Pasaporte"`, `"Carnet de Extranjería"`).
`FechaCreacion`	datetime?	Audit: creation timestamp.
`FechaModificacion`	datetime?	Audit: last modification timestamp.
`UsuarioCreacion`	string	Audit: creating username.
`UsuarioModificacion`	string	Audit: last modifying username.

POST /api/ADM_DOCUMENTO_IDENTIDAD/GetAllActives — returns all active identity document types. No request body required.

curl -s -X POST \
  https://{base_url}/api/ADM_DOCUMENTO_IDENTIDAD/GetAllActives \
  -H "Authorization: Bearer {token}" \
  -H "Content-Type: application/json"

Example response

{
  "Success": true,
  "Data": [
    { "id_documento_identidad": 1, "c_codigo": "DNI", "t_descripcion": "Documento Nacional de Identidad" },
    { "id_documento_identidad": 2, "c_codigo": "PAS", "t_descripcion": "Pasaporte" },
    { "id_documento_identidad": 3, "c_codigo": "CE",  "t_descripcion": "Carnet de Extranjería" }
  ],
  "Message": null,
  "Warning": false
}

ADM_GRUPO_SANGUINEO — Blood Type Groups

Lists all blood type groups (ABO + Rh factor combinations) available for patient clinical records. Extends EntityAuditableDTO.DTO fields — ADM_GRUPO_SANGUINEODTO

Field	Type	Description
`id_grupo_sanguineo`	integer	Unique primary key.
`c_codigo`	string	Short code (e.g., `"O+"`, `"A-"`, `"AB+"`).
`t_descripcion`	string	Full label (e.g., `"O Positivo"`, `"A Negativo"`, `"AB Positivo"`).
`FechaCreacion`	datetime?	Audit: creation timestamp.
`FechaModificacion`	datetime?	Audit: last modification timestamp.
`UsuarioCreacion`	string	Audit: creating username.
`UsuarioModificacion`	string	Audit: last modifying username.

POST /api/ADM_GRUPO_SANGUINEO/GetAllActives — returns all active blood type groups. No request body required.

curl -s -X POST \
  https://{base_url}/api/ADM_GRUPO_SANGUINEO/GetAllActives \
  -H "Authorization: Bearer {token}" \
  -H "Content-Type: application/json"

Example response

{
  "Success": true,
  "Data": [
    { "id_grupo_sanguineo": 1, "c_codigo": "O+",  "t_descripcion": "O Positivo" },
    { "id_grupo_sanguineo": 2, "c_codigo": "O-",  "t_descripcion": "O Negativo" },
    { "id_grupo_sanguineo": 3, "c_codigo": "A+",  "t_descripcion": "A Positivo" },
    { "id_grupo_sanguineo": 4, "c_codigo": "A-",  "t_descripcion": "A Negativo" },
    { "id_grupo_sanguineo": 5, "c_codigo": "B+",  "t_descripcion": "B Positivo" },
    { "id_grupo_sanguineo": 6, "c_codigo": "B-",  "t_descripcion": "B Negativo" },
    { "id_grupo_sanguineo": 7, "c_codigo": "AB+", "t_descripcion": "AB Positivo" },
    { "id_grupo_sanguineo": 8, "c_codigo": "AB-", "t_descripcion": "AB Negativo" }
  ],
  "Message": null,
  "Warning": false
}

ADM_OCUPACION — Occupation Catalog

The occupation catalog is the most fully-featured reference table: it supports create, update, delete, and both filtered and by-ID lookups in addition to the standard GetAllActives. Occupations are recorded on patient registration for statistical and epidemiological reporting. Extends EntityAuditableDTO.DTO fields — ADM_OCUPACIONDTO

Field	Type	Description
`id_ocupacion`	integer	Unique primary key.
`c_codigo`	string	Short occupation code.
`t_descripcion`	string	Full occupation name (e.g., `"Agricultor"`, `"Docente"`, `"Ingeniero"`).
`t_observacion`	string	Optional free-text observations or notes.
`f_estado`	integer?	Numeric status flag (active/inactive).
`estado`	string	Human-readable status label (e.g., `"Activo"`, `"Inactivo"`).
`FechaCreacion`	datetime?	Audit: creation timestamp.
`FechaModificacion`	datetime?	Audit: last modification timestamp.
`UsuarioCreacion`	string	Audit: creating username (required on `Add`).
`UsuarioModificacion`	string	Audit: modifying username (required on `Update`/`Delete`).

Available actions

Endpoint	Body required	Description
`POST /api/ADM_OCUPACION/GetAllActives`	None	Returns all active occupation records.
`POST /api/ADM_OCUPACION/GetAllFilters`	`ADM_OCUPACIONDTO` (filter fields)	Returns filtered records by code, description, or status.
`POST /api/ADM_OCUPACION/GetById`	`{ "id_ocupacion": N }`	Returns a single occupation by its ID.
`POST /api/ADM_OCUPACION/Add`	Full `ADM_OCUPACIONDTO`	Creates a new occupation if one with the same code doesn’t already exist.
`POST /api/ADM_OCUPACION/Update`	Full `ADM_OCUPACIONDTO`	Updates an existing occupation record.
`POST /api/ADM_OCUPACION/Delete`	`{ "id_ocupacion": N, "UsuarioModificacion": "..." }`	Logically deactivates an occupation record.

# Get all active occupations
curl -s -X POST \
  https://{base_url}/api/ADM_OCUPACION/GetAllActives \
  -H "Authorization: Bearer {token}" \
  -H "Content-Type: application/json"

# Search by description
curl -s -X POST \
  https://{base_url}/api/ADM_OCUPACION/GetAllFilters \
  -H "Authorization: Bearer {token}" \
  -H "Content-Type: application/json" \
  -d '{"t_descripcion": "docente"}'

# Add new occupation
curl -s -X POST \
  https://{base_url}/api/ADM_OCUPACION/Add \
  -H "Authorization: Bearer {token}" \
  -H "Content-Type: application/json" \
  -d '{
    "c_codigo": "DOC",
    "t_descripcion": "Docente",
    "t_observacion": "",
    "UsuarioCreacion": "admUser",
    "id_usuarioCreacion": 1,
    "IdUsuarioActual": 1
  }'

ADM_UBIGEO — Peruvian Geographic Codes (Ubigeo)

Ubigeo is Peru’s national geographic coding system, maintained by INEI (Instituto Nacional de Estadística e Informática). Each code uniquely identifies a country → department → province → district combination and is required on patient registration for domicile and epidemiological reporting. Extends EntityAuditableDTO.DTO fields — ADM_UBIGEODTO

Field	Type	Description
`id_ubigeo`	integer	Unique primary key.
`c_codigo`	string	Official INEI ubigeo code (e.g., `"150101"` = Lima, Lima, Lima).
`t_pais`	string	Country name (typically `"Perú"`).
`t_departamento`	string	Department name (e.g., `"Lima"`, `"Arequipa"`, `"Cusco"`).
`t_provincia`	string	Province name (e.g., `"Lima"`, `"Arequipa"`, `"Cusco"`).
`t_distrito`	string	District name (e.g., `"Lima"`, `"Miraflores"`, `"San Isidro"`).
`ValorBusqueda`	string	Free-text search token — used only on `GetAllFilters` requests.
`FechaCreacion`	datetime?	Audit: creation timestamp.
`FechaModificacion`	datetime?	Audit: last modification timestamp.
`UsuarioCreacion`	string	Audit: creating username.
`UsuarioModificacion`	string	Audit: last modifying username.

Available actions

Endpoint	Body required	Description
`POST /api/ADM_UBIGEO/GetAllActives`	None	Returns all ubigeo records.
`POST /api/ADM_UBIGEO/GetAllFilters`	`ADM_UBIGEODTO` with `ValorBusqueda`	Filters by free-text across department, province, or district.

# Fetch ubigeos matching "miraflores"
curl -s -X POST \
  https://{base_url}/api/ADM_UBIGEO/GetAllFilters \
  -H "Authorization: Bearer {token}" \
  -H "Content-Type: application/json" \
  -d '{"ValorBusqueda": "miraflores"}'

Example response

{
  "Success": true,
  "Data": [
    {
      "id_ubigeo": 1042,
      "c_codigo": "150122",
      "t_pais": "Perú",
      "t_departamento": "Lima",
      "t_provincia": "Lima",
      "t_distrito": "Miraflores",
      "ValorBusqueda": null
    }
  ],
  "Message": null,
  "Warning": false
}

The full ubigeo table contains over 1,800 records (all districts in Peru). Always use GetAllFilters with a ValorBusqueda term on user-facing district pickers rather than loading GetAllActives into a dropdown.

ADM_TIPO_ATENCION — Attendance / Service Types

Classifies the type of clinical service or care modality rendered during an encounter (e.g., emergency, scheduled outpatient, telemedicine). Used when opening a patient attendance record (ADM_ATENCION).DTO fields — ADM_TIPO_ATENCIONDTO

Field	Type	Description
`id_tipo_atencion`	integer	Unique primary key.
`c_codigo`	string	Short code (e.g., `"CE"` = Consulta Externa, `"EM"` = Emergencia).
`t_descripcion`	string	Full label (e.g., `"Consulta Externa"`, `"Emergencia"`, `"Hospitalización"`).

POST /api/ADM_TIPO_ATENCION/GetAllActives — returns all active attendance types. No request body required.

curl -s -X POST \
  https://{base_url}/api/ADM_TIPO_ATENCION/GetAllActives \
  -H "Authorization: Bearer {token}" \
  -H "Content-Type: application/json"

ADM_TIPO_EGRESO — Discharge Types

Lists the possible discharge (egreso) types that can be assigned when closing a hospitalisation episode — for example, voluntary discharge, transfer, death, or recovery. Required by SUSALUD reporting.DTO fields — ADM_TIPO_EGRESODTO

Field	Type	Description
`id_tipo_egreso`	integer	Unique primary key.
`c_codigo`	string	Short code (e.g., `"AL"` = Alta Médica, `"FU"` = Fuga, `"FA"` = Fallecido).
`t_descripcion`	string	Full description (e.g., `"Alta Médica"`, `"Fallecido"`, `"Traslado"`).

POST /api/ADM_TIPO_EGRESO/GetAllActives — returns all active discharge types. No request body required.

curl -s -X POST \
  https://{base_url}/api/ADM_TIPO_EGRESO/GetAllActives \
  -H "Authorization: Bearer {token}" \
  -H "Content-Type: application/json"

ADM_TIPO_HOSPITALIZACION — Hospitalisation Types

Defines the category of hospitalisation (e.g., elective surgery, emergency admission, day surgery, ICU). This value is assigned when admitting a patient to a ward and influences workflow and billing rules.DTO fields — ADM_TIPO_HOSPITALIZACIONDTO

Field	Type	Description
`id_tipo_hospitalizacion`	integer	Unique primary key.
`c_codigo`	string	Short code (e.g., `"EL"` = Electiva, `"EM"` = Emergencia).
`t_descripcion`	string	Full label (e.g., `"Hospitalización Electiva"`, `"Hospitalización por Emergencia"`).

POST /api/ADM_TIPO_HOSPITALIZACION/GetAllActives — returns all active hospitalisation types. No request body required.

curl -s -X POST \
  https://{base_url}/api/ADM_TIPO_HOSPITALIZACION/GetAllActives \
  -H "Authorization: Bearer {token}" \
  -H "Content-Type: application/json"

ADM_TIPO_PACIENTE — Patient Types

Patient types determine the financial and coverage classification of a patient at the point of registration — for example, SIS (Seguro Integral de Salud), EsSalud, private payer, or particular (out-of-pocket). The type directly influences copayment rules and billing rates.DTO fields — ADM_TIPO_PACIENTEDTO

Field	Type	Description
`id_tipo_paciente`	integer	Unique primary key.
`c_codigo`	string	Short code (e.g., `"SIS"`, `"ESS"`, `"PAR"`).
`t_descripcion`	string	Full label (e.g., `"Seguro Integral de Salud"`, `"EsSalud"`, `"Particular"`).
`id_moneda`	integer	FK to currency table — the currency used for copayment amounts.
`n_copago_variable`	decimal	Variable copayment amount for clinical services.
`n_copago_variable_far`	decimal	Variable copayment amount for pharmacy dispensing.
`f_siteds`	integer	Flag indicating SITEDS (MINSA information system) integration.

POST /api/ADM_TIPO_PACIENTE/GetAllActives — returns all active patient types. No request body required.

curl -s -X POST \
  https://{base_url}/api/ADM_TIPO_PACIENTE/GetAllActives \
  -H "Authorization: Bearer {token}" \
  -H "Content-Type: application/json"

ADM_TIPO_FILIACION — Filiation Types

Filiation types classify the relationship or origin through which a patient is affiliated to a payer or insurance plan (e.g., titular, beneficiary, dependant). This catalog includes a SUSALUD-specific code field for regulatory reporting.DTO fields — ADM_TIPO_FILIACIONDTO

Field	Type	Description
`id_tipo_filiacion`	integer	Unique primary key.
`c_codigo`	string	Internal short code for the filiation type.
`c_codigo_susalud`	string	SUSALUD-specific code required for regulatory submissions.
`t_descripcion`	string	Full description (e.g., `"Titular"`, `"Beneficiario"`, `"Dependiente"`).

POST /api/ADM_TIPO_FILIACION/GetAllActives — returns all active filiation types. No request body required.

curl -s -X POST \
  https://{base_url}/api/ADM_TIPO_FILIACION/GetAllActives \
  -H "Authorization: Bearer {token}" \
  -H "Content-Type: application/json"

ADM_TIPO_AFILIACION — Affiliation Types

Affiliation types identify the insurance or social-security scheme a patient is enrolled in (e.g., contributory EsSalud, SIS subsidised, private insurer). Used alongside the patient type to determine applicable tariff schedules.DTO fields — ADM_TIPO_AFILIACIONDTO

Field	Type	Description
`id_tipo_afiliacion`	integer	Unique primary key.
`t_descripcion`	string	Full description of the affiliation scheme (e.g., `"EsSalud Contributivo"`, `"SIS Gratuito"`, `"Seguro Privado"`).

POST /api/ADM_TIPO_AFILIACION/GetAllActives — returns all active affiliation types. No request body required.

curl -s -X POST \
  https://{base_url}/api/ADM_TIPO_AFILIACION/GetAllActives \
  -H "Authorization: Bearer {token}" \
  -H "Content-Type: application/json"

TIPO_ESTADO — Status Types

The TIPO_ESTADO controller is unique among reference tables because it is cross-table: the same endpoint serves status values for multiple entities by accepting a tabla (table name) filter. This allows a single call to retrieve the valid status values for any given entity type (e.g., patient, attendance, hospitalisation). Extends EntityAuditableDTO.DTO fields — TIPO_ESTADODTO

Field	Type	Description
`tabla`	string	Required filter. The name of the entity/table whose statuses you want (e.g., `"ADM_ATENCION"`, `"ADM_PACIENTE"`).
`id_estado`	integer	Unique primary key for the status record.
`estado`	string	Human-readable status label (e.g., `"Activo"`, `"Inactivo"`, `"En espera"`, `"Atendido"`).
`FechaCreacion`	datetime?	Audit: creation timestamp.
`FechaModificacion`	datetime?	Audit: last modification timestamp.
`UsuarioCreacion`	string	Audit: creating username.
`UsuarioModificacion`	string	Audit: last modifying username.

POST /api/TIPO_ESTADO/GetAllFilters — returns status values filtered by the tabla field. Unlike the other reference controllers this action requires a body with at minimum the tabla field set.

# Fetch all statuses applicable to ADM_ATENCION (patient encounters)
curl -s -X POST \
  https://{base_url}/api/TIPO_ESTADO/GetAllFilters \
  -H "Authorization: Bearer {token}" \
  -H "Content-Type: application/json" \
  -d '{"tabla": "ADM_ATENCION"}'

Example response

{
  "Success": true,
  "Data": [
    { "id_estado": 1, "estado": "Pendiente", "tabla": "ADM_ATENCION" },
    { "id_estado": 2, "estado": "En Atención", "tabla": "ADM_ATENCION" },
    { "id_estado": 3, "estado": "Atendido",    "tabla": "ADM_ATENCION" },
    { "id_estado": 4, "estado": "Anulado",     "tabla": "ADM_ATENCION" }
  ],
  "Message": null,
  "Warning": false
}

Always pass the tabla parameter when calling GetAllFilters; omitting it may return an empty result set or statuses from multiple tables merged together, which can produce unexpected behaviour in UI dropdowns.

Quick Reference — All Reference Endpoints

Controller	Endpoint	Actions
`ADM_GENERO`	`/api/ADM_GENERO/GetAllActives`	GetAllActives
`ADM_ESTADO_CIVIL`	`/api/ADM_ESTADO_CIVIL/GetAllActives`	GetAllActives
`ADM_DOCUMENTO_IDENTIDAD`	`/api/ADM_DOCUMENTO_IDENTIDAD/GetAllActives`	GetAllActives
`ADM_GRUPO_SANGUINEO`	`/api/ADM_GRUPO_SANGUINEO/GetAllActives`	GetAllActives
`ADM_OCUPACION`	`/api/ADM_OCUPACION/{action}`	GetAllActives, GetAllFilters, GetById, Add, Update, Delete
`ADM_UBIGEO`	`/api/ADM_UBIGEO/{action}`	GetAllActives, GetAllFilters
`ADM_TIPO_ATENCION`	`/api/ADM_TIPO_ATENCION/GetAllActives`	GetAllActives
`ADM_TIPO_EGRESO`	`/api/ADM_TIPO_EGRESO/GetAllActives`	GetAllActives
`ADM_TIPO_HOSPITALIZACION`	`/api/ADM_TIPO_HOSPITALIZACION/GetAllActives`	GetAllActives
`ADM_TIPO_PACIENTE`	`/api/ADM_TIPO_PACIENTE/GetAllActives`	GetAllActives
`ADM_TIPO_FILIACION`	`/api/ADM_TIPO_FILIACION/GetAllActives`	GetAllActives
`ADM_TIPO_AFILIACION`	`/api/ADM_TIPO_AFILIACION/GetAllActives`	GetAllActives
`TIPO_ESTADO`	`/api/TIPO_ESTADO/GetAllFilters`	GetAllFilters (requires `tabla` body param)

Security

Patient Management

Clinical Catalog

Insurance & Billing

Pharmacy

Accounting

Clinical Reference Data Endpoints — Lookup Tables

Standard Response Envelope

Reference Catalog Endpoints

Quick Reference — All Reference Endpoints

Build docs developers (and LLMs) love

Security

Patient Management

Clinical Catalog

Insurance & Billing

Pharmacy

Accounting

Documentation Index

​Standard Response Envelope

​Reference Catalog Endpoints

​Quick Reference — All Reference Endpoints

Build docs developers (and LLMs) love

Standard Response Envelope

Reference Catalog Endpoints

Quick Reference — All Reference Endpoints