The Medical Consensus API enables you to submit clinical queries and receive comprehensive medical opinions synthesized from multiple expert sources. This feature is useful for validating diagnoses, exploring treatment options, and getting second opinions on complex cases.Documentation Index
Fetch the complete documentation index at: https://docs.sully.ai/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Medical Consensus helps clinicians with:- Second Opinions: Get AI-synthesized expert perspectives on clinical cases
- Diagnosis Validation: Confirm or explore differential diagnoses
- Treatment Options: Review current guidelines and treatment approaches
- Drug Interactions: Understand potential medication interactions
Authentication
Alpha endpoints use Bearer token authentication, which differs from the header-based authentication used by stable API endpoints.You use the same API key for both stable and alpha endpoints. Only the authentication header format differs. Get your API key from dashboard.api.sully.ai.
Creating a Request
Submit a clinical query to the consensus endpoint. The API returns immediately with a request ID while processing happens asynchronously.Endpoint
Request Body
| Field | Type | Required | Description |
|---|---|---|---|
query | string | Yes | Your clinical question or scenario |
Response
| Field | Type | Description |
|---|---|---|
data.id | string | Unique identifier for the consensus request |
data.status | string | Initial status (always pending) |
data.created_at | string | Timestamp when the request was created (ISO 8601) |
Code Examples
Response Example
Polling for Results
After creating a request, poll the GET endpoint to check status and retrieve results when processing completes.Endpoint
Status Flow
| Status | Description |
|---|---|
pending | Request received, queued for processing |
processing | Actively analyzing your clinical query |
completed | Analysis complete, results available in result.consensus_response |
failed | Processing failed, error details in result.error |
Polling Example
Understanding Results
When a consensus request completes, the response includes the full request details and result.Response Fields
| Field | Type | Description |
|---|---|---|
data.id | string | Unique identifier for the request |
data.status | string | Current status: pending, processing, completed, or failed |
data.created_at | string | Timestamp when request was created |
data.updated_at | string | Timestamp when request was last updated |
data.result.consensus_response | string | The medical consensus text (when completed) |
data.result.error | string | Error message (when failed) |
Completed Response Example
Failed Response Example
Example Queries
The quality of the consensus response depends on the specificity and clinical relevance of your query. Here are examples of effective clinical queries:Differential Diagnosis
Treatment Guidelines
Drug Interactions
Symptom Evaluation
Pediatric Considerations
Rate Limits
The Medical Consensus endpoint is rate limited to ensure fair usage across all users.| Aspect | Details |
|---|---|
| Limit | Configurable requests per day (based on your plan) |
| Window | 24 hours |
| Exceeded | Returns 429 Too Many Requests |
Handling Rate Limits
When you exceed the rate limit, the API returns a429 status code:
- Wait 24 hours for your limit to reset
- Contact support@sully.ai to discuss higher limits
- Review your usage to optimize query frequency
Best Practices
Follow these guidelines to get the best results from Medical Consensus.Be Specific in Your Queries
| Less Effective | More Effective |
|---|---|
| ”Patient has chest pain" | "55-year-old male with substernal chest pain radiating to left arm, onset 2 hours ago, associated with diaphoresis" |
| "What about diabetes?" | "What are first-line treatment options for newly diagnosed Type 2 diabetes with HbA1c of 8.5%?” |
Include Relevant Patient Details
When appropriate, include:- Age and sex
- Relevant medical history
- Current medications
- Symptom duration and characteristics
- Relevant lab values or vital signs
Use for Clinical Decision Support
Appropriate Use Cases
| Appropriate | Not Appropriate |
|---|---|
| Exploring differential diagnoses | Making definitive diagnoses |
| Reviewing treatment guidelines | Prescribing without clinical evaluation |
| Getting second opinions on complex cases | Emergency medical decisions |
| Understanding drug interactions | Replacing specialist consultation |
Verify Results
Always:- Cross-reference with current clinical guidelines
- Consider patient-specific factors not in the query
- Apply clinical judgment to all recommendations
- Document the use of AI-assisted decision support appropriately
Next Steps
Alpha API Overview
Learn about alpha features and stability expectations
Alpha Authentication
Detailed authentication guide for alpha endpoints
Create Consensus API
Full API reference for creating consensus requests
Get Consensus API
Full API reference for retrieving consensus results