Entity persistence

[samkanga]

We inherently create a conflict in the Android client across plans if a task has been generated server side and the Android client hasn’t synced. This is the case when we have multiple plans working in the same operational area and a new plan is created in that same operational area. Additionally, The current process requires a duplicate registration of that family in the second plan.

Below is a list of entities that must persist across plans: Jurisdiction Location (We may need to edit jurisdiction locations at some time in the future in the Android client) Non-Jurisdiction Location Family Family Member

Documentation found on Reveal Jira

How to create a CarePlan for a location without a patient discussion. No timelines, ending discussion - RESOLVED.

[ekigamba]

Output from discussions:

• This issue might be fixed by FHIR Workflow
• FHIR Workflow is dependent on this issue
• This will be fixed by authoring the PlanDefinition to close all duplicate tasks across plans for a structure/patient. CQL enables us to have multiple inputs when evaluating expressions eg. QuestionnaireResponse, Structure, Patients(at structure) and Task

[pld]

@ekigamba what do you mean by "workflow" in this context? a workflow is defined by one or more plan and activity definitions

[rkodev]

@pld This refers to the workflow api being implemented on the SDK

[pld]

K cool, thanks, so that's not really a FHIR thing but the Android FHIR SDK Workflow API.

Reading through the issue, the way we're structuring the FHIR resource graph might also address these issues