0.55.1

Bug fixes

• Correctly handle acceptable media types (#63)

0.55.0

New features

• Add get_remaining parameter to search methods to recursively fetch remaining search results (#60)

0.54.4

Bug fixes

• Fix opening of files in file client
• Fix retrieval of studies in file client

0.54.3

Bug fixes

• Fix import of typing extension for Python versions < 3.8 (#59)

v0.54.2

Bug fixes

• Fix insertion of instances into database

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 aims to correct this. However, since this behavior is allowed according to the current version of standard, we decided to support it.