Published: 14 Jan 2024

After you successfully send the POST request, Diagnosis API system starts to generate list of Possible Health Conditions.
Please generate unique Ids since your clinical decision system's users may access simultaneously. You can retrieve the suggested diagnoses list by applying GET request:
https://diagnosisapi.azurewebsites.net/api/DDxItems/9999?AuthenticationID=DEMO_AuthenticationID
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. You have to replace the DEMO_AuthenticationID with your production registered ID.

Typically, diagnosis API includes two major components.
A knowledge base. How do healthcare organizations quickly implement such tools in their daily practice? The answer is clear and short - via APIs (application programming interfaces). The content is constantly reviewed and updated by medical professionals.
A diagnostic engine. This is an overview of available diagnosis API along with their primary use cases. Their mission is to keep patients better informed about the possible roots of their conditions and provide clinicians with decision support. It contains data on conditions, diseases, and treatment procedures. Often powered by AI, it analyzes patient data inputs (like demographics, symptoms, and lab tests) or automatically extracts clinical features from electronic health records. The engine links patient information with pieces of content in the knowledge base and returns a list of likely conditions (preliminary diagnosis), care suggestions (triage), or both.But first, let's examine the main parts and core functionality of diagnosis API that can be integrated into a hospital's daily workflow.
DDxHub API is not here to put real physicians out of work.