Skip to main content
Version: 3.0

Tag

A tag in Care is a reusable label that you attach to a record, such as a patient, an encounter, or an order. An administrator defines each tag one time, and staff then apply it to records of one resource type. Tags let a deployment add its own vocabulary — diet notes, safety alerts, drug groups — on top of the clinical model, and filter records by that vocabulary.

Key Attributes​

ComponentsWhat it captures
Display nameThe label that users see on the record.
CategoryThe group that the tag belongs to, such as Clinical or Safety.
ResourceThe one record type that the tag applies to, such as Patient or Encounter.
PriorityThe order weight of the tag in a list. A lower number shows first.
DescriptionA short text that tells staff when to use the tag.
StatusShows if staff can apply the tag to new records.
Managing OrganizationThe organization or facility department that governs the tag.
Parent TagThe broader tag above this tag in the tag tree.

Resource​

A tag applies to one resource type only. You select the resource type when you create the tag, and you cannot change it later. Care offers these resource types:

Patient, Encounter, Token Booking, Activity Definition, Service Request, Charge Item, Charge Item Definition, Medication Request Prescription, Delivery Order, Request Order, and Account.

A Patient tag can never go on an encounter. This keeps the vocabulary of each record type clean.

Tag tree​

Tags form a tree, so a deployment can go from broad to narrow:

Allergy → Drug Allergy → Penicillin Allergy

A tag with no parent is a root tag. A child tag makes its parent more specific, and it keeps the resource type of the parent. Care shows the full path on the record, for example "Allergy: Drug Allergy". You can apply only one tag from each tree to the same record.

Scope​

Each tag has one scope. An instance tag is available in every facility of the deployment. A facility tag is available in one facility only. A Managing Organization can narrow which staff can apply the tag.

A patient carries instance tags and facility tags at the same time. The facility tags are visible with the patient in that facility.

Status​

StatusDescription
ActiveStaff can apply the tag to new records.
ArchivedThe tag is retired. Records that carry the tag keep it, and the history stays correct.

Care archives a tag instead of deleting it. The past classification of a record therefore stays valid.