godicom-devDICOM for Go

Read, modify and write DICOM datasets, decode and encode Pixel Data, talk DIMSE and DICOMweb — from idiomatic Go, with no CGO for callers.

Getting started

Browse the modules

GitHub

godicom

The dataset library — Part 10 files, transfer syntaxes, the data dictionary, Pixel Data, DICOM JSON, and a CLI. Everything else in the organisation builds on it.

Datasets, diagnostics, Pixel Data

gonetdicom

DICOM networking — association negotiation, DIMSE-C and DIMSE-N as SCU or SCP, TLS, and a DICOMweb client with an origin-server MVP.

DIMSE and DICOMweb

goopenjpeg

JPEG 2000 and HTJ2K, decode and encode. purego plus embedded prebuilt OpenJPEG and OpenJPH — no CMake, no CGO for callers.

JPEG 2000 / HTJ2K

golibjpeg

Baseline and lossless JPEG, JPEG-LS, JPEG XT decode; JPEG and JPEG-LS encode. Same purego architecture, native 8- and 16-bit precision.

JPEG / JPEG-LS

gorle

DICOM RLE Lossless, pure Go. Frame and pixel-data APIs, PackBits helpers for 1-bit images, and a low-level segment API.

RLE Lossless

Checked against pydicom

Each module is aligned with a Python counterpart — pydicom, pynetdicom, pylibjpeg-openjpeg, pylibjpeg-libjpeg, pylibjpeg-rle — and tested against its behaviour, not just against itself.

How the pieces fit

Read a file, change it, write it back

package main

import (
	"log"

	"github.com/godicom-dev/godicom"
	"github.com/godicom-dev/godicom/tag"
)

func main() {
	ds, err := godicom.ReadFile("ct.dcm", nil)
	if err != nil {
		log.Fatal(err)
	}
	if err := ds.SetString(tag.PatientID, "12345678"); err != nil {
		log.Fatal(err)
	}
	if err := ds.SaveAs("ct_updated.dcm", nil); err != nil {
		log.Fatal(err)
	}
}

bash

go get github.com/godicom-dev/godicom@latest

Where to go next

Getting started — install, read your first file, and find out what a malformed one is hiding.
The ecosystem — which module owns what, and which one pulls in which.
godicom — the dataset library in detail.
gonetdicom — if you need to move images between machines rather than parse them.

About this site

These pages are written against the released versions of each module and link to pkg.go.dev for the full API reference, which is generated from the source and therefore never out of date. Where the two disagree, pkg.go.dev is right.