Skip to main content
QMSQMS
QMS
  • Welcome to your QMS
  • Quality Manual
  • Procedures
    • GP-001 Control of documents
    • GP-002 Quality planning
    • GP-003 Audits
    • GP-004 Vigilance system
    • GP-005 Human Resources and Training
    • GP-006 Non-conformity, Corrective and Preventive actions
    • GP-007 Post-market surveillance
    • GP-008 Product requirements
    • GP-009 Sales
    • GP-010 Purchases and suppliers evaluation
    • GP-011 Provision of service
      • Templates
        • T-011-001 Device OAuth Order
        • T-011-003 Acces Key Order
      • Deprecated
    • GP-012 Design, Redesign and Development
    • GP-013 Risk management
    • GP-014 Feedback and complaints
    • GP-015 Clinical evaluation
    • GP-016 Traceability and identification
    • GP-017 Technical assistance service
    • GP-018 Infrastructure and facilities
    • GP-019 Software validation plan
    • GP-020 QMS Data analysis
    • GP-021 Communications
    • GP-022 Document translation
    • GP-023 Change control management
    • GP-024 Cybersecurity
    • GP-025 Corporate Governance
    • GP-026 Product requirements for US market
    • GP-027 Product requirements for UK market
    • GP-028 Product requirements for the Brazilian market
    • GP-050 Data Protection
    • GP-051 Security violations
    • GP-052 Data Privacy Impact Assessment (DPIA)
    • GP-100 Business Continuity (BCP) and Disaster Recovery plans (DRP)
    • GP-101 Information security
    • GP-200 Remote Data Acquisition in Clinical Investigations
  • Records
  • TF_Legit.Health_Plus
  • Licenses and accreditations
  • External documentation
  • Procedures
  • GP-011 Provision of service
  • Templates
  • T-011-003 Acces Key Order

T-011-003 Acces Key Order

DeepLink and App keys order template​

To access to our iFrame and Deep Link integration, the business development person will send the following email:

Dear Person B,

I'd like to welcome you to our developer community on behalf of our our team. Don't hesitate to reach out if there is anything you need from us while using our iFrame integration or while consummin our Deep Link API. We are happy to help.

I'm sending this email to your technical lead, Person A, and our Chief Technology Officer, Gerardo Fernández. In the following hours, Mr. Fernández will send you and Person B an email with a password protected PDF. The password to view the PDF will be full name of the person that signed the contract [Name Lastname]. Inside the PDF, you will find two keys: a key to use our iFrame integration and a key to consume our Deep Link API. Please, keep this key secure and well protected.

In the PDF you will also find the documentation, but I'm also sending it here for your convenience:

Deep Link documentation

https://apidocs.legit.health/integration/deep-link/

iFrame documentation

https://apidocs.legit.health/integration/iframe/

Kind regards,

Being:

  • Person A: The technical lead of the customer's company
  • Person B: The manager of owner of the customer's company

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:

  • Author: Team members involved
  • Reviewer: JD-003, JD-004
  • Approver: JD-001
Previous
T-011-001 Device OAuth Order
Next
Deprecated
  • DeepLink and App keys order template
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.)