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.

Sign up for GitHub

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

Jump to bottom

Implementation overview: Operations #507

Open
timonmasberg opened this issue Nov 16, 2023 · 0 comments
Open

Implementation overview: Operations #507

timonmasberg opened this issue Nov 16, 2023 · 0 comments
Labels
status:needs-triage type:epic A theme of work that contains sub-tasks type:feature-request
Milestone
MVP

Comments

@timonmasberg
Copy link
Member

Feedback from UI/UX study:

  • In Operation Dialog, show Units like in Divera (List with units to click)
  • Directions (geo point directions e.g. Anleger or WRPs) should be included in alerts (Divera description)
  • Get Operation Location from map, Create Operation via right click on map
  • Automatically add Operation Types (If Divera Alert => SEG)
  • Operation Type should have clear descriptions on when to use them
  • Operations should only be deactivated and archived when "deleted", should be restorable
  • Patient data should not be visible to everyone
  • Keep autosave and sync
@timonmasberg timonmasberg added status:needs-triage type:feature-request type:epic A theme of work that contains sub-tasks labels Nov 16, 2023
@timonmasberg timonmasberg added this to the MVP milestone Nov 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
status:needs-triage type:epic A theme of work that contains sub-tasks type:feature-request
Projects
None yet
Milestone
MVP
Development

No branches or pull requests
1 participant
@timonmasberg