Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/FlasheyEstudi/Oasis-Liquido/llms.txt

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

Oasis Liquido runs as two separate Next.js applications that communicate over HTTP. The Backend serves the REST API on port 8000 and owns the SQLite database through Prisma. The Frontend runs on port 3000 and is what users interact with. Both apps live in the same repository, so a single clone is all you need to get started.
1

Prerequisites

Make sure you have the following installed before continuing:
  • Node.js 18 or later — required by both apps
  • npm (bundled with Node.js) or bun (used by the seed script and the production start command)
Verify your Node.js version:
node --version
2

Clone the repository

git clone https://github.com/FlasheyEstudi/Oasis-Liquido.git
cd Oasis-Liquido
3

Set up the Backend

Install dependencies, apply the database schema, seed demo data, then start the dev server. The Backend runs on port 8000.
cd Backend
npm install
npx prisma migrate dev
bun run seed
npm run dev
The seed command populates the database with a complete Nicaragua healthcare ecosystem: hospitals such as Vivian Pellas, Hospital Militar, and Bautista; pharmacies including Saba, Kielsa, and Medco; and a catalogue of medicines with realistic inventory levels. This data is required for most features to work correctly.
Once running, the API is available at http://localhost:8000/api/v1.
4

Set up the Frontend

Open a new terminal tab, then install dependencies and start the Frontend dev server. The Frontend runs on port 3000.
cd Frontend
npm install
npm run dev
5

Access the app

Open http://localhost:3000 in your browser. You will see the Oasis Liquido login screen.The platform has five user roles: Patient, Doctor, Pharmacist, Delivery Driver, and Administrator. Each role unlocks a different set of features — from booking appointments to managing inventory and dispatching deliveries. You can create test accounts for any role directly through the registration flow on the login page.
Create at least one Doctor account and one Patient account to explore the full appointment-booking and digital prescription workflow end to end.

Build docs developers (and LLMs) love