Requirements
Overview
This is a contrato menor (minor contract) awarded by exclusivity under art. 168.a).2 of the LCSP. Unlike open tenders (e.g., AQUAS-2025-42), there is no competitive bidding process. The Gobierno de Aragón has determined that only one provider can meet the technical requirements, and the exclusivity justification has been prepared by us.
The entire tender is defined in a single document: the Documento de Requisitos (Expediente SAN_DGSDI_2026_MN01).
Contract summary
| Field | Value |
|---|---|
| Expediente | SAN_DGSDI_2026_MN01 |
| Contracting entity | Gobierno de Aragón, Departamento de Sanidad (CIF: S5011001D) |
| Destination unit | Dirección General de Salud Digital e Infraestructuras (DGSDI) |
| Contract type | Contrato menor de servicios (art. 118 LCSP) |
| Award procedure | Exclusivity (art. 168.a.2 LCSP) |
| Value | 14,995.00 EUR (excl. VAT) / 18,143.95 EUR (incl. VAT) |
| Duration | 4.5 months from contract formalization |
| Subject | AI-based digital solution for dermatological diagnosis and severity measurement + temporary corporate use license |
Contract object (section 3)
The contract is for an AI-based technology platform that:
- Supports diagnosis and automatic severity measurement of dermatological lesions
- Includes deployment and operational availability for the Servicio Aragonés de Salud
- Provides a corporate use license allowing:
- Up to 10,000 diagnostic reports
- Up to 3 images per report
- 6 months availability from contract formalization
- Covers integration with corporate systems, training, and support
Functional requirements (section 4)
Core capabilities
| Requirement | Description |
|---|---|
| Image quality analysis | Automated verification of image quality (sharpness, illumination, focus, contrast, framing) with immediate user feedback |
| Differential diagnosis | Identification and classification of dermatological pathologies (malignant, autoimmune, infectious, vascular, chronic wounds). Probabilistic ranking by severity/probability with manual validation |
| Automatic severity measurement | Automated calculation of lesion severity using standardized clinical metrics and validated algorithms. Must support longitudinal patient tracking |
| Corporate integration | Integration with HCE (Historia Clínica Electrónica) and mobile App HCE, enabling interoperability and automated report incorporation |
| Support and training | Technical support (incident resolution, corrective maintenance) + online training for healthcare and technical staff |
| Regulatory compliance | RGPD, LOPDGDD, ENS compliance. CE marking as medical device under MDR (EU) 2017/745 for AI components with clinical impact |
| Administration and monitoring | Access monitoring, action auditing, usage statistics, request management, control panel for authorized personnel |
| Portability and scalability | Modular design allowing evolution, license transfer, and migration to different technological environments |
Differential diagnosis capabilities (section 4.1)
The solution must:
- Recognize and categorize lesions across malignant, autoimmune, inflammatory, infectious, vascular pathologies, and chronic wounds using validated, evidence-based algorithms
- Offer probabilistic/estimative analysis showing differential diagnoses ordered by probability, severity, or urgency
- Detect alarm signs related to malignancy, extensive infections, or conditions requiring urgent/preferential referral
- Allow incorporation of additional clinical data (symptoms, duration, history, treatments, anatomical location) to refine the diagnosis
- Generate structured reports with analysis results and management recommendations
- Guarantee full traceability of analyses (versions, results, metadata) for audits, clinical reviews, and algorithm validation
Integration capabilities (section 4.2)
The solution must:
- Connect securely with the HCE corporativa and App HCE móvil
- Incorporate structured results (differential diagnosis, severity metrics, clinical metadata, traceability) into official repositories
- Respect corporate access models: SSO, digital certificates, electronic health identity, role-based authorization
- Use SOA architecture with APIs supporting SOAP, REST/JSON, HTTPS, JWT, SAML, WS-Security
Technology environment (section 5)
Corporate infrastructure available
| Component | Technology |
|---|---|
| Web frontend | Apache HTTP Server |
| Middleware | J2EE on JBoss (JBOSS Enterprise Application Platform) |
| Database | Oracle 19c (proprietary schema + exploitation schema) |
| Virtualization | VMWare |
| OS options | Red Hat Enterprise / Windows Server Standard + IIS |
| Resources | 12 vCPUs, 24 GB RAM, 500 GB HDD (+ up to 200 GB for DB) |
Integration modalities
- JSON API (section 5.2): Direct communication via image submission and structured JSON responses. No predefined UI; the SALUD team builds their own presentation layer.
- Iframe (section 5.3): Ready-to-use interface embedded in corporate applications. User uploads images directly, platform returns structured JSON. Minimal technical effort for adoption.
Planning (section 6)
Phase A: Setup ("Puesta en marcha")
- Remote configuration until formal validation by the Servicio Aragonés de Salud
- Integration support with corporate systems
- Training tasks, basic support, incident resolution, and product improvements throughout the contract
Phase B: Return ("Devolución del servicio")
At contract end, a structured and documented return process including:
- Closing report with activity history, consumption data, incidents, configurations, and operational recommendations for continuity
Offer structure (section 9)
Technical offer (APTA / NO APTA)
| Section | Content |
|---|---|
| 1.1 | Company presentation and suitability for the services |
| 1.2 | Formal acceptance of requirements |
| 1.3 | High-level methodology and planning |
| 1.4 | Technical description of the offered solution |
| 1.5 | Functional description of the offered solution |
| 1.6 | Project timeline |
- Format: PDF, max 50 pages DINA4, Arial 11 or similar
- Evaluation: binary APTA/NO APTA (not scored, just pass/fail)
Economic offer
- Fill out Annex I (Modelo de Oferta Económica)
Billing (section 7.5)
Single invoice after solution goes into production and scope is fulfilled. FACE electronic billing with DIR3 codes:
| Entity | Code |
|---|---|
| Entidad contratante | S5011001D |
| Órgano de contratación | A02002843 |
| Oficina contable | GE0000768 |
| Unidad tramitadora | A02045537 |
Data processing agreement (Annex II)
The contract includes an Acuerdo de Encargado del Tratamiento (data processing agreement) with standard RGPD Article 28 provisions:
- Purpose limitation, instruction-based processing, confidentiality obligations
- Security measures: pseudonymization, encryption, availability, resilience
- Breach notification within 72 hours
- DPIA support, audit access, data return/destruction at contract end
- No subcontracting of personal data processing allowed
📄️ Requirements
Overview