The patient's experience

First time through

1. Start. They see your app's name and what you're asking for, then agree that FinchNode may import records from the health system they choose.
2. Pick a health system. They search for their hospital, clinic, or insurer.
3. Sign in there. They use their own portal login on the health system's page. FinchNode never sees that password.
4. Wait for the import. FinchNode pulls the records they authorized.
5. Secure their FinchNode account. They enter an email, open the verification link in the same browser, and set a password. This lets them see and revoke their shares later.
6. Review and share. They see which categories arrived, the sharing terms, and any warnings, then approve sharing with your app.
7. Done. They get a consent receipt and, if you set a returnUrl, a "Return to" button with your app's name.

A patient already signed in to their FinchNode account skips step 5. A returning patient on a new device signs in before starting.

Things to tell your users

• They'll sign in to their health system's own portal, so they need that login ready.
• They'll create a FinchNode account the first time, and must open the verification email in the same browser.
• They can see and revoke what they share from their FinchNode account at any time.

When something goes wrong

• They cancel. They go to your returnUrl, or FinchNode's home page if you didn't set one. The session reads canceled, unless they left on the very first screen.
• They can't find their health system. FinchNode logs searches that find nothing, so it knows which systems people look for.
• The import is partial. They can share whatever arrived, as long as at least one category you asked for came through.