Skip to main content
QMSQMS
QMS
  • Welcome to your QMS
  • Quality Manual
  • Procedures
  • Records
    • GP-001 Documents and records control
    • GP-002 Quality planning
    • GP-003 Audits
    • GP-004 Vigilance system
    • GP-005 HR and training
    • GP-007 Post-market surveillance
    • GP-009 Sales
    • GP-010 Suppliers
    • GP-012 Design, Redesign and Development
    • GP-018 Infrastructure and facilities
    • GP-019 Software validation
      • Deprecated
        • R-019-001_Software validation report 22_001 AppFire
      • R-019-001 Software validation report_Atlassian_2023
      • R-019-001 Software validation report_HubSpot_2024
      • R-019-001 Software validation report_GitHub_GPG key signature_2024
      • R-019-001 Software validation report_Atlassian_2024
      • R-019-001 Software validation report_CVAT_2024
      • R-019-001 Software validation report_Docker_2024
      • R-019-002 External software list
    • GP-023 Change control management
    • GP-050 Data Protection
    • GP-051 Security violations
    • GP-052 Data Privacy Impact Assessment (DPIA)
    • GP-200 Remote Data Acquisition in Clinical Investigations
  • TF_Legit.Health_Plus
  • Licenses and accreditations
  • External documentation
  • Records
  • GP-019 Software validation
  • Deprecated
  • R-019-001_Software validation report 22_001 AppFire

R-019-001_Software validation report 22_001 AppFire

NameClassificationProvider companyDeveloper company
AppfireElectronic signatureAppfire Technologies, LLCAppfire Technologies, LLC

Expected use​

This software will be used to electronically sign QMS documentation.

Objective​

This procedure has an objective to validate the software in accordance with its expected use.

Methodology​

Initially, the software is validated with a general procedure; all applications will be subjected to this generic procedure. Then, depending on its type, the software will be subjected, or not, to additional tests detailed below:

  1. Executable file in path.
  2. Software execution.
  3. Absence of error messages.
  4. Operating system stability.

Acceptance criteria​

The acceptance criteria for each identified test is described below. If the results are not exactly the same as the ones defined in the acceptance criteria, the validation will be rejected:

  1. Not applicable, it is a cloud-based application.
  2. The software runs satisfactory. The application can be integrated in the QMS system.
  3. Absence of error messages. Error messages do not appear nor it does not harm other programs in execution.
  4. No color changes in the monitor, no unjustified or unusual delays or any other hardware or software error associated with the start of the program. The computer does not slow down.

Verification matrix​

TestPassedObservations
Sotware executionYes
Opening the application in several browsersYes
Creating and editing a documentYes
Saving a documentYes
Signing a documentYes
Registering signature dateYes

Validation history​

ResponsibleDatePassed
Taig Mac Carthy15/10/2022Yes
Written byReviewed byApproved by

E-Signature (Appfire integration):

Signature logo

Taig Mac Carthy

6759627FEFF4185E59808AEA1237659D

Signer name: Taig Mac Carthy

Signing time: Wed, 12 Oct 2022 13:56:15 GMT

Reason: Creation of document

E-Signature (Appfire integration):

Signature logo

Alfonso Medela

23728E51DB3B53136F3F4C4F1E0F331D

Signer name: Alfonso Medela

Signing time: Fri, 14 Oct 2022 14:08:37 GMT

Reason: Reviewed

E-Signature (Appfire integration):

Signature logo

Andy Aguilar

ED6F6C3CAA00A1C2CF2E06B9D0ADF5DC

Signer name: Andy Aguilar

Signing time: Sat, 15 Oct 2022 14:07:45 GMT

Reason: Approving document

Quality manager (QM)Technical manager (PRRC)General manager (GM)
Previous
GP-019 Software validation
Next
R-019-001 Software validation report_Atlassian_2023
  • Expected use
  • Objective
  • Methodology
  • Acceptance criteria
  • Verification matrix
  • Validation history
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.)