AuroraMed v0.5.0 is a synthetic-data pilot. See exactly what's built →

Product tour

Patient portal

A separate patient identity, activated in person. Appointments, released results, messages and refill requests.

Portal activationStaff invite a patient, the patient is given a one-time activation code in person, sets their own password, and signs in to a portal that has its own sessions.Staff invitethe patientActivation codegiven in person(72 hours, 5 tries)Patient setsown passwordPortal session,separate fromstaff sessionsIn the pilotDesigned, not builtSimulatedDecision / caution

Diagram: portal activation. A portal account is never a staff account, and staff tokens do not work on portal routes (or the reverse).

What exists Pilot

  • A patient identity separate from staff accounts, with its own password and sessions.
  • View appointments, released results, medications and allergies.
  • Secure messages to the care team (2,000 characters, with a daily cap) and refill requests for staff to decide.
  • Staff screens to invite patients, manage portal accounts and answer messages.

Limits Open

  • Identity proofing is in person only. There is no online identity check.
  • No text-message sign-in codes, no proxy access for family or guardians, and no payments.
  • Results appear only when staff release them.
  • Only synthetic patients exist.

Common questions

Can patients sign up online by themselves?
No. A patient receives a one-time activation code in person at the clinic. The code expires after 72 hours and allows five tries.
Can staff sign in to the portal, or patients to the staff app?
No. The two kinds of account and session are separate, and a token from one is refused on the other’s routes.

See patient portal on synthetic data

A short walkthrough. No patient information needed.

See the synthetic-data demo first.Request a demo