Personal Medication List Programme

This programme is intended to view a sample medication list. This programme came into being because there are still paper lists for medication intake in Germany, which are often not up to date or going to lose. The programme is intended to remedy this situation and make it possible to make timely entries both on the patient's side and on the doctor's side and to make the digital list accessible to emergency services in case of an emergency.

How to use

As an example, the patient ID you can use is '123456'. Otherwise, the programme creates a new patient ID, if you want it. You can create a new medication list, view and manage your existing list. You can update medications or add new medications. It`s not possible to delete medications; you can only set a 'Stop Date' on it. This is important to keep an overview of all medications (current AND past) for your (potential) doctors.

The live website on Heroku can be accessed at the following link: View my Live Website on Heroku here

CONTENTS

• Introduction
• How to use
• Features
  • Existing features
  • Proccess flow
  • Future features
• Testing
  • Validator Testing
  • Bugs
• Technologies Used
  • Languages Used
  • Frameworks, Libraries and Programs Used
• Deployment
• Credits

Features

Existing features

• Welcome Screen

  • The first screen shows the name of the programme and asks the user to type his/her name.
  • If a name is not entered or if the user only types in numbers, a validation message appears and informing the user that his/her input is not valid.
  • The name is then requested again.

  

  • Once a name is entered, the programme moves to the introduction.
  • The user is asked whether he already has a patient ID or needs a new one.
  • If the choice is not valid, a validation message appears and informing the user that his/her input is not valid.
  • The choice is then requested again.

  

• New patient

  • When the user selects the new patient ID, the programme generates a new worksheet with a randomised ID.
  • Then the programme asks the user to type the ID. The programme also asks this to users with a known ID.

  

• Old patient

  • If the user chooses that he/she already has a patient ID, the programme will ask them to type this in.
  • If the patient ID input is not valid, a validation message appears and informing the user that his/her input is not valid.
  • The patient ID input is then requested again.
  • If the patient ID input is valid, the user is given three options: show list, add a medication, update an existing mediaction.

  

  • If the input for one of the three options is not valid, a validation message appears and informing the user that his/her input is not valid.
  • The three options input is then requested again.

  

  • If the input is valid, the user goes further to show list, add a medication or update an existing medication.

• Show list

  • If the user chooses to display the list, there are two options: Either the list is displayed or the user receives a message that the list is empty.
  • If the list is empty, there are two options: add a medication or return to the main menu.
  • If the input for one of the two options is not valid, a validation message appears and informing the user that his/her input is not valid.
  • The two options input is then requested again.

  

  • If the list is not empty, the programme shows the list of medications.
  • After that the user gets three options: add a medication, update a medication or return to the main menu.
  • If the input for one of the three options is not valid, a validation message appears and informing the user that his/her input is not valid.
  • The three options input is then requested again.

  

  • The 'return to the main menu' option brings up the initial screen again with the input of the name.

  

  • Add medication
    • If the user chooses to add a medication: The programme asks the user to enter the individual details: name of the medication, form of the medication, strength of the medication, dosage of the medication, what is the medicine used for, when you take it, start date, stop date and special instructions. Only the stop date and the special instructions can be leave empty.
    • If other fields are empty, a validation message appears and informing the user that his/her input is not valid.
    • The add medication input is then requested again.

  

  • After entering the data, the new medication appears and the user is asked whether the details entered are correct.

  

  • If the input for one of the two options is not valid, a validation message appears and informing the user that his/her input is not valid.
  • The add medication input then appears again.

  

  • If the user confirms the medication entry, the medication is added to the list and the user is taken back to the main menu.

  

  • If the user doesn`t confirm the medication entry, he/she gets two options: re-entry the medication details or return to the main menu.
  • If the input for one of the two options is not valid, a validation message appears and informing the user that his/her input is not valid.
  • The two options input is then requested again.

  

  • If the user chooses to re-enter the medication, he/she will be returned to this input.
  • If the user selects 'return to the main menu', he/she will be returned to the initial screen with the input of the name.

  

• Update medication

  • If the user chooses to update an existing medication: The user receives an overview of the existing medicines in the list.
  • The user can select the line that he/she wants to update.

  

  • If the input for the row is not valid, a validation message appears and informing the user that his/her input is not valid.
  • The row input is then requested again.

  

  • If the input for the row is valid, the user can update his/her medication.
  • After the input of the medication details, a message appears that the medication details updated succesfully and the programme brings the user back to the main menu.

  

  • If the list is empty, the programme brings the user back to the patient ID input.

  

  • Worksheet update
    • If the user successfully adds or updates a medication, the date in the row 'J1' in the worksheet updates automatically.

  

Process Flow

• Below is a flow chart to demonstrate the actions that take place while using the programme:

  

Future features

• In the future, the programme could perhaps be extended with a suitable frontend, so that it can later be used with a user-friendly interface in doctors' surgeries and hospitals as a digital medication list, which also allows direct input from both: doctor and patient. If necessary, it could also be expanded to include tools such as medication reminders on mobile phones or similar.

Testing

I have manually tested this project by doing the following:

• Given invalid inputs
• Tested in my local terminal

The W3C Validator, Jigsaw W3 Validator and PEP8 Validator from Code Institute were used to validate the pages to ensure there were no syntax errors in the project.

Validator Testing

• HTML

  • No errors were returned when passing through the official W3C validator.

• CSS

  • No errors were returned when passing through the official Jigsaw W3 Validator.

• Python

  • The code was run through the Code Institute Python Linter and showed no errors.

  

Remaining Bugs

• No bugs remaining

Technologies used

Languages used

• HTML5: Provides the content and structure
• CSS: Provides the styling
• Python: Provides the functionality

Frameworks - Libraries - Programs Used

• Git
  • Git was used for version control by utilizing the Gitpod terminal to commit to Git and push to GitHub.
• Github
  • GitHub was used to store the project's code after being pushed from Git.
• Am I Responsive
  • Am I responsive was used to create the multi-device mock-up you can see at the start of this README.md file.
• Favicon.io
  • Favicon.io was used for making the site favicon.
• Draw.io
  • Draw.io was used for making the flow chart.
• WC3 Validator, Jigsaw W3 Validator and PEP8 were all used to validate the website.

Deployment

The project was deployed on Heroku using the following method:

• Add dependencies in GitPod to requirements.txt file with command "pip3 freeze > requirements.txt"
• Commit and push to GitHub as usual
• Go to the Heroku Dashboard
• Click "Create new app"
• Name app and select location
• Add Config Vars for Creds and Port in Settings tab
• Add the buildbacks to Python and NodeJS in that order.
• Select appropriate deployment method e.g. GitHub
• Connect to Github and link to repo
• Enable Automatic Deploys and deploy manually
• Click on Deploy.

Credits

• The pictures (background image, favicons) were taken from Pixabay.