Skip to content
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

Retrieve assigned resources from PractionerDetails contained field #3702

Closed
Rkareko opened this issue Jan 23, 2025 · 0 comments · Fixed by #3707
Closed

Retrieve assigned resources from PractionerDetails contained field #3702

Rkareko opened this issue Jan 23, 2025 · 0 comments · Fixed by #3707

Comments

@Rkareko
Copy link
Contributor

Rkareko commented Jan 23, 2025

Describe the feature request.
The current implementation stores the user assignment resources in the FhirPractitionerDetails class.
During parsing of the bundle on the android app the HAPI FHIR JsonParser only populates 1 item for each of the fields in the FhirPractitionerDetails even though the payload from the server contains multiple values. This issue is documented #3659

The HAPI FHIR JsonParser parses all resource entries in the contained field correctly.

As such, changes have been made on the server that populate the PractitionerDetails.contained field with the user assigned resources such as locations, teams, groups e.t.c

The LoginViewModel.savePractitionerDetails needs to be updated so that the assigned resources are retrieved from the PractitionerDetails.contained field

Acceptance criteria
A check list of all things to verify once the implementation by the engineer is complete

Area path
A list of ordered steps in the app on usage of the feature to support anyone testing it e.g. Code reviewer, QA e.g.

  1. Login to the app
  2. Open Navigation bar
  3. Click on Children register
  4. Click on Child profile
  5. Click on Edit profile from menu

Implementation plan (For Engineers)
The plan for implementing the solution e.g. via a description or a check list for the various ordered tasks that will need to be completed.
i.e. Describe how you intend to solve the problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants