Skip to content
This repository has been archived by the owner on Feb 22, 2020. It is now read-only.

Inspect a DICOM directory and create appropriate model instances #39

Closed
2 tasks
isms opened this issue Aug 4, 2017 · 0 comments
Closed
2 tasks

Inspect a DICOM directory and create appropriate model instances #39

isms opened this issue Aug 4, 2017 · 0 comments

Comments

@isms
Copy link
Contributor

isms commented Aug 4, 2017

Overview

The interface backend has some model stubs for tracking metadata about DICOM imagery. The Case model tracks a radiologist's workflow examining an image series, so it's the heart of this application. But the Case has foreign keys to the ImageSeries model, which needs to know about the data.

Expected Behavior

We should be able to pass a directory URI to this method (helpful ref here) and expect that an ImageSeries object should be created if necessary, with metadata fields filled in.

Technical details

  • The DICOM standard may be helpful here
  • The pydicom library is excellent and probably what we want to use
  • This should likely live in the ImageSeries class, possibly as a classmethod; this could be like:
    uri = 'file:///path/to/project/tests/assets/LIDC-IDRI-0001/1.3.6.1.4.1.14519.5.2.1.6279.6001.298806137288633453246975630178/1.3.6.1.4.1.14519.5.2.1.6279.6001.179049373636438705059720603192'
    ImageSeries.get_or_create(uri)

Out of scope

  • Adding new fields to the models (let's get the ones we have working first)
  • Using or storing the array data; an issue already exists to pull in the DICOM image's numerical array (Add function that loads DICOM images #12) for the prediction service, but that doesn't have anything to do with our DB models on the interface side of the house.

Acceptance criteria

  • Working implementation of the method described above
  • Tests added

NOTE: All PRs must follow the standard PR checklist.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant