The link to the Google Play store page for the OpenMRS Android client is not active anymore. Can the person in charge of our OpenMRS’s Play store account re-publish the app back to the Play store? This project is actively being worked on and we are planning to release the next version (2.7) soon. CC @raff @dkayiwa @shivtej
As a workaround, implementers and developers can go to the releases page on GitHub and manually install the latest APK.
@tmarzeion or any one from @SolDevelo do you have a response to this?
Unfortunately as far as I know no one from the SolDevelo has access to the OpenMRS’s Play store account.
@c.antwi can we bring this to our tomorrow’s PM call?
@raff do you happen to know who this could be?
I do have access. Interestingly, after logging in I see this message:
This app has been removed from Google Play for violating the Google Play Developer Program Policies. We’ve sent more details to firstname.lastname@example.org."
Anyone who is in charge of email@example.com, please check that. One should be able to add more users after logging in with that address to Google Play Console.
android.permission.READ_PHONE_STATE privilege isn’t needed, then we should remove it.
Once the decision is made, I’ll make a JIRA issue for this and make a PR for it. Hopefully AC developers will review it a lot, and make sure it complies well.
@f4ww4z i would suggest that instead of waiting, just go ahead and do what you see best. The rest of the comments will follow you there after.
I would like to help out with the Issue https://issues.openmrs.org/browse/AC-561.
The auto-generated generated text is a bit vague. I think we should be a little more specific about data collected. For example, what information is stored on the mobile device and what information is passed to/from the OpenMRS server and not stored locally on the device?
@vankineenitawrun What is the need of having Children’s Policy ?As a child below 13 can also be registered as Patient?
For each patient, data stored are:
- Given, middle, family name
- Photo (permission to access Gallery and Camera)
- Birth date
- Address: Street name, city, state, country, postal code
Biometric data is stored when capturing a vital, like in the web app. Next, I think diagnosis and encounters are sent straight to the server, and not kept locally.
Regarding the READ_PHONE_STATE permission, this post suggests it’s only for target Android SDK 4 and below (Android 1.5 and below), so we can safely delete this.
I see your privacy policies are for personal apps like mentioned by @burke . You’ll need to adapt and create one that is for provider’s access to an OpenMRS instance and working with patient data.
We’ve just decided on the template, and still need to discuss the content of the policy. It’s very unlikely that we’ll use the content from the generator, we need to be way more specific and aim for the correct target audience - providers.
" Children’s Privacy
These Services do not address anyone under the age of 13. We do not knowingly collect personally identifiable information from children under 13. In the case we discover that a child under 13 has provided us with personal information, we immediately delete this from our servers. If you are a parent or guardian and you are aware that your child has provided us with personal information, please contact us so that we will be able to do necessary actions."