Hi, we're adding Tasks to our EHR and had a couple of questions around these requirements and if our assumptions are correct. Requirements: 1. Show the task

code

in the front-end as the task title 2. Query a set of tasks by an enum (such as

TASK_A

or

TASK_B

) to report upon task completion rates, tasks in-progress, etc. I'm assuming we can achieve this by adding an additional

Identifier

to the Task with `use=secondary`and

value=TASK_A

. This would allow us to use the

code

as the UI display text and a secondary identifier as a queryable enum, right?

Hi @taylorqj I think i don't quite understand the use case of the enum. Would they be an alternate name for the task type, or more like a status for the task?

We're looking for a way to query a group of tasks by an identifier -- if this was outside of FHIR we would probably add a

type

with a value of

SOME_TASK_TYPE

. We'd like to keep the "name" of the task ephemeral if possible.

I'd actually probably recommend using

code

for the

SOME_TASK_TYPE

, and then use

description

for the editable text.

Awesome, we'll update our tasks to use description for the editable text! Thank you for the help @rahul1