Release 5

This page is part of the FHIR Specification (v5.0.0: R5 - STU). This is the current published version. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2

FHIR Infrastructure icon Work GroupMaturity Level: 4 Trial UseSecurity Category: Not Classified Compartments: Device, Patient, Practitioner

Detailed Descriptions for the elements in the List resource.

List
Element IdList
Definition

A List is a curated collection of resources, for things such as problem lists, allergy lists, facility list, organization list, etc.

Short DisplayA list is a curated collection of resources
Cardinality0..*
TypeDomainResource
Alternate NamesCollection; WorkingList; Organizer
Summaryfalse
Invariants
Defined on this element
lst-1Rule A list can only have an emptyReason if it is emptyemptyReason.empty() or entry.empty()
List.identifier
Element IdList.identifier
Definition

Identifier for the List assigned for business purposes outside the context of FHIR.

Short DisplayBusiness identifier
NoteThis is a business identifier, not a resource identifier (see discussion)
Cardinality0..*
TypeIdentifier
Summaryfalse
List.status
Element IdList.status
Definition

Indicates the current state of this list.

Short Displaycurrent | retired | entered-in-error
Cardinality1..1
Terminology BindingList Status (Required)
Typecode
Is Modifiertrue (Reason: This element is labeled as a modifier because it is a status element that contains status entered-in-error which means that the resource should not be treated as valid)
Summarytrue
Comments

This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.

List.mode
Element IdList.mode
Definition

How this list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted.

Short Displayworking | snapshot | changes
Cardinality1..1
Terminology BindingList Mode (Required)
Typecode
Is Modifiertrue (Reason: If set to "changes", the list is considered incomplete, while the other two codes indicate the list is complete, which changes the understanding of the elements listed)
Requirements

Lists are used in various ways, and it must be known in what way it is safe to use them.

Summarytrue
Comments

This element is labeled as a modifier because a change list must not be misunderstood as a complete list.

List.title
Element IdList.title
Definition

A label for the list assigned by the author.

Short DisplayDescriptive name for the list
Cardinality0..1
Typestring
Requirements

Allows customization beyond just the code identifying the kind of list.

Summarytrue
List.code
Element IdList.code
Definition

This code defines the purpose of the list - why it was created.

Short DisplayWhat the purpose of this list is
Cardinality0..1
Terminology BindingExample Use Codes for List (Example)
TypeCodeableConcept
Requirements

Lists often contain subsets of resources rather than an exhaustive list. The code identifies what type of subset is included.

Summarytrue
Comments

If there is no code, the purpose of the list is implied where it is used, such as in a document section using Document.section.code.

List.subject
Element IdList.subject
Definition

The common subject(s) (or patient(s)) of the resources that are in the list if there is one (or a set of subjects).

Short DisplayIf all resources have the same subject(s)
Cardinality0..*
TypeReference(Any)
Requirements

The primary purpose of listing the subject explicitly is to help with finding the right list.

Summarytrue
Comments

Some purely arbitrary lists do not have a common subject, so this is optional. Lists having multiple subjects may raise challenges for systems that base access control or other security considerations on linkages to 'subject'. E.g. if a List is associated with multiple Patient subjects, then it would be nominally part of multiple patient compartments, which might drive access rights.

List.encounter
Element IdList.encounter
Definition

The encounter that is the context in which this list was created.

Short DisplayContext in which list created
Cardinality0..1
TypeReference(Encounter)
Summaryfalse
List.date
Element IdList.date
Definition

Date list was last reviewed/revised and determined to be 'current'.

Short DisplayWhen the list was prepared
Cardinality0..1
TypedateTime
Requirements

Identifies how current the list is which affects relevance.

Summarytrue
Comments

The actual important date is the date of currency of the resources that were summarized, but it is usually assumed that these are current when the preparation occurs.

List.source
Element IdList.source
Definition

The entity responsible for deciding what the contents of the list were. Where the list was created by a human, this is the same as the author of the list.

Short DisplayWho and/or what defined the list contents (aka Author)
Cardinality0..1
TypeReference(Practitioner | PractitionerRole | Patient | Device | Organization | RelatedPerson | CareTeam)
Requirements

Allows follow-up as well as context.

Alternate NamesAuthor
Summarytrue
Comments

The primary source is the entity that made the decisions what items are in the list. This may be software or user.

List.orderedBy
Element IdList.orderedBy
Definition

What order applies to the items in the list.

Short DisplayWhat order the list has
Cardinality0..1
Terminology BindingList Order Codes (Preferred)
TypeCodeableConcept
Requirements

Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries.

Summaryfalse
Comments

Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order.

List.note
Element IdList.note
Definition

Comments that apply to the overall list.

Short DisplayComments about the list
Cardinality0..*
TypeAnnotation
Summaryfalse
List.entry
Element IdList.entry
Definition

Entries in this list.

Short DisplayEntries in the list
Cardinality0..*
Element Order MeaningOrder has no meaning unless specifically asserted by List.orderedBy, in which case the List SHALL be interpreted as being ordered as specified by List.orderedBy.
Summaryfalse
Comments

If there are no entries in the list, an emptyReason SHOULD be provided.

Invariants
Affect this element
lst-1Rule A list can only have an emptyReason if it is emptyemptyReason.empty() or entry.empty()
List.entry.flag
Element IdList.entry.flag
Definition

The flag allows the system constructing the list to indicate the role and significance of the item in the list.

Short DisplayStatus/Workflow information about this item
Cardinality0..1
Terminology BindingPatient Medicine Change Types (Example)
TypeCodeableConcept
Requirements

This field is present to support various clinical uses of lists, such as a discharge summary medication list, where flags specify whether the medication was added, modified, or deleted from the list.

Summaryfalse
Comments

The flag can only be understood in the context of the List.code. If the flag means that the entry has actually been deleted from the list, the deleted element SHALL be true

List.entry.deleted
Element IdList.entry.deleted
Definition

True if this item is marked as deleted in the list.

Short DisplayIf this item is actually marked as deleted
Cardinality0..1
Typeboolean
Is Modifiertrue (Reason: If deleted is true, then the item included in the list isn't actually part of the list anymore)
Meaning if MissingList items are generally only treated as deleted when this element explicitly carries a value of true. Systems SHOULD always populate this value when mode is 'changes'
Requirements

The flag element may contain codes that an application processing the list does not understand. However there can be no ambiguity if a list item is actually marked as "deleted".

Summaryfalse
Comments

If the flag means that the entry has actually been deleted from the list, the deleted element SHALL be true. A deleted entry should be displayed in narrative as deleted. This element is labeled as a modifier because it indicates that an item is (to be) no longer in the list.

List.entry.date
Element IdList.entry.date
Definition

When this item was added to the list.

Short DisplayWhen item added to list
Cardinality0..1
TypedateTime
Requirements

The date may be significant for understanding the meaning of items in a working list.

Summaryfalse
List.entry.item
Element IdList.entry.item
Definition

A reference to the actual resource from which data was derived.

Short DisplayActual entry
Cardinality1..1
TypeReference(Any)
Summaryfalse
List.emptyReason
Element IdList.emptyReason
Definition

If the list is empty, why the list is empty.

Short DisplayWhy list is empty
Cardinality0..1
Terminology BindingList Empty Reasons (Preferred)
TypeCodeableConcept
Requirements

Allows capturing things like "none exist" or "not asked" which can be important for most lists.

Summaryfalse
Comments

The various reasons for an empty list make a significant interpretation to its interpretation. Note that this code is for use when the entire list has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases.

Invariants
Affect this element
lst-1Rule A list can only have an emptyReason if it is emptyemptyReason.empty() or entry.empty()