Qure.ai Documentation
  • User's Manual
    • Qure.ai App User's Manual
      • Getting Started
        • Installation in Windows/Mac
        • Installation in Mobile
        • To Log In to Qure.ai App
      • Qure.ai App Features
        • Windows/Mac OS App UI
          • Worklist Panel
            • Worklist Search
            • Saveable Filters
          • Navigation Toolbar
            • Dark/Light Mode
            • Add
              • Add Patient
              • Import Scans
            • Settings
              • Notification Settings
              • Automated Sharing
              • User Groups Management
              • Worklist Tags
              • Report Templates & Formatting
              • Workspace Management
              • Connection to modality
            • Profile
          • Patient Channel
            • To Edit/Merge Patient Worklist Information
            • To Sent Photos/Videos/Document
            • To Add Clinical Forms
              • Tuberculosis Diagnosis Forms
                • Risk Groups
                • Symptoms
                • TB Vouchers
                • Confirmatory Lab Test - GeneXpert
                • Confirmatory Lab Test - CBNAAT
              • Stoke Evaluation Forms
                • NIHSS Evaluation
                • Clinical History of Stoke Suspects
          • Preview Panel
            • Studies Filter
          • Share Function
            • To Share the Patient File
          • Emergency Activation
          • Support
            • Report an Issue
            • Send an Idea
          • Qure.ai App Viewer
            • Navigation Toolbar
            • STUDIES Panel
            • DICOM Viewer
              • Tool
                • Window/Level
                • Measuring Tool Menu
              • Viewer
            • REPORTING Panel
              • Edit Report
              • Download Report
          • Qure.ai App Widget
        • Mobile App UI
          • Worklist
            • Menu
          • Patient Channel
          • Studies Panel
          • Support
      • Configuration
      • Troubleshooting
      • FAQs
        • Security and Privacy
    • Gateway User Manual
      • Installation pre-requisite
      • Installation Process
      • Configuration
        • Setting up the Medical System (modality) Configuration
          • Configuring Medical System (modality)
      • DCMIO features
      • Troubleshooting
      • FAQs
  • Release Notes
    • Qure.ai App
    • Gateway
  • API
    • Platform API
      • Overview
      • Get Started
        • qXR
        • qER
        • qCT
        • qMSK
      • API Specifications
        • Uploading the Dicoms
        • Initiating Computation
        • Fetching Results
      • On-premises Deployment Specifications
        • Server Setup
        • Deployment Files
        • Starting the Service
      • Output Specifications
        • qXR
        • qER
        • qCT
        • qMSK
Powered by GitBook
On this page
  • Fetching the Results
  • Response Attribute

Was this helpful?

  1. API
  2. Platform API
  3. API Specifications

Fetching Results

The processed series results can be fetched via API call.

Use the following sample script to get the processed series results.

Python
# Make the HTTP Get request to the service
r = requests.get(URL, headers={'Authorization': 'Token {}'.format(TOKEN)})

Fetching the Results

GET http://BASE URL + results/ + [SERIES INSTANCE UID]

Use the URL to make a GET call.

Path Parameters

Name
Type
Description

URL*

String

The URL pointing to the service.

Headers

Name
Type
Description

Authorization*

String

Bearer token.

Json
{
    "success": true,
    "message": "Results retrieved successfully!",
    "triage_status": "Routine/Critical",
    "usecase": "qxr/qer/qct/not_implemented",
    "result": {
         "report": "string",
         "files": {
             "output_type": ["pre_signed_urls"],
             .
             .
             .
         }
     },
     "report": []
}
Json
{
    "success": false,
    "message": "Image Series with resource_uid
 series_instance_uid is under process. 
Please check back in some time.
}
Json
{
    "success": false,
    "message": "Not a valid use case",
    "debug_info": {
        "reason": "string"
    },
    "remarks": "{}",
    "result": {}
}
Json
{
    "message": "Invalid token header.
 No credentials provided.",
    "next": "/accounts/login/",
    "authenticated": false
}
Json
{
    "success": false,
    "message": "Access denied!"
}
Json
{
    "success": false,
    "message": "Series with SeriesInstanceUID
 series_instance_uid is not yet uploaded!"
}
Json
{
    "success": false,
    
"message": "Series with resource_uid
 series_instance_uid has not yet been invoked
 for computation. You can invoke by doing a GET on base_url/compute/series_instance_uid."
}

Response Attribute

Attribute
Value type
Description
Sample Value

Boolean

It indicates whether the API call was successful or not.

  • True: The call was successful.

  • False: The call was not successful.

String

It validates the post call action based on the response status code.

String

It prioritize the results.

  • Critical: It indicates high priority results and requires an expert supervision.

  • Routine: It indicates standard priority results and requires an expert supervision.

String

It indicates type of usecase results.

  1. qXR: Chest X-rays results.

  2. qER: Head CT scans results.

  3. qCT: Lungs X-rays results.

  4. Not implemented: No usecase defined.

String

PreviousInitiating ComputationNextOn-premises Deployment Specifications

Last updated 2 years ago

Was this helpful?

It contains the results of the API call. For more information, see .

success
"success": true
message
"message": "Results retrieved successfully!"
triage_status
"triage_status": "Routine"
usecase
"usecase": "qer"
result
"result": {
        "report": "No intracranial hemorrhage found",
        "files": {
                "reports": [],
                "sc_key_slices": [],
                "sc": [],
                "gsps": [],
                "sc_png": []
        }
},
Output Specification