Skip to main content

Configuring your Image Data Source

Updated

FlexView allows you to configure one or many sources for DICOM images; however, only one data source can be set as default. You may choose to load for a cloud location or from a local source.

 

  1. To add a datasource, go to the settings tab and choose Add Data Source.
  2. Choose the type of data source you will be connecting.

If you wish to connected other data sources or PACS, please contact support for assistance.

 

DICOMweb or Static WADO Configuration

When you choose to add a DICOMweb data source, you will see an expanded configuration panel. You can find the details of your data source in your PACS. If you do not have a PACS, you can follow this tutorial to setup Orthanc locally.

  • Display name - This is just a short name to be shown on your data source list.
  • Source name - This field is used to differentiate the data source and will be part of the url when reading exams. Default is "flexview". Edit this field only if you have multiple data sources.
  • DICOMweb Root - Enter the URL for your Static WADO source root locations.
  • Authentication - Choose the type of authentication for your data source. Choices are Unauthenticated (data source is public), JWT, or FlexView (used if your data source is provided/hosted by FlexView). Default is Unauthenticated.
  • Advanced Options
    • Image Rendering- You only need to change this if you have custom rendering in the implementation. Choose wadors or curie. Default is wadors.
    • Thumbnail Rendering- You only need to change this if you have custom rendering in the implementation. Choose wadors or curie. Default is wadors.
    • Viewer Behaviors
      • Supports Wildcards - check if your DICOM supports "*" as wildcard search
      • Fuzzy matching - If the DICOMweb back end supports fuzzy matching, such as for using ae instead of æ (or vice versa), or sound based matching (such as matching "egcellent" instead of "excellent") then you can check this option. Note that fuzzy matching may result in many more matches, and slower matching times.
      • Study lazy load - If checked (true), then images load only when required. Images may take render more slowly in a stack, but will use less network bandwidth and less memory.    By default this is unchecked (false), which allows all images to load in advance. The results is that images may read more quickly, but will use more memory and network.
      • Supports Writing SR - Check this box if your datasource is configured to allows SRs to be saved (a configured STOW endpoint).
    • Supported Singe Part Types - Some type of objects can only be displayed using a simple retrieve mechanism, instead of the more complex multipart/related retrieve often used in DICOMweb.  Check the boxes for the DICOMweb types that can be retrieved in your datasource.
      • Video - The rendered endpoint will be used for displaying video directly.  Large video instances cannot be displayed using the non single part endpoints, or may be very slow.

      • PDF - the rendered endpoint will be used for displaying PDF directly. 

      • Image/HTJ2K - Some back ends can return High Throughput JPEG 2000 images more quickly as single part than as multi-part, or may only retrieve as single part.

 

AWS HealthImaging Configuration

  • Display name - This is just a short name to be shown on your data source list.
  • Source name - This field is used to differentiate the data source and will be part of the URL when reading exams. Default is "flexview". You will want to edit this field only if you have multiple data sources.
  • Data Store ID - This is the unique number provided in AWS HealthImaging portal.
  • AWS Access Key ID -This can be found in the Security credentials menu on the AWS HealthImaging portal.
  • AWS Access Key Secret - This is the secret associated to the above Access Key ID and can be found in the Security credentials menu on the AWS HealthImaging portal.
  • Advanced Configuration (optional)
    • Endpoint (URL) - This is the AWS API or proxy URL provided in the AWS HealthImaging portal.
    • Query JSON - URL of the JSON file or service associated with AWS HealthImaging to return exam list.
    • ImageSet Cap per Study - This sets the max number of images sets retrieved from AHI in a single call. By default this is set to 300 to prevent triggering additional calls API calls to AHI that could impact study list loading time when datasets include a very large studies.
  • Supported Singe Part Types - Some type of objects can only be displayed using a simple retrieve mechanism, instead of the more complex multipart/related retrieve often used in DICOMweb. 
      • Bulkdata -
      • Video - The rendered endpoint will be used for displaying video directly.  Large video instances cannot be displayed using the non single part endpoints, or may be very slow.
      • PDF - the rendered endpoint will be used for displaying PDF directly. 
      • Image/jphc - Some back ends can return High Throughput JPEG 2000 images more quickly as single part than as multi-part, or may only retrieve as single part.

More information about AWS HealthImaging can be found on the Amazon website: https://aws.amazon.com/ healthimaging/

 

Google Cloud Healthcare

When you choose to add a Google Cloud Healthcare data source, you will see an expanded configuration panel. You can find the details of your data source in Google Cloud Healthcare account. You can view a short video on configuring your Google Heathcare account on our YouTube Channel.

  • Display name - This is just a short name to be shown on your data source list.
  • Source name - This field is used to differentiate the data source and will be part of the url when reading exams. Default is "flexview". Edit this field only if you have multiple data sources.
  • Datasoure Path - Copy the datasource path from your Google Account. You will be asked to sign-in with your Google ID when opening the viewer.
    •  
  • Supported Singe Part Types - Some type of objects can only be displayed using a simple retrieve mechanism, instead of the more complex multipart/related retrieve often used in DICOMweb.  Check the boxes for the DICOMweb types that can be retrieved in your datasource.
      • Video - The rendered endpoint will be used for displaying video directly.  Large video instances cannot be displayed using the non single part endpoints, or may be very slow.

      • PDF - the rendered endpoint will be used for displaying PDF directly. 

      • Image/HTJ2K - Some back ends can return High Throughput JPEG 2000 images more quickly as single part than as multi-part, or may only retrieve as single part.

 

Microsoft Azure DICOMweb

When you choose to add a Microsoft Azure data source, you will see an expanded configuration panel. You can find the details of your data source in Microsoft Azure account.

  • Display name - This is just a short name to be shown on your data source list.
  • Source name - This field is used to differentiate the data source and will be part of the url when reading exams. Default is "flexview". Edit this field only if you have multiple data sources.
  • Datasource Path - Add your DICOM service URL that you generated in your Azure account, followed by a /v2
  • Authority URL- This is usually https://login.microsoftonline.com/YourDirectory (tenant)ID/v2.0/
  • Client ID - This will be found in your app registration in the Azure dashboard. The format will look something like: 1231234-1234-abcd-1234-abcd12314
  • Supported Singe Part Types - Some type of objects can only be displayed using a simple retrieve mechanism, instead of the more complex multipart/related retrieve often used in DICOMweb.  Check the boxes for the DICOMweb types that can be retrieved in your datasource.
    • Video - The rendered endpoint will be used for displaying video directly.  Large video instances cannot be displayed using the non single part endpoints, or may be very slow.

    • PDF - the rendered endpoint will be used for displaying PDF directly. 

    • Image/HTJ2K - Some back ends can return High Throughput JPEG 2000 images more quickly as single part than as multi-part, or may only retrieve as single part.

If you have questions about setting up your Azure account and permissions, please contact our support team.

 

Local File Source

You may choose to load studies from your local file system.

1. Go to the setting page.

2. Check the box in Local DICOM section.

3. Save and return to the study page.

4. In the upper right, corner you will see a link to Load.

When you click this link it will open a dialog box to either drag or select the files or folders containing your images.

 

 

 

Related articles