Last updated: 29 August 2026
NICE HMS documentation lives on the docs site and covers the product, the APIs, and the ABDM/NHCX workflows. If you find an error, a missing section, or something that needs correcting, report it and it will be folded into the next documentation revision.
Use the same ticketing system as other support issues — see Raising Tickets and Reporting Issues.
You can also email admin@nicehms.com with "Documentation" in the subject.
To help the docs team fix it quickly, include:
| Item | Example |
|---|---|
| Which page | The URL, or the section title (e.g. "ABDM API — Error Handling") |
| What's wrong | The current text, or what is missing |
| Suggested correction | The corrected wording, or the field/value that should be listed |
| Context | The feature, API endpoint, or workflow the page relates to |
For API docs specifically, mention the endpoint and the field name — for example,
"/diagnostic_report category should list the accepted enum values."
Q: Is documentation feedback the same as a bug report? A: No. A bug report is about the product not working; documentation feedback is about the docs being wrong or incomplete. Both use the same ticketing system, but choose the category that fits — Feature Request or General Inquiry for docs.
Q: Can I report a doc issue from inside the chatbot? A: Yes. The chatbot captures unanswered questions and doc gaps as feedback for review. For a specific correction, a ticket with the page URL and suggested wording is the most direct route.
Q: How do I know my doc correction was applied? A: You will be emailed when the ticket is resolved. The docs site is updated in the next revision.