> For the complete documentation index, see [llms.txt](https://cjay-1.gitbook.io/lifelyn-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cjay-1.gitbook.io/lifelyn-docs/introduction.md). # Introduction **Your health, remembered.** Lifelyn is a patient-owned health memory: a continuous, evidence-cited timeline of a person's medical history that only the patient controls. It exists because the default today is the opposite of that — a patient's medical record is scattered across however many providers and hospital systems they've ever visited, none of which are required to share it with any other, and none of which are required to share it with the patient in a form they can actually use. In the United States alone, the Office of the National Coordinator for Health IT has repeatedly found that fewer than half of patients access their records digitally even when a portal exists, precisely because the record lives in dozens of disconnected silos rather than one place the patient owns. When someone changes providers, moves cities, or sees a specialist, the burden of reconstructing their own history falls on them. Lifelyn's answer is: the patient holds the key, not the hospital, not a data broker, and not a health-tech company's ad business. ## How it works, step by step 1. **You connect a Stellar wallet.** [Freighter](https://www.freighter.app/) is the only login — there's no email/password, and no way for anyone (including us) to log in as you without your wallet's signature. See Protocol Mechanics for exactly how the challenge/signature flow works. 2. **You upload a record** (a PDF, an image, a lab result). It's encrypted before it touches disk, scanned for malware, and hashed so any later tampering is detectable. 3. **Lifelyn AI extracts structured events** from the document — dates, values, provider names — but only ones it can point to an exact page and passage for. Nothing gets into your timeline without a citation. 4. **You review it.** Self-reported and provider-issued information are kept visibly distinct; you can correct anything. 5. **You grant scoped, time-limited consent** to a clinician when you choose to. Consent is enforced by the API on every request, and the fact that a grant or revocation happened is anchored on Stellar — an opaque, timestamped proof, never the medical content itself. 6. **You ask questions about your own history** ("Ask History") and get answers with a citation for every material claim — or an honest "insufficient evidence" instead of a guess. Lifelyn never diagnoses, prescribes, or recommends treatment. ## What's Stellar-specific about this, not just decorative A lot of "blockchain for healthcare" pitches use a chain as a marketing checkbox. Lifelyn only puts on-chain what actually benefits from being verifiable, tamper-evident, and independent of any single database: * **Consent grants and revocations** — a patient's authorization decision is provable and timestamped without trusting Lifelyn's own database not to have been quietly edited. * **Provider verification status** — set only by a constructor-fixed authority address, so it can't be forged by compromising the API alone. * **Record attestation hashes** — a content hash anchored per record version, immutable once written, so tampering with the encrypted original is detectable. * **Access receipts** — an append-only, ledger-timestamped proof that access happened, recorded with `require_auth`, not a caller-supplied timestamp that could be backdated. Stellar/Soroban is a good fit here specifically because of low transaction costs (this needs to scale to every consent change and every access event, not just occasional high-value transfers) and Soroban's authorization primitives (`require_auth`) map directly onto "prove you're the grantor/authority/recorder," which is exactly the property this system needs. Nothing readable — no medical content, no names, no diagnoses — ever goes on-chain; see Smart Contract Reference for the exact data shapes. ## Who this is for * **Patients** get a single place their health history lives, permanently, portably, and under their own control. See the Patient Guide. * **Clinicians** get evidence-cited context on a new patient in seconds instead of chasing down records, only once the patient has explicitly granted scoped, time-limited access. See the Clinician Guide. ## Status This is a live, service-backed application — not a demo. There is no mock login, no fixture data on a protected screen, and every dependency fails closed (returns an explicit error) rather than a fake success when unavailable. It is not yet authorized for real patient data: an independent security review, a medical-safety review, and jurisdiction-specific legal review are still pending. See the Developer Guide for exactly what's implemented and what isn't. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://cjay-1.gitbook.io/lifelyn-docs/introduction.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.