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

Develop generic needs assessment #1

Open
1 of 6 tasks
tareko opened this issue May 25, 2014 · 3 comments
Open
1 of 6 tasks

Develop generic needs assessment #1

tareko opened this issue May 25, 2014 · 3 comments
Assignees

Comments

@tareko
Copy link
Member

tareko commented May 25, 2014

Currently, here is the needs assessment draft:

- [ ] **Gut check**: Does it make sense to make this device
- [x] **Other people's gut check**: Talk to at least 2 other clinical physicians to ask if these devices are actually needed
- [ ] **Target people's gut check**: Talk to at least 2 'on-the-ground' physicians in high-needs areas to ask if these devices are actually needed
- [ ] **Price check**: How much does the device currently cost?
- [ ] **Price reduction**: How much do we anticipate we can drop the price?
- [ ] **Safety check**: Can we make this product safely for the builders and for the users?

Linked to GliaX/pulseox#3

Here is the task list for completion of this issue:

  • @tareko to develop first draft
  • @amashari to review
  • Send to external reviewers for comment
    • Who?
  • Send to group for final comment
  • Commit to wiki
@tareko tareko self-assigned this May 25, 2014
@tareko
Copy link
Member Author

tareko commented May 25, 2014

@amashari Perhaps developing the generic needs assessment list should be part of the 'meta' list so we can have a template for each project.

@tareko
Copy link
Member Author

tareko commented Jan 8, 2015

@amymiller The idea here is to develop a template for use when we come up with other devices. And so, device-specific information doesn't belong in this ticket. Ostensibly, each device should have its information there.

However, it might be an idea to amalgamate all of the needs assessments within the Meta repository somewhere. Thoughts?

@amymiller
Copy link

@tareko Makes sense to me however I am not sure how to move forward with this issue. I have it as an issue to discuss when we talk next.

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

No branches or pull requests

2 participants