Skip to content

[EPIC] Code Management #1315

@kplaneaux

Description

@kplaneaux

Background

With TES code sets now being commonly expanded into the 10,000+ codes range, there are two potential problems users may face:

  1. Challenges with quickly understanding the contents of a code set of that size (types of codes, # of similar codes, logical groupings, etc.)
  2. Over-retention of data due to inclusion of undesired codes that cannot be removed or disabled currently

There are also potential efficiencies we can realize by unifying how codes of any kind (code sets, custom codes, etc.) are managed.

🏗️ Potential User Stories

  • As a user, I can see what types of codes I have in a code set, so that I can more easily determine what to do with them
  • As a user, I can modify the codes included in condition code sets, so that I only keep the ones that I really need

✏️ Potential code actions

  • Enable/disable (or add/delete) code set codes
  • Enable/disable (or add/delete) code set reporting specification groupers (RSGs) or additional context groupers (ACGs)
  • Add/delete code sets
  • Add/upload/edit/delete custom codes
  • Export codes

🎨 Design Notes

  • We should consider how we'll bring in TES updates -> how will we know if a particular configuration is attached to particular code sets if we're slicing and dicing them? How will we bring in those updates (codes added or removed) and reconcile them with what the user currently has?
  • Need to decide how we want to treat condition code sets: whether they're just a bunch of codes you can add any number of, or if it comes as a package and you need to down-select. Do/should the excluded codes remain somewhere visible in the configuration?
  • Might want to consider how to make bulk actions easier (e.g. enabling or disabling larger groupings of codes like RSGs or ACGs) since we're working with thousands of codes
  • Need to think about how this might interact with codes the user might specify to omit rather than retain - will that be managed in the same place in a different tab? Some option for each code to either be a retained or omitted code? etc.

📜 Additional context

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions