Ndhm Health Data Consent Manager

Name: Health Data Consent Manager API
Brand: NDHM Health Data Consent Manager
Availability: InStock

★ Only Publicly Available OpenAPI DocumentHealthcareEhr Emrnone22 Endpoints

Install Jentic One Beta

Connect the Health Data Consent Manager to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Health Data Consent Manager, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Health Data Consent Manager API.

Receive care-context discovery responses from registered HIPs and present them to the patient

Initiate consent requests on behalf of an HIU and capture the patient's grant or denial

Fetch consent artefacts and forward them to the requesting HIU

GET STARTED

Start building with Health Data Consent Manager API

Explore with Jentic

View OpenAPI Document

For Agents

Build a patient-facing Consent Manager that aggregates Indian health data across HIPs and shares it with HIUs based on explicit consent.

Use for: I need to receive a care-context discovery response from a HIP, Initiate a consent request on behalf of an HIU, Fetch a consent artefact and forward it to the requesting HIU, Notify an HIP that consent was revoked

Not supported: Does not store HIP-side patient records, issue ABHA Health IDs, or perform clinical workflows — use for the patient-facing consent and care-context aggregation role only.

Jentic publishes the only available OpenAPI specification for Health Data Consent Manager, keeping it validated and agent-ready. The Health Data Consent Manager (CM) is the patient-facing component of India's NDHM that aggregates health information across Health Information Providers and shares it with Health Information Users based on the patient's explicit consent. The 22-endpoint surface covers care-context discovery responses, consent request initiation and fetching, health-information request handling, link confirmation, and heartbeat monitoring.

Use Cases

Patterns agents use Health Data Consent Manager API for, with concrete tasks.

★ Patient Consent Manager App Backend

A health-tech company builds a patient-facing CM app where users can see which hospitals hold their records, grant consent to share with insurers or telehealth apps, and revoke access at any time. The CM endpoints handle the discovery responses, consent request lifecycle, and health-information requests that the patient authorises through the app.

Receive POST /v0.5/care-contexts/on-discover events, persist them, and present the linkable care contexts to the patient

HIU-Triggered Consent Requests

When an HIU (e.g., insurer or telehealth platform) needs patient records, it asks the patient's CM to issue a consent request. POST /v0.5/consent-requests/init records the request, the patient approves through the CM UI, and POST /v0.5/consents/fetch delivers the signed artefact back to the requesting HIU.

Call POST /v0.5/consent-requests/init with the HIU id, purpose, and HIP scope; on patient approval, call POST /v0.5/consents/fetch and forward the artefact

Health-Information Data Request Coordination

After consent is granted, the CM mediates the actual data transfer by forwarding HIU requests to the HIP, receiving acknowledgements, and emitting status notifications. Endpoints like POST /v0.5/health-information/request, /on-request, and /notify capture each step of the encrypted data exchange.

Call POST /v0.5/health-information/request with the consent artefact reference and listen for the corresponding /notify event when delivery completes

Agent-Driven CM Operations

An AI agent operating inside a CM platform handles routine tasks like fetching consent artefacts, posting acknowledgements, and reconciling expiry events. Jentic resolves natural-language requests to the correct CM endpoint and signs the JWT-based payloads from the encrypted vault.

Search Jentic for 'fetch ndhm consent artefact', execute POST /v0.5/consents/fetch with the consent ID and forward the result

Key Endpoints

22 endpoints — jentic publishes the only available openapi specification for health data consent manager, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/v0.5/consent-requests/init

Create a consent request

POST

/v0.5/consents/fetch

Fetch a consent artefact

POST

/v0.5/health-information/request

Request health information from an HIP

POST

/v0.5/health-information/notify

Notify on data flow events

POST

/v0.5/links/link/add-contexts

Confirm HIP-initiated care-context linking

GET

/v0.5/heartbeat

Get service heartbeat

POST

/v0.5/consent-requests/init

Create a consent request

POST

/v0.5/consents/fetch

Fetch a consent artefact

POST

/v0.5/health-information/request

Request health information from an HIP

POST

/v0.5/health-information/notify

Notify on data flow events

POST

/v0.5/links/link/add-contexts

Confirm HIP-initiated care-context linking

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

JWT signing keys and CM client credentials are stored encrypted in the Jentic vault. Agents receive scoped execution tokens — private keys and raw bearer tokens never enter the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'fetch NDHM consent artefact') and Jentic returns POST /v0.5/consents/fetch with its schema, so the agent supplies the consentId without browsing 22 paths.

Time to first call

Direct NDHM CM integration: 2-3 weeks including JWT setup, patient UI wiring, and certification testing. Through Jentic: under a day for the core consent and data-request flows.

FAQs

Specific to using Health Data Consent Manager API through Jentic.

Why is there no official OpenAPI spec for Health Data Consent Manager?

NDHM does not publish a maintained OpenAPI specification for the CM role — only Markdown reference docs and a deprecated apis.guru import. Jentic generates and maintains this spec so that AI agents and developers can call Health Data Consent Manager via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the NDHM Health Data Consent Manager use?

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

Can I fetch a consent artefact through this API?

Yes. POST /v0.5/consents/fetch retrieves a signed consent artefact by its consentId. The CM forwards the artefact to the requesting HIU after the patient grants approval through the CM application.

What are the rate limits for the Health Data Consent Manager?

Rate limits are not declared in the OpenAPI spec. The sandbox at dev.ndhm.gov.in/cm applies fair-use throttling for development; production limits depend on the CM operator's onboarding tier with the National Health Authority.

How do I initiate a consent request through Jentic?

Search Jentic for 'initiate NDHM consent request', load the schema for POST /v0.5/consent-requests/init, and execute with the HIU id, purpose, and date-range. The CM then prompts the patient and your callback handler receives the consent artefact.

How does this differ from the NDHM Gateway?

The Gateway is the central router across all roles. The Consent Manager is the patient-facing aggregator that holds consent records and presents the patient UI for grant or revocation. Most CM endpoints have a Gateway counterpart that forwards messages between roles.

Ndhm Health Data Consent Manager

Connect the Health Data Consent Manager to your agent

Capabilities

Start building with Health Data Consent Manager API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs