UX Mock-ups and Guidance

jmandel commented 2 years ago

Key screens or functional requirements

[x] Create a new SHL, setting passcode, expiration, etc, and populating label, and "inclusion policy" (i.e. what is shared)
- [ ] UX decision: can there be >1 SHL active for a given patient at a time (e.g. with different policies, passcodes, expiration times, etc to allow for a short-term link on top of long-term links)?
[x] Share a SHL by presenting QR, label, patient details
[x] Share a SHL by copying a link or maybe OS-level "share" to text/email/etc
[ ] What SHLs exist for an individual?
[ ] Delete a SHL (may include an access log review)
[x] Review access log for SHL

Guidance / Considerations to go along with UX?

mperretta commented 2 years ago

Generic_SHL_Mock-ups_091322.pdf Generic_SHL_Mock-ups_091322.pptx

mperretta commented 2 years ago

Generic_Mobile_UX_Access_Log Generic_Mobile_UX_Link_Manage Generic_Mobile_UX_Link_Set-up Generic_Mobile_UX_SHL_QR

jpp9 commented 2 years ago

these look good!

just echoing one piece of feedback from the workgroup call, it would be a good to add a couple of more words of explanation to the Access Log screen, in some way indicating that those are the orgs who have identified themselves as having viewed the records.

then i'd say upload add the files to the repo! once that's done i'd be happy to take a first pass at some text along the lines of the overview we did for SMART Health Card designs.

smart-on-fhir / health-links-designs

UX Mock-ups and Guidance #1