Make the mockups

[mapsam]

Working branch: make-the-mocks

Components

• [x] patient sidebar navigation
• [x] notifications
• [x] patient header
• [x] filters on landing page

Views

• [x] NEW patient overview page
  • [x] created route
  • [x] edit history
  • [x] referral history
• [x] NEW referral > review & send
• [x] UPDATE landing page
• [x] UPDATE patient details > view/edit basic info
• [x] login/security page styles

[mapsam]

Patient sidebar navigation:

Notifications:

[mapsam]

Patient header:

[mapsam]

Updated filters

note: colors are definitely not chosen here :wink:

[mapsam]

Started working on patient overview page and incorporated the patient header, navigation, and notifications:

[mapsam]

@esmithayer starting to work on the filters on the landing page. I moved the new filter names from views.py into the index.html template and am getting a different error:

ProgrammingError: (ProgrammingError) missing FROM-clause entry for table "patient_referral"
LINE 6: ..._referral.status = 'COMPLETED') ORDER BY coalesce(patient_re...

Here is the full error

[esmithayer]

Hmm do you have the full stack trace?

[mapsam]

Filter styles and counts have been added to the landing page:

[mapsam]

@esmithayer I'm confused on a couple of these, would you mind clearing up some questions?

1. In regards to the "review & send page" are we still putting unique clinic questions there? If not, does the page stay the same as the make referral page then?
2. Do we want to have new information in the filter lists on the landing page? If so, what info?
3. The patient overview page exists, but I'm not exactly sure what information goes on it. General sums (i.e. FPL) and the form that allows a clinic to say if the individual is eligible or not?
4. Referral history page - stays the same?

Thanks!

[esmithayer]

1. [x] I think we decided not to put the unique clinic questions on there. We talked about changing the behavior when the user sends a referral, though--like listing who sent the referral and when rather than just saying "referral sent", and if the patient already has a screening result for a given organization, listing that rather than the prescreening results.
2. [x] When I showed this to people at Daily Planet, they were less interested in DOB and more interested in when the referral was from. It seems like it would make sense to list the completion date for completed referrals, the creation date for open referrals, and the renewal due date for patients who need updates (i.e. the date that's a year after their last document update). The to/from organization could be useful for the outgoing/incoming referral lists too.
3. [x] Yeah, I think household size, income, FPL%, documents, and the screening result form that's currently on the referral history page. Maybe also the "do you currently have insurance" and "how long have you lived in the area" questions since we know those are key to the determination at some orgs.
4. [x] I think we had discussed some possible ways to reorganize it, but I don't remember deciding anything. We can remove the screening result form if we're putting that on the new patient overview page, but other than that probably makes sense to leave it for now unless there's something you're excited about changing.

[mapsam]

@esmithayer most of this is just about done. In order to get the first one complete, I'll need the proper models to reference in the templates (i.e. to show "has been actually approved for services at Daily Planet" vs. "likely eligible for services at Daily Planet") - what are the proper models to hit for that?

[esmithayer]

You'll want to look at patient.screening_results--you can filter for ones with a particular service id within Jinja using something like this:

{{ patient.screening_results | selectattr("service_id", service.id) }}

If that doesn't return results, the patient doesn't have any screening results for that service. If it does, you can look at the eligible_yn and sliding_scale attributes (like the referral/screening history page does right now).