Skip to content

Conversation

@dariusmb85
Copy link
Collaborator

Adding chapter to get feedback and suggestions. Still working to add figures and analysis section.

@mitchellmanware
Copy link
Collaborator

@dariusmb85 do you know how to find the error causing lines from the Super Linter check?

@dariusmb85
Copy link
Collaborator Author

Maybe? I explored the issue earlier by clicking on the failing check and scrolling up to all the warnings. Are those warning messages the reason it failed or is it something else I missed? @mitchellmanware

@mitchellmanware
Copy link
Collaborator

@dariusmb85 yes that is it. the important linting folder is chapters/ since thats where our additions go. if you run lintr::lint_dir("chapters") locally it will be easier to clean up than going back and forth with the GitHub output.

@dariusmb85
Copy link
Collaborator Author

Looks like everything is now in order @mitchellmanware


HCUP provides detailed hospitalization records, including diagnoses, procedures, and patient demographics, making it a valuable resource for studying health effects driven by environmental conditions. By linking these data with exposure metrics—such as air quality indices, satellite-derived pollution estimates, or weather-related hazard data—researchers can identify spatial and temporal trends in health conditions like respiratory diseases, cardiovascular events, and heat-related illnesses.

This integration also offers an opportunity to assess differences in environmental health risks across various populations. Many environmental hazards disproportionately impact underserved communities, including economically disadvantaged groups and historically underrepresented populations. By combining HCUP data with geographic and socioeconomic indicators, researchers can explore how broader social factors influence vulnerability to environmental stressors. This approach supports targeted policy strategies aimed at improving health outcomes for affected groups.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would delete this paragraph. I think it borders on the sensitive language we discussed in meeting last Friday. Unfortunately better to be extra cautious

Copy link
Collaborator Author

@dariusmb85 dariusmb85 Feb 27, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Delete it outright and decide if we need more information later on? I can shelf this and revise it later on. And I agree, more caution is better

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

having it in a previous version like this we can always refer back and copy+paste it in if the group thinks it is fine, but for now i would delete :(

# install required packages
install.packages(c("readr", "data.table", "sf", "tidyverse", "tigris",
"dplyr"))
pak::pak("NIEHS/amadeus@1.1.4")
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

install amadeus from CRAN. most recent version is 1.2.3


We will start with State level data (SID, SEDD, SASD)

### Read and format HCUP datafiles
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In this section I would be very specific about what each line of code does. for example, what does SEDD stand for? What is fwf_positions function? What is the expected output?

When writing demos, it is good practice to use the full package name and :: to make it clear to readers where each function comes from like you did with amadeus::download_hms(... and tigris:zctas(...

Cleaned some descriptions and added an image for clarification on fwf().
@dariusmb85 dariusmb85 merged commit ab0620e into staging Feb 28, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants