Regions ADR (architecture decision record) #1381
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This PR is stale. Please review/update it or close it. |
|
Re-opening this. |
|
This PR is stale. Please review/update it or close it. |
|
This PR is stale. Please review/update it or close it. |
|
This pull request has been linked to Clubhouse Story #2440: Document a Regions ADR. |
kpethtel
approved these changes
Mar 9, 2021
doc/arch/012-regions.md
Outdated
|
|
||
| Our mobile app sync has been built around FacilityGroup. As we have grown, syncing all patients within a FacilityGroup loads far too much data -- sometimes tens of thousands of patients. This can overload mobile phones and introduce many UX challenges. Most Simple app users work with hundreds or maybe a thousand of patients over the course of a week, not 10k+. | ||
|
|
||
| In the admin UI, there are many users who want to monitor performance at differnt levels than the district or facility level. Some admin users should have access to levels above or below the FacilityGroup that do not yet exist. For example, in India some users should have reports access at the [state level](https://en.wikipedia.org/wiki/States_and_union_territories_of_India), which is above the district (ie FacilityGroup). The current model does not suppor this, in any sort of clean way. |
There was a problem hiding this comment.
Couple of typos here: differnt and suppor
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Story card: ch2440
Because
Our Regions model is a large change, and could use some explanation, even after the fact 😁 . This adds a retroactive architecture decision record to help explain some of the context, motivation, and tradeoffs around our move to the Regions model.