In-App Reporting using MeasureReports and support for a new configurable design #1735
Replies: 3 comments 13 replies
-
|
How are Measures linked to Compositions now? |
Beta Was this translation helpful? Give feedback.
-
|
We have it as a measure config in the app configs . See here https://github.com/opensrp/fhir-resources/blob/main/ecbis/app_configurations/ecbis_cha_preview/measure_report_config.json |
Beta Was this translation helpful? Give feedback.
-
|
OK cool, so we could structure sets of reports by changing the value for reports to a dictionary, like ...
"reports": {
"Household": [
{
"id": "1",
"title": "Household Members",
"description": "Number of Households, Household members registered, disaggregated by age and gender for each age group",
"url": "http://fhir.org/guides/who/anc-cds/Measure/HOUSEHOLDIND01"
},
{
"id": "2",
"title": "Household Members ANC",
"description": "Number of Households, Household members enrolled into ANC, disaggregated by age",
"url": "http://fhir.org/guides/who/anc-cds/Measure/HOUSEHOLDPREGNANCY"
}
],
...
}the keys are the name of the set of reports, then when you click in you'd see the results for everything in the list of values. |
Beta Was this translation helpful? Give feedback.
-
From our discussion, with @ahsanbhatti49 and @ellykits this will be in the below format ...
"reports": {
"id": "1",
"title": "Household Members",
"description": "Number of Households, Household members registered, disaggregated by age and gender for each age group",
"url": "http://fhir.org/guides/who/anc-cds/Measure/HOUSEHOLDIND01",
"module" : "Module 1 indicators"
},
{
"id": "2",
"title": "Household Members ANC",
"description": "Number of Households, Household members enrolled into ANC, disaggregated by age",
"url": "http://fhir.org/guides/who/anc-cds/Measure/HOUSEHOLDPREGNANCY",
"module" : "Module 1 indicators"
}} |
Beta Was this translation helpful? Give feedback.
-
|
so you'd split the modules by grouping on the module key after parse? Why that versus nested? Seems like more computational effort to do the grouping, but maybe trivially more idk
… On Nov 11, 2022, at 07:17, Francis Odhiambo Otieno ***@***.***> wrote:
OK cool, so we could structure sets of reports by changing the value for reports to a dictionary, like
...
"reports": {
"Household": [
{
"id": "1",
"title": "Household Members",
"description": "Number of Households, Household members registered, disaggregated by age and gender for each age group",
"url": "http://fhir.org/guides/who/anc-cds/Measure/HOUSEHOLDIND01"
},
{
"id": "2",
"title": "Household Members ANC",
"description": "Number of Households, Household members enrolled into ANC, disaggregated by age",
"url": "http://fhir.org/guides/who/anc-cds/Measure/HOUSEHOLDPREGNANCY"
}
],
...
}
the keys are the name of the set of reports, then when you click in you'd see the results for everything in the list of values.
@pld
From our discussion, with @ahsanbhatti49 and @ellykits this will be in the below format
...
"reports": {
"id": "1",
"title": "Household Members",
"description": "Number of Households, Household members registered, disaggregated by age and gender for each age group",
"url": "http://fhir.org/guides/who/anc-cds/Measure/HOUSEHOLDIND01",
"module" : "Module 1 indicators"
},
{
"id": "2",
"title": "Household Members ANC",
"description": "Number of Households, Household members enrolled into ANC, disaggregated by age",
"url": "http://fhir.org/guides/who/anc-cds/Measure/HOUSEHOLDPREGNANCY",
"module" : "Module 1 indicators"
}
}
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.
|
Beta Was this translation helpful? Give feedback.
-
|
can we use a FHIR resource for the report config as well? Not sure what the appropriate resource would be, but the structure's pretty simple. I also don't remember why we have ID in there, maybe that was to give an ordering? We could have the field key be order if that's the only purpose, or find a FHIR resource with a field we can use for that. If we need to discuss happy to do that, but we have more thinking to do before we make a decision here. |
Beta Was this translation helpful? Give feedback.
-
|
I see. List resource uses references for the entries, meaning will need a reference of a Binary resource with all the relevant indicators for the module instead of a Binary resource per indicator. |
Beta Was this translation helpful? Give feedback.
-
|
each entry in the list could be a separate indicator and the list itself is a group of indicators, then you have a binary (or other, there might be something more appropriate) resource per indicator |
Beta Was this translation helpful? Give feedback.
-
|
Using FHIR resource/custom model entirely is okay. Combining custom models with FHIR resource adds the complexity of serialization. |
Beta Was this translation helpful? Give feedback.
-
|
@dubdabasoduba pointed out we can have the entries in the list be the measures. So if we have a set of List resources, each List resource defines the module, then the entry points to the measure, that should satisfy our requirements here |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Context
At the moment In-app reporting and MeasureReporting do not match one-to-one in implementation and reporting both on implementation and report view, thus we need to do some research and design on how to adopt this based on the specification and achieve the same level of accurate reporting to support the workflows for both CHAs and CHSS.
Measure reporting interface
We need to figure out a way in which we can be able to update the previous In-App reporting to conform to Measurereporting based on the FHIR specification.
Proposed Solution
At the moment we have implemented measure reporting by invoking the $evalute_measure operation in the Android FHIR SDK to allow FHIR Core to be able to generate measure reports. We thus need to add a few components to make it compatible with the In-App reporting mechanism
Feature Scope
The scope of this work is limited to providing an interface to filter the desired subjects and periods for reporting, set the coverage for the indicators and then view aggregated reports, charts and graphs for reporting purposes.
In-App Reporting
The "In-App Reporting" feature empowers the health worker to see how she is performing against her daily task list and allows for offline peer-to-peer syncing of the data collected on a daily basis. This greatly simplifies reporting requirements by eliminating the need for cumbersome paper registries and tally sheets.
Data collection and extraction (StructureMaps)
Tabulation of indicators
- Proportion - In use
- Ratio - Needs some RnD
- Continuous Variable - Needs some RnD
- Cohort - Needs some RnD
- Common Libraries - DONE
- Primary Logic Libraries - DONE
- Filter by the practitioner - Needs some RnD as this has not yet been done on the $evaluate_measure SDK API
Transformation of data for user interpretation
Reporting Interface
- Development of Mock-ups - DONE
- Update of mock-ups based on inputs - TBD
- Group work to Prepare Indicator Matrix for Dashboard Visualization - TBD
Sync Data
We have the following mechanisms in place
Params for $evaluate_measure
Generation and bundling of Measure
For the purposes of this scoping the MeasureReports may be generated on-demand (for the current month) or as a background task (for the previous past months)
Afterwards, we need to see how these MeasureReports representing indicators can be :
Open Questions
- https://semicolonspace.com/pie-chart-android-compose/
- https://www.geeksforgeeks.org/pie-chart-in-android-using-jetpack-compose/
Gaps/Assumptions
The implementation approach will involve having an MVP and then an updated Alpha version
Next Steps
Read more here
Beta Was this translation helpful? Give feedback.
All reactions