Mock sample for your project: Health Data Consent Manager API

Integrate with "Health Data Consent Manager API" from ndhm.gov.in in no time with Mockoon's ready to use mock sample

Health Data Consent Manager

ndhm.gov.in

Version: 0.5


Use this API in your project

Integrate third-party APIs faster by using "Health Data Consent Manager API" ready-to-use mock sample. Mocking this API will help you accelerate your development lifecycles and improves your integration tests' quality and reliability by accounting for random failures, slow response time, etc.
It also helps reduce your dependency on third-party APIs: no more accounts to create, API keys to provision, accesses to configure, unplanned downtime, etc.

Description

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 by ndhm.gov.in

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 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.

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 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

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.

Other APIs in the same category

Dr. A. P. J. Abdul Kalam Technical University, Lucknow, Uttar Pradesh

apisetu.gov.in
Marksheets and Degree Certificates of academic year 2017-18 issued by AKTU can be pulled by students into their DigiLocker accounts

Written Questions Service API

Data around written questions and answers, as well as written ministerial statements.

Accountants General, Tripura

apisetu.gov.in
APIs provided by Accountants General, Tripura.

Motor Vehicle Department, Maharashtra

apisetu.gov.in
Driving License (DL) and Vehicle Registration Certificate (RC) of the State, as available on Parivahan Sewa (http://parivahan.co.in/) of Ministry of Road Transport and Highways, are available on DigiLocker. Citizens can pull these documents into their DigiLocker accounts.

Haryana State Board of School Education, Haryana

apisetu.gov.in
Board of School Education, Haryana (http://www.bseh.org.in/home/) has made available 2016-2019 Class XII & Class X results in DigiLocker, which can be pulled by students into their accounts.

College Football Data API

collegefootballdata.com
This is an API for accessing all sorts of college football data. Please note that API keys should be supplied with "Bearer " prepended (e.g. "Bearer your_key"). API keys can be acquired from the CollegeFootballData.com website.

Chitkara University

apisetu.gov.in
Degree Certificates of various courses issued by Chitkara University can be downloaded in citizen's DigiLocker account.

Transport Department, Haryana

apisetu.gov.in
Driving License (DL) and Vehicle Registration Certificate (RC) of the State, as available on Parivahan Sewa (http://parivahan.co.in/) of Ministry of Road Transport and Highways, are available on DigiLocker. Citizens can pull these documents into their DigiLocker accounts.

FireBrowse Beta API

firebrowse.org
A simple and elegant way to explore cancer data

GlobalWineScore API Documentation

globalwinescore.com
The GlobalWineScore API is designed as a RESTful API, providing several resources and methods depending on your usage plan.
For further information please refer to our plans.
Authentication
The API uses token-based authentication.
In order to authenticate your requests, you need to include a specific header in each of your requests:
The word Token must be written. Your requests must also use the HTTPS protocol.
If you don't have a token yet, you need to apply for one here.
Your personal token can be found under the My account > API section of the GlobalWineScore website
Format
The API provides several rendering formats which you can control using the Accept header or format query parameter.
JSON (default): no header or Accept: application/json
XML: Accept: application/xml
Rate limiting
For API requests, the rate limit allows for up to 10 requests per minute.
Error handling
Whether a request succeeded is indicated by the HTTP status code. A 2xx status code indicates success, whereas a 4xx status code indicates failure.
When a request fails, the response body is still JSON, but always contains a detail field with a description of the error, which you can inspect for debugging.
For example, trying to access the API without proper authentication will return code 403 along with the message:
{"detail": "Authentication credentials were not provided."}
Found a bug ? send us an email at [email protected]
Ordering
At the moment, GlobalWineScores may be sorted by date and score. Use "-"
to sort in descending order.
Continuous synchronization
If you need to synchronize your database with our API, you can query our API using ?ordering=-date to get the newest scores first, which means you won't have to crawl the whole catalog every time :-)
Quick search interface
If you need to search our catalog (e.g. to align it with yours), we're providing you with a handy interface accessible here: https://api.globalwinescore.com/search/
You need to be logged in (email/password) to access this page, but other than that you can share it with anyone in your team and start searching right away !
Resources
The details about available endpoints can be found below.
You can click on each endpoint to find information about their parameters.

CISCE

apisetu.gov.in
CISCE (http://www.cisce.org/) is issuing marksheets, passing certificates, migration certificates through DigiLocker. These can be pulled by students into their DigiLocker accounts. Currently available - 2014-2019 (marksheets, passing certificates of ICSE & ISC and migration certificates of ISC).

Space Radiation API

amentum.space
Space has a hostile radiation environment that increases the risk of cancers in humans and malfunctions in spacecraft electronics. The types of space radiation of primary concern are:
Galactic Cosmic Rays from outside our solar system generated by
supernovae and other phenomena;
Solar Energetic Particles produced by the Sun during intense and
sporadic bursts of activity; and
Trapped Radiation: energetic particles confined by Earth's magnetic
field, usually comprising an inner belt of mostly high energy protons
and an outer belt dominated by lower energy electrons and plasma.
Understanding the space radiation environment for a particular mission profile is becoming increasingly important. Commercial off-the-shelf electronic components that aren't resilient to space radiation are now prevalent. Longer duration missions to cislunar space, Mars, and beyond are placing astronauts at greater risk of radiation exposure.
API requests must contain a key "API-Key" in the header (see code samples). Obtain a key from here.
Help us improve the quality of our web APIs by completing our 2 minute survey here.
Amentum Pty Ltd is not responsible nor liable for any loss or damage of any sort incurred as a result of using the API.
Copyright Amentum Pty Ltd 2021.