Adaven app documentation
Last updated
This page describes the Adaven patient application for health systems, app reviewers and anyone who wants to know exactly what it does. Adaven is made by Avalen LLC. Questions: hello@adaven.ai.
What Adaven is
Adaven is a personal health record for individuals and their families. A person signs in with their Google account and gathers their health information from the sources they choose, such as a hospital’s patient portal, a laboratory, their phone’s Health app or a document they upload, into one record that belongs to them. Adaven is a patient-facing application: it acts for the patient, at the patient’s request, and never for a provider.
How the connection to a health system works
- Launch type: standalone patient launch, SMART App Launch with FHIR R4, from the Adaven web application.
- Client type: public client with PKCE (S256). Adaven holds no client secret.
- Sign-in: the person is sent to the health system’s own patient-portal sign-in page (MyChart). Adaven never sees or stores the portal password.
- Consent: before any connection, Adaven shows the person a plain-language screen explaining what will be read and why, and the person can stop there. The health system’s own authorization screen follows.
- Access: read-only. Adaven never writes to, or changes anything at, the health system.
- Refresh: with the person’s offline-access permission, Adaven refreshes the record on request and on a schedule, so new results appear without a new sign-in. The person can disconnect at any time, which discards the tokens.
What Adaven reads
Only the resources below, for the signed-in patient, and nothing else.
| Resource | Why |
|---|---|
| Patient | Name and date of birth, to confirm the connected account belongs to the signed-in person. |
| Observation (laboratory, vital signs) | Lab results and vitals, the core of the record. |
| DiagnosticReport | The report a set of results belongs to. |
| Condition | Diagnoses and problem list. |
| MedicationRequest | Current and past prescriptions. |
| Immunization | Vaccination history. |
| AllergyIntolerance | Allergies and intolerances. |
| Procedure | Procedures performed. |
What happens to the records
- Each record is stored as received (FHIR R4), with a label naming the health system it came from and when it was read, in the person’s own encrypted record on Google Cloud in the United States, under a Business Associate Agreement between Avalen LLC and Google.
- Each person’s record is encrypted with a key created for that person alone. Deleting the record destroys the key.
- Every read and write of a record is written to an access log the person can read, and that log cannot be edited.
- Records are shown to the person and to anyone the person explicitly names. They are never sold, never used for advertising, and never shared with anyone else.
Support
People using Adaven, and health systems with questions about it, can write to hello@adaven.ai. The privacy policy and terms of service apply.
Status
Adaven is in its first phase, built for one family and tested against Epic’s sandbox before any health-system connection is offered to others.