Feature request - Data pruning

Android FHIR SDK
,
1

One of the issues with native FHIR apps is they generate a lot of data! Much of it is also somewhat replicative. Eg. FHIR QR and the extracted resources created from that. With normal use apps can start to collect 10’s of thousands of resources on a device.

It would be important if we come up with developer friendly strategies to help manage this. Since this is complex, I think having this as a set of presents / configs that can be implemented at the SDK level would make the most sense.

Some potential strategies would be:

  • Delete certain resources of the device (eg. questionnaire responses) after they have been synced.
  • Create an IPS summary and delete CarePlan and all associated data when the plan is closed eg. ANC / Pregnancy. Once the pregnancy is done you may only want to know if there were risk signs and the outcome, etc. In some cases you may just want to archive / prune completed data.

I’m sure there are many other strategies. This is a bit of a ticking time bomb that will need to be addressed as OHS apps start to achieve more scale.

Blockquote

1 Like
2

Thanks Matt.

On the FHIR SDK side, there is the Pruning API which provides developers control over how to handle resources. Today its up to the implementers to determine and implement specific strategies.

It would be interesting to hear from other groups on:

  1. Is this a problem they have encountered?
  2. If so, how have they handled it?
  3. What are different strategies that seem feasible?

It’s also an open question whether there is additional features on the core Android FHIR SDK or whether this is part of an “app config” layer that should be defined?

Keen to hear others thoughts on this.