0% found this document useful (0 votes)
13 views

ODAS API Integration

Uploaded by

nhmrajnandgaon22
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
13 views

ODAS API Integration

Uploaded by

nhmrajnandgaon22
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 14

ODAS API

Welcome to Oxygen Demand Aggregation System’s API Documentation. We've designed this document to help developers and
ODAS users fully understand and integrate our API for a seamless and easy deployment. These APIs enable you to update Hospital
profile and infrastructure and also update the daily oxygen demand and consumption details.
We've listed all the APIs, their required parameters, and their example requests and responses in this document for easy
understanding. The easiest way to start using the ODAS APIs is by trying them out in Postman (a free tool that helps developers run
and debug API requests) or our Swagger UI ( https://oxygen.nha.gov.in/ODAS/swagger-ui.html# ).
Our APIs are based around REST architecture and use the basic HTTPS request methods. Our APIs accept JSON- encoded body
requests and return data in the same form.

Getting Started
First, you will need to white list the Public IP of ODAS to access the APIs. Please make note of the details
 Public IP : 59.160.177.51
 Port to be opened : Port : 443
 Domain : oxygen.nha.gov.in

To access ODAS update APIs you will need to use the Authentication API to obtain an access-token. To be able to use the
Authentication API please follow these steps
1. Please reach out to ODAS team for a set of unique values specific for your State. The values will be namely clientId and
clientSecret.
2. These two unique values need to be used in the Request Body of Authentication API.
3. The access-token thus received from the Authentication API will be used to authenticate further API calls.
.

Document and API Usage Guidelines


 Our APIs use the basic HTTP request codes : POST and GET.
 Each API has been described in detail with the attribute description, format followed if any and mandatory or not.
 Please note that to use the generated access-token in your code, you will need to pass the token in the following format
in the appropriate header of your code
Authorization : Bearer <access-token>
 Note: The APIs are constructed at the hospital/facility level. All the information has to be updated with respect to a
hospital/facility only.
 Note: The APIs will work for hospital / facility IDs unique to ODAS system. The Update Facility Info is the first API to be
integrated to register the hospital/facility in ODAS system. This API will return a odasFacilityId which will be created for
the hospital/facility when updating its information for the first time. Further all the APIs will use this unique id to update
the respective set of data.
 The APIs and related details are also present on our swagger interface (https://oxygen.nha.gov.in/ODAS/swagger-ui.html#
).

1. Authentication API
The clientId and clientSecret are alphanumeric code, unique to your State. Use this API with these values and obtain the access-
token. Copy this token and use it further to validate your API calls.
Step to Use access-token:
1. Copy the access-token value received in the Authentication API
2. Include ‘Authorization : Bearer <access-token>’ in the header of the all the other APIs.
3. That’s all! In case of any error, try checking your parameters.

Specifications:
URL: https://oxygen.nha.gov.in/ODAS/v1.0/odas/get-access-token
Request Method: POST
Headers:
Content-Type application/json
Accept application/json
Body:
{
“clientId” : ””,
“clientSecret” : ””
}
(clientId and clientSecret will be provided by ODAS team with respect to your state. )
Response:
{
“access-token” : “”,
“expiresIn” : ,
“refreshExpiresIn” : ,
“refreshToken” : “”,
“tokenType” : “”
}
(access-token received here is to be used in further APIs for Authorization.)

2. Update Facility Information API


Use this API to create and update hospital/facility information in ODAS system. This API takes in all the basic profile details for a
hospital/facility.
Please note:
1. The hospital/facility work with unique IDs based on ODAS system. When consuming this API for the first time, the field
“id” needs to be empty. This will create an ODAS specific unique ID for your hospital (odasFacilityId). This unique id will
now be the facilityId for your hospital/facility with respect to ODAS. This facilityId shall be used in all the APIs now.
2. You have to pass in all the required parameters for a successful update.
3. Please note the format of data that needs to be passed wherever specified.
4. At least 1 nodal contact person’s detail is mandatory. Maximum number of nodal contact persons can be 2.
5. The odasFacilityId returned in the response is the id created for your hospital/facility unique to ODAS system. Please save
this id as this shall be used in all the APIs henceforth.
6. Certain demographic details need to be filled in as LGD codes (Local Government Directory). Please visit
https://lgdirectory.gov.in/ for more information.
7. A duplicity check will be applied before creating your facility. Duplicity parameters include Ownership,
State, District, Pincode, Facility Type and Facility Name. If there are more than one facility with the
same dataset present in the system, then your request for the facility creation will be rejected with a
412 Precondition Failed error.

Parameters:
Params Required Description Data type Format if any

addressLine1 Yes Address Line 1 of the hospital/facility String

addressLine2 No Address Line 2 of the hospital/facility String


city No City of the hospital/facility. The value should be Sting LGD Code
from LGD (Local Government Directory)
district Yes District of the hospital/facility. The value should String LGD Code
be from LGD
pincode No Pin code of the hospital/facility. This needs to String 6 digit number
be a valid 6 digit value.
state Yes State of the hospital/facility. The value should String LGD code
be from LGD.
subdistrict No Sub district of the hospital/facility. The value String LGD code
should be from LGD
facilitytype Yes This field specifies the facility type of your String Only values accepted are the
hospital/facility. For e.g. it can be a Hospital / codes as provided in the
Nursing Home / Maternity Home or a Medical Facility Type Master
College. The value should be the respective
Code from the master provided by ODAS
facilitysubtype No This field specifies the facility sub type of your String Free text
hospital/facility. There is no specified format for
this field; you can enter free text here.
id Yes This field should be unique to the ODAS system. String ODAS created unique id
(No- only for first When you are updating hospital profile for the
time) first time and you don’t have an ODAS specific
unique id the hospital/facility, send this value
as an empty string. The ODAS system will create
a unique id for your hospital/facility
(odasFacilityId) and update the data with
respect to the unique id. This unique id should
be used as facilityId mandatorily for all the
APIs.
langitude Yes This field takes the longitude value of the String Only digits, (.),(-) are allowed
geographic coordinates of the hospital/facility
latitude Yes This field takes the latitude value of the String Only digits, (.),(-) are allowed
geographic coordinates of the hospital/facility
name Yes This field takes the name of your String
hospital/facility.
ownershiptype Yes This field specifies the ownership type of your String Only values accepted are the
hospital/facility. There are only 3 types – codes as provided in the
Government, Private and Public-Private- Ownership Type master
Partnership. Please enter the code of these
values as provided in the master dataset.
ownershipsubtype Yes This field specifies the ownership type of your String Only values accepted are the
hospital/facility. Please enter the code of these codes as provided in the
values as provided in the master dataset. Ownership Sub-Type master
nodalcontacts Yes The sub fields in this array are related to the Array
Nodal Contact Person of your hospital/facility.
Only Nodal contact person’s details should be
provided in this array
countrycode Yes This field specifies country code (+91) for String
contact numbers

designation Yes This field specifies Designation of the nodal String


contact person (for e.g. MD, Director, etc)

email Yes This field specifies the Email of the nodal String Proper format for email is to be
contact person. followed
firstname Yes This field specifies the First name of the nodal String
contact person.

lastname No This field specifies the Last name of the nodal String
contact person.

middlename No This field specifies the Last name of the nodal String
contact person (if any)
mobilenumber Yes This field specifies the Mobile number of the String A valid 10 digit mobile number
nodal contact person.
salutation Yes This field takes the salutation of the Nodal String Accepted values are – Dr. / Ms.
Contact Person. / Mr.
requestId Yes This field will be a 36 character UUID. String 36 character UUID
timestamp Yes Timestamp of the instance the API is called. String It should be in GTC format
Specifications:
URL: https://oxygen.nha.gov.in/ODAS/v1.0/odas/update-facility-info
Request Method: POST
Headers:
Content-Type application/json
Accept application/json
Authorization Bearer <access-token>
Body:
{
“facility” : {
“address” : {
“addressLine1” : “”,
“addressLine2” : “”,
“city” : “”,
“district” : “”,
“pincode” : “”,
“state” : “”,
“subdistrict” : “”
},
“facilitysubtype” : “”,
“facilitytype” : “”,
“id” : “”,
“langitude” : “”,
“latitude” : “”,
“name” : “”,
“ownershipsubtype” : “”,
“ownershiptype” : “”

},
“nodalcontacts” : [
{
“countrycode” : “”,
“designation” : “”,
“email” : “”,
“firstname” : “”,
“lastname” : “”,
“middlename” : “”,
“mobilenumber” : “”,
“salutation” : “”
}
],
“requestId” : “”,
“timestamp” : “”

}
Response:
{
“odasfacilityid” : “”,
“referencenumber” : “”,
“status” : “”
}

3. Update Facility Infrastructure API


Use this API to create and update hospital/facility infrastructure (beds and oxygen concentrators) information in ODAS system. This
API takes in the basic infrastructure that might be available at a hospital/facility, namely General, HDU, ICU beds and Ventilators
along with Oxygen Concentrators
Please note:
1. You have to pass in all the required parameters for a successful update.
2. Please note the format of data that needs to be passed wherever specified
3. If any type of bed is not available in your hospital/facility’s infrastructure then please keep value to “0”.
4. The facilityId needs to be the id unique to ODAS system (odasfacilityid returned in Update Facility Information API).
5. Please note: The number of Ventilators cannot be more than the number of ICU beds.

Parameters:
Params Required Description Data type Format if any

no_gen_beds Yes This field specifies the number of General Beds String Whole Number,
with oxygen available at your facility/hospital. 0 if not available
no_hdu_beds Yes This field specifies the number of HDU (High String Whole Number,
Dependency Units) beds available at your 0 if not available
facility/hospital.
no_icu_beds Yes This field specifies the number of ICU Sting Whole Number,
(Intensive Care Units) beds available at your 0 if not available
facility/hospital.
no_o2_concentrators Yes This field specifies the number of oxygen String Whole Number,
concentrators available at your facility/hospital. 0 if not available
no_vent_beds Yes This field specifies the number of Ventilators String Whole Number,
available at your facility/hospital. Please Note: 0 if not available
number of ventilators cannot be more than the
number of ICU beds.
facilityid Yes This field specifies the Facility Id unique to String ODAS Id generated after
ODAS system. successful data update using
Update Facility Information API
requestId Yes This field will be a 36 character UUID. String 36 character UUID
timestamp Yes Timestamp of the instance the API is called. String It should be in GTC format

Specifications:
URL: https://oxygen.nha.gov.in/ODAS/v1.0/odas/update-facility-bed-info
Request Method: POST
Headers:
Content-Type application/json
Accept application/json
Authorization Bearer <access-token>
Body:
{
"beds": {
"no_gen_beds" : "",
"no_hdu_beds" : "",
"no_icu_beds" : "",
"no_o2_concentrators" : "",
"no_vent_beds": ""
},
"facilityid" : "",
"requestId" : "",
"timestamp" : ""
}
Response:
{
"referencenumber" : "",
"status" : ""
}

4. Update Facility Oxygen Infrastructure API


Use this API to create and update hospital/facility oxygen infrastructure (various types of oxygen cylinders, LMO tanks, etc.)
information in ODAS system. This API takes information regarding the basic oxygen infrastructure that might be available at a
hospital/facility, namely Oxygen Cylinders (various types), LMO (Liquid Medical Oxygen) tanks, PSA (Pressure Swing Adsorption)
oxygen plants, MGP (Medical Gas Pipeline) and cylinder refilling option availability.
Please note:
1. You have to pass in all the required parameters for a successful update.
2. Please note the format of data that needs to be passed wherever specified
3. For availability of any infrastructure please send “Y” if available and “N” if not.
4. If any type of oxygen infrastructure is available at your hospital/facility the corresponding capacity or storage becomes a
mandatory field. For e.g. , if Cylinder Type A is available, then field “cylinder_a_type_yn” = “Y” , and correspondingly the
field “cylinder_a_type_capacity” becomes a mandatory field. Similarly if Cylinder Type A is not available then field
“cylinder_a_type_yn” = “N”, and correspondingly the field “cylinder_a_type_capacity” becomes a non mandatory field.
5. The cylinder capacity being captured basically refers to the count of filled cylinders available at your hospital/facility at the
time of updating this information. The cylinder capacity values should be a whole number and not a fraction or decimal
figure.
6. If LMO is available, then its storage capacity and current stock are captured in MT (metric tonnes). These fields will accept
decimal values as well. Please note that LMO current stock cannot be more than the LMO tank’s storage capacity. Same
applies to PSA oxygen plants.

Parameters:
Params Required Description Data type Format if any

facilityid This field specifies the Facility Id unique to String ODAS Id generated after
ODAS system. successful data update using
Update Facility Information API
cylinder_a_type_capacity Yes - if Cylinder Type This field specifies the count/capacity of String Whole number
A available Cylinder Type A available at your
hospital/facility
cylinder_a_type_yn Yes This field specifies whether Cylinder Type A is String Y/N
available at your hospital/facility or not
cylinder_b_type_capacity Yes - if Cylinder Type This field specifies the count/capacity of String Whole number
B available Cylinder Type B available at your
hospital/facility
cylinder_b_type_yn Yes This field specifies whether Cylinder Type B is String Y/N
available at your hospital/facility or not
cylinder_c20_type_capac Yes - if Cylinder Type This field specifies the count/capacity of String Whole number
ity C 2.0 available Cylinder Type C 2.0 available at your
hospital/facility
cylinder_c20_type_yn Yes This field specifies whether Cylinder Type C String Y/N
2.0 is available at your hospital/facility or not
cylinder_c35_type_capac Yes - if Cylinder Type This field specifies the count/capacity of String Whole number
ity C 3.5 available Cylinder Type C 3.5 available at your
hospital/facility
cylinder_c35_type_yn Yes This field specifies whether Cylinder Type C String Y/N
3.5 is available at your hospital/facility or not
cylinder_c45_type_capac Yes - if Cylinder Type This field specifies the count/capacity of String Whole number
ity C 4.5 available Cylinder Type C 4.5 available at your
hospital/facility
cylinder_c45_type_yn Yes This field specifies whether Cylinder Type C String Y/N
4.5 is available at your hospital/facility or not
cylinder_d6_type_capaci Yes - if Cylinder Type This field specifies the count/capacity of String Whole number
ty D 6.0 available Cylinder Type D 6.0 available at your
hospital/facility
cylinder_d6_type_yn Yes This field specifies whether Cylinder Type D String Y/N
6.0 is available at your hospital/facility or not
cylinder_d7_type_capaci Yes - if Cylinder Type This field specifies the count/capacity of String Whole number
ty D 7.0 available Cylinder Type D 7.0 available at your
hospital/facility
cylinder_d7_type_yn Yes This field specifies whether Cylinder Type D String Y/N
7.0 is available at your hospital/facility or not
lmo_available_yn Yes This field specifies whether LMO (Liquid String Y/N
Medical Oxygen) tank is available at your
hospital/facility or not
lmo_current_stock Yes - if LMO available This field specifies the LMO - Current stock (in String Real number
MT) available at your hospital/facility
lmo_storage_capacity Yes - if LMO available This field specifies the LMO - Storage capacity String Real number
(in MT) available at your hospital/facility
psa_available_yn Yes This field specifies whether PSA(Pressure String Y/N
Swing Adsorption) Oxygen plant is available
at your hospital/facility or not
psa_gen_capacity Yes - if PSA available This field specifies the PSA plant’s Generation String Real number
capacity (in MT)
psa_has_mgp_option_yn Yes This field specified whether your String Y/N
hospital/facility has MGP(Medical Gas
Pipeline) option available at your
hospital/facility or not.
psa_has_refil_option_yn Yes This field specifies whether the PSA plant String Y/N
allows cylinder refilling as well or not.
psa_storage_capacity Yes - if PSA available This field specifies the PSA plant’s Storage String Real number
capacity (in MT)
requestId Yes This field will be a 36 character UUID. String 36 character UUID
timestamp Yes Timestamp of the instance the API is called. String It should be in GTC format

Specifications:
URL: https://oxygen.nha.gov.in/ODAS/v1.0/odas/update-facility-o2-infra
Request Method: POST
Headers:
Content-Type application/json
Accept application/json
Authorization Bearer <access-token>
Body:
{
"facilityid" : "",
"o2Infra" : {
"cylinder_a_type_capacity" : "",
"cylinder_a_type_yn" : "",
"cylinder_b_type_capacity" : "",
"cylinder_b_type_yn" : "",
"cylinder_c20_type_capacity" : "",
"cylinder_c20_type_yn" : "",
"cylinder_c35_type_capacity" : "",
"cylinder_c35_type_yn" : "",
"cylinder_c45_type_capacity" : "",
"cylinder_c45_type_yn" : "",
"cylinder_d6_type_capacity" : "",
"cylinder_d6_type_yn" : "",
"cylinder_d7_type_capacity" : "",
"cylinder_d7_type_yn" : "",
"lmo_available_yn" : "",
"lmo_current_stock" : "",
"lmo_storage_capacity" : "",
"psa_available_yn" : "",
"psa_gen_capacity" : "",
"psa_has_mgp_option_yn" : "",
"psa_has_refil_option_yn" : "",
"psa_storage_capacity" : ""
},
"requestId" : "",
"timestamp" : ""
}
Response:
{
"referencenumber" : "",
“status" : ""
}

5. Update Bed Occupancy Information API


Use this API to update the hospital/facility’s daily occupancy of the beds available. This API captures the daily occupancy of the
hospital/facility’s infrastructure namely, General, HDU, ICU beds, ventilators and oxygen concentrators.
Please note:
1. You have to pass in all the required parameters for a successful update.
2. Please note the format of data that needs to be passed wherever specified.
3. This information needs to be updated every day on a timely basis.
4. The occupancy of any type of bed cannot be greater than the total number of that type of bed available as specified in the
Facility Infrastructure API.
5. The number of ventilators occupied cannot be more than the number of ICU beds occupied.

Parameters:
Params Required Description Data type Format if any

no_gen_beds Yes This field specifies the number of general beds with String Whole number
oxygen occupied on the mentioned date
no_hdu_beds Yes This field specifies the number of HDU (High String Whole number
Dependency Units) beds occupied in a given date
no_icu_beds Yes This field specifies the number of ICU (Intensive String Whole number
Care Units) beds occupied in a given date
no_o2_concentrators Yes This field specifies the number of Oxygen String Whole number
Concentrators occupied in a given date
no_vent_beds Yes This field specifies the number of ventilators String Whole number
occupied in a given date
facilityid Yes This field specifies the Facility Id unique to ODAS String ODAS Id generated after
system. successful data update using
Update Facility Information API
occupancyDate Yes This field specifies the Date for which the String "YYYY-MM-DD"
occupancy is being updated
requestId Yes This field will be a 36 character UUID. String 36 character UUID
timestamp Yes Timestamp of the instance the API is called. String It should be in GTC format

Specifications:
URL: https://oxygen.nha.gov.in/ODAS/v1.0/odas/update-bed-occupancy-info
Request Method: POST
Headers:
Content-Type application/json
Accept application/json
Authorization Bearer <access-token>
Body:
{
"beds": {
"no_gen_beds" : "",
"no_hdu_beds" : "",
"no_icu_beds" : "",
"no_o2_concentrators" : "",
"no_vent_beds" : ""
},
"facilityid" : "",
"occupancyDate" : "",
"requestId" : "",
"timestamp" : ""
}
Response:
{
"referencenumber" : "",
"status" : ""
}

6. Update Facility Oxygen Demand API


Use this API to update the hospital/facility’s daily oxygen demand. This API captures the daily demand estimation of the
hospital/facility. Along with the total estimated demand, it also captures the hospital/facility’s inputs whether the estimation is
Accurate, Overestimated or Underestimated.
Please note:
1. You have to pass in all the required parameters for a successful update.
2. Please note the format of data that needs to be passed wherever specified.
3. This information needs to be updated every day on a timely basis.
4. Total estimated demand for your hospital/facility has to be updated mandatorily without fail.
5. If your state’s demand estimation system captures the hospital’s inputs on the total estimated demand then the following
fields are relevant for state

 Accuracy flag – This field captures a flag value which is updated by the hospital/facility with respect to the total
estimated oxygen demand. If the estimation is correct according to the hospital/facility then flag value needs to
be “Accurate”. If the hospital/facility feels the oxygen estimation is more than what they require
(Overestimated) then flag value becomes “Over”. Similarly, if the hospital/facility feels the oxygen estimation is
less than what they require (Underestimated) then flag value becomes “Under”.

 In case of “Over”, you are required to specify by how much the hospital/facility wants to reduce the demand by.
This value will come in “over_estimated_by” field. The value in this field cannot be greater than the total oxygen
estimated by your system.

 In case of “Under”, you are required to specify by how much the hospital/facility wants to increase the demand
by. This value will come in “under_estimated_by” field. The value in this field cannot be greater than the total
oxygen estimated by your system.
 If your system captures hospital/facility’s remarks on the demand estimation then that value should be captures
in “accuracy_remarks”.

Parameters:
Params Required Description Data type Format if any

accuracy_remarks No This field specifies the remarks entered by the String Free text
hospital/facility on the demand estimation
demand_accuracy_flag Yes This field specifies the Accuracy flag captured String value can be -
by your system with respect to oxygen demand Accurate/Over/Under
estimated for the hospital/facility.
demand_for_date Yes This field capture the Date for which the String YYYY-MM-DD
demand is estimated
demand_raised_date Yes This field captures the Date when the demand String in UTC
is being estimated
over_estimated_by Yes - if accuracy This field specifies the reduction in demand (or String It should be in numeric
flag = Over by how much the total has been overestimated
by) as stated by the hospital/facility in your
system (in MT)
total_estimated_demand Yes This field specifies the total estimated demand String It should be in numeric
being calculated by your system for the
hospital/facility.
under_estimated_by Yes - if accuracy This field specifies the increment in demand (or String It should be in numeric
flag = Under by how much the total has been
underestimated by) as stated by the
hospital/facility in your system (in MT)
facilityid Yes This field specifies the Facility Id unique to String ODAS Id generated after
ODAS system. successful data update using
Update Facility Information API
requestId Yes This field will be a 36 character UUID. String 36 character UUID
timestamp Yes Timestamp of the instance the API is called. String It should be in GTC format

Specifications:
URL: https://oxygen.nha.gov.in/ODAS/v1.0/odas/update-facility-oxygen-demand
Request Method: POST
Headers:
Content-Type application/json
Accept application/json
Authorization Bearer <access-token>
Body:
{
"demandInfo": {
"accuracy_remarks" : "",
"demand_accuracy_flag" : "",
"demand_for_date" : "",
"demand_raised_date" : "",
"over_estimated_by" : "",
"total_estimated_demand" : " ",
"under_estimated_by" : ""
},
"facilityid" : "",
"requestId" : "",
"timestamp" : ""
}
Response:
{
"referencenumber" : "",
"status" : ""
}

7. Update Facility Oxygen Consumption API


Use this API to update the hospital/facility’s daily oxygen consumption details. Along with the total oxygen consumption details, it
also captures the amount of oxygen delivered and generated at the hospital/facility on a daily basis.
Please note:
1. You have to pass in all the required parameters for a successful update.
2. Please note the format of data that needs to be passed wherever specified.
3. This information needs to be updated every day on a timely basis.
4. Oxygen consumption, oxygen consumed and oxygen delivered values need to in MT (metric tonnes).
5. Oxygen delivered constitutes the oxygen delivered in the form of Cylinders and LMO.
6. Oxygen generated comes from the oxygen plant (PSA in this case).
7. Oxygen consumed is calculated as total consumption from cylinders, LMO and oxygen plants.

Parameters:
Params Required Description Data type Format if any

consumption_for_date Yes This field specifies the Date for which the String "YYYY-MM-DD"
oxygen consumption details are being updated
for your hospital/facility.
consumption_updated_d Yes This field specifies the Date on which the String "YYYY-MM-DD"
ate oxygen consumption details are being updated
for your hospital/facility.
total_oxygen_consumed Yes This field specifies the total oxygen consumed String Real number
on the specified consumption_for_date (in MT)
total_oxygen_delivered Yes This field specifies the total oxygen delivered on String Real number
the specified consumption_for_date (in MT)
total_oxygen_generated Yes This field specifies the total oxygen generated String Real number
on the specified consumption_for_date (in MT)
facilityid Yes This field specifies the Facility Id unique to String ODAS Id generated after
ODAS system successful data update using
Update Facility Information API
requestId Yes This field will be a 36 character UUID. String 36 character UUID
timestamp Yes Timestamp of the instance the API is called. String It should be in GTC format

Specifications:
URL: https://oxygen.nha.gov.in/ODAS/v1.0/odas/update-facility-oxygen-consumption
Request Method: POST

Headers:
Content-Type application/json
Accept application/json
Authorization Bearer <access-token>
Body:
{
"consumptionInfo" : {
"consumption_for_date" : "",
"consumption_updated_date" : "",
"total_oxygen_consumed" : "",
"total_oxygen_delivered" : "",
"total_oxygen_generated" : ""
},
"facilityid" : "",
"requestId" : "",
"timestamp" : ""
}
Response:
{
"referencenumber" : "",
"status" : ""
}

Masters
Please refer to the following master data set for “facilitytype”, “ownershiptype” and “ownershipsubtype”. Please make sure to send
the code while consuming the API.

Sno Master Type

1. Facility Types

Code Owner Facility Type


2 Government Medical College
3 Government Hospital/ Nursing Home/ Maternity Home
4 Government Community Health Centre (CHC)
5 Government Dispensary/ Clinic/ Polyclinic
6 Government Primary Health Centre (PHC)
7 Government Sub Centre (SC)
8 Government Other Converted Facility
9 Government Daycare Center
10 Government Infertility Clinic
11 Government Dialysis Center
12 Government Palliative Care
13 Government Rehabilitation Center
14 Government Physiotherapy Clinic
15 Government Physiotherapy Hospital
16 Government Physiotherapy College
17 Government Ayurveda Hospital/ Nursing Home
18 Government Ayurveda College
19 Government Unani Hospital/ Nursing Home

20 Government Unani College


21 Government Siddha Hospital/ Nursing Home
22 Government Siddha College
23 Government Sowa-Rigpa Hospital/ Nursing Home
24 Government Sowa-Rigpa College
25 Government Homeopathy Hospital/ Nursing Home
26 Government Homeopathy College
27 Private / Public-Private-Partnership Medical College
28 Private / Public-Private-Partnership Hospital/ Nursing Home/ Maternity Home
29 Private / Public-Private-Partnership Dispensary/ Clinic/ Polyclinic (OPD only)
30 Private / Public-Private-Partnership Other Converted Facility
31 Private / Public-Private-Partnership Daycare Center
32 Private / Public-Private-Partnership Infertility Clinic
33 Private / Public-Private-Partnership Dialysis Center
34 Private / Public-Private-Partnership Palliative Care
35 Private / Public-Private-Partnership Rehabilitation Center
36 Private / Public-Private-Partnership Physiotherapy Clinic
37 Private / Public-Private-Partnership Physiotherapy Hospital
38 Private / Public-Private-Partnership Physiotherapy College
39 Private / Public-Private-Partnership Ayurveda Hospital/ Nursing Home
40 Private / Public-Private-Partnership Ayurveda College
41 Private / Public-Private-Partnership Unani Hospital/ Nursing Hom
42 Private / Public-Private-Partnership Unani College
43 Private / Public-Private-Partnership Siddha Hospital/ Nursing Home
44 Private / Public-Private-Partnership Siddha College
45 Private / Public-Private-Partnership Sowa-Rigpa Hospital/ Nursing Home
46 Private / Public-Private-Partnership Sowa-Rigpa College
47 Private / Public-Private-Partnership Homeopathy Hospital/ Nursing Home
48 Private / Public-Private-Partnership Homeopathy College
2. Ownership
Code Ownership
G Government
P Private
PP Public-Private-Partnership
3. Ownership Sub Type
For Ownership = G
Code Ownership Sub type
S State
C Central
For Ownership = P or PP
Code Ownership Sub type
NP Not for Profit

You might also like