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.

Romsoft Gestión Clínica API is an ASP.NET Web API backend designed for healthcare clinics. It exposes a structured REST interface for managing the full patient lifecycle — from registration and clinical attendance through insurance billing and pharmacy dispensing — all secured with JWT bearer tokens and audited via a rolling log.

Quickstart

Make your first authenticated API call in minutes

Authentication

Obtain a JWT token and secure your requests

API Reference

Full endpoint reference with request/response schemas

Architecture

Understand the layered design and response envelope

What the API covers

Patient Management

Register patients, search by DNI, and query clinical history

Medical Attendance

Create and track attendances with pending-state workflows

Insurance Plans

Manage SEGUS/SUSALUD insurance plans and tariffs

Pharmacy

Maintain the pharmaceutical product catalog

Billing

Generate and query payment documents (comprobantes)

User Security

Manage system users and roles

Getting started

1

Configure the server

Set your SQL Server connection string and JWT secret in Web.config. See Database Configuration and JWT Settings.
2

Authenticate

Call POST /api/Account/Login with a username and password to receive a user object. Pass the token on subsequent requests in the Authorization: Bearer <token> header. See Authentication.
3

Make your first request

Query active insurance plans with POST /api/CVN_PLAN_SEGURO/GetAllActives or retrieve patient records with POST /api/ADM_PACIENTE/GetAllFilters. See the Quickstart for a complete walkthrough.
4

Explore the API reference

Browse the full endpoint documentation organized by domain: Security, Patients, Pharmacy, and more.
All endpoints use POST and return a consistent JsonResponse envelope with Success, Warning, Message, and Data fields. See Response Format for details.

Build docs developers (and LLMs) love