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
Any FHIR R4 serverOn requestInterSystems TrakCareOn request
BahmniOn requestOpenMRSOn request
Eka Care EMROn request
Planned
Akhil Systems Miracle HISPlanned
KareXpertPlanned
MocDocPlanned
| System | Status | How we reach it | Used by |
|---|---|---|---|
| LotusPond sandbox hospital | Available | Synthetic patients, visits and claims, for building and testing | Every new organisation, from the first key |
| Any FHIR R4 server | Available on request | FHIR R4 REST: Patient, Encounter and DocumentReference | Hospitals whose HIS exposes FHIR R4 |
| Bahmni and OpenMRS | Available on request | OpenMRS FHIR2 module (FHIR R4) | Public and non-profit hospitals and clinics |
| InterSystems TrakCare | Available on request | FHIR R4 through the hospital’s InterSystems interoperability toolkit | Manipal Hospitals, Sir Ganga Ram Hospital |
| Eka Care EMR | Available on request | Eka’s published EMR APIs, with the clinic’s sharing key for its Eka workspace; agent tasks in Eka’s doctor web app | Clinics and doctors using Eka |
| ABDM-certified HIS (consented records) | Planned | ABDM health-information-user flow, with each patient’s consent | C-DAC e-Sushrut, NIC NextGen eHospital and other certified systems |
| NHCX claims exchange | Planned | National Health Claims Exchange (FHIR claim profiles) | Insurers and TPAs on NHCX |
| Akhil Systems Miracle HIS | Planned | Needs Akhil Systems’ partnership | Aster, Paras, probably CARE |
| KareXpert | Planned | Needs KareXpert’s partnership | Artemis and mid-size hospitals |
| Practo Insta HMS | Planned | Needs Practo’s partnership | Clinic chains and hospitals |
| Suvarna HIMS | Planned | Needs Suvarna’s partnership | Probably KIMS; medical colleges |
| MocDoc | Planned | Published REST API; keys come through each MocDoc customer | Small 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
- 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.
- Make an API key and choose what it may do. The key is shown once; keep it in your secret store.
- 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
| Operation | Input | Returns |
|---|---|---|
patients.search | connection and an identifier (MRN, UHID or ABHA number), name or phone; optional birthDate, limit | Bundle of Patient |
encounters.list | connection, patient; optional limit | Bundle of Encounter and DocumentReference |
documents.upload | connection, patient, title, contentType (PDF, JPEG, PNG or text), base64 data up to 5 MB; optional encounter, author | Held for approval, then DocumentReference |
claims.status | connection, claim | ClaimResponse (sandbox today; NHCX and TPA portals later) |
tasks.run | connection, instruction (what to do, naming the patient); optional patient, maxSteps | Held 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.submit | Planned | Claim 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.