NameFlagsCard.TypeDescription & Constraintsdoco
.. List TUDomainResourceA list is a curated collection of resources
+ Rule: A list can only have an emptyReason if it is empty

Elements defined in Ancestors: id, meta, implicitRules, language, text, contained, extension, modifierExtension
... identifier 0..*IdentifierBusiness identifier

... status ?!Σ1..1codecurrent | retired | entered-in-error
Binding: List Status (Required)
... mode ?!Σ1..1codeworking | snapshot | changes
Binding: List Mode (Required)
... title Σ0..1stringDescriptive name for the list
... code Σ0..1CodeableConceptWhat the purpose of this list is
Binding: Example Use Codes for List (Example)
... subject Σ0..*Reference(Any)If all resources have the same subject(s)

... encounter 0..1Reference(Encounter)Context in which list created
... date Σ0..1dateTimeWhen the list was prepared
... source Σ0..1Reference(Practitioner | PractitionerRole | Patient | Device | Organization | RelatedPerson | CareTeam)Who and/or what defined the list contents (aka Author)
... orderedBy 0..1CodeableConceptWhat order the list has
Binding: List Order Codes (Preferred)
... note 0..*AnnotationComments about the list

... entry C0..*BackboneElementEntries in the list
This repeating element order: Order 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.
.... flag 0..1CodeableConceptStatus/Workflow information about this item
Binding: Patient Medicine Change Types (Example)
.... deleted ?!0..1booleanIf this item is actually marked as deleted
.... date 0..1dateTimeWhen item added to list
.... item 1..1Reference(Any)Actual entry
... emptyReason C0..1CodeableConceptWhy list is empty
Binding: List Empty Reasons (Preferred)

doco Documentation for this format