Mock sample for your project: Health Repository Provider Specifications for HIU API

Integrate with "Health Repository Provider Specifications for HIU API" from ndhm.gov.in in no time with Mockoon's ready to use mock sample

Health Repository Provider Specifications for HIU

ndhm.gov.in

Version: 0.5


Use this API in your project

Speed up your application development by using "Health Repository Provider Specifications for HIU API" ready-to-use mock sample. Mocking this API will allow you to start working in no time. No more accounts to create, API keys to provision, accesses to configure, unplanned downtime, just work.
It also improves your integration tests' quality and reliability by accounting for random failures, slow response time, etc.

Description

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.
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.
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 the Gateway label.
Gateway relevant APIs for HIUs are grouped under Gateway label. These include the APIs that HIPs are required to call on the Gateway. For example, to request a CM for consent, HIU would call /consent-requests/init API on gateway.
NOTE, in some of the API documentations below, X-HIP-ID is mentioned in header (for example in /auth/on-init). These are the cases, when a particular API is applicable for both HIU and HIP (e.g an entity is playing the role of HRP representing both HIU and HIP). If you are only playing the role of HIP, then only X-HIU-ID header will be sent

Other APIs by ndhm.gov.in

Health ID Service

It is important to standardize the process of identification of an individual across healthcare providers, to ensure that the created medical records are issued to the right individual or accessed by a Health Information User through appropriate consent.
In order to issue a Health ID to an individual, one only needs basic demographic details like Name, Year of Birth, Gender. In addition, citizens should be able to update contact information easily.

Health Repository Provider Specifications for HIP

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 HIP. The specs are essentially duplicates from the Gateway and Health Repository, but put together so as to make it clear to HIPs which set of APIs they should implement to participate in the network.
Gateway is the hub that routes/orchestrates the interaction between consent managers and API bridges. There are 5 categories of APIs; discovery, link, consent flow, data flow and monitoring. To reflect the consumers of APIs, the above apis are also categorized under cm facing, hiu facing and hip facing

Health Data Consent Manager

Entity which provides health information aggregation services to customers of health care services.
It enables customers to fetch their health information from one or more Health Information Providers
(e.g., Hospitals, Diagnostic Labs, Medical Device Companies), based on their explicit Consent and to share such
aggregated information with Health Information Users i.e. entities in need of such data (e.g., Insurers,
Doctors, Medical Researchers).
Specifications
This document maintains only the Health Information Gateway relevant APIs.

Other APIs in the same category

Revenue & Disaster Management Department, Assam, Assam

apisetu.gov.in
APIs provided by Revenue & Disaster Management Department, Assam, Assam.

Reisezentren-API

deutschebahn.com
This REST-API enables you to query information about travel centers in Germany.

Mizoram Police, Mizoram

apisetu.gov.in
Identification cards, as issued by Mizoram Police to its personnels, can be downloaded by them in their DigiLocker accounts

Madhya Pradesh Medical Science University, Jabalpur M.P., Madhya Pradesh

apisetu.gov.in
Migration certificate issued from 2018 onward can now be fetched by Citizens in their DigiLocker account.

CPCT-MAPIT, Madhya Pradesh

apisetu.gov.in
Computer Proficiency Certification Exam (https://cpct.mp.gov.in) is mandatory for data entry/IT Operator/Assistant Grade-3/steno/shorthand/typist and other similar Permanent/Contractual positions in the departments, corporations and agencies in MP. The CPCT Score Card of 2016 can be pulled into citizens' DigiLocker accounts.

Andaman Law College, Andaman & Nicobar

apisetu.gov.in
Transfer Certificate issued by Andaman Law College can be downloaded in citizen's DigiLocker account.

Revenue Department - Land Records, Karnataka

apisetu.gov.in
APIs provided by Revenue Department - Land Records, Karnataka.

Jharkhand State Board (Jharkhand Academic Council), Jharkhand

apisetu.gov.in
Jharkhand Academic Council (JAC) is issuing marksheets & passing certificates through DigiLocker. These can be pulled by students into their DigiLocker accounts. Currently available - 2009-2017 [Class XII], 2009-2017 [Class X].

Lords Votes API

An API that allows querying of Lords Votes data.

Jawaharlal Nehru Rajkeeya Mahavidyalaya

apisetu.gov.in
Transfer Certificates issued by JNRM can be downloaded in citizen's DigiLocker account.

UK Parliament Search Service

Performs search on parliament.uk domain. Implements OpenSearch specification. Throttled at 10 requests per second per IP address.

Future Generali Total Insurance Solutions

apisetu.gov.in
Two Wheeler, Car, Commercial Vehicle, Home and Travel Insurance policies issued by Future Generali are available on DigiLocker and can be pulled by citizens in their account.