MRI/DICOM export and assisted review is a core Spine Harmony workflow. It helps users convert their own imaging files into high-resolution review images, organize those images with the rest of their spine-health materials, and prepare better questions for qualified clinicians.
Depending on the local tools available, the workflow may:
Spine Harmony includes a reference DICOM export utility at:
tools/dicom-export/dicom_export.py
From the repository root:
python -m pip install -r tools/dicom-export/requirements.txt
Equivalent manual install:
python -m pip install pydicom pillow numpy
Use a folder outside version control, for example:
/private/path/to/my-dicom-study/
Do not place real DICOM files inside this public repository. DICOM metadata may contain personal medical information.
python tools/dicom-export/dicom_export.py /private/path/to/my-dicom-study /private/path/to/spine-harmony-exports
The tool recursively scans the input folder, reads DICOM files, applies DICOM rescale/windowing where available, and writes PNG files grouped by series. It does not downsample source pixel data.
Example output:
/private/path/to/spine-harmony-exports/
├── series-001_T2_SAG/
│ ├── series-001_instance-0001_T2_SAG.png
│ ├── series-001_instance-0002_T2_SAG.png
│ └── ...
├── series-002_T1_AXIAL/
│ └── ...
└── export_manifest.csv
python tools/dicom-export/dicom_export.py /private/path/to/my-dicom-study /private/path/to/spine-harmony-exports --contact-sheet
This also creates:
contact_sheet.jpg
Use contact sheets for fast orientation and consultation preparation. Do not treat contact sheets as diagnostic images.
A safe prompt pattern is:
These are converted review images from my own MRI study. Please help me organize what questions to ask my clinician. Do not diagnose, do not provide treatment advice, and clearly separate visual observations from clinical interpretation.
A good Spine Harmony response should use language such as:
The model appears to notice...
This may be worth asking your clinician about...
This should be checked against the formal radiology report...
It should avoid language such as:
The MRI proves...
You have...
You need...
If no images are exported:
If images look inverted or too dark/bright:
The workflow must not claim to provide:
The image-review text is generated by the user’s chosen LLM or vision model/runtime. Spine Harmony does not validate, certify, control, or guarantee that model. Outputs may be wrong, incomplete, overconfident, misleading, or inconsistent with the actual imaging and clinical record.
Use model-generated image observations only as a prompt for further questions and clinician discussion. Do not use them instead of radiologist reporting, clinician interpretation, diagnosis, treatment planning, validated measurement, or emergency care. Do not describe the workflow as safe, validated, clinically reliable, regulator-approved, or suitable for unsupervised medical use.
DICOM files often contain personal information in metadata, including patient name, internal identifiers, study date, institution, study/reference numbers, and device/site details. Some images may contain burned-in annotations.
Treat all of the following as sensitive medical data:
Do not commit real imaging files or derived outputs to a public repository. Use synthetic or properly de-identified public test data only.
Use cautious phrasing such as:
“The model appears to notice…”
“This could be a question to ask your clinician…”
“This should be checked against the formal radiology report and a qualified clinician’s interpretation.”
Avoid phrasing such as:
“The MRI shows…”
“You have…”
“This means you need…”