-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement the Family Planning profile #8
Comments
Ver: 1.0.2 (19th Dec 2019)
|
If a client is on the FP and PNC register, on their All families profile, what takes precedence? To discuss with @msschroeder and @cafootitt |
@AnnieMungai what do you mean by "precedence"? Does this mean which due buttons and rows show up first? I think those items should build as a list in their respective spots. So if a PNC visit becomes due then a FP visit, they should appear in that order. For registers that include new rows in the profile, it's chronological where additional registers get added to the next row. |
@rowo @AnnieMungai @cafootitt I think Anne is saying what client profile should be used - The FP profile or PNC profile. @rowo I think it would might be helpful to have a mock-up for what this might look like, but what I would expect this to look like:
What are your thoughts? |
I think what @msschroeder has written up is generally correct. If upcoming services needs to be split up I think that is okay too. I can provide a mockup soon. This might take a longer discussion with an engineer like @manutarus because the multiple register thing has been done in bits and pieces. If this is indeed being built as flavors, we should talk about what the long term goal is and how it would work in a way where all profiles are built one way and things are shown or hidden based on condition. |
First Row: {first_name} {middle_name} {surname}, {age}
Second Row: {sex} [interpunct] {village_town} [interpunct] ID: {opensrp_id}
The text was updated successfully, but these errors were encountered: