This repository is a starting point for a three-day team project. This repository is populated with a starting template for team organization and planning. Use it to plan, build, and document work. Please adjust this repository to suit the needs of your team.
Team leads: Start with the team lead checklist before the event or during your first team meeting.
- Project name: Where Healing Happens: Mapping Mental Health in Childhood Cancer
- Question, problem, or opportunity: We are exploring how environmental and socio-economic factors surrounding where pediatric cancer patients live may be associated with their mental health and quality-of-life outcomes. Specifically, we will examine relationships between environmental exposures and neighborhood characteristics—such as air pollution, noise, green space, land use, Child Opportunity Index, and other SES measures—and PROMIS and MSPSS scores. The goal is to determine whether spatial patterns or environmental stressors may help explain differences in psychological well-being and social support among pediatric patients.
- Data, inputs, or evidence: [What will you use, and where does it come from?]
- Expected output:
- find patient location and map them onto greenery, pollutions, and COI maps
- look for spatial relationships between psychological well-being and environmental and social variables
- compare results of statistical as analyses using SPSS/SAS to spatial analysis using Geographic Information System (GIS)
- create interactive visualizations to present the results
- Tools and stack: ESRI ArcGIS Pro, QGIS, SAS, SPSS, Power BI, PowerPoint, Excel
- Team lead: Sylwia Feibelman and GitHub sfeibelm
- Team members and roles: [Link to
project-management/team.md] - Communication: [Add the agreed channel or contact]
Naming the tools and stack early helps the team lead create useful roles and divide work realistically. It is fine to revise this section as the project develops.
- Vision: [Describe the change, insight, or capability you hope this project supports.]
- Mission: [Describe what the team will do during the biohackathon to move toward that vision.]
[Add a short explanation of the motivation, background, and why the question or problem matters.]
| When | Focus | Expected outcome |
|---|---|---|
| Day 1 | Agree on the question, inputs, stack, roles, and first tasks | A shared plan and a first small change in the repository |
| Day 2 | Build, test, and compare approaches | A working result or clear evidence about what does not work |
| Day 3 | Stabilize, document, and present | A demo or handoff with methods, limitations, and next steps |
The goal is not a perfect production system. The goal is a clear, honest, useful result that the team can explain and others can build on.