FAQ

Practical answers for patients, clinicians, and pilot partners.

Yanga is built around patient-owned access, source-linked extraction, and cautious clinical use. The questions below state what is live, what is planned, and what is intentionally out of scope.

Patients

What problem does Yanga solve?

Many patients move between clinics with paper books, prescriptions, lab reports, and discharge notes. Yanga turns those documents into a patient-owned record that can be shared at the next visit.

Can the AI change my record without me?

No. AI extraction creates structured fields from the document photo, but each field remains linked to the source image and can be reviewed or corrected before sharing.

What happens when I share a code?

The clinician can open a read-only web view of the record you chose to share. Codes are intended to be short-lived and patient-initiated.

Clinicians

Do providers need an account?

No. The provider view is designed to open in a browser after the patient gives a code. It is read-only and keeps source pages visible.

How should clinicians treat AI-extracted fields?

Treat them as structured notes derived from a source document. Review the original page, confidence state, and human review status before relying on any field.

Does Yanga replace a hospital EHR?

No. It is a patient-owned record and handoff layer. Clinics can document into their normal systems while using Yanga to inspect the records the patient carries.

Security and standards

Is Yanga FHIR-compatible?

The MVP schema is FHIR-aligned and designed for a future FHIR export layer. It does not currently claim ONC certification or production FHIR server certification.

Is Yanga HIPAA-compliant?

The first pilot is designed for Cameroon, where HIPAA is not the governing law. A US deployment would require a HIPAA path, including appropriate vendor agreements, before US patient data is stored.

What is stored?

The app stores captured document images, extracted clinical fields, review state, share history, and emergency profile details needed for the patient-owned record workflow.

Pilot

Who is the first pilot for?

The first deployment is designed for African care settings where patients already carry paper records and clinicians need faster context at the point of care.

Does it work offline?

The mobile app is designed for offline capture and queued upload. Provider viewing still requires a network connection.

What should a clinic evaluate first?

Start with capture quality, extraction accuracy, patient correction burden, provider trust, and whether source-linked records reduce missing-history friction during visits.

Next step

Review the demo or discuss a pilot workflow.