Populating drop-down options in FHIR Core from Resources in DB

[allan-on]

Feature request

Syncing location (hierarchy) data from the server and populating drop-down options in a Questionnaire

Context

In Questionnaires where the user needs to input location-related data such as the name of a physical location or Health Facility tied to a jurisdiction, a selection from a list would offer the best UX.

Implementation

Server-side implementation

The implementation should provide syncing of location data from the server added through location hierarchy or practitioner assignments on FHIR Web.

• We can use the implementation that will be available on the FHIR Gateway that allows getting Location and LocationHierarchy details as part of the Practitioner details
• This will be once moving of the Practitioner details endpoint to plugins in the FHIR Gateway in [ServerSide] Move the Practitioner Details endpoint to plugins on the FHIR Gateway #2213 is done

Android FHIR SDK SDC Support

• Currently, it is only possible to use answerExpressions with an expression that takes a query and populates a drop-down item control. Support was added here Support for answerExpression extension google/android-fhir#1039

• This means that we can query against a Resource and use the values in a drop-down. This happens on loading of the Questionnaire and doesn't support multi-level selections. For instance, in a Questionnaire with multiple (multi-level) location selection options, a prior location selection within the same Questionnaire would not result in a change in the options in the next drop-down

• With initialExpression x-fhir-query support that will be introduced in Initial expression with x-fhir-query support google/android-fhir#2036 it'll be possible to Query for and set an initially selected option

FHIR Core implementation

• On FHIR Core we'd need to sync & persist the Location data using the location/practitioner details API.
  • We'll also need a menu option to trigger syncing of locations/hierarchy manually whenever assignment updates are done on FHIR Web
  • There might be performance implications depending on the amount of data that is being synced.
    • Might be beneficial to be able to define which locations to sync in the hierarchy defined

a) Drop-down selection

• The drop-down options can be populated using answerExpression. A sample implementation can be seen here Use initial expressions to select the initial value from a dropdown list populated using answer expressions google/android-fhir#1830 (comment)

b) Multi-level selections

• To implement multi-level selections that facilitate This would need SDK support for answerExpressions to work with an already loaded Questionnaire

---

Additional Context

See Loading of data on SDC widgets meeting notes

[allan-on]

@f-odhiambo @dubdabasoduba @pld Please have a look at this and add any thoughts on the same

[pld]

This looks good, it's unclear to me that we would need any changes on the SDK or FHIRCore to support the syncing use-case you are describing here, I believe that's all supported through configurations now.

Then the code change needed here is to support answerExpression on the SDK. This is a P1 issue but looks quiet recently. For that do we need both google/android-fhir#1830 and google/android-fhir#2036?

[FikriMilano]

We need 1830 to initialize the location id value in the case we want to edit the response that has multi level location.
For context: when we use answer expression, the questionnaire item type is 'reference' a.k.a the id of the resource.

Not really sure why we need 2036.
@allan-on what do you think?

[FikriMilano]

For instance, in a Questionnaire with multiple (multi-level) location selection options, a prior location selection within the same Questionnaire would not result in a change in the options in the next drop-down

Turns out, answer-expression can only access FHIRPath context from launch-context.
Therefore it cannot access:

• variables from variable expression
• other response item (simply)

@f-odhiambo remember our chat about "can answerExpression works on rendered questionnaire? just like calculated-expression".
I have confirmed it yesterday and the answer is we can't, the reason is as I mentioned above.

The code:
https://github.com/google/android-fhir/blob/master/datacapture/src/main/java/com/google/android/fhir/datacapture/QuestionnaireViewModel.kt#L585-L589

@pld @allan-on

[FikriMilano]

@f-odhiambo definitely need an SDK ticket for this, we can talk about it tomorrow if you need more explanation

[pld]

this feels like a silly question, but, can we use calculated expression here instead of answerExpression?

[FikriMilano]

not really, it's 2 different things.

calculated-expression

This expression allows for dynamic calculation of answers to questions as other questions are answered

answer-expression

Just like answerOption and answerValueSet, this is the third mechanism for capturing the allowed set of answers.

[pld]

can a calculated-expression generate a set of answers for another question, only a single answer? I guess no, that's what answer-expression is for.

But given the similarity in use-case, it sounds like answer-expression should function very similarly (or even the same as?) calculated-expression

[FikriMilano]

now you mention it, well it's very similar.

the only difference is:
calculated-expression: gives the answer selections
answer-expression: gives the answer options

[FikriMilano]

@pld @f-odhiambo @dubdabasoduba
tracked by this sdk ticket google/android-fhir#2052
I think someone from the google side will pick that up as Jing mentioned.
@MJ1998

[FikriMilano]

@pld @f-odhiambo @dubdabasoduba
I think we are unblocked, as long we create a snapshot w this branch
google/android-fhir#2066

device-2023-07-11-191923.webm

[SebaMutuku]

@FikriMilano when you run the app with locations, you need to click on the questionnaire fields twice for it to load filtered resources from the local db. Have you experienced this?

[FikriMilano]

@SebaMutuku can you share the steps to replicate that? including the branch, appId, and user credentials to login

[FikriMilano]

if it's using the questionnaire I shared, it doesn't need to double tap to the field.
https://drive.google.com/file/d/1aweK2JZ-3dzG9N7M2KoPwy_80sqZF9my/view

but you can try it, to make sure, by following these steps, and the same branch (use jajoo's fork/branch):
google/android-fhir#2052

[SebaMutuku]

This is how it appears the first time

However, when you press the dash and press the drop-down again, the x-fhir-query is executed.

[SebaMutuku]

@FikriMilano can you try testing the drop-down on the questionnaire without this part

 "_text": {
       "extension": [
         {
           "url": "http://hl7.org/fhir/StructureDefinition/cqf-expression",
           "valueExpression": {
             "language": "text/fhirpath",
             "expression": "'Find Patient From: ' + %city + ' City'"
           }
         }
       ]
     },

[FikriMilano]

@SebaMutuku are you referring to this questionnaire? (the one I wrote)
https://drive.google.com/file/d/1aweK2JZ-3dzG9N7M2KoPwy_80sqZF9my/view

or is it the one you wrote for locations?

[SebaMutuku]

@FikriMilano , the one you wrote. I notice if you remove the _text block, the questionnaire needs you to press on the fields twice for it to fetch data using x-fhir-query. Sometimes it's not. Let me know when we can sync up on this

[FikriMilano]

@SebaMutuku let me try again today, investigate a bit, and get back to you

[FikriMilano]

@SebaMutuku you're correct, it's oddly not working without the cqf expression (_text block), I had a quick look, haven't found the reason.

can you submit a bug report to the SDK?

[sharon2719]

@pld @allan-on Can I pick up on documenting this implementation? It will be very useful for the entire team to get to understand how this is done.

[pld]

Yes please go aheadOn Dec 18, 2023, at 02:00, Sharon Akinyi ***@***.***> wrote: @pld @allan-on Can I pick up on documenting this implementation? It will be very useful for the entire team to get to understand how this is done. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>