Skip to content
This repository has been archived by the owner on Apr 9, 2024. It is now read-only.

Ability to edit and save "Case definitions" #59

Open
aninek opened this issue Sep 27, 2017 · 3 comments
Open

Ability to edit and save "Case definitions" #59

aninek opened this issue Sep 27, 2017 · 3 comments
Labels
Admin Admin Bounded context frontend
Milestone

Comments

@aninek
Copy link
Collaborator

aninek commented Sep 27, 2017

Purpose:
Recognizing that standard approaches may not reflect local realities, Data owners may need to allow teams to change the pre-filled Case definition of a Health risk.

  • Allow user to select "Edit"
  • User selects form field and can rewrite the [Case definition]
  • User must record a reason why the [case definition] is being changed (comment field)
  • System records; new case definition (without overwriting original), timestamp, user details, project affiliation, and comment.

Related to #54 and #60

@RFMoore RFMoore changed the title Ability to edit and save case definitions Ability to edit and save "Case definitions" Sep 29, 2017
@karolikl karolikl added this to the MVP milestone Dec 17, 2017
@karolikl
Copy link
Collaborator

Related to #332

@alexanderhoset
Copy link
Collaborator

Is it ok if I re-write this to fit the mvp design @karolikl ? Case definitions is an meta data to a health risk, not a separate thing

@eprom eprom added the Admin Admin Bounded context label Apr 6, 2018
@eprom
Copy link
Collaborator

eprom commented Sep 3, 2018

@aninek Could you define what a "user" is since this involves access control checks on the backend.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Admin Admin Bounded context frontend
Projects
None yet
Development

No branches or pull requests

4 participants