Skip to main content

Python - DICOM Modality WorkList

Project description

Pylantir

Pylantir

This project's goal is to significantly reduce the number of human-related errors when manualy registering participants for medical imaging procedures.

It effectively provides a python based DICOM Modality Worklist Server (SCP) and Modality Performed Procedure Step (SCP) able to receive requests from medical imaging equipemnt based on DICOM network comunication (e.g., a C-FIND, N-CREATE, N-SET requests).

It will build/update a database based on the information entered in the study-related REDCap database using a REDCap API (You will require to have API access to the study).

Getting Started

To get started simply install using:

pip install pylantir

Start a server called with AEtitle MWL_SERVER.

pylantir start --ip 127.0.0.1 --port 4242 --AEtitle MWL_SERVER

Tests

Once your modality worklist server is running you can test it running the following:

Query the worklist database to check that you have some entries using:

pylantir query-db

Then, you can get a StudyUID from one of the entries to test the MPPS workflow. For example: 1.2.840.10008.3.1.2.3.4.55635351412689303463019139483773956632

Take this and run a create action to mark the worklist Procedure Step Status as IN_PROGRESS

pylantir test-mpps --AEtitle MWL_SERVER --mpps_action create --callingAEtitle MWL_TESTER --ip 127.0.0.1 --port 4242 --study_uid 1.2.840.10008.3.1.2.3.4.55635351412689303463019139483773956632

You can verify that this in fact modified your database re-running:

pylantir query-db

Finally, you can also simulate the pocedure completion efectively updating the Procedure Step Status to COMPLETED or DISCONTINUED:

pylantir test-mpps --AEtitle MWL_SERVER --mpps_action set --mpps_status COMPLETED --callingAEtitle MWL_TESTER --ip 127.0.0.1 --port 4242 --study_uid 1.2.840.10008.3.1.2.3.4.55635351412689303463019139483773956632 --sop_uid 1.2.840.10008.3.1.2.3.4.187176383255263644225774937658729238426

Usage

usage: pylantir [-h] [--AEtitle AETITLE] [--ip IP] [--port PORT] [--pylantir_config PYLANTIR_CONFIG] [--mpps_action {create,set}] [--mpps_status {COMPLETED,DISCONTINUED}] [--callingAEtitle CALLINGAETITLE] [--study_uid STUDY_UID] [--sop_uid SOP_UID] {start,query-db,test-client,test-mpps}

pylantir - Python DICOM Modality WorkList and Modality Performed Procedure Step compliance

Positional Arguments:

  • {start,query-db,test-client,test-mpps}: Command to run:
    • start: Start the MWL server
    • query-db: Query the MWL database
    • test-client: Run tests for MWL
    • test-mpps: Run tests for MPPS

Options:

  • -h, --help: Show this help message and exit
  • --AEtitle AETITLE: AE Title for the server
  • --ip IP: IP/host address for the server
  • --port PORT: Port for the server
  • --pylantir_config PYLANTIR_CONFIG: Path to the configuration JSON file containing pylantir configs:
    • allowed_aet: List of allowed AE titles e.g. ["MRI_SCANNER", "MRI_SCANNER_2"]
    • mri_visit_session_mapping: Mapping of MRI visit to session e.g., {"T1": "1", "T2": "2"}
    • site: Site ID:string
    • protocol: {"site": "protocol_name"}
    • redcap2wl: Dictionary of REDCap fields to worklist fields mapping e.g., {"redcap_field": "worklist_field"}
  • --mpps_action {create,set}: Action to perform for MPPS either create or set
  • --mpps_status {COMPLETED,DISCONTINUED}: Status to set for MPPS either COMPLETED or DISCONTINUED
  • --callingAEtitle CALLINGAETITLE: Calling AE Title for MPPS, it helps when the MWL is limited to only accept certain AE titles
  • --study_uid STUDY_UID: StudyInstanceUID to test MPPS
  • --sop_uid SOP_UID: SOPInstanceUID to test MPPS

Configuration JSON file

As a default pylantir will try to read a JSON structured file with the following structure:

{
  "db_path": "/path/to/worklist.db",
  "db_echo": "False",
  "db_update_interval": 60,
  "allowed_aet": [],
  "mri_visit_session_mapping": {
    "t1_arm_1": "1",
    "t2_arm_1": "2",
    "t3_arm_1": "3"
  },
  "site": "792",
  "redcap2wl": {
    "study_id": "study_id",
    "family_id": "family_id",
    "youth_dob_y": "youth_dob_y",
    "t1_date": "t1_date",
    "demo_sex": "demo_sex",
    "scheduled_date": "scheduled_start_date",
    "scheduled_time": "scheduled_start_time",
    "mri_wt_lbs": "patient_weight_lb",
    "referring_physician": "referring_physician_name",
    "performing_physician": "performing_physician",
    "station_name": "station_name",
    "status": "performed_procedure_step_status"
  },
  "protocol": {
    "792": "BRAIN_MRI_3T"
  }
}

Clean Stop of the MWL and Database Sync

To cleanly stop the MWL server and ensure the database syncronization properly, press Ctrl + C (you might need to press it twice).

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

pylantir-0.0.3.tar.gz (16.7 kB view details)

Uploaded Source

Built Distribution

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

pylantir-0.0.3-py3-none-any.whl (16.0 kB view details)

Uploaded Python 3

File details

Details for the file pylantir-0.0.3.tar.gz.

File metadata

  • Download URL: pylantir-0.0.3.tar.gz
  • Upload date:
  • Size: 16.7 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.1.0 CPython/3.11.9

File hashes

Hashes for pylantir-0.0.3.tar.gz
Algorithm Hash digest
SHA256 d748a74c17359b2ff8ece543f57a012b51901e16339f1932b3cdbab5c3662658
MD5 10df2c0fca9083dc47a59a3a3066ebbe
BLAKE2b-256 373b2909a71bda0095195a15069dd8630993bb832eba3edc38e12bc3f68b3d77

See more details on using hashes here.

File details

Details for the file pylantir-0.0.3-py3-none-any.whl.

File metadata

  • Download URL: pylantir-0.0.3-py3-none-any.whl
  • Upload date:
  • Size: 16.0 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.1.0 CPython/3.11.9

File hashes

Hashes for pylantir-0.0.3-py3-none-any.whl
Algorithm Hash digest
SHA256 a0b940071bdf65d3089a90aa15659db084119403889821e3828d74d200ffb373
MD5 f90acf178d1b1db8c2235f66c37c6d08
BLAKE2b-256 715bae82d3ec0e9f2988fb0a6432de6e9c40ba6a54a35175f187591489bc0e74

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