| Literature DB >> 35557480 |
Jane Ireson1,2, Amy Taylor2,3, Ed Richardson, Beatrice Greenfield, Georgina Jones1.
Abstract
BACKGROUND: In 2020, the long-lasting effects of the Covid-19 virus were not included in public messages of risks to public health. Long Covid emerged as a novel and enigmatic illness with a serious and life-changing impact. Long Covid is poorly explained by objective medical tests, leading to widespread disbelief and stigma associated with the condition. The aim of this organic research is to explore the physical and epistemic challenges of living with Long Covid.Entities:
Keywords: Long Covid; United Kingdom; epistemic injustice; invisibility; lived experience; person-centred care; qualitative
Mesh:
Year: 2022 PMID: 35557480 PMCID: PMC9327841 DOI: 10.1111/hex.13518
Source DB: PubMed Journal: Health Expect ISSN: 1369-6513 Impact factor: 3.318
Figure A1Percentage of submissions by gender.
Figure A2Percentage of submissions by age.
Figure A3Percentage of submissions by ethnicity.
Figure A4Percentage of submissions that had either a Covid‐19 ANTIGEN or ANTIBODY test and results.
Project team expertize/background
| Team member | Expertize/background |
|---|---|
| B. G. | Consumer representative (Covid‐19 diagnosis & long‐standing myalgic encephalomyelitis) |
| E. R. | Consumer representative (Covid‐19 diagnosis), website cocreator/owner, researcher |
| G. J. | Health psychologist, mixed‐method researcher |
| J. I. | Consumer representative (Covid‐19 diagnosis), website cocreator/owner, specialist nurse, researcher |
| A. T. | Therapeutic radiographer, qualitative researcher, coproduction specialist |
Figure 1Three‐step process of data analysis.
Research process
| Format | Process | |
|---|---|---|
| Part 1: Coding | The four project team members were divided into two subteams (E. R. + A. T. & B. G. + J. I.). Thirty‐three stories were allocated to each subteam for analysis. |
|
| Each individual conducted a line‐by‐line review of their allocated 33 stories. | ||
| Each subteam collaborated on a single Quirkos workspace. | Any relevant text was highlighted, and a ‘Quirk’ code was created on the workspace based on the content of the text. | |
| Texts perceived to be related to the same theme were added to existing Quirk categories. | ||
| New Quirk codes were created when appropriate. | ||
| Process was repeated a further three times to ensure data saturation of each story. | ||
| For emergent themes, codes were organized into loose clusters for discussions within each analysis subteam. | ||
|
| ||
| Codes and emergent themes of the 33 stories were discussed in the collective subteams. | ||
| Duplications were merged/removed, and a consensus of meaning was generated across each subteam. | ||
| Showing objectivity and dependability. | ||
| 2. Theme development | Four project team members (B. G., J. I., E. R., A. T.). |
|
| Collaboration was on a single Quirkos workspace. | The two workspaces were merged enabling the team to collectively discuss the codes generated by each subteam. | |
| A table of themes and a thematic map presented the key themes and subthemes enhancing the team's conceptual understanding of the data through visual organization | ||
| The data codes and thematic map were collectively reviewed and discussed to establish coproduced themes. | ||
| During coding, emergent Quirk categories were labelled with the language used by the participants. At this stage, the categories were relabelled where appropriate using inclusive language, to incorporate distinctions in the data. | ||
| A system of indexing was established, visually reviewing the categories to establish similarities, contrary and interconnectivity. | ||
| The ‘drag and drop’ function of Quirkos was used to merge similar categories when duplicates were identified and designate categories as a ‘parent’ when subthemes emerged. | ||
| Quotes assigned to each code were examined to ensure they were representative of the theme. Themes were removed or reassigned where appropriate. | ||
| Discussion supported by the participant quotes ensured all decisions were based on a mutual agreement and reflective of the data. | ||
| The table of themes and thematic map were updated to reflect the iterative changes arising from the group analysis. | ||
| Showing objectivity and dependability. | ||
| 3. Theme finalization and representation | The four project team members (E. R., A. T., B. G., J. I.) plus G. J. | The development and agreement of the final themes were an iterative process occurring through a series of team meetings with all members of the project. |
| The table of themes and thematic map were updated at each stage of discussion until the final themes and subthemes were agreed upon. All emergent themes and subthemes were supported by direct participant quotes. | ||
| Showing transferability. |
Figure 2Process of data analysis.
Figure 3Key themes.