...
The program would like to conduct 'mop-up' from a central location, which means that families may show up with their QR code or with no QR code at a health facility. This requires the following features:
- Register new floating families to who present at the health facility catchment level and use
- Use QR code to lookup across synced data and link to their location
- Register as floating at HFC level
- Global look-up
- with search functionality in list view
- with QR code
- NEED to CONFIRM EXTENT OF WORK IF THIS WERE ADAPTED FOR REVEAL - current state, what needs to be ported to Reveal, timelines, and level of effort.
- Server-side QR code reconciliation/matching ONLY NEED IF NO GLOBAL LOOK-UP
- Could lead to dual registration of family members/families
- Simple facility-level aggregate form so we do not register at the facility, and reconcile the totals against the registration #s, capture aggregate consent at this level
- If pre-registered, match back numbers
- If not pre-registered, use aggregate numbers as they are
- Anyone who shows up with a QR code gets linked
- Simple facility-level aggregate form so we do not register at the facility, and reconcile the totals against the registration #s, capture aggregate consent at this level
- Could lead to dual registration of family members/families
MB: Finding this section a bit confusing.
...
If not QR code, just register a family and assign them to either the highest level catchment or sub area if they can identify it. I don't think we should try and link them to structures though. I modified this write-up to be less confusing, as I think I was mixing up the hamburger menu selection with syncing.
Option A - Implement 1, 2 ,3 → 2 → Global lookup
Working at the health facility level, where families from multiple (20+ OAs may show up for treatment), select hamburger menu option for that catchment.
...
- If have QR code paper
- Conduct QR code look up
- If no QR code: stay at health facility level in hamburger menu with a full list view.
- Family must be registered as a floating family.
Option C - Implement 1,3
- Could lead to dual registration of family members/families
- Simple facility-level aggregate form so we do not register at the facility, and reconcile the totals against the registration #s, capture aggregate consent at this level
- If pre-registered, match back numbers
- If not pre-registered, use aggregate numbers as they are
- Anyone who shows up with a QR code gets linked
- Simple facility-level aggregate form so we do not register at the facility, and reconcile the totals against the registration #s, capture aggregate consent at this level
Use QR code to link family to location
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
...
- In looking up family, when triggered to open QR scanner, scan QR code
- Potential results from scan
- Success
- QR code matches and is not yet linked.
- Confirmed match, show view of household location on map . MB: I don't know if this is worth the added complexity. I'm assuming this means we are trying to link a family to an unclaimed structure on a map? What does this give us if we are providing the service when we see them? This only should be attempted if you are visiting the household at their house. This is if we have been to that house and left a QR code there, and they visit you later not at there house, with their QR code, this applies. WE may not need to show location of the house, but linking back to a location if these criteria are met is important. This is complex and may not be essential? Not MVP.
- "Confirm link?"
- If yes, make link and proceed with workflow
- If no, warning message "This QR code links with the house shown on the map; are you sure you do not want to link?"
- Do not link → back to question in form asking "Does this family have a QR code"?
- Confirmed match, show view of household location on map . MB: I don't know if this is worth the added complexity. I'm assuming this means we are trying to link a family to an unclaimed structure on a map? What does this give us if we are providing the service when we see them? This only should be attempted if you are visiting the household at their house. This is if we have been to that house and left a QR code there, and they visit you later not at there house, with their QR code, this applies. WE may not need to show location of the house, but linking back to a location if these criteria are met is important. This is complex and may not be essential? Not MVP.
- QR code matches and has already been linked
- Enter family module
- QR code matches and is not yet linked.
- Failure
- QR code does not match.
- "Okay"→ back to question in form asking "Does this family have a QR code"?
- QR code does not match.
- Success
...
- Add list of floating families view (likely from list view)
- QR code
- Scanning screen (think this already exists in OpenSRP)
- Visualize matched house screen (show on the map view, the location of the house that matches with the QR code
- Follow-on/confirmation questions
- View to family-look up → icon from list view?
- to look up families with QR code
- to add floating families
Out of scope
- Registering a family ad hoc (i.e. not at their household location) and then dropping a point for their location
Justification
Notes
Questions
...