You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following on from UX sync:
To speak to your point about reporting @laurenfrohlich, I think we have a fair bit of existing insight when it comes to many of the existing high priority reports. 2909 dug into the reports DIGIT saw a prime opportunity for automating (and we have a lot of that discussion captured here)
Some of what we were seeing in our preliminary analysis of the provided SAS files suggested to us that some of what's happening there might have relevance to some of those reports. Whether or not that's accurate, I think one of the core open questions standing in the way of automating some of these reports is a holistic view of what cleansing / preparation / calculation is needed to get the data into a suitable state for reporting, which is where a lot of the utility of the SAS files comes in for dev.
Hopefully that's helpful context! On a next steps front are there any days/times this week that are looking good for you and the rest of the OFA team for the spinoff discussion on the above? AC:
Research sessions have occurred.
Anonymized session notes or other top-line synthesis have been documented.
Changes to recruitment criteria have been documented if recruitment/target participant pool has been expanded.
Tasks:
---Aggregate notes from research sessions---
Supporting Documentation:
---Link to hack.md, Mural, or other relevant top-line documentation materials---
The text was updated successfully, but these errors were encountered:
Description:
Following on from UX sync:
To speak to your point about reporting @laurenfrohlich, I think we have a fair bit of existing insight when it comes to many of the existing high priority reports. 2909 dug into the reports DIGIT saw a prime opportunity for automating (and we have a lot of that discussion captured here)
Some of what we were seeing in our preliminary analysis of the provided SAS files suggested to us that some of what's happening there might have relevance to some of those reports. Whether or not that's accurate, I think one of the core open questions standing in the way of automating some of these reports is a holistic view of what cleansing / preparation / calculation is needed to get the data into a suitable state for reporting, which is where a lot of the utility of the SAS files comes in for dev.
Hopefully that's helpful context! On a next steps front are there any days/times this week that are looking good for you and the rest of the OFA team for the spinoff discussion on the above?
AC:
Tasks:
Supporting Documentation:
The text was updated successfully, but these errors were encountered: