---
title: 'LifeCare.ID® - Your Life. Your Data. Your Control.'
description: 'LifeCare.ID® is patient-sovereign consent infrastructure for intelligent healthcare. Cryptographic, revocable consent over your health data - wherever it lives. Zero PHI, ever.'
canonical: https://lifecare.id/
generated: 2026-10-08
---
LifeCare.ID® - Your Life. Your Data. Your Control.

[LifeCare.ID®](https://lifecare.id/#top)

[Book a call](https://calendly.com/hcvc/15min)

Patient-sovereign consent infrastructure

# Your Life. Your Data.Your Control.

LifeCare.ID® is the consent layer for intelligent healthcare -
cryptographic, revocable permission over your health data, wherever it
lives. Built for patients, trusted by physicians, compliant by design.

[Book a 15-minute discovery call](https://calendly.com/hcvc/15min)
[See who it's for](https://lifecare.id/#audiences)

Zero PHI, ever
The key never leaves your device
Revoke anything, any time

The guarantee

## No health data ever passes through LifeCare.ID®.

A full compromise of LifeCare.ID® yields tokens, public keys,
and consent metadata - never a single health value. Your data flows
directly between where it lives and whatever destination you authorize. Our
infrastructure touches only `{ DID, key, token, scope, consent receipt, revocation status }`.
This is architecture, not a privacy policy.

Who it's for

## One foundation.

The individual is the principal. Individuals own their health data and
authorize every use of it, every time. Everything else flows from that.

For individuals

### You own your health data

A passkey on your device holds your key - nothing to install, no
password to remember, no one able to act as you. LifeCare.ID®
knows where your health data is held and enforces your permissions
wherever it lives: on the nodes of the LifeCare network, run by your
providers, the node itself enforces them; elsewhere, your rights are
asserted for you. No one sees your data without your explicit,
revocable consent. You enroll through your participating provider;
the data stays where it was created. You hold the keys.

For physicians

### Honor the patient relationship at scale

Physicians built their practices around patient relationships
long before the rest of healthcare caught up. LifeCare.ID®
is the consent infrastructure that enables you to deliver outcomes
without surrendering your patients' data to a third-party cloud.

For researchers

### Outcomes data you can trust and defend

LifeCare.ID® makes patient consent the foundation, not the
obstacle: every data point is traceable to a patient who explicitly
authorized its inclusion.

For developers

### Build on the consent layer

Add “Sign in with LifeCare.ID®” and request consented,
purpose-bound access to health data with a few standards-based
calls - OAuth 2.0 + PKCE, UMA-pattern tokens, signed consent
receipts, all against a published, versioned API contract.

The architecture

## Built around data sovereignty.

Most healthcare systems aggregate patient data. LifeCare.ID®
makes this data accessible without moving it. Data stays with whoever
holds it - a provider's node in the LifeCare network, a lab, a device
maker - and LifeCare.ID® keeps the map of where it is and the
permissions that govern it. Who owns a node and who controls the data
on it are separate questions: providers own and operate the network's
nodes, the individual controls the data, and every node publishes a
signed statement of what it runs. Queries run through federated infrastructure that never touches
PHI; the patient authorizes every query through their own
identifier.

🔑

#### Cryptographic consent

Each authorization is signed with a key held in the patient's device
secure element via a WebAuthn/FIDO2 passkey, and bound to their W3C
decentralized identifier (`did:web`). Recorded as a
verifiable consent receipt.

🌐

#### Federated query

Outcomes queries run against distributed clinical sources and
aggregate at query time. No protected health information ever moves
to a central warehouse.

🛡️

#### Zero PHI in the cloud

The network is a coordination layer, not a data store: no
LifeCare.ID® component ever holds a health value, whether a
node is a machine in a practice or a virtual one. There is no
warehouse to attack, no database to subpoena, no aggregated
population to be re-identified. The models run where the data is:
[zero-egress health AI](https://lifecare.id/zero-egress).

↩️

#### Revocable, auditable, end to end

Patients revoke any consent at any time - tokens die in under half a
second. Every grant, access, and revocation is recorded in a
hash-chained, tamper-evident ledger.

Built on open standards
WebAuthn / FIDO2
W3C DID
W3C DPV
[ISO/IEC TS 27560](https://lifecare.id/consent-receipt)
[UMA 2.0](https://lifecare.id/authorization-server)
GDPR Art. 25

Don't trust. Verify.

## Check what any node is running.

Consent decides who may touch your data. Attestation lets you check what
a node says it runs. Every LifeCare.ID® node publishes a signed
record of its code and AI models. Anyone can check in their own browser
that the record was not altered and that the key that signed it is the
one LifeCare.ID® lists for that node.

[Verify a node](https://lifecare.id/verify)
[How the transparency model works](https://lifecare.id/attestation)

For developers

## Sign in with LifeCare.ID®

Federate identity and request consented, purpose-bound health data
without ever holding a key or touching a raw value. Apps integrate
over OAuth 2.0 + PKCE; data sources serve directly under
UMA-pattern tokens they validate by introspection. Everything is
specified in a published, drift-tested API contract.

Get building in minutes: clone-and-run quickstarts, runnable cURL /
JavaScript / Python examples, task-oriented recipes, and a drop-in
"verify your node" badge. Concepts, the API reference, the roadmap,
and the procurement pack are open to read.

[Read the developer docs](https://developers.lifecare.id)
[Request access](mailto:hello@lifecare.id?subject=Developer%20access%20request)

# 1 - federate the user in (OAuth2 + PKCE)
GET /authorize?response_type=code&client_id=…
  &code_challenge=…&code_challenge_method=S256
# → { did, access_token }
# 2 - request a purpose-bound data token
POST /v1/token
{ "scope": "cgm", "purpose": "weekly synthesis" }
# → lc_… (min-scope, time-boxed)

Why now

## The legal ground is moving.

Patient data sovereignty is not aspirational - it is where
policymakers are converging. State health-privacy law is the leading
edge of a national shift toward affirmative consent.

**My Health My Data Act**Affirmative consent required for any sharing of consumer health data.

**Connecticut Data Privacy Act**Explicit opt-in required for sensitive personal data, including health.

**Colorado Privacy Act**Sensitive data, including health information, requires affirmative consent.

Federal legislation along the same lines is being drafted
now. Any platform that fails to respect patient data ownership will be
legally indefensible by 2030. The infrastructure to do it right exists
today.

From the blog

## Subscribe to our Substack

Long-form on patient data sovereignty, healthcare AI, and the
architecture of trust. New writing lands on our Substack.

Paper

#### The paper: design and early operation

A preprint describing the consent receipt, the authorization
server, zero-egress enforcement and attestation, with the
limits stated plainly. Permanent DOI on Zenodo.

[Read the paper →](https://lifecare.id/paper)

Substack

#### Read the latest from LifeCare.ID®

Essays on patient-sovereign healthcare data, consent infrastructure,
and where the field is heading.

[Visit the Substack →](https://lifecare.substack.com/)

[Subscribe on Substack](https://lifecare.substack.com/)

Get started

## Curious to learn more?

Whether you're a physician, a researcher, or a developer building
toward intelligent, outcome-driven care, we'd like to talk.

[Book a discovery call](https://calendly.com/hcvc/15min)
[Explore the docs](https://developers.lifecare.id)

LifeCare.ID®
Consent-first infrastructure for patient-centric, outcome-driven healthcare. Your Life. Your Data. Your Control.

Built by HCVC.net (Enbarca Inc), founded by Raphael Gernot, with [ProForta](https://proforta.com/) and the [Healthspan Node](https://github.com/enbarca/healthspannode).

Ecosystem

- [For individuals](https://lifecare.id/#audiences)

- [For physicians](https://lifecare.id/#audiences)

- [For researchers](https://lifecare.id/#audiences)

- [Architecture](https://lifecare.id/#architecture)

Developers

- [Documentation](https://developers.lifecare.id)

- [Verify a node](https://lifecare.id/verify)

- [Roadmap](https://developers.lifecare.id/roadmap.html)

- [Source](https://github.com/enbarca/lifecareid)

Get started

- [Book a call](https://calendly.com/hcvc/15min)

- [Raphael Gernot on LinkedIn](https://www.linkedin.com/in/hcvc/)

- [hello@lifecare.id](mailto:hello@lifecare.id)

- [Member terms](https://lifecare.id/terms)

- [Privacy notice](https://lifecare.id/privacy)

© 2026 HCVC. All rights reserved. [Member terms](https://lifecare.id/terms) · [Privacy notice](https://lifecare.id/privacy)
LifeCare.ID® is a registered trademark of Enbarca Inc. in the United States.