Skip to content

Class: TimePoint

A structured representation of a single point in time that allows direct/explicit declaration as a dateTime, specification in terms of offset from a defined index, or description of an event type as a proxy for the time point when it occurred.

URI: crdch:TimePoint

img

Parents

  • is_a: Entity - Any resource that has its own identifier

Referenced by class

Attributes

Own

  • id 0..1
    • Description: The 'logical' identifier of the entity within the system of record. The simple value of this attribute stands for an identifier of this data object within the system, it can be used as a reference from other objects within the same system (i.e. primary and foreign keys), and it should be unique per type of object. The same data object copied to a different system will likely have a different "id" in the new system since "id" values are system specific and do not represent persistent business identifiers. Business identifiers are assigned outside the information system and are captured in the "identifier" field. The "id" field is more likely to be a serially or randomly generated value that is assigned to the data object as it is created in a system.
    • Range: CrdchString
  • date_time 0..1
    • Description: An explicitly specified timepoint described in terms of a date and optionally a time on that date.
    • Range: CrdchDateTime
  • index_time_point 0..1
    • Description: Another TimePoint from which this point is offset.
    • Range: TimePoint
  • offset_from_index 0..1
    • Description: A quantity of time that, together with the index date or event, can be used to derive a specific timepoint.
    • Range: Quantity
  • event_type 0..*
    • Description: An event that occurred at the point in time specified by this TimePoint.
    • Range: CodeableConcept

Other properties

Comments: The TimePoint object supports three ways to specify a point in time. The date_time field is the most direct - capturing an explicit date (e.g. 2021-05-05). The paired fields index_time_point and offset_from_index allows specification of a point in time as an offset from a related fixed time point. Finally, the event_type field uses type of event as a proxy for the time point when the event occurred.