What authentication does the HIU specification require?

HIU endpoints are secured with signed JWTs issued through the NDHM Gateway and validated against certificates fetched from /v0.5/certs. The OpenAPI spec leaves `securitySchemes` empty because authorisation is enforced at the JWT layer rather than via a standard HTTP scheme.

Can I initiate a consent request as an HIU through this spec?

Yes. POST /v0.5/consent-requests/init starts the flow on the Gateway with the HIU id, purpose, HIP scope, and time range. The CM then prompts the patient and your /v0.5/consents/hiu/notify endpoint receives the consent artefact reference.

What are the rate limits for the HIU endpoints?

Rate limits are not declared in the OpenAPI spec. The sandbox at dev.ndhm.gov.in applies fair-use throttling for development; production rate limits depend on the HIU's onboarding tier with the National Health Authority and the volume of consents in flight.

How do I request a health-information bundle through Jentic?

Search Jentic for 'request NDHM health-information bundle as HIU', load the schema for POST /v0.5/health-information/cm/request, and execute with the granted consent artefact reference. The CM forwards the request to the HIP, which transfers the encrypted bundle to your /on-request endpoint.

Can I limit what my agent is allowed to do with the NDHM HIU Specifications API?

Yes. Because Jentic One is self-hosted, you decide which HIU operations the agent may call, so you can allow it to run consent-requests init or consents fetch while withholding everything else. The agent can only execute the operations you selected, which means callbacks and endpoints you leave out stay unavailable to it. The consent request, HIU id, and purpose travel inside the signed request body rather than the URL path, so your scoping rules govern exactly which calls the agent makes with your signing credentials.