Skip to content
LotusPond Health

LotusPond Health for developers Sandbox open

One API for India’s hospital systems.

Find patients, list their visits, attach documents and check claims through one REST API and one MCP server, on your organisation’s authority. Results come back as FHIR R4. Start today in our sandbox hospital, with no sales call.

Systems you can reach

The status of each system is stated plainly. We do not have partnership agreements with these vendors; product names and logos, trademarks of their owners, are used only to say which systems a connection can reach. The same list is published as JSON at /v1/connectors.

  • LotusPond sandbox hospitalAvailable now
  • HL7 FHIRAny FHIR R4 serverOn request
  • InterSystemsInterSystems TrakCareOn request
  • BahmniBahmniOn request
  • OpenMRSOpenMRSOn request
  • Eka CareEka Care EMROn request

Planned

  • Akhil SystemsAkhil Systems Miracle HISPlanned
  • KareXpertKareXpertPlanned
  • MocDocMocDocPlanned
SystemStatusHow we reach itUsed by
LotusPond sandbox hospitalAvailableSynthetic patients, visits and claims, for building and testingEvery new organisation, from the first key
Any FHIR R4 serverAvailable on requestFHIR R4 REST: Patient, Encounter and DocumentReferenceHospitals whose HIS exposes FHIR R4
Bahmni and OpenMRSAvailable on requestOpenMRS FHIR2 module (FHIR R4)Public and non-profit hospitals and clinics
InterSystems TrakCareAvailable on requestFHIR R4 through the hospital’s InterSystems interoperability toolkitManipal Hospitals, Sir Ganga Ram Hospital
Eka Care EMRAvailable on requestEka’s published EMR APIs, with the clinic’s sharing key for its Eka workspace; agent tasks in Eka’s doctor web appClinics and doctors using Eka
ABDM-certified HIS (consented records)PlannedABDM health-information-user flow, with each patient’s consentC-DAC e-Sushrut, NIC NextGen eHospital and other certified systems
NHCX claims exchangePlannedNational Health Claims Exchange (FHIR claim profiles)Insurers and TPAs on NHCX
Akhil Systems Miracle HISPlannedNeeds Akhil Systems’ partnershipAster, Paras, probably CARE
KareXpertPlannedNeeds KareXpert’s partnershipArtemis and mid-size hospitals
Practo Insta HMSPlannedNeeds Practo’s partnershipClinic chains and hospitals
Suvarna HIMSPlannedNeeds Suvarna’s partnershipProbably KIMS; medical colleges
MocDocPlannedPublished REST API; keys come through each MocDoc customerSmall and mid-size hospitals and clinics
Available
Works today with an API key.
Available on request
Works today through FHIR R4 or the vendor’s published API. We set it up for your hospital or clinic once it confirms your access in writing and gives the access its system needs: an interface switched on, or a sharing key.
In build
The vendor publishes developer access; our connector is being built.
Planned
Needs the vendor’s partnership or a national network’s onboarding first.

Quickstart

  1. Open the developer console and make an organisation account, with your organisation. It is separate from a personal LotusPond Health account, and works like LotusPond Works: add your team by email with a role (owner, admin, editor or viewer), and mark the clinicians who approve writes.
  2. Make an API key and choose what it may do. The key is shown once; keep it in your secret store.
  3. List your connections. Every organisation has a sandbox hospital with synthetic patients.
curl https://health.lotuspond.ai/v1/connections \
  -H "Authorization: Bearer lpk_…"

curl https://health.lotuspond.ai/v1/operations/patients.search \
  -H "Authorization: Bearer lpk_…" -H "Content-Type: application/json" \
  -d '{"connection": "<connection id>", "name": "asha"}'

Every answer is JSON: {"status": "done", "result": …} with a FHIR R4 resource or Bundle, or 202 with {"status": "pending_approval", "approval": …} for a write that waits for a clinician. Errors carry a code and a plain message.

MCP server

Give your own agents the same operations as tools. Point any MCP client that supports Streamable HTTP at the organisation endpoint and send your key as a bearer token:

{
  "mcpServers": {
    "lotuspond-hospitals": {
      "type": "http",
      "url": "https://health.lotuspond.ai/v1/mcp",
      "headers": { "Authorization": "Bearer lpk_…" }
    }
  }
}

The tools follow the key: list_connections, search_patients, list_encounters, upload_document, get_claim_status, run_task, get_task and get_approval. A key without an operation does not see its tool. This server is for organisations; people connect their own records at /mcp instead.

Operations

OperationInputReturns
patients.searchconnection and an identifier (MRN, UHID or ABHA number), name or phone; optional birthDate, limitBundle of Patient
encounters.listconnection, patient; optional limitBundle of Encounter and DocumentReference
documents.uploadconnection, patient, title, contentType (PDF, JPEG, PNG or text), base64 data up to 5 MB; optional encounter, authorHeld for approval, then DocumentReference
claims.statusconnection, claimClaimResponse (sandbox today; NHCX and TPA portals later)
tasks.runconnection, instruction (what to do, naming the patient); optional patient, maxStepsHeld for approval, then a task: a computer-use agent (GPT-6.1 Terra) does it in the system’s web app, in an isolated browser, and every action it takes is logged. Sandbox and Eka Care today
preauth.submitPlannedClaim and ClaimResponse

Also: GET /v1/organisation (who the key belongs to), GET /v1/connections, GET /v1/approvals/{id}, GET /v1/tasks/{id} and GET /v1/tasks/{id}/actions (the agent’s action log).

Going live with a hospital

New organisations reach only the sandbox. To reach a real hospital system, ask for live access in the console and tell us which hospital and which system. Before we add the connection we need:

  • The hospital’s written authority for your organisation to read or write the records you named.
  • A service account or token from the hospital’s IT team, and the interface switched on (FHIR R4 for TrakCare, Bahmni and other FHIR systems). For an Eka Care clinic: a sharing key for its Eka workspace.
  • A data-processing agreement between your organisation and LotusPond.

We never sign in as a hospital’s staff, never work around multi-factor sign-in or a vendor’s access controls, and never use a system against its vendor’s terms.

Safety and records

  • Writes wait for a clinician. An upload is held, with its content encrypted, until someone with approval rights in your organisation approves it in the console. Then it is sent and the held copy is deleted.
  • Every call is recorded. Each key lists what it may do; every call, allowed or refused, is logged with its outcome and shown in the console.
  • Credentials are sealed. Hospital credentials are encrypted at rest and never returned by the API.
  • Data in India. The organisation API runs on servers in India.