1.0.4 • Published 2 years ago

ct-ohif-aws-healthimaging v1.0.4

Weekly downloads
-
License
MIT
Repository
-
Last release
2 years ago

OHIF AWS HealthImaging adapter

Setting up

Prerequisites

  • Node.js +14
  • OHIF follow the Getting started guide if needed
  • Make sure you are checkout in the branch v3-stable
  • Install ct-ohif-aws-healthimaging package:
  • Create an access key in the AWS portal
  • Follow AWS documentation on how to create an AWS Health Imaging Datastore and load it with DICOM data
  • Start the proxy to secure your access keys
# AWS_HOST
docker run -p 8089:8089 -e AWS_ACCESS_KEY_ID='YOUR_KEY' -e AWS_SECRET_ACCESS_KEY='YOUR_SECRET' -e AWS_REGION='YOUR_REGION' flexview/ohif-aws-healthimaging-proxy
  • Add healthimaging as a dependency
yarn cli add-extension ct-ohif-aws-healthimaging
  • Add healthimaging adapter as an OHIF plugin platform/viewer/pluginConfig.json
  "extensions": [
    //....
    {
      "packageName": "ct-ohif-aws-healthimaging"
    }
  ],
  • Configure the data source to access healthimaging via the proxy

platform/app/public/config/default.js

  //...
  dataSources: [{
    friendlyName: 'AWS HealthImaging',
    namespace: 'ct-ohif-aws-healthimaging.dataSourcesModule.healthlake',
    sourceName: 'healthlake',
    configuration: {
      name: 'healthlake',
      healthlake: {
        datastoreID: $YOUR_DATASTORE_ID,
        endpoint: 'http://localhost:8089',// Add here the address to you proxy
		storeEndpoint: 'http://localhost:3001' // Add address to the S3 Store Proxy
      },
      singlepart: 'bulkdata,video,pdf,image/jphc',
    }
  }
  ],
  • Run OHIF
yarn start # in the OHIF platform/viewer folder
  • Opening your first exam
http://localhost:3000/viewers?StudyInstanceUIDs=$DICOMStudyUIDHere&ImageSetID=$ImageSetIDHere
## Description 
Support metadata and imaging data loading from AWS HealthImaging and storing SR (Annotations) to S3 Bucket.


## FAQ
## Why do we need the proxy server?
* You should never expose your AWS keys to the client. We created this tiny proxy with the only purpose of hiding the AWS keys in the backend.
* The Proxy server available here is meant to be for development only. In actual use cases, we encourage you to implement authentication on top of the proxy so you secure access to your data.


## Authors 
Sobhika P, Karan Rane

## License 
MIT
1.0.2

2 years ago

1.0.1

2 years ago

1.0.4

2 years ago

1.0.3

2 years ago

1.0.0

2 years ago

0.9.8

2 years ago