This is the home of the Pydicom documentation. If you are a Python developer looking to get started with Dicom and Python, this will be the place to learn and contribute! For now, here are some helpful links, and general plan for some of the code bases in the organization.
- pydicom: The best software in python I've found to work with dicom (datasets) is pydicom. There is substantial documentation if you want to get started.
- pynetdicom3: is where you want to start if you want to create Service Class Providers (SCPs) or Service Class Users (SCUs). These are the little servers/processes that echo/store/move/find dicom datasets around. This is the bread and butter of the protocol, and is based on the original pynetdicom. We will hopefully consolidate these two so that it is less confusing.
We will be developing different dicom applications that are container-based. This means using Docker and Singularity to easily deploy servers (more suited for Docker), and general tools and applications (Singularity is more suited for tools on shared resources).
Singularity Dicom This will be a "quick start" image that you can build to easily start using some basic tools for working with dicom files. Currently, the image just installs the Dicom ToolKit.
As a new person to Dicom, I found it hard to find and programatically download a quick (and maybe fun?) Dicom dataset. Toward this goal, I created a statically served Dicom Cookies dataset. The human readable entrypoint is here, and you can see it being used programatically here.
I (@vsoch) will be creating a set of web application (Dockerized) to be deployed in different cloudy places to work with Dicom. I'm new to most of this, so will take some time to learn of course. You can expect this README to be replaced with a more suitable site soon!
If you are interested in medical imaging, python, or dicom, please join the organization!
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent