Retrieves an organization by its hospital ID.

Updates an existing organization.

Uploads medication master data for a hospital in JSON format and stores it as a CSV file.

Requirements:

• hospital_id and a non-empty medications array are required.
• Each medication must contain BRAND NAME and GENERIC NAME.
• BRAND ID is optional, but if provided in any item, it must be present in all items.

Optional Fields:

• UOM CODE
• UOM DESCRIPTION (if provided, UOM CODE is required).
• ACTIVE FROM (DD/MM/YYYY)
• ACTIVE TO (DD/MM/YYYY)
• MEDICATION TYPE

Validation:

• Duplicate BRAND ID values in the request are marked invalid.
• Duplicate BRAND NAME and GENERIC NAME combinations are marked invalid.

The API stores the valid data as a CSV file and returns the processed file URL along with any invalid rows.

Accepts patient, doctor, hospital, and vitals data for integration.

Creates a new patient record.

Creates a doctor record and associates it with an organization.

Updates a doctor's profile and organization details using practitioner_id and hospital_id.

Fetches a doctor's details using practitioner_id.

Updates a doctor's opdassessment, opdsheet, and advanced_settings based on provided practitioner_id.

Fetches a patient's record using their hospital-specific ID and organization ID.

Retrieves patient details, including inpatient status, by their primary ID.

Retrieves all vital sign details for a specific patient.

Retrieves a list of all available languages.

Retrieves the OPD form configuration and related organization data for a given hospital ID.
The API returns base64-encoded images (left and right), processed URLs for medication and investigation data, and other key organization settings like inpatient setup, lab model, and upload configurations.

This endpoint uploads edited OPD (Outpatient Department) interaction data, stores it in cloud storage, and triggers ingestion for updated patient records.
It handles both new and previously edited OPD interactions.
If no previous edited OPD record exists, it falls back to using the last audio interaction.

Updates the OPD form configuration for a hospital, including optional image uploads for left and right logos via multipart/form-data.

Sends chatbot interaction data for a hospital session to the CareScribe Simmer API. This endpoint forwards the request to the upstream chatbot engine and returns its response. Accepts a dynamic payload containing user, patient, and session context.

Creates a new patient record if not found or adds an interaction if the patient exists.

Searches for patients by name, phone number, or patient ID within an organization.

Creates a new speciality.

Retrieves a single speciality by its ID.

Retrieves a list of all specialities.

Updates an existing speciality.

Creates a new assessment template for a given practitioner.