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

Record should have states for actions complete/reject/accept #29

Closed
blcham opened this issue Dec 6, 2023 · 5 comments
Closed

Record should have states for actions complete/reject/accept #29

blcham opened this issue Dec 6, 2023 · 5 comments
Assignees

Comments

@blcham
Copy link

blcham commented Dec 6, 2023

We have roles:
OA - operator admin
SA - supplier admin

We have following states of record:

    1. open record (manually by "save record" or automatic when record is imported)
    1. valid record (automatic)
    1. completed record (either manually or automatically if valid)
    1. accepted record (manually)
    1. rejected record (manually)

In AVA we have:

  • open
  • closed
  • published
  • unpublished
  • processed
  • unprocessed
  • rejected
  • approved
  • grounded

Image

and we map:

    1. to button "Complete" (closed in AVA) to do "valid record-> completed record"
    1. to button "Approve" to do "accepted record"
    1. to button "Reject" to do "rejected record"

(All buttons from Have posibility in RM to complete set of records are covered)

A/C:

  • design the model in RM and map it to AVA model above
  • implement it in RM backend service related to records
@blcham
Copy link
Author

blcham commented Dec 6, 2023

TODO:

  • we need validated failure record
  • @LaChope can you put mapping of buttons with names for operator and supplier deployments ?

@blcham
Copy link
Author

blcham commented Dec 7, 2023

Here is the mapping:
Image

Here is mapping to icons:
Image

kostobog added a commit that referenced this issue Dec 8, 2023
kostobog added a commit that referenced this issue Dec 8, 2023
kostobog added a commit that referenced this issue Dec 11, 2023
- refactor type of PatientRecord.phase from RecordState to RecordPhase.
kostobog added a commit that referenced this issue Dec 12, 2023
@LaChope
Copy link
Collaborator

LaChope commented Dec 13, 2023

@blcham Just to make sure, there should not be any "Accept" button anymore, only reject right?

blcham added a commit that referenced this issue Dec 13, 2023
@blcham
Copy link
Author

blcham commented Dec 13, 2023

@kostobog still need to refactor labels in ontology "record state" --> "record phase" + there is missing enum "rejected"

@kostobog
Copy link

@blcham labels fixed in #36.

blcham added a commit that referenced this issue Dec 13, 2023
Issues/29 fix phase resource labels and new phase
@blcham blcham closed this as completed Dec 13, 2023
blcham added a commit that referenced this issue Dec 15, 2023
…der-size-by-env-var

[#29] Bind server.max-http-request-header-size to MAX_HTTP_REQUEST_SIZE evn variable
blcham added a commit that referenced this issue Dec 15, 2023
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

3 participants