opensafely-core / opensafely-core/opencodelists

User research - impact of sharing all codes to open code usage tool

Open
#2,615 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

initiative:codelist-builder
Dominant language
Python
Stars
60
Forks
16
Avg merge
4d 12h
Merged PRs (30d)
17

Description

Why are we doing this?

It was suggested that the Code Usage Tool can present all the codes in a codelist, selected or not, to help users decide which codes are useful. However, by including all codes regardless of selection status then you could lose the ability to see the impact of selection of codes on your coverage.

How will we know when it's done?

We want to do some user research to test the assumption that users will find it useful to see all codes regardless of selection status in the Code Usage tool to help decide which to include

  • find an example user test to test an extreme? i.e. a codelist with 100s of codes to review?
  • any issues that might impede the user's ability to effectively decide if a code should be included/not are highlighted - i.e. visibility in Code Usage Tool, although this is out of scope for this ticket, any issues can be picked up and shared with Arina/Milan for further improvements

What are we doing?

  • talk with Arina/Milan to set up user test
  • running user test with 2-3 users
  • decide whether all codes (selected/unselected) should be shared to Code Usage tool per #2553

Defining delivery tasks guidance

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading issue #2553 and talking with Arina and Milan to define the user test. Run the test with 2–3 users, including an example codelist with hundreds of codes, and record any barriers to deciding which codes to include. Done means sharing the findings and deciding whether selected and unselected codes should appear in the Code Usage Tool.

Written by the indexing model from the issue text.

Assessment

Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.