Skip to main content

Concepts and relations to describe the process of DICOM deidentification

Project description

MIDOM - Medical Image Deidentification Object Model

A set of concepts and relations to describe the process of DICOM deidentification and a structured format for a deidentification protocol.

Why?

For projects related to DICOM deidentification, I'm running into the problem of not having the right words. I keep inventing terms, coming up with long-winded descriptions There is a lack of conceptual clarity. Lack of clarity causes:

  • misunderstandings
  • Ineffective communication
  • misguided programming efforts
  • wasted time generally.

The DICOM standard does not have enough detail. DICOM PS3 E-E1 gives thorough information on what to do to a single dataset, but not on how to reason or talk about multiple deidentifying processess, their differences, their characteristics.

For whom?

People developing or maintaining image deidentification pipelines.

What is it?

An information model first and foremost. Concept definitions with clear descriptions of their relations. There might be python code to define constants, transformations between objects maybe.

What is it not?

Anything that does any actual image processing. No loading of DICOM files anywhere.

For docs editors

Render html docs

Go to (in docs/build): make docs_html

Fancy auto-updating

Auto-reload a html view as you change the docs source. Requirements:

  • Linux or WSL (this uses some subshell and piping tricks)
  • entr - Run a command when files change. Apt install this
  • livereload - Serve local files and auto-reload on change. Python lib found as dev dependency in midom.
  • Possibly firefox to make livereload work properly

Steps:

  • Start a shell in this midom base dir (where Makefile is)
  • run uv run make launch_source_listener
  • Open the livereload url printed in the script output. By default this is http://127.0.0.1:35729/

You might have to reload the page once to link livereload to the browser. After that, any save to a .rst or .puml file will trigger rebuild of docs/build, which will in turn trigger a page reload

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

midom-0.1.0.tar.gz (30.5 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

midom-0.1.0-py3-none-any.whl (26.6 kB view details)

Uploaded Python 3

File details

Details for the file midom-0.1.0.tar.gz.

File metadata

  • Download URL: midom-0.1.0.tar.gz
  • Upload date:
  • Size: 30.5 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: uv/0.6.9

File hashes

Hashes for midom-0.1.0.tar.gz
Algorithm Hash digest
SHA256 538d6cf96af935506d07777fe01a7d6b520c04533d64211feecf4b2c43e775cf
MD5 f3046f4f4280d9c3da4ad92362c0c939
BLAKE2b-256 0d65a3d19846fa80bd04e782bb23086a719898e422563f3d9fa697182a07ea69

See more details on using hashes here.

File details

Details for the file midom-0.1.0-py3-none-any.whl.

File metadata

  • Download URL: midom-0.1.0-py3-none-any.whl
  • Upload date:
  • Size: 26.6 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: uv/0.6.9

File hashes

Hashes for midom-0.1.0-py3-none-any.whl
Algorithm Hash digest
SHA256 2334db3b35f62dc0c3e0afd67dd6d7d83859a3e8441a0c02e39b3ada8afdca53
MD5 c4556d05b58c19c0cbd4c7a70d11c7b2
BLAKE2b-256 39978f1c3da29d0694cee05efbb8384dae2f3888f9f2d5820417823a47b2e965

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page