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
          • PLAN-001 Users submit their credentials to receive an access token
          • PLAN_002 Token expiration in user authentication process
          • PLAN_003 Account lockout for user authentication
          • PLAN_004 Enforcing HTTPS protocol for API communications
          • PLAN_005 Valid SSL/TLS certificates
          • PLAN_006 Rate limiting for anonymous users
          • PLAN_007 Rate limiting for authenticated users
          • PLAN_008 Logging and monitoring of rate limit violations
          • PLAN_009 Validation of request and response data against FHIR schemas
          • PLAN_010 Base64 encoded images are accepted
          • PLAN_011 Non-Base64 encoded images are rejected
          • PLAN_012 Diagnosis support endpoint accepts multiple images
          • PLAN_013 Improved accuracy with multiple images
          • PLAN_014: Password hashing during user registration
          • PLAN_015: Password hash comparison during login
          • PLAN_016: Registration of a new user by authorized individuals
          • PLAN_017 Specification of body zone for scoring systems requiring zone factor
          • PLAN_018 The device's API maintains an uptime of at least 99% over a one-month period
          • PLAN_019 API penetration testing with Intruder.io
        • Test runs
        • Review meetings
        • 🥣 SOUPs
    • 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
  • Test plans
  • PLAN_010 Base64 encoded images are accepted

PLAN_010 Base64 encoded images are accepted

Description​

This test verifies that the REST API can handle images encoded in Base64 format properly. It checks that the software can process these images without any data corruption and that it returns images encoded in Base64 format in its responses, also without data corruption.

System requirements​

This test can be executed with standard hardware, and it is not necessary to use any specific software. Any commonly available system should be sufficient for the task.

Preconditions​

  • The entire system (including the reverse proxy, REST API, and all upstream services) is deployed, operational, and accessible online.

Input data​

Download this sample image, convert it to Base64 and save the encoded image to clipboard or a text file. Then, replace the placeholder text <Paste-the-encoded-image-here> with the encoded image in the following JSON payloads:

  1. Request body for diagnosis support service.
{
"subject": {
"reference": "fake-patient-id"
},
"media": [
{
"contentType": "image/jpeg",
"data": <Paste-the-encoded-image-here>,
}
]
}
  1. Request body for severity assessment service.
{
"subject": {
"reference": "fake-patient-id"
},
"media": {
"contentType": "image/jpeg",
"data": <Paste-the-encoded-image-here>
},
"known_condition": {
"conclusion": {
"code": "EA80",
"display": "Atopic dermatitis",
"system_alias": "ICD-11"
}
},
"body_site": "arm_left",
"scoring_systems": [
"ascorad"
],
"questionnaire_response": [
{
"questionnaire": "ascorad",
"item": [
{"code": "surface", "answer": [{"value": 40}]},
{"code": "itchiness", "answer": [{"value": 3}]},
{"code": "sleeplessness", "answer": [{"value": 2}]},
],
},
],
}

Steps​

  1. Send a POST request to the /diagnosis-support endpoint, including the Base64 encoded image from "Input data" in the JSON payload for the diagnosis support service.
  2. Send a POST request to the /severity-assessment endpoint, including the Base64 encoded image from "Input data" in the JSON payload for the severity assessment service.

Expected outcome​

  • Both endpoints successfully handle their respective requests containing the Base64 image and generate a well-structured preliminary report.
  • The response from the /severity-assessment endpoint includes any image data in Base64 format. If everything worked correctly, you can find the image results in the response at the JSON path: patientEvolution.ascorad.media.attachments[0].data.

Verifies software requirements​

  • REQ_005

Risk control for​

    1. Data transmission failure from care provider's system
    1. Data input failure

Signature meaning

The signatures for the approval process of this document can be found in the verified commits at the repository for the QMS. As a reference, the team members who are expected to participate in this document and their roles in the approval process, as defined in Annex I Responsibility Matrix of the GP-001, are:

  • Tester: JD-017, JD-009, JD-004
  • Approver: JD-005
Previous
PLAN_009 Validation of request and response data against FHIR schemas
Next
PLAN_011 Non-Base64 encoded images are rejected
  • Description
  • System requirements
  • Preconditions
  • Input data
  • Steps
  • Expected outcome
  • Verifies software requirements
  • Risk control for
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.)