-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add search_series and search_study #10
Comments
@dillonwilliams these APIs will be needed by the autoregister project. |
@orwonthe FYI this ticket is for autoregister. |
What fields would the |
I see. My intention was to just pass in the search dataset directly. I think this will actually be trivial. In the case of pynetdicom: def search_series(self, query_dataset, additional_tags=None):
query_dataset.QueryRetrieveLevel = 'SERIES'
return assoc.send_c_find(query_dataset, query_model='S')
def search_study(self, query_dataset, additional_tags=None):
query_dataset.QueryRetrieveLevel = 'STUDY'
return assoc.send_c_find(query_dataset, query_model='S') |
@yujanshrestha in this example code, where do we use |
We can probably remove it entirely. I think the convention is add the attributes into The implementation for this should be trivial, writing tests for it may be a bit more involved. |
It looks like we can get rid of the |
In an identical api to
search_patients
, provide APIs for Study and Series level queries.At each level, also return the additional query / retrieve attributes as found here. http://dicom.nema.org/medical/dicom/2017c/output/chtml/part04/sect_C.3.4.html
For example, for the
search_study
query return theNumber of Study Related Series
and for thesearch_series
return theNumber of Series Related Instances
The text was updated successfully, but these errors were encountered: