Datatypes
Class PointInTime

A data type containing date and/or time information. This data type is a placeholder, as various platforms have differing built-in date-time data types. This data type is intended to handle both precise dates and imprecise dates (e.g., just a year), which would likely be implemented using different data types. Therefore, it is anticipated that this data type will be replaced by a different data type when transforming to a particular implementation platform.
Note that the FHIM has one data type that can be used to hold a date, a date-and-time, or just a time. In contrast FHIR has four data types: date, dateTime, time, and instant. The FHIM currently does not distinguish among the levels of precision that might be used in actual implementations, but leaves the datatype broad to handle all possible use cases. The FHIM PointInTime data type is most closely aligned with the FHIR dateTime data type.
"A date, or partial date (e.g. just year or year + month) as used in human communication. There is no time zone. Dates SHALL be valid dates" - HL7 FHIR, date
"A date, date-time or partial date (e.g. just year or year + month) as used in human communication. If hours and minutes are specified, a time zone SHALL be populated. ... Dates SHALL be valid dates…." - HL7 FHIR, dateTime
"A time during the day, with no date specified (can be converted to a Duration since midnight). … A time zone [is not allowed]." - HL7 FHIR, time
"An instant in time - known at least to the second and always includes a time zone. Note: This is intended for precisely observed times (typically system logs etc.), and not human-reported times - for them, use date and dateTime. instant is a more constrained dateTime" - HL7 FHIR, instant

Attributes
String literal literal

"TS literals are simple calendar expressions ... [which] conform to the constrained ISO 8601... Western calendar expressions begin with the 4-digit year; followed by the 2-digit month of the year; followed by the 2-digit day of the month; followed by the 2-digit hour of the day (beginning with zero); and so forth. For example, '200004010315' is a valid expression for April 1, 2000, 3:15 AM. A calendar expression can be of variable precision, omitting parts from the right. For example, '20000401' is precise only to the day of the month. The least defined calendar period (i.e. the second) may be written as a REAL, with the number of integer digits specified, followed by the decimal point and any number of fractional digits. For example, '20000401031520.34' means April 1, 2000, 3:15 and 20.34 seconds. When other calendars are used in the future, a prefix 'GREG:' can be placed before the western (Gregorian) calendar expression to disambiguate from other calendars. Each calendar shall have its own prefix. However, the western calendar is the default if no prefix is present. In the modern Gregorian calendar (and all calendars where time of day is based on UTC), the calendar expression may contain a time zone suffix. The time zone suffix begins with a plus (+) or minus (-) followed by digits for the hour and, for non UTC times, minute cycles. UTC is designated as offset '+00' or '-00'; the ISO 8601 and ISO 8824 suffix 'Z' for UTC is not permitted." - HL7 V3


Properties:

Alias
Classifier Behavior
Is Abstractfalse
Is Activefalse
Is Leaffalse
KeywordsTS
NamePointInTime
Name Expression
NamespaceDatatypes
Owned Template Signature
OwnerDatatypes
Owning Template Parameter
PackageDatatypes
Qualified NameFHIM::Datatypes::PointInTime
Representation
Stereotype
Template Parameter
VisibilityPublic

Attribute Details

 literal
Public String literal

"TS literals are simple calendar expressions ... [which] conform to the constrained ISO 8601... Western calendar expressions begin with the 4-digit year; followed by the 2-digit month of the year; followed by the 2-digit day of the month; followed by the 2-digit hour of the day (beginning with zero); and so forth. For example, '200004010315' is a valid expression for April 1, 2000, 3:15 AM. A calendar expression can be of variable precision, omitting parts from the right. For example, '20000401' is precise only to the day of the month. The least defined calendar period (i.e. the second) may be written as a REAL, with the number of integer digits specified, followed by the decimal point and any number of fractional digits. For example, '20000401031520.34' means April 1, 2000, 3:15 and 20.34 seconds. When other calendars are used in the future, a prefix 'GREG:' can be placed before the western (Gregorian) calendar expression to disambiguate from other calendars. Each calendar shall have its own prefix. However, the western calendar is the default if no prefix is present. In the modern Gregorian calendar (and all calendars where time of day is based on UTC), the calendar expression may contain a time zone suffix. The time zone suffix begins with a plus (+) or minus (-) followed by digits for the hour and, for non UTC times, minute cycles. UTC is designated as offset '+00' or '-00'; the ISO 8601 and ISO 8824 suffix 'Z' for UTC is not permitted." - HL7 V3

Constraints:
Properties:

AggregationNone
Alias
Association
Association End
Class«TS» PointInTime
Datatype
Default
Default Value
Is Compositefalse
Is Derivedfalse
Is Derived Unionfalse
Is Leaffalse
Is Orderedfalse
Is Read Onlyfalse
Is Staticfalse
Is Uniquetrue
Keywords
Lower1
Lower Value(1)
Multiplicity1
Nameliteral
Name Expression
Namespace«TS» PointInTime
Opposite
Owner«TS» PointInTime
Owning Association
Owning Template Parameter
Qualified NameFHIM::Datatypes::PointInTime::literal
Stereotype
Template Parameter
TypeString
Upper1
Upper Value(1)
VisibilityPublic

Comments