The Curo - Health Care Management APIs collection is a comprehensive suite of RESTful APIs designed to manage various aspects of healthcare services and applications. This collection enables seamless integration of health records, appointment scheduling, medicine management, user authentication, and advanced features like premium prediction and chatbot functionality. Below is a detailed overview of the key components of this collection
\n","schema":"https://schema.getpostman.com/json/collection/v2.0.0/collection.json","toc":[],"owner":"26636117","collectionId":"04056783-ab16-4d33-b379-2a217fcdaea8","publishedId":"2sAYQdjALr","public":true,"customColor":{"top-bar":"FFFFFF","right-sidebar":"303030","highlight":"FF6C37"},"publishDate":"2025-01-22T14:02:28.000Z"},"item":[{"name":"Maps","item":[{"name":"Get Nearby Hospitals","id":"84b51c39-a608-4ffd-a944-046d18d3f6cd","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[],"url":"https://curo-156q.onrender.com/api/maps/nearby-hospitals?lat=12.9716&lng=77.5946&radius=5000","description":"lat (required)
Description: Latitude of the user's current location.
\nType: string
Example: \"37.7749\"
lng (required)
Description: Longitude of the user's current location.
\nType: string
Example: \"-122.4194\"
radius (optional)
Description: The search radius (in meters) for finding nearby hospitals. Defaults to a specific range if not provided.
\nType: integer
Example: 5000
/api/maps/nearby-lablat (required)
Description: Latitude of the user's current location.
\nType: string
Example: \"37.7749\"
lng (required)
Description: Longitude of the user's current location.
\nType: string
Example: \"-122.4194\"
radius (optional, defaults to 5000)
Description: The search radius (in meters) for finding nearby medical labs.
\nType: integer
/api/maps/nearby-lablat (required)
Description: Latitude of the user's current location.
\nType: string
Example: \"37.7749\"
lng (required)
Description: Longitude of the user's current location.
\nType: string
Example: \"-122.4194\"
radius (optional, defaults to 5000)
Description: The search radius (in meters) for finding nearby medical labs.
\nType: integer
/api/health-recordstype (required)
Description: The type/category of the health record (e.g., \"Prescription,\" \"Lab Report,\" etc.).
\nType: string
Example: \"Prescription\"
details (required)
Description: Additional details about the health record, provided in JSON format.
\nType: JSON string
Example: { \"doctor\": \"Dr. John Doe\", \"date\": \"2025-01-20\", \"remarks\": \"Follow up in 2 weeks\"}
\nfile (optional)
Description: A file attachment associated with the health record, such as a scanned report or prescription.
\nType: file
Example: A .pdf, .jpg, or .png file uploaded via the request.
type (required)
Description: The updated type/category of the health record (e.g., \"Prescription,\" \"Lab Report,\" etc.).
\nType: string
Example: \"Lab Report\"
details (required)
Description: Updated details about the health record in JSON format.
\nType: JSON object
Example: { \"doctor\": \"Dr. Jane Doe\", \"date\": \"2025-02-01\", \"remarks\": \"Updated remarks for follow-up.\"}EndFragment
\ntype (required)Description: The updated type/category of the health record (e.g., \"Prescription,\" \"Lab Report,\" etc.).
\nType: string
Example: \"Lab Report\"
details (required)Description: Updated details about the health record in JSON format.
\nType: JSON object
Example: { \"doctor\": \"Dr. Jane Doe\", \"date\": \"2025-02-01\", \"remarks\": \"Updated remarks for follow-up.\"}
\nname (required)Description: The updated name of the medicine.
\nType: string
Example: \"Paracetamol\"
dosage (required)Description: The updated dosage of the medicine.
\nType: string
Example: \"500 mg\"
time (required)Description: The updated time(s) when the medicine should be taken. Can be a single time or an array of times.
\nType: string or array of strings
Example: \"08:00 AM\" or [\"08:00 AM\", \"08:00 PM\"]
days (required)Description: The updated days of the week or specific dates when the medicine should be taken.
\nType: array of strings
Example: [\"Monday\", \"Wednesday\", \"Friday\"] or [\"2025-02-01\", \"2025-02-02\"]
name (required)Description: The name of the medicine to be reminded about.
\nType: string
Example: \"Aspirin\"
dosage (optional)Description: The dosage of the medicine.
\nType: string
Example: \"100 mg\"
time (required)Description: The time(s) when the medicine should be taken. Can be a single time or an array of times.
\nType: string or array of strings
Example: \"08:00 AM\" or [\"08:00 AM\", \"08:00 PM\"]
days (required)Description: The days of the week or specific dates when the medicine should be taken.
\nType: array of strings
Example: [\"Monday\", \"Wednesday\", \"Friday\"] or [\"2025-02-01\", \"2025-02-02\"]
uid (required)Description: The unique identifier for the user in Firebase.
\nType: string
Example: \"abc123\"
email (required)Description: The email address of the user.
\nType: string
Example: \"user@example.com\"
name (required)Description: The name of the user, which will also be set as the Firebase display name.
\nType: string
Example: \"John Doe\"
uid (required)Description: The unique identifier for the user in Firebase, retrieved from Google sign-in.
\nType: string
Example: \"abc123\"
email (required)Description: The email address of the user, retrieved from Google sign-in.
\nType: string
Example: \"user@example.com\"
name (required)Description: The name of the user, retrieved from Google sign-in.
\nType: string
Example: \"John Doe\"
fcmToken (required)Description: The Firebase Cloud Messaging (FCM) token to be updated for the user.
\nType: string
Example: \"abcd1234efgh5678\"
provider_id (required)Description: The ID of the healthcare provider (doctor) offering the appointment.
\nType: string
Example: \"doctor123\"
start_time (required)Description: The start date and time of the appointment in a valid date/time format.
\nType: string (ISO 8601 format)
Example: \"2025-02-10T14:00:00Z\"
notes (optional)Description: Additional notes for the appointment.
\nType: string
Example: \"Patient is feeling unwell and needs a follow-up\"
StartFragment
\nfeatures (required)Description: An array of 10 numeric values representing various health-related features for the prediction model. These features include, but are not limited to, medical and demographic data such as age, weight, health conditions, and surgeries.
\nType: array of numbers
Example: { \"features\": [45, 1, 130, 0, 1, 175, 80, 0, 1, 2]}
\nWhere:
\nAge = 45
Diabetes = 1 (1 for yes, 0 for no)
BloodPressureProblems = 130
AnyTransplants = 0 (0 for no, 1 for yes)
AnyChronicDiseases = 1 (1 for yes, 0 for no)
Height = 175 cm
Weight = 80 kg
KnownAllergies = 0 (0 for no, 1 for yes)
HistoryOfCancerInFamily = 1 (1 for yes, 0 for no)
NumberOfMajorSurgeries = 2
blood_group (optional)
\nDescription: The user's blood group, used for medical information purposes.
\nType: string
\nExample: \"O+\"
allergies (optional)
\nDescription: List of allergies the user has, stored as a string.
\nType: string
\nExample: \"Peanuts, Shellfish\"
heart_rate (optional)
\nDescription: The user's average heart rate, measured in beats per minute.
\nType: number
\nExample: 72
blood_pressure (optional)
\nDescription: The user's blood pressure, typically measured as systolic/diastolic (e.g., 120/80).
\nType: string
\nExample: \"120/80\"
height (optional)
\nDescription: The user's height, typically measured in centimeters or feet/inches.
\nType: number
\nExample: 175
weight (optional)
\nDescription: The user's weight, typically measured in kilograms or pounds.
\nType: number
\nExample: 70
dob (optional)
\nDescription: The user's date of birth, formatted as YYYY-MM-DD.
\nType: string
\nExample: \"1990-05-15\"
Note: The uid is automatically extracted via the authenticateUser middleware and does not need to be explicitly included in the request body. This endpoint only requires the fields that need updating, and all are optional based on the user's input.
uid (required)
\nDescription: The unique identifier for the user in Firebase, retrieved from Google sign-in.
\nType: string
\nExample: \"abc123\"
email (optional)
\nDescription: The email address of the user, retrieved from Google sign-in.
\nType: string
\nExample: \"user@example.com\"
name (optional)
\nDescription: The name of the user, retrieved from Google sign-in.
\nType: string
\nExample: \"John Doe\"
Note: The uid is retrieved automatically through the authenticateUser middleware and does not need to be explicitly included in the request body by the client. Other fields like email and name are inferred during profile creation or updates and do not need to be sent here.