Reading experiences of care through interviews

An event sequence can show recorded stages. Interview material can help us understand how people describe moving through those stages. Here we explore listening, access and coordination using a new, clearly labelled fictional teaching dataset.

The companion file contains 24 excerpts from 12 invented interviews, with two excerpts per interview. It has no shared participants with SAM’s synthetic Endometriosis Diagnostic Delay Pathways sample. Keeping the examples separate allows us to connect analytical questions without creating a false data linkage.

Start with an account

Read these two excerpts from the same invented interview:

The pair suggests a distinction between the quality of individual encounters and the work of coordinating care. A first memo might ask who connects information, how responsibility for the next step is understood, and what a named contact changes in the account.

Make a coding decision visible

Upload the teaching CSV, map text as the text field and preserve record_id and interview_id. Open Classic Coding, choose Qualitative, and review the active code scheme. The starter codebook contains Being heard, Practical access, Continuity and coordination, Navigating uncertainty and Self-advocacy.

Apply Continuity and coordination to SYN-CARE-07-A because it describes carrying information between services. A second code, Self-advocacy, is worth discussing. Does carrying information show an active effort to make a need visible, or might it describe an administrative burden? The answer depends on the definition and the wider account. Record the boundary decision so that later coding can be reviewed consistently.

These codes are teaching suggestions. Develop their definitions in relation to your question and material. A useful revision includes what belongs, what falls outside the code and an example record ID.

Seek variation deliberately

Compare SYN-CARE-03-A, where a convenient evening appointment is paired with a rushed conversation, with SYN-CARE-11-B, where a supportive encounter follows difficulty attending. The contrast suggests examining access arrangements and the encounter as related but distinct parts of experience.

Then read SYN-CARE-09-B, where the speaker wants one clear explanation rather than more messages. Frequency of contact may matter differently across accounts. Preserve that variation when developing an interpretation of support.

Sentiment can add a reading of evaluative tone. Stance requires a stated target: for the excerpt requesting a telephone option, a useful proposition is “Telephone access should remain available alongside online forms.” Keep that target beside the stance categories so that the interpretation can be inspected.

Develop and review in the Studio

Adaptive Coding Studio can carry the coding approach into a cycle of reviewed examples, learning and evaluation. Use separate evaluation material when comparing profiles. Approve the version you choose, then select where to apply it and inspect the resulting coding. Keep the codebook, profile version and review conditions in the project record.

This small exercise supports practice and discussion. It does not supply the distinct-record evidence required for SAM’s current overall Coding Quality Score. Consult the saved method contract and report the evidence actually available for the study.

Return from Results to the account

Use Results to explore the corpus and identify material for further reading. Narrative Synthesis can help organise an account around source anchors; follow those anchors back to the excerpts and interview pairs. Because this teaching file has no dates, use an undated synthesis rather than implying a chronology through Narrative Timeline.

Export the coded texts and codebook, then write a memo that names the supporting and contrasting IDs. The new question might be: “How do institutional accounts describe coordination and support?” The next article follows that question into public records.

Download the fictional interview CSV · Starter codebook · Read the provenance note

Earlier in the series: Exploring diagnostic journeys with Pathways.