Open wbryant opened 2 years ago
This point needs a lot more thought and community engagement but IMO the community needs to get out and about and find and solve problems for people who
a) are completely non-technical b) are analytical but not code-first (Excel users, e.g.) c) may use R or Python but are not currently being heard in our community
Your point about data engineering is a good one- if you could describe some common problems in data engineering that would be really helpful, thanks
A few internal data engineering challenges (from a hospital analyst's/DE's point-of-view):
When thinking about data/model/app sharing the following are challenges (overlap with the above):
Happy to expand on this to contribute to the vision. Or I guess as a blog post. I should emphasize that this is very much from a team working inside a Trust with (at least initially) a primarily research focus.
I have broken the link in the original post, please note that the correct link is now https://nhs-r-community.github.io/nhs-r_vision/docs/background/#what-can-the-nhs-r-community-do-to-support-the-system
If you would like to contribute to this issue please make a PR here https://github.com/nhs-r-community/nhs-r_vision/blob/main/content/docs/event/_index.md
Mentioned here, number 7 - what would the specific purpose of this be? Data engineering is very important as a prerequisite for "data science" and there is a lot of space for identifying and addressing common problems in that space.
On the other hand, if the event could generate fundable ideas to drive data science (and consequently the underlying data/analytics infrastructure) then that would be great!