Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/ttpullima/RomsoftBackEnd2021_v2/llms.txt

Use this file to discover all available pages before exploring further.

The Gestión Clínica system manages two distinct physical spaces within a healthcare facility: consultorios (consultation rooms), used for outpatient appointments where patients meet with a physician for evaluation or follow-up, and habitaciones (hospital rooms), used for inpatient care where patients are admitted and housed during a hospitalisation episode. Both catalogs are maintained under the administrative domain (ADM_) and are referenced throughout scheduling, admissions, and billing modules. The ADM_CONSULTORIO and ADM_HABITACION controllers each expose a GetAllActives endpoint to retrieve the currently active records from their respective tables. All endpoints require a valid Authorization bearer token.
Both controllers follow the API-wide HTTP POST convention. No request body is needed for either GetAllActives call.

​
Use Cases

ModuleSpace typeTypical usage
Outpatient schedulingADM_CONSULTORIOAssign a consultation room when booking an appointment for a doctor
Inpatient admissionsADM_HABITACIONAssign a bed/room when admitting a patient to the ward
Occupancy reportingBothGenerate a daily room-occupancy report across the facility
BillingADM_CONSULTORIOAssociate a specific consulting room with a charge item

​
Data Transfer Objects

​
ADM_CONSULTORIODTO

Represents a single consultation room (outpatient).
​
id_consultorio
integer
Unique numeric surrogate key for the consultation room.
​
c_codigo
string
Short alphanumeric code for the room (e.g., "C-01", "CONS-A"). Used internally for quick identification.
​
t_descripcion
string
Full descriptive name of the consultation room (e.g., "Consultorio 1 – Medicina General", "Consultorio Pediatría").

​
ADM_HABITACIONDTO

Represents a single hospital room (inpatient ward).
​
id_habitacion
integer
Unique numeric surrogate key for the hospital room.
​
c_codigo
string
Short alphanumeric code for the room (e.g., "H-101", "UCI-3").
​
t_descripcion
string
Full descriptive name of the room (e.g., "Habitación 101 – Piso 1", "Unidad de Cuidados Intensivos – Cama 3").

​
ADM_CONSULTORIO Endpoints

​
POST /api/ADM_CONSULTORIO/GetAllActives

Returns the complete list of active outpatient consultation rooms registered in the facility. No request body is required. This list is consumed by appointment scheduling screens to present available rooms when booking a consultation.
Cache this response at the session level on the frontend — the consultation room catalogue changes infrequently, so repeated requests on the same screen are unnecessary overhead.
Request 
curl -s -X POST \
  https://{base_url}/api/ADM_CONSULTORIO/GetAllActives \
  -H "Authorization: Bearer {token}" \
  -H "Content-Type: application/json"
Response — success 
{
  "Success": true,
  "Data": [
    {
      "id_consultorio": 1,
      "c_codigo": "C-01",
      "t_descripcion": "Consultorio 1 – Medicina General"
    },
    {
      "id_consultorio": 2,
      "c_codigo": "C-02",
      "t_descripcion": "Consultorio 2 – Cardiología"
    },
    {
      "id_consultorio": 3,
      "c_codigo": "C-03",
      "t_descripcion": "Consultorio 3 – Pediatría"
    }
  ],
  "Message": null,
  "Warning": false
}
Response — error 
{
  "Success": false,
  "Data": null,
  "Message": "Ocurrió un error, inténtelo más tarde.",
  "Warning": false
}

​
ADM_HABITACION Endpoints

​
POST /api/ADM_HABITACION/GetAllActives

Returns the complete list of active hospital rooms (inpatient rooms and beds) registered in the system. No request body is required. This list is used in the admissions module when assigning a room to a patient being hospitalised, as well as in inpatient census reports. Request 
curl -s -X POST \
  https://{base_url}/api/ADM_HABITACION/GetAllActives \
  -H "Authorization: Bearer {token}" \
  -H "Content-Type: application/json"
Response — success 
{
  "Success": true,
  "Data": [
    {
      "id_habitacion": 1,
      "c_codigo": "H-101",
      "t_descripcion": "Habitación 101 – Hospitalización General"
    },
    {
      "id_habitacion": 2,
      "c_codigo": "H-102",
      "t_descripcion": "Habitación 102 – Hospitalización General"
    },
    {
      "id_habitacion": 10,
      "c_codigo": "UCI-1",
      "t_descripcion": "Unidad de Cuidados Intensivos – Cama 1"
    }
  ],
  "Message": null,
  "Warning": false
}
Response — error 
{
  "Success": false,
  "Data": null,
  "Message": "Ocurrió un error, inténtelo más tarde.",
  "Warning": false
}

​
Response Envelope

Both controllers return responses wrapped in the standard JsonResponse envelope:
FieldTypeDescription
Successbooleantrue if the request completed without a server-side exception.
Dataarray / nullArray of ADM_CONSULTORIODTO or ADM_HABITACIONDTO objects on success.
Messagestring / nullHuman-readable message, populated on warning or error states.
Warningbooleantrue when a business-rule condition was triggered rather than a hard failure.
Neither ADM_CONSULTORIODTO nor ADM_HABITACIONDTO extends EntityAuditableDTO, so audit fields (FechaCreacion, UsuarioCreacion, etc.) are not included in these responses. Room management (create, update, deactivate) is handled by separate administrative screens and is not exposed through this API version.

Build docs developers (and LLMs) love

Get started for freeTalk to us