Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

security considerations mentioning access restrictions based on content #83

Open
JohnMoehrke opened this issue May 15, 2020 · 3 comments
Labels
Connectathon 24 Issues from Connectathon 24

Comments

@JohnMoehrke
Copy link
Collaborator

Note that some measureReports may be against sensitive subjects. For example where a measureReport is specific to regions, these reports might not be available outside the catchment area for that location (e.g. a state Public Health authority would have read access to all regions within that state, but might not have access to any region outside their state).

@JohnMoehrke JohnMoehrke self-assigned this May 15, 2020
@szitello
Copy link

This crisis has not only created opportunities for technology solutions but also shown us the socio-political difficulties that expansive technologies bring. And so that becomes a technical issue to solve. Some form of interest/proximity areas may seem to be useful. Surely NJ CT and PA all have strong interests in what is happening in NY. Conversing, the governors of some states don't even want their own residents know their numbers. Facilitating such behavior seems wrong at some level, but it cuts both ways. So what is the granularity, does each Population have its own sensitivity, should it be at Measure definition level. Do we have Public consumers and Private consumers. Thats feels like a closed system, and runs counter to what we have already seen in the market and sort of takes the public out of Public Health, already facing down public scrutiny.

@keithboone keithboone added the Connectathon 24 Issues from Connectathon 24 label May 30, 2020
@keithboone
Copy link
Member

Address the issue of reidentifiable data sets in measure development process. Partly addressed in defining your measure definition, but also in definition of reporting region.

@keithboone keithboone added this to the Post-Connectathon Draft milestone Jun 29, 2020
@JohnMoehrke JohnMoehrke removed their assignment Mar 30, 2022
@JohnMoehrke
Copy link
Collaborator Author

I removed my assignment as I am not sure if this is still an issue, and a not sure how to determine that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Connectathon 24 Issues from Connectathon 24
Projects
None yet
Development

No branches or pull requests

3 participants