Customer story · Lusíadas
Lusíadas runs human approvals through Humanos.
Lusíadas is a national private hospital network with a multi-vendor stack — Medify, Glintt, NewSoft, Pipedrive, internal systems and the patient mobile app. Humanos sits across all of it as a global, independent approval OS. One API any system can call when a human needs to consent, sign, prove identity, or authorize an action — collected once, verifiable everywhere.
Lusíadas
TL;DR
One API for every consent, KYC, signature and prescription — across every system.
Lusíadas is a national private hospital network with a multi-vendor stack — Medify, Glintt, NewSoft, Pipedrive, internal systems and the patient mobile app. Every one of those surfaces eventually needs the same thing: a signed, verifiable human approval — a consent, a KYC, a signature, a prescription.
Humanos sits across the ecosystem as a global, independent approval OS. One API any system can call. Approvals are collected once, anchored as portable proofs, and verifiable from any other system that needs them.
Every approval emits a cryptographic receipt with signer, scope, timestamp, and validity. When AI agents start acting inside Lusíadas systems, they inherit the same approval infrastructure that humans use today.
01 · The Customer
Lusíadas is a national private hospital network running on a multi-vendor clinical stack.
Their ecosystem spans third-party clinical and back-office software — Medify, Glintt, NewSoft, Pipedrive — and their own internal systems and patient mobile app. Every one of those surfaces eventually needs the same thing: a signed, verifiable human approval — a consent, a KYC, a signature, a prescription.
Humanos sits across the ecosystem as a global, independent approval OS. One API any system can call. Approvals are collected once, anchored as portable proofs, and verifiable from any other system that needs them — making every clinical and administrative process faster, safer, and audit-ready by default.
- Customer
- Lusíadas
- Domain
- National private hospital network
- Surface area
- Consents · KYCs · Signatures · Prescriptions
- Stack
- Medify · Glintt · NewSoft · Pipedrive · mobile
- Integration
- humanos.requestApproval() · global approval OS
- Site
- lusiadas.pt ↗
- Anchored
- 2026-05-29 · v1
02 · The Problem
Every system needed its own approval flow. Patients re-signed the same consent on three apps.
A modern hospital network runs on a multi-vendor stack. Each vendor — clinical software, back-office, CRM, mobile — shipped its own way to collect a signature, a consent, a KYC. None of them spoke to the others.
An approval signed in Medify couldn't be reused in Glintt. A KYC done in the mobile app didn't carry over to NewSoft. GDPR compliance had to be re-proven per integration.
- What’s happening
- Each vendor reimplements signatures, KYCs, consents.
- Every clinical or admin system needs human approvals — but every one of them builds it differently. Same patient, different flows, different storage, different proof formats. Approvals end up trapped inside whichever app collected them.
- What it costs
- Approvals can’t travel between systems.
- An informed consent signed at admission doesn’t reach the OR system. A GDPR consent given in the mobile app doesn’t propagate to the back-office. Patients sign the same thing two or three times. Audit becomes a reconstruction exercise across disconnected vendors.
One patient, one approval, three apps re-asking for it. Not anymore.
03 · The Solution
One approval API, shared by every system in the stack.
Any clinical or admin system in the Lusíadas ecosystem — Medify, Glintt, NewSoft, Pipedrive, internal apps, the patient mobile app — can request and verify a human approval through a single call to Humanos.
Approvals are collected once, signed by the right human(s), anchored as portable proofs, and consultable from any other system that needs them.
- ✓ Approved
- Procedure can proceed.
- Both signers verified, scope correct, receipt anchored. The proof is attached to the patient’s clinical record and becomes visible to NewSoft, Glintt, the OR system, and the patient mobile app — without anyone re-collecting it.
- ✕ Missing approval
- Collect inline — then continue.
- Missing a signature, an expired KYC, an outdated GDPR consent. Humanos requests the missing approval in real time through whichever surface the human is on (mobile, web, in-clinic), and the original flow resumes once the receipt is valid.
Lusíadas approves once — and the rest of the ecosystem just verifies.
04 · Implementation
How Lusíadas implemented it.
Five stages in chronological order, walking through one informed-consent flow end-to-end — collected in Medify, verified by Humanos, surfaced across NewSoft, Glintt, and the patient mobile app without anyone re-asking.
- 01
Issue · Define approval template
Lusíadas Compliance authorizes the approval template — consent type, required signers, scope, validity. Humanos issues a machine-verifiable schema — one template, reusable across every system that needs that approval.
- 02
Prepare · Medify renders the consent
The clinical software (Medify) renders the informed-consent document for the patient and the signing physician. It attaches the approval template to its outbound request as x-humanos-approval.
- 03
Verify · Humanos verifies signers
Both signers (patient + physician) sign through Humanos. Identity, scope, registered counterparty, signatures, and anchor are checked in 188 ms — deterministic, single API across every system in the stack.
- 04
Execute · Commit to clinical record
Approved → the consent is written to the patient’s clinical record and becomes consultable by NewSoft, Glintt, the OR system, and the patient mobile app — no re-collection. Missing → step-up is requested inline (mobile, SMS, in-clinic) and the original flow resumes.
- 05
Prove · Portable receipt
Every approval emits a cryptographic receipt — anchored to the Lusíadas approval ledger, attached to the clinical record, portable forever. Auditors, regulators, and insurance partners verify the receipt directly against Humanos; nothing reconstructs trails from scattered vendor logs.
- Issuer
- Compliance · Lusíadas
- Signers
- Patient + Cardiologist
- Scope
- consent.informed · cardiology
- Linked
- GDPR processing
- Latency
- 188 ms total
- Surfaced in
- Medify · NewSoft · Glintt · mobile
- Verifiers
- Auditor · Regulator · Insurance partner
- Result
- Independently verifiable · forever
05 · The Outcome
What you get the moment it’s wired in.
- Unified
- One approval API across every system.
- Medify, Glintt, NewSoft, Pipedrive, internal apps, the mobile app — they all consume the same single endpoint. Every kind of human approval, one integration.
- Reusable
- Collect once, verify everywhere.
- An approval signed in one corner of the ecosystem is valid in every other. Patients sign once; clinicians sign once. The proof travels with them.
- Compliant
- GDPR- and regulator-ready by default.
- Every approval emits a cryptographic receipt with signer, scope, timestamp, and validity. Compliance proven at the approval layer — not reproven per vendor integration.
- Faster
- Procedures proceed without rework.
- No duplicate signatures, no re-asking the patient, no re-doing the KYC. Missing approvals are collected inline and the original clinical or admin flow resumes immediately.
- Verifiable
- Portable, independently verifiable proof.
- Auditors, regulators, and insurance partners verify the receipt directly against Humanos. No log reconstruction from scattered vendor systems.
- Agent-ready
- Same API for humans today, agents tomorrow.
- When AI agents start acting inside Lusíadas systems, they inherit the same approval infrastructure that humans use today. No re-engineering, no parallel stack.
Approvals collected in one corner of the ecosystem — verified, trusted, and reusable across all of it.
06 · Build vs Humanos
Approvals don’t scale built per system.
| Approvals locked per app | One API, every system |
|---|---|
| ✕ Each vendor implements its own signature, consent, and KYC flow. | ✓ One API every system in the stack calls — consents, signatures, KYCs, prescriptions. |
| ✕ Approvals are trapped inside whichever app collected them. | ✓ Approvals are portable proofs, consultable from any other system that needs them. |
| ✕ GDPR compliance reproven per vendor integration. | ✓ Compliance proven once at the approval layer; every system inherits it. |
| ✕ Audit assembled from scattered vendor logs. | ✓ Every approval emits a portable receipt anchored at the Lusíadas approval ledger. |
| ✕ Patients re-sign the same consent across two or three apps. | ✓ Patients sign once; the rest of the ecosystem just verifies. |
| ✕ Re-engineer the approval layer when AI agents arrive. | ✓ Same API today for humans, tomorrow for agents — no parallel stack. |
07 · Network Effect
One approval becomes shared infrastructure — not something each vendor rebuilds.
An approval signed in one system works in every other. Sign in Medify, verify in Glintt. Sign in the mobile app, verify in NewSoft. The proof travels with the patient.
Every vendor consumes the same approval layer. No re-collection. No duplicated KYCs. No re-asking the patient for a consent they already gave somewhere else in the ecosystem.
New vendor? Same API. Onboarding a new clinical or admin system means calling the same endpoint. No new approval logic per integration.
Each system strengthens the network. The more systems run on the same approval OS, the more reusable every signed receipt becomes — and the simpler every audit gets.
Any approval. Any system. One API.
- 01
- GDPR consents
- Captured at first contact — mobile, web, or in-clinic. Valid across every Lusíadas touchpoint. Compliance proven at the approval layer, not reproven per integration.
- 02
- Remote identity verification
- KYC the patient before any clinical or admin action that requires it. Done once, verifiable across the mobile app, clinical software, and back-office systems.
- 03
- Informed consents
- Signed by both the patient and the healthcare professional. Receipt anchored, attached to the clinical record, visible to every system that needs it — without re-collection.
- 04
- Prescription signing
- Physicians sign through Humanos; the pharmacy dispenses against the verified receipt. Same integration covers Medify, Glintt, and the patient mobile app surface.
08 · The Model
Issue → Verify → Collect → Prove.
- 01 · Issue
- Mandate.
- Human authorizes scope. Humanos issues a machine-verifiable mandate, reusable across every system that verifies.
- 02 · Verify
- Check.
- Any external system runs humanos.verify(). Deterministic yes / no.
- 03 · Collect
- Approval.
- Out of scope? Request step-up authorization from the human principal in real time — API, SMS, or email.
- 04 · Prove
- Receipt.
- Cryptographic Proof per action. Auditable forever. Verifiable by anyone.
09 · Category Definition
Humanos is the approval OS across the Lusíadas ecosystem — the moment a human action needs to be authorized.
At that moment, the approval must be unified across every system, portable across every vendor, and future-proofed for the agents that come next. Everything else follows.
- Unified
- One API, every system. Medify, Glintt, NewSoft, Pipedrive, internal apps and the mobile app all consume the same single approval endpoint.
- Portable
- An approval works wherever it's needed. Signed once. Verifiable everywhere. Patients and clinicians never re-sign what the ecosystem already has.
- Future-proof
- Humans today, agents tomorrow. The same API serves human approvals now and the AI agents that will act on behalf of those humans next.
Each system reimplements approvals.
Every system shares one approval layer.