UWSpace is currently experiencing technical difficulties resulting from its recent migration to a new version of its software. These technical issues are not affecting the submission and browse features of the site. UWaterloo community members may continue submitting items to UWSpace. We apologize for the inconvenience, and are actively working to resolve these technical issues.
 

Exploring the Requisites and Design Requirements for Adding ‘Reason for Use’ Information to Prescription Labels

dc.contributor.authorHussein, Thana
dc.date.accessioned2018-10-01T15:06:18Z
dc.date.available2018-10-01T15:06:18Z
dc.date.issued2018-10-01
dc.date.submitted2018-09-26
dc.description.abstractIndividuals with multiple medical conditions and polypharmacy are at higher risk of inappropriate prescribing and consequent adverse drug events. Moreover, individuals may not adequately understand the therapeutic intention of their medications as this information is conveyed to patients inconsistently from their healthcare providers. One way to address this problem is to inform the patient of the reason for using a prescribed medication. The present research is an initial attempt to design a prescription label that incorporates Reason for Use (RFU) by first understanding how patients are currently receiving RFU information, their feelings of being provided with that information in a future health care system, and secondly, exploring their design preferences for this newly designed prescription label. Twenty patients (10 female; 10 male) throughout the Kitchener-Waterloo region were interviewed using a semi-structured questionnaire and 15 (9 female; 6 male) of these individuals participated in a design workshop that aimed to understand where the RFU information should be placed on a prescription label, the amount of detail, language, and overall layout of the label. Participant responses were analyzed thoroughly to discover important and/or frequent themes. Results from the study revealed that all 20 patients are in favor of having RFU information shared with their pharmacist and overall, would feel more informed if they were provided with RFU information from their healthcare providers. Results from the design workshop revealed that patients preferred RFU information printed in one to three words (80%) with its placement underneath the dosage instructions (33.3%) and/or next to the drug name (46.7%) because it felt the most ‘logical’ (73.3%). The participants showed a high preference for adding RFU to the prescription label for sake of being better-informed and more capable of participating fully in health decisions. Results from this study suggest a need for including RFU into the Ontario medication prescribing practices and adopting recently released United States Pharmacopeia (USP) patient-centered prescription label standards, which also include adding RFU to the labels.en
dc.identifier.urihttp://hdl.handle.net/10012/13965
dc.language.isoenen
dc.pendingfalse
dc.publisherUniversity of Waterlooen
dc.subjectPrescription Labelen
dc.subjectCo-Designen
dc.subjectParticipatory Designen
dc.subjectMedicationen
dc.subjectPatienten
dc.subjectHealthcare Systemen
dc.titleExploring the Requisites and Design Requirements for Adding ‘Reason for Use’ Information to Prescription Labelsen
dc.typeMaster Thesisen
uws-etd.degreeMaster of Applied Scienceen
uws-etd.degree.departmentSystems Design Engineeringen
uws-etd.degree.disciplineSystem Design Engineeringen
uws-etd.degree.grantorUniversity of Waterlooen
uws.contributor.advisorBurns, Catherine
uws.contributor.affiliation1Faculty of Engineeringen
uws.peerReviewStatusUnrevieweden
uws.published.cityWaterlooen
uws.published.countryCanadaen
uws.published.provinceOntarioen
uws.scholarLevelGraduateen
uws.typeOfResourceTexten

Files

Original bundle
Now showing 1 - 1 of 1
Loading...
Thumbnail Image
Name:
Hussein_Thana.pdf
Size:
1.16 MB
Format:
Adobe Portable Document Format
Description:
License bundle
Now showing 1 - 1 of 1
No Thumbnail Available
Name:
license.txt
Size:
6.08 KB
Format:
Item-specific license agreed upon to submission
Description: