harm-matthias-harms / rpm Goto Github PK

As a user, I want to delete my own medical cases to not spam the database with test cases.

Different use cases exist, where I may want to delete an exercise. Later it must be ensured, that resources like injects, codes, etc. are also deleted.

To assign injects in an exercise, teams are needed to fulfill the task. Teams are a global resource, to keep track of them even if they are participating in different exercises. A use case could be that a team should not be assigned to the same medical case multiple times.

Data structure:

{
  name: string,
  author: {
    id: bson.ObjectID,
    username: string
  },
  editor: {
    id: bson.ObjectID,
    username: string
  },
  created_at: Time,
  updated_at: Time,
  type: ["AMP", "AMPS", "EMT 1", "EMT 1 mobile", "EMT 2", "EMT 3", "other"],
  medivac: bool
}

As a user, I want to create an exercise to be able to assign different roles to users and manage injects for different teams.

As a user, I want to be able to create an account to use the application.

Acceptance criteria:

• user name provided
• email address provided
• password provided
• password verified
• Snackbar when register fails
• Redirect, if an account already exists
• Redirect, if an account is successfully created

To ensure quality and give opinions medical cases should be commentable.

Comment should have the following data:

• Author
• Time
• Message
• Subcomments

I may want to make changes to the exercise. Dependencies on teams and users.

Both are not needed anymore, because a user could filter by his name.

The backend tests need a refactor:

• Extract setup function to make the tests more readable
• Cleanup after tests not before
• Test more error cases

The user can view a page, where he can edit his personal information.

Acceptance criteria:

• Change email
• Need to verify the new email
• Change password
• Change user-name
• Delete account

The sidebar opens over the viewport.

Good medical cases are a foundation for every working exercise producing good results and learning effects. To handle medical cases in its entirety, different functions need to be provided. This Epic will list all depending user stories. Over time different user stories may be added.

User stories:

• Create medical cases (#29)
• Update medical cases (#30)
• Delete medical cases (#31)
• Print medical case (#33)
• Evolving medical cases (advanced)(#32)
• Filter medical cases (#63)
• Comment medical cases (#34)
• Rate medical cases (#35)

As a user, I want to delete my own presets.

Acceptance criteria:

• Preset is deleted.
• Can only delete own presets.

The tests in the backend should end fatally if an error in any called method exists.

Requirements:

• Jest frontend
• Cypress frontend
• Backend test
• Build frontend
• Build backend
• Push frontend-image
• Push backend-image
• Only on master
• Badge in Readme

As a user, I want to have a landing page. There I can find information about the rpm. The more features get implemented the more should be shown later on.

As a provider, I want to secure my app vs bots.

Acceptance criteria:

• A registered user gets a verification email sent.
• He can confirm it.
• He can use the application if he is verified.
• He can trigger a resend.

If someone is going into cardiac arrest zero values are possible and could be shown. It must be evaluated if it is possible to differentiate null and zero values.

The install section in the main readme and the one in deploy should have the same instructions.

As different locations need different data it is preferable to have different printing view. Therefor different documents need to be created. Printing will make the most sense in terms of an inject. But specific parts can be generated just by the medical case, like live sign views.

A medical case should only be shown in an inject, if it is approved, by anyone including the author. Also, medical cases, which need to be reviewed should be easily filterable.

Requirements:

• Docker-Compose file with env variables
• Database backup script
• nignx config
• apache config

Example

medical_cases/review activates "All" and Review

If the number of teams grows over time, they should be searchable to improve usability.

All information can be viewed in the changes in the merge request.

To have a quick overview of all medical cases they should be rateable. This is done in a 5-star manner. A rating under 3 stars needs a text message, why it has such a bad rating to improve the medical case.

As a user, I want to have presets for the vital signs in a medical case. This offers me the fast creation of medical cases.

Acceptance criteria:

• Offer a backend method for post requests
• Offer a form to create presets
• Offer a table to see presets
• Offer a show function

Fields of a preset:

• author required
• created_at required
• updated_at required
• edited_by
• name required
• vital signs
  • Onset of symptoms - text
  • AVPU - [Altert, Voice, Pain, Unresponsive] - select
  • Mobility - text
  • Respiratory rate - breath per minute - integer
  • Pulse - bpm - integer
  • Temperatur - °C - float
  • Capillary refill - float
  • Blood pressure - systolic / diastolic - integer/integer
  • Oxygen saturation - percent - integer
  • weight - kg - float
  • heigth - cm - integer

As a user, I want to edit every medical case to ensure its quality. Therefore the time and user, who updated the case should be stored for transparency.

Setup of the frontend in a /frontend folder
Requirements:

• Nuxt.JS
• Typescript
• Axios
• Store
• Env variables
• Jest testing
• Optimized Dockerfile
• Cypress e2e testing
• readme

As an author, I would like to delete a file from one of my medical cases.

When creating and editing a medical case it should be possible to select a preset for the vital signs.

The Backend should have unified error messages. For better readability and usage in the frontend.

As the app needs a backend, it should be located in a /backend folder.
Following requirements needs to be fulfilled:

• Based on https://github.com/harm-matthias-harms/echo-template
• Readme instructions for run, test and build
• Optimized production Dockerfile
• JWT secret from env
• Connection to MongoDB

There could be reasons to make changes to teams over time, so it should be possible to update them.

By European law each website needs a cookie hint, to inform the user about cookies used on the website.

Acceptance criteria:

• Inform the user about cookies for authentification.

There could be reasons to delete a team, but only the author should be able to delete his team

Error in new medical case vital sign section. The error seems to be in the select preset autocompletion.

As a user, I want to create medical cases to use them later in an exercise.

Cursive ones need to be checked if this is part of a medical case or inject.

Acceptance criteria:

• created_by required
• updated_by
• created_at required
• updated_at required
• data:
  • general information:
    • surgical - boolean
    • need for hospilisation - boolean
    • USAR - boolean
    • Medivac - boolean
    • Triage - 3 way drop down
    • short summary
    • age - dropdown
    • gender - dropdown
  • medical history
    • problems/condition - text
    • Vaccinations - text
    • Allergiees - text
    • Medication - text
    • Implantable devices - text
  • vital signs (also preload from presets)
    • Onset of symptoms - text
    • AVPU - [Altert, Voice, Pain, Unresponsive] - select
    • Mobility - text
    • Respiratory rate - breath per minute - integer
    • Pulse - bpm - integer
    • Temperatur - °C - float
    • Capillary refill - float
    • Blood pressure - systolic / diastolic - integer/integer
    • Oxygen saturation - percent - integer
    • weight - kg - float
    • heigth - cm - integer
  • Expectations
    • general status - text
    • on examination
    • Expectations and outcome
  • Makeup - text
  • Other Information
  • Documents - files under 15 MB (resize images)

We should stream new data via WebSocket.

First, we should test with presets and medical cases. Later different kind like injects should follow.

As a user, I may want to update my preset. Therefore a form should be provided. I also want to update presets from other users. It should be stored, that I was the one who updated the preset.

Acceptance criteria:

• Preset is updated.
• Editor is stored.
• Time of editing is stored.

All information can be viewed in the changes in the merge request.

The readme should provide the following information:

• What is this project about?
• How to use it?
• How to develop and test?
• Env variables backend / Options

As a user, I want to log into the application.

Acceptance criteria:

• User can log in with email password
• User can log in with user name password
• User receives a valid JWT Token

To mark a good transition in therapy medical cases should evolve over time. Therefore it should be analyzed how this can be done in a simple and graphical easy way. More will follow later.

Searching medical cases would improve the usability.

My presets and medical cases are not shown if I haven't created one yet.

Presets should be possible to filter by title and author name.

It would be helpful if the medical cases could be tagged with different categories. This would make them later easily searchable and would make the selection of a medical case for an inject easier.

As a makeup center, I don't want to sign in as a normal user. Therefore I want to enter a code.

Acceptance criteria:

• Generate code
• Enter Code
• Store access rights at code