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-009 Sales
      • Deprecated
      • Templates
      • Specific procedures
        • SP-009-001 How to use the CRM
        • SP-009-002 Contracts
        • SP-009-003 How to share performance metrics
        • SP-009-004 Implementation plan helpers
        • SP-009-005 Implementation plan helpers for Clinical Trials
        • SP-009-006 Integration workflow helpers
        • SP-009-007 Scoring Systems Catalog
        • SP-009-008 Conditions List & Visual Assets
        • SP-009-009 Service Provision Guidelines for Intermediaries
        • Copypasters
        • SP-009-010 Customer KPI Definition and Alignment Helpers
    • GP-010 Purchases and suppliers evaluation
    • GP-011 Provision of service
    • 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 Non-product software validation
    • GP-020 QMS Data analysis
    • GP-021 Communications
    • GP-022 Document translation
    • GP-023 Change control management
    • GP-024 Predetermined Change Control Plan
    • GP-025 Usability and Human Factors Engineering
    • GP-026 Market-specific product requirements
    • GP-027 Corporate Governance
    • GP-028 AI Development
    • GP-029 Software Delivery and Commissioning
    • GP-030 Cyber Security Management
    • GP-031 Training Data Governance
    • GP-032 CE Mark Process (MDR)
    • 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-110 Esquema Nacional de Seguridad
    • GP-200 Remote Data Acquisition in Clinical Investigations
    • GP-600 Equality Planning
  • Records
  • Legit.Health Plus Version 1.1.0.0
  • Legit.Health Plus Version 1.1.0.1
  • Legit.Health version 2.1 (Legacy MDD)
  • Legit.Health US Version 1.1.0.0
  • Legit.Health Utilities
  • Licenses and accreditations
  • Applicable Standards and Regulations
  • BSI Non-Conformities
  • Pricing
  • Public tenders
  • Trainings
  • Procedures
  • GP-009 Sales
  • Specific procedures
  • SP-009-006 Integration workflow helpers

SP-009-006 Integration workflow helpers

This is a draft

This document is a draft version.

Choosing the right integration option​

When discussing the integration with a customer's IT team, it is important to define which approach best suits their objectives and technical capabilities. If dedicated standalone solutions are discarded, there are two primary options: Iframe and JSON Only.

JSON Only​

The JSON Only approach provides full flexibility for the frontend. It allows the customer to only consume the endpoints they really need (if they do not need all features).

Best for​

  • Projects where the final user is an IT professional (e.g., retrospective studies).
  • Also for customers with an existing platform or app who want full control over UI/UX, accepting a more complex integration.

Considerations​

  • Slower integration: Requires significant development effort from the customer.
  • Maintenance: The customer's IT team is responsible for ongoing API maintenance.

Iframe​

The Iframe approach delegates the complex logic and API maintenance to us, providing a much faster integration process. The customer simply embeds the interface and receives a single JSON response with the final data.

Best for​

  • Customers who do not yet have a teledermatology feature developed and either do not have an IT team, or have one but do not want to invest resources in developing this functionality due to the integration complexity.
  • Customers whose final users are non-technical (e.g., healthcare professionals in hospitals), even if the customer has an IT team.

Why Iframe is the recommended approach for healthcare environments​

When dealing with hospitals or clinics where the end user is a doctor or healthcare professional, the Iframe option significantly increases the probability of a successful deal because:

  • Easier and faster to integrate: Lowers the technical barrier for the customer's IT department.
  • Fewer integration issues: We manage the complexities of the workflows and internal logic.
  • Zero API maintenance for the customer: All maintenance and updates remain on our side.
  • Quality: It ensures the customer uses the device exactly as intended, providing a validated user experience.

The only trade-off is limited UI customization on the customer's end, but the operational and reliability benefits make it the superior choice in most clinical settings.

Workflows​

Iframe integration workflow​

JSON Only integration workflow​

Data flow using the Legit.Health API (JSON Only) for local severity assessment​

Data flow using the Legit.Health API (JSON Only) for local severity assessment​

Example of request for APASI severity assessment​

{
  "resourceType": "ServiceRequest",
  "bodySite": "armLeft",
  "payload": {
    "contentAttachment": {
      "title": "string",
      "contentType": "image/png",
      "data": "imageBase64String"
    }
  },
  "knownCondition": {
    "conclusion": {
      "coding": [
        {
          "system": "https://icd.who.int/browse/2024-01/mms/en",
          "systemDisplay": "ICD-11",
          "version": null,
          "code": "EA90",
          "display": "Psoriasis"
        }
      ],
      "text": "Psoriasis"
    }
  },
  "scoringSystem": {
    "apasi": {
      "questionnaireResponse": {
        "item": {
          "surface": 6
        }
      }
    }
  }
}

Example of request for APASI severity assessment​

{
  "resourceType": "ServiceRequest",
  "bodySite": "armLeft",
  "payload": {
    "contentAttachment": {
      "title": "string",
      "contentType": "image/png",
      "data": "imageBase64String"
    }
  },
  "knownCondition": {
    "conclusion": {
      "coding": [
        {
          "system": "https://icd.who.int/browse/2024-01/mms/en",
          "systemDisplay": "ICD-11",
          "version": null,
          "code": "EA89",
          "display": "Eczematous dermatitis"
        }
      ],
      "text": "Eczematous dermatitis"
    }
  },
  "scoringSystem": {
    "aeasi": {
      "questionnaireResponse": {
        "item": {
          "surface": 34,
          "patientAge": 20 //only needed if age below 7 years or above 7 years
        }
      }
    },
    "ascorad": {
      "questionnaireResponse": {
        "item": {
          "surface": 34,
          "pruritus": 4,
          "sleeplessness": 6
        }
      }
    }
  }
}

(TBC before sending) Example of request for APASI, EASI, ASCORAD severity assessment​

{
  "resourceType": "ServiceRequest",
  "bodySite": "armLeft",
  "payload": {
    "contentAttachment": {
      "title": "string",
      "contentType": "image/png",
      "data": "imageBase64String"
    }
  },
  "knownCondition": {
    "conclusion": {
      "coding": [
        {
          "system": "https://icd.who.int/browse/2024-01/mms/en",
          "systemDisplay": "ICD-11",
          "version": null,
          "code": "EA89",
          "display": "Eczematous dermatitis"
        }
      ],
      "text": "Eczematous dermatitis"
    }
  },
  "scoringSystem": {
    "apasi": {
      "questionnaireResponse": {
        "item": {
          "surface": 6
        }
      }
    },
    "aeasi": {
      "questionnaireResponse": {
        "item": {
          "surface": 34,
          "patientAge": 20 //only needed if age below 7 years or above 7 years
        }
      }
    },
    "ascorad": {
      "questionnaireResponse": {
        "item": {
          "surface": 34,
          "pruritus": 4,
          "sleeplessness": 6
        }
      }
    }
  }
}

ㅤㅤ ㅤ

Previous
SP-009-005 Implementation plan helpers for Clinical Trials
Next
SP-009-007 Scoring Systems Catalog
  • Choosing the right integration option
    • JSON Only
      • Best for
      • Considerations
    • Iframe
      • Best for
      • Why Iframe is the recommended approach for healthcare environments
  • Workflows
    • Iframe integration workflow
    • JSON Only integration workflow
    • Data flow using the Legit.Health API (JSON Only) for local severity assessment
      • Data flow using the Legit.Health API (JSON Only) for local severity assessment
    • Example of request for APASI severity assessment
    • Example of request for APASI severity assessment
    • (TBC before sending) Example of request for APASI, EASI, ASCORAD severity assessment
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.)