Skip to main content
QMSQMS
QMS
  • Welcome to your QMS
  • Quality Manual
  • Procedures
  • Records
  • TF_Legit.Health_Plus
    • Legit.Health Plus TF index
    • Legit.Health Plus STED
    • Legit.Health Plus description and specifications
    • R-TF-001-007 Declaration of conformity
    • GSPR
    • Clinical
    • Design and development
    • Design History File (DHF)
      • Version 1.1.0.0
        • Requirements
        • Test plans
        • Test runs
        • Review meetings
        • 🥣 SOUPs
          • Albumentations
          • Authlib
          • AWS DocumentDB
          • AWS S3
          • Bcrypt
          • Boto3
          • CPython
          • FastAPI
          • Numpy
          • OpenCV Python
          • Pandas
          • Pillow
          • Pydantic
          • PyMongo
          • Python Benedict
          • PyTorch
          • Requests
          • Ultralytics
          • Uvicorn
    • IFU and label
    • Post-Market Surveillance
    • Quality control
    • Risk Management
  • Licenses and accreditations
  • External documentation
  • TF_Legit.Health_Plus
  • Design History File (DHF)
  • Version 1.1.0.0
  • 🥣 SOUPs
  • Python Benedict

Python Benedict

Description​

Python-benedict is a powerful enhancement of the standard Python dictionary that introduces additional functionality to simplify and enhance data manipulation and processing tasks. This library is especially useful for developers working with data transformation, as it provides extended methods for keypath support, merge, update, search, and more. With python-benedict, navigating and manipulating nested dictionaries becomes more intuitive and efficient, making it a valuable tool for any task that involves complex data structures.

General details​

  • Developer(s): Fabio Caccamo
  • Open source: Yes
  • Language(s): Python
  • Repository: https://github.com/fabiocaccamo/python-benedict
  • License: MIT
  • Operating system(s): OS Independent (can run on any operating system that supports Python)
  • Actively maintained: Yes (within the past week)

Intended use on the device​

The SOUP is used in the medical device for the following specific purposes only:

  • Backend of the builders that assemble the preliminary reports returned by the device. Its data structure, which inherits from the Python dictionary, facilitates state management within the application and offers a convenient way to gather the generated results.

Requirements​

For the integration and safe usage of this SOUP within a software system, it's important to outline both functional and performance requirements. These requirements help mitigate risks and ensure compatibility and performance standards are met.

Functional​

  • Data manipulation: Provide comprehensive tools for manipulating dictionary objects, including but not limited to merging, updating, and searching within nested structures.
  • Keypath support: Allow accessing and setting values in nested dictionaries using a keypath string, simplifying operations on deep data structures.
  • Serialisation and deserialisation: Support serialisation and deserialisation features for various formats (e.g., JSON, YAML, XML) to easily convert between dictionary objects and string representations.
  • Data validation: While not primarily a validation tool, it should facilitate basic data integrity checks as part of the manipulation features.

Performance​

  • Efficiency: Handle large and deeply nested dictionary objects efficiently, without significant performance degradation.
  • Speed: Critical operations such as search, merge, and keypath navigation must be optimised for speed to support high-performance requirements.

System requirements​

Establishing minimum software and hardware requirements is important to mitigate risks, such as security vulnerabilities, performance issues, or compatibility problems, and to ensure that the SOUP functions effectively within the intended environment.

Software​

After evaluation, we find that there are no specific software requirements for this SOUP. It works properly on standard computing devices, which includes our environment.

Hardware​

After evaluation, we find that there are no specific hardware requirements for this SOUP. It works properly on standard computing devices, which includes our environment.

Documentation​

This SOUP does not have a dedicated website to host the library documentation. The README file available in its code repository provides instructions for installation and a comprehensive user's guide.

Additionally, a criterion for validating the SOUP is that all the items of the following checklist are satisfied:

  • The vendor maintains clear and comprehensive documentation of the SOUP describing its functional capabilities, user guidelines, and tutorials, which facilitates learning and rapid adoption.
  • The documentation for the SOUP is regularly updated and clearly outlines every feature utilized by the medical device, doing so for all integrated versions of the SOUP.

Related software items​

We catalog the interconnections between the microservices within our software architecture and the specific versions of the SOUP they utilise. This mapping ensures clarity and traceability, facilitating both the understanding of the system's dependencies and the management of SOUP components.

Although the title of the section mentions software items, the relationship with SOUP versions has been established with microservices (also considered software items, by the way) because each one is inside a different Docker container and, therefore, has its own isolated runtime environment.

SOUP versionSoftware item(s)
0.33.2REPORT BUILDER

Related risks​

The following are risks applicable to this SOUP from the table found in document R-TF-013-002 Risk management record_2023_001:

  • 58. SOUP presents an anomaly that makes it incompatible with other SOUPs or with software elements of the device.
  • 59. SOUP is not being maintained nor regularly patched.
  • 60. SOUP presents cybersecurity vulnerabilities.

Lists of published anomalies​

The incidents, anomalies, known issues or changes between versions for this SOUP can be found at:

  • Python Benedict Changelog
  • Python Benedict Release Notes
  • Python Benedict Issue Tracker

History of evaluation of SOUP anomalies​

01 Mar 2024​

  • Reviewer of the anomalies: Alejandro Carmena Magro
  • Version(s) of the SOUP reviewed: 0.33.2

No anomalies have been found.

Record signature meaning​

  • Author: JD-004
  • Reviewer: JD-003
  • Approver: JD-005
Previous
PyMongo
Next
PyTorch
  • Description
  • General details
  • Intended use on the device
  • Requirements
    • Functional
    • Performance
  • System requirements
    • Software
    • Hardware
  • Documentation
  • Related software items
  • Related risks
  • Lists of published anomalies
  • History of evaluation of SOUP anomalies
    • 01 Mar 2024
  • Record signature meaning
All the information contained in this QMS is confidential. The recipient agrees not to transmit or reproduce the information, neither by himself nor by third parties, through whichever means, without obtaining the prior written permission of Legit.Health (AI LABS GROUP S.L.)