npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

dicomweb-websocket-bridge

v1.2.0

Published

Redirect dicomweb traffic over websockets to a local PACS server

Downloads

8

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

knopkemknopkem

Keywords

DICOMWEBPROXYWEBSOCKETDICOM

Readme

dicomweb-websocket-bridge

A proxy to forward dicomweb requests via websockets to a local server

Description

  • Handy light proxy to connect to DICOMWEB-PROXY via websockets to expose an internal PACS server to the public.

What is it for?

  • if you want to view image data from a legacy PACS (hosted behind firewalls) without opening up ports
  • the websocket proxy can be installed on any other hoster and will relay any DICOMWEB traffic to the PACS (via the DICOMWEB-PROXY plugin)

How does it work?

  • the app should be installed on a cloud server exposed
  • it hosts a default DICOMweb viewer (ohif) which can be replaced
  • the webserver exposes the default QIDO and WADOURI API needed for the viewer
  • to be able to work it needs a local instance of DICOMWEB-PROXY running somewhere (e.g. inside hospital)
  • the DICOMWEB-PROXY needs to be setup to point to the dicomweb-websocket-bridge (you probably will need a http/ws proxy to not expose it directly)
  • the token configured in the DICOMWEB-PROXY client needs to match the token configured in dicomweb-websocket-bridge
  • once both are running, each request will be relayed to the actual DICOMWEB-PROXY which in turn connects to the PACS to get data
  • make sure to know what you are allowed to publicly expose (!)

Setup Instructions

  • clone repository and install dependencies:
    npm install

  • update config file located in:
    ./config

  • start proxy:
    npm start

  • run an instance of DICOMWEB-PROXY somewhere that is configured to connect to this bridge

License

MIT