Consolidated CDA
3.0.0-ballot - ballot United States of America flag

This page is part of the CCDA: Consolidated CDA Release (v3.0.0-ballot: CCDA 3.0 Ballot 1) based on FHIR (HL7® FHIR® Standard) v5.0.0. . For a full list of available versions, see the Directory of published versions

Logical Model: US Realm Date and Time - Interval

Official URL: http://hl7.org/cda/us/ccda/StructureDefinition/USRealmDateTimeInterval Version: 3.0.0-ballot
Draft as of 2023-12-21 Computable Name: USRealmDateTimeInterval
Other Identifiers: id: urn:oid:2.16.840.1.113883.10.20.22.5.3

The US Realm Clinical Document Date and Time datatype flavor records date and time information. If time is provided, it must include a time zone offset.

This data type uses the same rules as US Realm Date and Time (Point in Time), but is used with elements having a datatype of IVL_TS.

Usage:

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

This structure is derived from IVL_TS

NameFlagsCard.TypeDescription & Constraintsdoco
.. IVL_TS C1..*IVL_TSXML Namespace: urn:hl7-org:v3
Elements defined in Ancestors: @nullFlavor, @value, @operator, low, center, width, high
Base for all types and resources
Logical Container: ClinicalDocument (CDA Class)
ivl-value-shall: If a time interval contains @value, then it shall be precise to at least the day.
ivl-value-should: If a time interval contains @value, then it SHOULD contain a time component.
... @value 0..1tsEither @value or low/high should be present, but not both
Date Format: YYYYMMDDHHMMSS.UUUU[+|-ZZzz]
... low C0..1IVXB_TS**MAY** be precise to at least the second
ts-shall-day: **SHALL** be precise to at least the day
ts-should-minute: **SHOULD** be precise to at least the minute
.... @value 0..1tsDate Format: YYYYMMDDHHMMSS.UUUU[+|-ZZzz]
... high C0..1IVXB_TS**MAY** be precise to at least the second
ts-shall-day: **SHALL** be precise to at least the day
ts-should-minute: **SHOULD** be precise to at least the minute
.... @value 0..1tsDate Format: YYYYMMDDHHMMSS.UUUU[+|-ZZzz]

doco Documentation for this format

Constraints

IdGradePath(s)DetailsRequirements
ivl-value-shallerrorIVL_TSIf a time interval contains @value, then it shall be precise to at least the day.
: value.exists() implies value.toString().length() >= 10
ivl-value-shouldwarningIVL_TSIf a time interval contains @value, then it SHOULD contain a time component.
: value.exists() implies value.toString().length() > 10
ts-shall-dayerrorIVL_TS.low, IVL_TS.high**SHALL** be precise to at least the day
: nullFlavor.exists() or value.toString().length() >= 10
ts-should-minutewarningIVL_TS.low, IVL_TS.high**SHOULD** be precise to at least the minute
: nullFlavor.exists() or value.toString().length() > 10
NameFlagsCard.TypeDescription & Constraintsdoco
.. IVL_TS C1..*IVL_TSXML Namespace: urn:hl7-org:v3
Elements defined in Ancestors: @nullFlavor, @value, @operator, low, center, width, high
Base for all types and resources
Logical Container: ClinicalDocument (CDA Class)
ivl-value-shall: If a time interval contains @value, then it shall be precise to at least the day.
ivl-value-should: If a time interval contains @value, then it SHOULD contain a time component.
... @value 0..1tsEither @value or low/high should be present, but not both
Date Format: YYYYMMDDHHMMSS.UUUU[+|-ZZzz]
... low C0..1IVXB_TS**MAY** be precise to at least the second
ts-shall-day: **SHALL** be precise to at least the day
ts-should-minute: **SHOULD** be precise to at least the minute
.... @value 0..1tsDate Format: YYYYMMDDHHMMSS.UUUU[+|-ZZzz]
... high C0..1IVXB_TS**MAY** be precise to at least the second
ts-shall-day: **SHALL** be precise to at least the day
ts-should-minute: **SHOULD** be precise to at least the minute
.... @value 0..1tsDate Format: YYYYMMDDHHMMSS.UUUU[+|-ZZzz]

doco Documentation for this format

Constraints

IdGradePath(s)DetailsRequirements
ivl-ts-centererrorIVL_TSCenter cannot co-exist with low or high
: center.empty() or (low.empty() and high.empty())
ivl-value-shallerrorIVL_TSIf a time interval contains @value, then it shall be precise to at least the day.
: value.exists() implies value.toString().length() >= 10
ivl-value-shouldwarningIVL_TSIf a time interval contains @value, then it SHOULD contain a time component.
: value.exists() implies value.toString().length() > 10
ts-shall-dayerrorIVL_TS.low, IVL_TS.high**SHALL** be precise to at least the day
: nullFlavor.exists() or value.toString().length() >= 10
ts-should-minutewarningIVL_TS.low, IVL_TS.high**SHOULD** be precise to at least the minute
: nullFlavor.exists() or value.toString().length() > 10
NameFlagsCard.TypeDescription & Constraintsdoco
.. IVL_TS C1..*IVL_TSXML Namespace: urn:hl7-org:v3
Elements defined in Ancestors: @nullFlavor, @value, @operator, low, center, width, high
Base for all types and resources
Logical Container: ClinicalDocument (CDA Class)
ivl-value-shall: If a time interval contains @value, then it shall be precise to at least the day.
ivl-value-should: If a time interval contains @value, then it SHOULD contain a time component.
... @nullFlavor 0..1csBinding: CDANullFlavor (required)
... @value 0..1tsEither @value or low/high should be present, but not both
Date Format: YYYYMMDDHHMMSS.UUUU[+|-ZZzz]
... @operator 0..1csBinding: SetOperator (required)
.... @nullFlavor 0..1csBinding: CDANullFlavor (required)
.... @value 0..1tsDate Format: YYYYMMDDHHMMSS.UUUU[+|-ZZzz]
.... @inclusive 0..1bl
... center 0..1TS
... width 0..1PQ
... high C0..1IVXB_TS**MAY** be precise to at least the second
ts-shall-day: **SHALL** be precise to at least the day
ts-should-minute: **SHOULD** be precise to at least the minute
.... @nullFlavor 0..1csBinding: CDANullFlavor (required)
.... @value 0..1tsDate Format: YYYYMMDDHHMMSS.UUUU[+|-ZZzz]
.... @inclusive 0..1bl

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet
IVL_TS.nullFlavorrequiredCDANullFlavor
IVL_TS.operatorrequiredSetOperator
IVL_TS.low.nullFlavorrequiredCDANullFlavor
IVL_TS.high.nullFlavorrequiredCDANullFlavor

Constraints

IdGradePath(s)DetailsRequirements
ivl-ts-centererrorIVL_TSCenter cannot co-exist with low or high
: center.empty() or (low.empty() and high.empty())
ivl-value-shallerrorIVL_TSIf a time interval contains @value, then it shall be precise to at least the day.
: value.exists() implies value.toString().length() >= 10
ivl-value-shouldwarningIVL_TSIf a time interval contains @value, then it SHOULD contain a time component.
: value.exists() implies value.toString().length() > 10
ts-shall-dayerrorIVL_TS.low, IVL_TS.high**SHALL** be precise to at least the day
: nullFlavor.exists() or value.toString().length() >= 10
ts-should-minutewarningIVL_TS.low, IVL_TS.high**SHOULD** be precise to at least the minute
: nullFlavor.exists() or value.toString().length() > 10

This structure is derived from IVL_TS

Summary

Differential View

This structure is derived from IVL_TS

NameFlagsCard.TypeDescription & Constraintsdoco
.. IVL_TS C1..*IVL_TSXML Namespace: urn:hl7-org:v3
Elements defined in Ancestors: @nullFlavor, @value, @operator, low, center, width, high
Base for all types and resources
Logical Container: ClinicalDocument (CDA Class)
ivl-value-shall: If a time interval contains @value, then it shall be precise to at least the day.
ivl-value-should: If a time interval contains @value, then it SHOULD contain a time component.
... @value 0..1tsEither @value or low/high should be present, but not both
Date Format: YYYYMMDDHHMMSS.UUUU[+|-ZZzz]
... low C0..1IVXB_TS**MAY** be precise to at least the second
ts-shall-day: **SHALL** be precise to at least the day
ts-should-minute: **SHOULD** be precise to at least the minute
.... @value 0..1tsDate Format: YYYYMMDDHHMMSS.UUUU[+|-ZZzz]
... high C0..1IVXB_TS**MAY** be precise to at least the second
ts-shall-day: **SHALL** be precise to at least the day
ts-should-minute: **SHOULD** be precise to at least the minute
.... @value 0..1tsDate Format: YYYYMMDDHHMMSS.UUUU[+|-ZZzz]

doco Documentation for this format

Constraints

IdGradePath(s)DetailsRequirements
ivl-value-shallerrorIVL_TSIf a time interval contains @value, then it shall be precise to at least the day.
: value.exists() implies value.toString().length() >= 10
ivl-value-shouldwarningIVL_TSIf a time interval contains @value, then it SHOULD contain a time component.
: value.exists() implies value.toString().length() > 10
ts-shall-dayerrorIVL_TS.low, IVL_TS.high**SHALL** be precise to at least the day
: nullFlavor.exists() or value.toString().length() >= 10
ts-should-minutewarningIVL_TS.low, IVL_TS.high**SHOULD** be precise to at least the minute
: nullFlavor.exists() or value.toString().length() > 10

Key Elements View

NameFlagsCard.TypeDescription & Constraintsdoco
.. IVL_TS C1..*IVL_TSXML Namespace: urn:hl7-org:v3
Elements defined in Ancestors: @nullFlavor, @value, @operator, low, center, width, high
Base for all types and resources
Logical Container: ClinicalDocument (CDA Class)
ivl-value-shall: If a time interval contains @value, then it shall be precise to at least the day.
ivl-value-should: If a time interval contains @value, then it SHOULD contain a time component.
... @value 0..1tsEither @value or low/high should be present, but not both
Date Format: YYYYMMDDHHMMSS.UUUU[+|-ZZzz]
... low C0..1IVXB_TS**MAY** be precise to at least the second
ts-shall-day: **SHALL** be precise to at least the day
ts-should-minute: **SHOULD** be precise to at least the minute
.... @value 0..1tsDate Format: YYYYMMDDHHMMSS.UUUU[+|-ZZzz]
... high C0..1IVXB_TS**MAY** be precise to at least the second
ts-shall-day: **SHALL** be precise to at least the day
ts-should-minute: **SHOULD** be precise to at least the minute
.... @value 0..1tsDate Format: YYYYMMDDHHMMSS.UUUU[+|-ZZzz]

doco Documentation for this format

Constraints

IdGradePath(s)DetailsRequirements
ivl-ts-centererrorIVL_TSCenter cannot co-exist with low or high
: center.empty() or (low.empty() and high.empty())
ivl-value-shallerrorIVL_TSIf a time interval contains @value, then it shall be precise to at least the day.
: value.exists() implies value.toString().length() >= 10
ivl-value-shouldwarningIVL_TSIf a time interval contains @value, then it SHOULD contain a time component.
: value.exists() implies value.toString().length() > 10
ts-shall-dayerrorIVL_TS.low, IVL_TS.high**SHALL** be precise to at least the day
: nullFlavor.exists() or value.toString().length() >= 10
ts-should-minutewarningIVL_TS.low, IVL_TS.high**SHOULD** be precise to at least the minute
: nullFlavor.exists() or value.toString().length() > 10

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. IVL_TS C1..*IVL_TSXML Namespace: urn:hl7-org:v3
Elements defined in Ancestors: @nullFlavor, @value, @operator, low, center, width, high
Base for all types and resources
Logical Container: ClinicalDocument (CDA Class)
ivl-value-shall: If a time interval contains @value, then it shall be precise to at least the day.
ivl-value-should: If a time interval contains @value, then it SHOULD contain a time component.
... @nullFlavor 0..1csBinding: CDANullFlavor (required)
... @value 0..1tsEither @value or low/high should be present, but not both
Date Format: YYYYMMDDHHMMSS.UUUU[+|-ZZzz]
... @operator 0..1csBinding: SetOperator (required)
.... @nullFlavor 0..1csBinding: CDANullFlavor (required)
.... @value 0..1tsDate Format: YYYYMMDDHHMMSS.UUUU[+|-ZZzz]
.... @inclusive 0..1bl
... center 0..1TS
... width 0..1PQ
... high C0..1IVXB_TS**MAY** be precise to at least the second
ts-shall-day: **SHALL** be precise to at least the day
ts-should-minute: **SHOULD** be precise to at least the minute
.... @nullFlavor 0..1csBinding: CDANullFlavor (required)
.... @value 0..1tsDate Format: YYYYMMDDHHMMSS.UUUU[+|-ZZzz]
.... @inclusive 0..1bl

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet
IVL_TS.nullFlavorrequiredCDANullFlavor
IVL_TS.operatorrequiredSetOperator
IVL_TS.low.nullFlavorrequiredCDANullFlavor
IVL_TS.high.nullFlavorrequiredCDANullFlavor

Constraints

IdGradePath(s)DetailsRequirements
ivl-ts-centererrorIVL_TSCenter cannot co-exist with low or high
: center.empty() or (low.empty() and high.empty())
ivl-value-shallerrorIVL_TSIf a time interval contains @value, then it shall be precise to at least the day.
: value.exists() implies value.toString().length() >= 10
ivl-value-shouldwarningIVL_TSIf a time interval contains @value, then it SHOULD contain a time component.
: value.exists() implies value.toString().length() > 10
ts-shall-dayerrorIVL_TS.low, IVL_TS.high**SHALL** be precise to at least the day
: nullFlavor.exists() or value.toString().length() >= 10
ts-should-minutewarningIVL_TS.low, IVL_TS.high**SHOULD** be precise to at least the minute
: nullFlavor.exists() or value.toString().length() > 10

This structure is derived from IVL_TS

Summary

 

Other representations of profile: CSV, Excel