Published: 3 Dec 2024

Request Format

* Each request must include a non-standard HTTP header titled: `AuthenticationID`.
* For demonstration purposes, use `AuthenticationID = DEMO_AuthenticationID`.

Patient Case Representation

* To utilize the Diagnosis API's diagnostic capabilities, depict patient cases as comments in the unfilled model.
* This requires passing Test Results and Symptoms to the `/DDxItems` endpoint.

Medical Concept Endpoints

* For each medical concept class, there are two read-only REST endpoints accessible via GET requests:
* `/GetTests`: Returns a list of all Lab Tests Procedures.
* `/GetSymptoms`: Returns a list of all possible Symptoms.

JSON Representation

* Each concept is represented as a JSON object with several attributes:
* `id`: Unique concept ID.
* `name`: Concept name (medical term).
* `description`: Complete description.

Authentication Mechanism

* Diagnosis API uses a custom authentication mechanism.
* Provide a unique `AuthenticationID` upon registration.

Example Request

```
https://diagnosisapi.azurewebsites.net/api/DDxItems/?AuthenticationID=DEMO_AuthenticationID
```

Base Health Terms

* Diagnostic data recognized by the API is categorized as Lab Test Procedures and Symptoms.
* Common attributes include:
* `id`: Unique concept ID.
* `name`: Concept name.
* `description`: Complete description.

Core Functionality

* Knowledge Center: Stores data on diseases, treatments, and patient information.
* Diagnostic Engine: Analyzes patient data and suggests possible diagnoses or treatment recommendations.

Integration into Healthcare Practice

* Diagnosis API can be integrated into healthcare workflow via APIs (application programming interfaces).
* Open diagnosis APIs enable healthcare organizations to instantly implement diagnostic tools.