API · source category: Open Data

Health Repository Provider Specifications for HIU

The following are the specifications for the APIs to be implemented at the Health Repository end if an entity is only serving the role of a…

The following are the specifications for the APIs to be implemented at the Health Repository end if an entity is only serving the role of a HIU. The specs are essentially duplicates from the Gateway and Bridge, but put together so as to make it clear to HIUs which set of APIs they should implement to participate in the network. 1. The APIs are organized by the flows - identification, consent flow, data flow and monitoring. They represent the APIs that are expected to be available at the HIU end by the Gateway. 2. For majority of the APIs, if Gateway has initiated a call, there are corresponding callback APIs on the Gateway. e.g for /consents/hiu/notify API on HIU end, its expected that a corresponding callback API /consents/hiu/on-notify on Gateway is called. Such APIs are organized under…

Open documentation ↗

Record

Type
Web API
Category
Open Data & Government
Authentication
Unknown
Pricing
Free
Base URL
https://apisetu.gov.in
Free tier
Public OpenAPI specification

Fields are reproduced from the source registry as-is. “Unknown” means the source did not describe the field — it is not an inference. See the methodology for how records are collected and normalised.

Tags

  • Open Data

Browse all Open Data & Government APIs.