Integrate with NICE HMS

Why Integrate?

If your hospital already uses a HIMS that is not ABDM-compliant, NICE HMS acts as middleware — your existing system integrates with NICE HMS in about 5 to 6 days, and through NICE HMS you become fully ABDM-compliant. No need to replace your HIMS or build ABDM from scratch.

This has been proven: a medical college with an existing non-ABDM HIMS was successfully integrated using NICE HMS as the middleware layer. Their system now creates ABHA Health IDs, links care contexts, and shares health records through ABDM — all handled by NICE HMS.

Every document submitted through the API automatically triggers ABDM notifications — care contexts are registered and health records flow to the patient's PHR app without any manual steps.

Common integration scenarios:

Non-ABDM HIMS — Make your existing hospital software ABDM-compliant in under a week via NICE HMS APIs
Lab information systems — Push diagnostic reports with automatic ABDM sharing
Hospital desktop agents — Local software that syncs data to the cloud
Third-party apps — Mobile apps, kiosks, or patient portals connecting to NICE HMS

Overview

All endpoints use JWT authentication and communicate via JSON. The API is CORS-enabled — every response includes Access-Control-Allow-Origin: * — so it can be called directly from browser-based clients. Full documentation is available at the Developer Portal — www.nicehms.com/developer — with interactive Swagger/OpenAPI docs. Credentials are provisioned by NICE HMS — contact admin@nicehms.com to get started.

Available APIs

The Swagger documentation currently covers:

Category	Capabilities
Auth	Token generation — bearer token expires in 15–30 minutes
Patient	Create patient, lookup by ID or ABHA address, ABHA registration via OTP
Visits	Create OPD visit, IPD admission, discharge
Documents	Discharge summary, diagnostic report, OPD consultation, procedure/OT notes, health document upload — all with ABDM notification
Doctor	Create/edit doctor profiles, list OPD/IPD patients by date

API Reference

Detailed endpoint-by-endpoint reference (request fields, response shapes, examples, and error codes):

Authentication

All endpoints use bearer tokens:

Authorization: Bearer <your-token>

Tokens are obtained from the /auth_token endpoint. Credentials are provisioned by NICE HMS — contact admin@nicehms.com.

Getting integration credentials

Credentials are provisioned by NICE HMS — there is no self-service signup for the integration API.

Prerequisites. Your organization must be registered and on a paid, active plan — the API rejects calls from an expired subscription with 403 SUBSCRIPTION_EXPIRED. For ABDM features (ABHA registration, care-context linking, record sharing) the organization also needs its ABDM facility linkage in place.
Request. Email admin@nicehms.com with: your organization name and org id; your HIMS/product name (if you are integrating an existing system); the intended use (which APIs you will call); a technical contact (name, email, phone); and your expected request volume.
What you receive. An integration email and password — one set per organization. Exchange them for a bearer token at /auth_token, and use that token on every other endpoint. The token is short-lived; call /auth_token again to renew (there is no separate refresh endpoint).
Environments. Nice HMS provides separate sandbox and production credentials. Never point sandbox credentials at production data — confirm which environment you have been issued.
Rotation and recovery. To rotate a password, or if credentials are lost or compromised, email admin@nicehms.com for a reset. Credentials are per organization, not shared between integrators.

FHIR Support

NICE HMS uses FHIR R4 internally for health data exchange, particularly for ABDM record sharing (M2 HIP) and NHCX insurance workflows (pre-auth, claims, discharge).

API Rate Limits

Contact admin@nicehms.com for current rate limits. Enterprise plans include higher limits and dedicated integration support.

Troubleshooting calls

Quick pointers — the full reference is on the Error handling page.

What you see	First thing to check
`401 UNAUTHORIZED`	Token missing, expired, or from another org — call `/auth_token` again and retry.
`400 VALIDATION_ERROR`	Read `error.details` — a required field is missing, a value has the wrong type (e.g. `patientId` as a string), or a template placeholder like `{{abhaAddress}}` was sent literally.
`403 SUBSCRIPTION_EXPIRED`	The organization's subscription has lapsed — renew before retrying.
`500 DB_ERROR` / `500 INTERNAL_ERROR`	Server-side. Retry 2–3 times with backoff; if it persists, escalate with the `x-request-id` header.

FAQ

Q: Does NICE HMS have an API? A: Yes. REST APIs with JWT authentication, documented in the Developer Portal with interactive Swagger docs. Contact admin@nicehms.com for credentials.

Q: Can I integrate my existing lab system? A: Yes. Lab results can be submitted via the diagnostic report API. Contact us with your specific integration requirements.

Q: Where is the full API documentation? A: The Developer Portal hosts Swagger/OpenAPI documentation with request/response schemas and example payloads.