Dicomweb-client

Latest version: v0.59.0

Safety actively analyzes 628969 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 8

0.54.1

Bug fixes

- Fix deletion of instances


Enhancements

- Update API documentation

0.54.0

New features

* Implement `DICOMfileClient` class for serverless access to locally stored DICOM files (56)
* Specify `DICOMClient` protocol, which is implemented by `DICOMfileClient` and `DICOMwebClient`

0.53.0

Bug fixes

* Fix example in usage section of document (51)
* Fix search for instances within a given study

Improvements

* Introduce `permissive` parameter to allow URIs that are not compliant with the standard (49)

New features

* Add `ext` subpackage to support vendor-specific extensions (49)
* Add extension for Google Healthcare API (49)

0.52.0

New features

- New module `dicomweb_client.uri` for creating and parsing DICOMweb URIs (48)

0.51.0

Improvements

* Allow single-part response message from origin server for the Retrieve Instance transaction. It is debatable whether this behaviour is compliant with the standard. Part 18 originally specified that an instance should be retrieved using content type `multipart/related; type="application/dicom"`, but Supplement 183 changed the wording of the standard and explicitly stated that `application/dicom` shall be used. This change in behavior was unintentional and [Correction Proposal 2040](https://www.dicomstandard.org/news-dir/current/docs/cpack108/cp2040.pdf) aims to correct this. However, since this behavior is allowed according to the current version of standard, we decided to support it.

0.50.4

Improvements

* Log additional information during decoding of multipart messages
* Apply stricter flake8 rules for improved PEP8 compliance

Page 3 of 8

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.