Diagnosis API online manual Medical

   Published: 7 Apr 2024
For your Demo Development you can use AuthenticationID = DEMO_AuthenticationID.
We will provide you with your unique AuthenticationID value after you made a production order registration.
First request
The most important part of the API, which handles medical diagnostics, is the /api/DDxItems/ endpoint, which accepts POST requests. POST requests also take JSON inputs (make sure you include the header Content-Type: application/json).
The Diagnosis API uses custom HTTP header to authenticate your requests. All responses (including error messages) use the JSON format. Setup
The current version of the Diagnosis API is available at https://diagnosisapi.azurewebsites.net. The lists cannot be empty, so first you need to collect an initial information to run diagnosis.Apart from laboratory test results, it requires a list of observed symptoms. You will need to add AuthenticationID header to every request you make. It is a standard web service (Web API) that accepts GET and POST requests.

For your Demo Development you can use AuthenticationID = DEMO_AuthenticationID. To take advantage of the diagnostic capabilities of Diagnosis API you must describe your patient cases in terms of observations available in the presented model; in other words, you need to know exact Test results and Symptoms to be passed to the /DDxItems endpoint.
For each medical concept category there are two REST-inspired read-only endpoints supporting GET requests:
one returns the list of all Lab Tests Procedures (https://diagnosisapi.azurewebsites.net/api/DDxItems/GetTests?AuthenticationID=DEMO_AuthenticationID),
the other returns the list of all possible Symptoms (https://diagnosisapi.azurewebsites.net/api/DDxItems/GetSymptoms?AuthenticationID=DEMO_AuthenticationID).
Each concept is represented by a JSON object with several attributes. Some attributes are common to both concepts:
id - short and unique concept (test or symptom) id,
name - concept name (professional medical term),
description - detailed description.Each request must include non-standard HTTP header: AuthenticationID. We will provide you with your unique AuthenticationID after registration.
An example of a request could look like this (finally you will replace DEMO_AuthenticationID with your credentials):
Base Health Terms
Diagnostic information recognized by the API engine is categorized as Lab Test Procedures and Symptoms. Authentication
Diagnosis API uses a custom authentication mechanism. This parameter corresponds to your unique application ID.