- "SCREENER" title on navigation doesn't link to anything. What should we link to? Or should we remove the link?
- "Browse Patients" doesn't specify "your patients" or "new patients" - is this confusing?
-
/preescreening_basic/only shows "Access Now" at the top. Probably hard coded right now, but may be confusing to user when doing multiple screenings or a different service. -
/prescreening_results/when "negative" shows a cryptic phrase without the name of the clinic and an empty period at the end of the sentence. - If you prescreen and submit without entering anything in the fields, you get a
400bad request error. - "Not eligible" has no alert, and gets mixed in with other successful entries
- Results do not work when prescreening a specific patient. The results always say
"You are likely not eligible for ." - No "not sure" option for "Are you eligible for Medicaid?" question
- [ ]
- Links to user and service don't go anywhere (no route exists)
- Print page shows "edit" fields
- Phone Number "primary" field shows
on- unsure of what this means - Phone number "primary" adds
Yas an extra row in the table - Title text hierarchy is hard to read, especially with bolded text beneath (turn to
<h1>for now?)
- View of searching new patients is confusing, let's add some different names
- Viewing new patient page (with consent form) always shows "New Patient" ... is this okay for testing?
- [ ]
- Error on "add new patient": description is too long (should limit characters?)
DataError: (DataError) (1406, "Data too long for column 'description' at row 1") 'INSERT INTO phone_number (patient_id, phone_number, description, primary_yn) VALUES (%s, %s, %s, %s)' (10L, '333-333-3333', 'This is another device that I sometimes use when my primary is out of data. ', None)
- Existing phone numbers are rendering as inputs, not read-only
- Error on phone number when "add is clicked" but nothing is entered. Seems related to updating "primary" checkbox. If I uncheck the box and make sure that no phone numbers are checked, the error doesn't happen. This error prevents the user from continuing to edit, even when they press the back button.
DataError: (raised as a result of Query-invoked autoflush; consider using a session.no_autoflush block if this flush is occurring prematurely) (DataError) (1406, "Data too long for column 'primary_yn' at row 1") 'UPDATE phone_number SET primary_yn=%s WHERE phone_number.id = %s' ('on', 5L)