[Malawi Core] Rebuild MWCore app in Quest

[Gental-Giant]

Feature Description
Workflow Description

1. Authentication - provide credentials for Malawi Core local.properties file for Keycloack and HAPI FHIR server URL

   • Add Malawi Core config
   • Move to Login page

2. Registration

   • Move into the default register
   • Add the client button
   • Add client via pressing 'Add client button'
   • View registration form
   • Submission and extraction of required resources
   • Go back to register

3. View Patient Profile

   • View vitals or any other patient info

4. Edit Patient profile

   • Accessed as menu item in the client profile

Once this boilerplate code is ready we can extend the functionality to do :

1. Clinic Registration

   • Detailed requirements available here

2. ART Clinic Visit (including appointments page, ICT, clinic history)

   • Detailed requirements available here

3. Tracing functionality

• List of requirements and workflows to be updated later*

Additional context

• Current codebase
• Registration questionnaires
• Registration workflows

SubTasks

• [Malawi Core] Failing to sign in on the application ID page #1146
• [Quest/Malawi Core] Add a configurable registration page
• [Quest/Malawi Core] Add a configurable View Patient Profile page
• [Quest/Malawi Core] Add Edit Patient functionality

[f-odhiambo]

Apart from enrolling clients on the app, which I assume is the 1st step, how do I get to either
a. Clinic Registration
b. ART Clinic Visit (including appointments page, ICT, clinic history)
What's the user journey to both workflows?

CC @Gental-Giant

[Gental-Giant]

DTree is still working on the workflows and will share as soon as they are ready.

[f-odhiambo]

On Malawi Core: adding this here for more visibility on the process to move Malawi core to Quest

1. @FikriMilano to complete and test the shared config now showing both Org ID and Publisher ID

For @AbdulWahabMemon: Create a Quest/Malawi Core app following the steps

1. On the config page add: mwcore as app id
2. Be able to authenticate using chw/Core123
3. App will then process to the Patient List view Landing page
4. Add the registration questionnaire for Malawi core - @Gental-Giant provide link to registration resource
5. Create/ Add Structure map for step 4 to create a patient
6. Ability to view Patient profile similar to the Quest default profile
7. Add ability to also edit patient profile

From here will have an entry point to the rest of the other workflows

1. Add icons once this ticket is complete Update the FHIRCore repo to add flavors #1165

CC @dubdabasoduba

[AbdulWahabMemon]

@f-odhiambo , we are done with 3 steps, now for
Step 4: Add the registration questionnaire for Malawi core - @Gental-Giant provide link to registration resource
I need link for that questionnaire if its ready,

Note:
No PinLogin is enabled, as its not mentioned anywhere for mwcore
"ic_liberia" logo file name is used for mwcore app-config, if its different for mwcore, do update here.

[Gental-Giant]

@AbdulWahabMemon Here is a link to the registration questionnaire.

• New client
• MWCore logo

CC : @f-odhiambo

[AbdulWahabMemon]

On Malawi Core: adding this here for more visibility on the process to move Malawi core to Quest

1. @FikriMilano to complete and test the shared config now showing both Org ID and Publisher ID

For @AbdulWahabMemon: Create a Quest/Malawi Core app following the steps

1. On the config page add: mwcore as app id
2. Be able to authenticate using chw/Core123
3. App will then process to the Patient List view Landing page
4. Add the registration questionnaire for Malawi core - @Gental-Giant provide link to registration resource
5. Create/ Add Structure map for step 4 to create a patient
6. Ability to view Patient profile similar to the Quest default profile
7. Add ability to also edit patient profile

From here will have an entry point to the rest of the other workflows

1. Add icons once this ticket is complete Update the FHIRCore repo to hold the Slim Apps to allow for Name & Icon configs #1165

CC @dubdabasoduba

@f-odhiambo , @Gental-Giant the mentioned steps are dev tested as working in the mwcore config

[pld]

is there a PR for that?

[AbdulWahabMemon]

is there a PR for that?

No PR as I have been updating composition and binaries for D-Tree

[Gental-Giant]

Do we need to start the flow from a generic patient registration or a newly diagnosed client questionnaire?

For "Register new client", we should have the newly diagnosed client questionnaire

cc @f-odhiambo @AbdulWahabMemon

[AbdulWahabMemon]

Do we need to start the flow from a generic patient registration or a newly diagnosed client questionnaire?

For "Register new client", we should have the newly diagnosed client questionnaire

cc @f-odhiambo @AbdulWahabMemon

I have updated the link for registration questionnaire to new-diagnosed-client-questionnaire, now there is crash on form submission as its StructureMap "newly-diagnosed-client-structure-map" isn't syncing in app,
is that StructureMap uploaded for D-Tree,

@Gental-Giant , @f-odhiambo

[f-odhiambo]

Here are the updated Questionnaire and Structure maps for this Done to unblock this
Questionnaire - https://fhir-dev.d-tree.org/fhir/Questionnaire/10189
StructureMap - https://fhir-dev.d-tree.org/fhir/StructureMap/10211

[pld]

Cool, can you please put them in the other repo so we have them under vc, then we can close this issue w/a pr into that repos main branch, thanks

On Apr 6, 2022, at 12:01 PM, Francis Odhiambo Otieno ***@***.***> wrote: Here are the updated Questionnaire and Structure maps for this Done Questionnaire - https://fhir-dev.d-tree.org/fhir/Questionnaire/10189 <https://fhir-dev.d-tree.org/fhir/Questionnaire/10189> StructureMap - https://fhir-dev.d-tree.org/fhir/StructureMap/10211 <https://fhir-dev.d-tree.org/fhir/StructureMap/10211> — Reply to this email directly, view it on GitHub <#1149 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAMMEW4QKCKKJ3DIONHVC3VDWYO7ANCNFSM5RBR2GBQ>. You are receiving this because you commented.

@AbdulWahabMemon Please add all the resources used for this PR here https://github.com/opensrp/fhir-resources cc: @Gental-Giant

[dubdabasoduba]

@dubdabasoduba @f-odhiambo

• Come up with a plan to version control resources used for the production apps.

[dubdabasoduba]

@AbdulWahabMemon How far are we with this?

[AbdulWahabMemon]

as I was working structure map for newly diagnose patient registration,
couple of fields need some validation that I am mapping to correct properties like in the questionnaire under Location Information
there is District, Tracing Catchment and Physical Locator,
I have mapped these to Patient.Address : District -> district, Tracing Catchment -> state and Physical Locator -> text
there is Chw Assigned
I am mapping it to Patient.generalPractitioner

@AbdulWahabMemon How far are we with this?

couple of patient properties need to validated and finalized

[dubdabasoduba]

Closing this based on the StructureMap extraction

@Gental-Giant We need open a new issue around practitioner assignment

[pld]

We need to store these in vcs, please push those to a branch, and open a PR if ready, for the related resources against this repo, https://github.com/opensrp/fhir-resources

…

On Apr 6, 2022, at 04:58, AbdulWahabMemon ***@***.***> wrote:  Do we need to start the flow from a generic patient registration or a newly diagnosed client questionnaire? For "Register new client", we should have the newly diagnosed client questionnaire cc @f-odhiambo @AbdulWahabMemon I have updated the link for registration questionnaire to new-diagnosed-client-questionnaire, now there is crash on form submission as its StructureMap "newly-diagnosed-client-structure-map" isn't syncing in app, is that StructureMap uploaded for D-Tree, @Gental-Giant , @f-odhiambo — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.