Integrate with NICE HMS

Last updated: 22 July 2026

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. Full documentation is available at the Developer Portalstage.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:

CategoryCapabilities
AuthToken generation — bearer token expires in 15–30 minutes
PatientCreate patient, lookup by ID or ABHA address, ABHA registration via OTP
VisitsCreate OPD visit, IPD admission, discharge
DocumentsDischarge summary, diagnostic report, OPD consultation, procedure/OT notes, health document upload — all with ABDM notification
DoctorCreate/edit doctor profiles, list OPD/IPD patients by date

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.

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.

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.

Was this page helpful?
NICE HMS. 1st Gate Nehru Stadium, City Hubballi, District Dhrawad, State Karnataka, 580020
INDIA, Phone : +919611560555 email admin@nicehms.com, GST 29AEYPB4702Q1ZS
facebook
twitter
linkedin
youtube
RSS