Popular Medical API for web applications reference

Published: 12 Nov 2023

The Diagnosis API is available at https://diagnosisapi.
azurewebsites.net. Azure Storage currently supports three versions of the TLS protocol: 1.0, 1.1, and 1.2. Error messages are also in JSON. /api/DDxItems).
JSON is the only data format supported by Diagnosis API. The API hosted on Azure storage. All requests to the API must be made via HTTPS. Requests, like responses, should be encoded in UTF-8.The API content is read-only and all of the API responses always return the same output for the same input, no matter how many times you call them. However, you need to use only two last of them.
Use GET requests to retrieve data that do not require any data to be sent in the requests body.
Use POST requests for actions that require data to be sent in the request's body (e.g. Moreover, the POST actions expect request bodies formatted as JSON objects. All of our endpoints return JSON objects or lists. As any RESTfull service, the API supports four HTTP methods: DELETE, PUT, GET, and POST. Azure Storage uses TLS 1.2 on public HTTPS endpoints, but TLS 1.0 and TLS 1.1 are still supported for backward compatibility.
Also, that provides cross-origin resource sharing (CORS) to allow client-side code of web applications to interact with the Diagnosis API, but please make sure you never expose your API credentials in any client-side code of public websites.
HTTP Methods
The Diagnosis API can be easily integrated with any existing HTTP client by using any popular programming languages and frameworks.

After you successfully send the POST request, Diagnosis API system starts to generate list of Possible Health Conditions. You can retrieve the suggested diagnoses list by applying GET request:
This is the last GET request listed in https://www.postman.com/collections/7445d89fda1d633e08dd Postman collection provided by us.
The 9999 is Id supplied with your POST statement. Please generate unique Ids since your clinical decision system's users may access simultaneously. You have to replace the DEMO_AuthenticationID with your production registered ID.