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
  • Uploading Dicoms to the Service
  • Response Attribute

Was this helpful?

  1. API
  2. Platform API
  3. API Specifications

Uploading the Dicoms

BASE URL will be the API service hostname and each request to the Qure.ai app is expected to carry a bearer TOKEN. Qure will provide both of these.

Use the following sample script to upload Dicoms to the service.

Python
import requests
from requests_toolbelt.multipart.encoder import MultipartEncoder
file_paths = ['dicom-file1.dcm', 'dicom-file2.dcm']

m = MultipartEncoder({
    file_path: (file_path, open(file_path, 'rb'), 'application/dicom')
    for file_path in file_paths
})
content_type = 'multipart/related; type=application/dicom; boundary={}'\
.format(m.boundary_value)

# Make the HTTP POST request to the service
r = requests.post(

    url=URL, data=m,

    headers={'Content-Type': content_type,
             'Authorization': 'Token {}'.format(TOKEN)})

Uploading Dicoms to the Service

POST http://BASE URL + studies

Use the URL to make a POST call with the multipart encoded payload.

Path Parameters

Name
Type
Description

file_paths*

String

Represents the file location.

URL*

String

The URL pointing to the service.

Headers

Name
Type
Description

Authorization*

String

Bearer token.

Content-Type*

String

Request Body

Name
Type
Description

data*

String

Json
{
    "message": "Success",
    "series_instance_uids": ["SERIES_INSTANCE_UID_1", "SERIES_INSTANCE_UID_2",],
    "detailed_info":[
        {
            "SeriesInstanceUID": "SERIES_INSTANCE_UID 1",
            "NumberOfSeriesRelatedInstances": "INTEGER"
        },
        {
            "SeriesInstanceUID": "SERIES_INSTANCE_UID 2",
            "NumberOfSeriesRelatedInstances": "INTEGER"
        }      

    ]
}
Json
{
    "message": "No DICOM files were uploaded!"
}
Json
{
    "message": "Invalid token header.
        No credentials provided.",
    "next": "/accounts/login/",
    "authenticated": false
}

For large data, it is recommended to perform batch uploads. Please ensure that the payload size of each request does not exceed 100 MB.

Response Attribute

Attribute
Value type
Description
Sample Value

String

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

Integer

It is a unique identifier given for a series of Dicom images.

String

It is an object which contains a set of Dicom images.

-

Integer

It is the number of series instance UID's that belong to a set of series.

Boolean

It validates the token validity.

PreviousAPI SpecificationsNextInitiating Computation

Last updated 2 years ago

Was this helpful?

message
"message": "Success"
series_instance_uids
"series_instance_uids": [
    "1.2.826.0.1.3680043.8.498.83895378777916398722746509596078492186"
detailed_info
NumberOfSeriesRelatedInstances
"NumberOfSeriesRelatedInstances": 50
authenticated
"authenticated": false