Static DICOMweb Creator
A Python library and CLI tool for generating static DICOMweb endpoints from DICOM files. Create self-contained, deployable medical imaging web applications without requiring a PACS server or database.
This project was inspired by the RadicalImaging/Static-DICOMWeb (javascript, node.js).
✨ Features
- 🚀 Zero Server Requirements: Generate static files that can be served from any web server or CDN
- 🔒 Self-Contained: All DICOM metadata and images converted to web-friendly formats
- 📊 DICOMweb Compatible: Generates standard DICOMweb API endpoints (WADO-RS)
- 🌐 OHIF Viewer Ready: Works out-of-the-box with OHIF Viewer for viewing medical images
- 📦 Easy Deployment: Includes docker templates
📋 Requirements
- Python 3.9 or higher
- Frontend viewer: OHIF Viewer (recommended) or any DICOMweb-compatible viewer
🚀 Installation
From PyPI
pip install static-dicomweb-creator
Development Installation
pip install -e ".[dev]"
📖 Usage
Command Line Interface
Basic usage:
static-dicomweb-creator input_dicom_dir base_url output_web_dir
For OHIF viewer:
static-dicomweb-creator --ohif input_dicom_dir base_url output_web_dir
Python API
from static_dicomweb_creator.creator import StaticDICOMWebCreator
from static_dicomweb_creator.utils import list_dicom_files
creator = StaticDICOMWebCreator(
output_path="/path/to/web",
root_uri="https://example.com/dicomweb/"
)
for dcm_path in list_dicom_files("/path/to/dicom_files"):
dcm = pydicom.dcmread(dcm_path)
creator.add_dcm_instance(dcm)
creator.create_json()
🏗️ Architecture
Input DICOM Files
↓
Static DICOMweb Creator
↓
Generated Output:
└ studies/
├ index.json
└ {StudyInstanceUID}/
└ series/
├ index.json
└ {SeriesInstanceUID}/
├ index.json
├ metadata
│ └ index.json
└ instances/
└ {SOPInstanceUID}/
├ metadata
│ └ index.json
├ frame
│ └ {frame_number}/
│ └ index.json
└ bulkdata
└ {tag}/
└ index.json
🌐 Deployment
With Docker Compose (Recommended)
This repository includes a ready-to-use Docker Compose setup with OHIF Viewer and Nginx:
# use samle_docker/docker-compose.yml placing your generated output in static_dicomweb/
docker-compose up
Access the viewer at http://localhost
🤝 Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
- Fork the repository
- Create your feature branch (
git checkout -b feature/amazing-feature) - Commit your changes (
git commit -m 'Add some amazing feature') - Push to the branch (
git push origin feature/amazing-feature) - Open a Pull Request
📄 License
This project is licensed under the MIT License - see the LICENSE file for details.
🙏 Acknowledgments
- OHIF Viewer - Open Health Imaging Foundation
- pydicom - Python library for DICOM files
- DICOMweb - Web standard for medical imaging
Metadata
Release files for static-dicomweb-creator 0.2.11
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| static_dicomweb_creator-0.2.11.tar.gz | 11.3 kB | With provenance | Details for static_dicomweb_creator-0.2.11.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| static_dicomweb_creator-0.2.11-py3-none-any.whl | Python 3 | none | any | Details for static_dicomweb_creator-0.2.11-py3-none-any.whl |
Total release size: 23.0 kB
Release files / static_dicomweb_creator-0.2.11.tar.gz
| Download URL | static_dicomweb_creator-0.2.11.tar.gz |
|---|---|
| Size | 11.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d10004ad13a20561ac43d3439af39265bf7571771ace50287eb4efdbd56ae799
|
|
BLAKE2b-256 checksum How to use checksums |
0b28cb9b98e5f0fd4f45f20a91408171439288aac0a54bf6dc6380c1b589f1a1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 2, 2026.
Transparency logRelease files / static_dicomweb_creator-0.2.11-py3-none-any.whl
| Download URL | static_dicomweb_creator-0.2.11-py3-none-any.whl |
|---|---|
| Size | 11.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dcddfa91965a946c413f92f0eb06c6b234df3c12310b939e1c980ecd86752edf
|
|
BLAKE2b-256 checksum How to use checksums |
54de2f62d9923c710e55c49669cf48e2dd30c986903d019e37e32d4c612fa62e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 2, 2026.
Transparency logSecurity for static-dicomweb-creator 0.2.11
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for static_dicomweb_creator-0.2.11.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 2, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.