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.
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.
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.
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.
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.
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.
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 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.
Five stages in chronological order. The animation on the right walks 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.
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.
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.
Both signers (patient + physician) sign through Humanos. Identity, scope, registered counterparty, signatures, and anchor are checked in 94 ms — deterministic, single API across every system in the stack.
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.
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.
Medify, Glintt, NewSoft, Pipedrive, internal apps, the mobile app — they all consume the same single endpoint. Every kind of human approval, one integration.
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.
Every approval emits a cryptographic receipt with signer, scope, timestamp, and validity. Compliance proven at the approval layer — not reproven per vendor integration.
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.
Auditors, regulators, and insurance partners verify the receipt directly against Humanos. No log reconstruction from scattered vendor systems.
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.
Sign in Medify, verify in Glintt. Sign in the mobile app, verify in NewSoft. The proof travels with the patient.
No re-collection. No duplicated KYCs. No re-asking the patient for a consent they already gave somewhere else in the ecosystem.
Onboarding a new clinical or admin system means calling the same endpoint. No new approval logic per integration.
The more systems run on the same approval OS, the more reusable every signed receipt becomes — and the simpler every audit gets.
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.
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.
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.
Physicians sign through Humanos; the pharmacy dispenses against the verified receipt. Same integration covers Medify, Glintt, and the patient mobile app surface.
Human authorizes scope. Humanos issues a machine-verifiable mandate, reusable across every system that verifies.
Any external system runs humanos.verify(). Deterministic yes / no.
Out of scope? Request step-up authorization from the human principal in real time — API, SMS, or email.
Cryptographic Proof per action. Auditable forever. Verifiable by anyone.
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.
Medify, Glintt, NewSoft, Pipedrive, internal apps and the mobile app all consume the same single approval endpoint.
Signed once. Verifiable everywhere. Patients and clinicians never re-sign what the ecosystem already has.
The same API serves human approvals now and the AI agents that will act on behalf of those humans next.
