Tag
Definition
A tag in Care is a label that you define once and then attach to records such as encounters, service requests, and accounts. You define a tag for one facility, and staff at that facility can then apply it. A superuser can also define an instance-wide tag that every facility can use.
Note: Care has no FHIR R5 resource for a tag. A tag works like a coded value that your organization defines for its own use.
Note: This document covers the tag definition only. To attach a tag to a record or remove it, read the documentation of that record. For encounters, read Manage Encounter tags.
Key Attributes
| Components | What it captures |
|---|---|
| Display | The name of the tag that Care shows to users. |
| Category | The subject area of the tag. |
| Resource | The type of record that you can attach the tag to. You select this when you create the tag, and you cannot change it later. |
| Priority | A number that sets the order of the tag in lists. The default value is 100. |
| Status | Whether staff can apply the tag. |
| Description | A short text that explains the purpose of the tag. |
| Managing Organization | The facility organization that manages the tag. For an instance-wide tag, this is an instance-level organization. |
| Has Children | Whether the tag has child tags under it. |
Category
Category groups tags by subject area. Select one of these values:
- Diet
- Drug
- Lab
- Admin
- Contact
- Clinical
- Behavioral
- Research
- Advance Directive
- Safety
Resource
Resource sets the type of record that staff can attach the tag to. Select one of these values:
- Encounter
- Service Request
- Charge Item
- Charge Item Definition
- Account
- Token Booking
- Medication Request Prescription
- Supply Request Order
- Supply Delivery Order
- Patient
Parent and child tags
You can arrange tags in a tree. A root tag holds one or more child tags. A child tag takes the Category and the Resource of its parent tag, and you cannot change these two fields on the child tag.
Child tags under the same parent work as a set of choices. Staff can apply only one child tag from a parent group to a record at a time. If staff select a different child tag under the same parent, Care replaces the earlier selection. A root tag without children has no such limit, and staff can combine it with other tags.
Status
Care has no delete action for a tag. To stop the use of a tag, set its status to Archived.
| Status | Description |
|---|---|
| Active | Staff can apply the tag to records. |
| Archived | Staff can no longer apply the tag to records. |
To archive a root tag, edit the tag. Change the Status field to Archived. Care has no one-click archive action for a root tag. For a child tag, Care shows an Archive action. Care asks you to confirm before it archives the child tag.
Permissions
| Permission | Who has it | What it allows |
|---|---|---|
| Can Create Tag Config on Facility | Facility Admin, Admin | Create and update a tag. |
| Can Apply Tag Config to Resources | Facility Admin, Admin, Staff, Doctor, Nurse, Pharmacist | Attach a tag to a record and remove it. |
| Can Read Tag Config | Facility Admin, Administrator, Admin, Staff, Doctor, Nurse, Volunteer, Pharmacist | View tags. |
Note: Only a superuser can create or update an instance-wide tag.
Where to find tags
Care shows facility tags in the Settings area of a facility, under Tag config. Care shows instance-wide tags in a separate global Admin area.
Related
- Flow: Create a tag
- Flow: Create a child tag
- Flow: View tags
- Flow: Edit a tag
- Flow: Archive a child tag
- Concept: Encounter