Profile Comparison between http://hl7.org/cda/us/ccda/StructureDefinition/USRealmDateTimeInterval vs http://hl7.org/cda/us/ccda/StructureDefinition/USRealmDateTimeInterval

Messages

Metadata

Name	Value		Comments
abstract	false
baseDefinition	http://hl7.org/cda/stds/core/StructureDefinition/IVL-TS
copyright
date	2023-12-21T01:13:10+10:00	2024-05-18T00:42:57-05:00	Values Differ
description	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.
experimental
fhirVersion	5.0.0
jurisdiction
jurisdiction[0]	urn:iso:std:iso:3166#US
kind	logical
name	USRealmDateTimeInterval
publisher	Health Level Seven
purpose
status	draft
title	US Realm Date and Time - Interval
type	http://hl7.org/cda/stds/core/StructureDefinition/IVL_TS
url	http://hl7.org/cda/us/ccda/StructureDefinition/USRealmDateTimeInterval
version	3.0.0-ballot	3.0.0	Values Differ

Structure

Name	L Flags	L Card.	L Type	L Description & Constraints	R Flags	R Card.	R Type	R Description & Constraints	Comments
IVL_TS	C	1..*	IVL_TS	Base for all types and resources Logical Container: ClinicalDocument (CDA Class) ivl-ts-center: Center cannot co-exist with low or high 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.	C	1..*	IVL_TS	Base for all types and resources Logical Container: ClinicalDocument (CDA Class) ivl-ts-center: Center cannot co-exist with low or high 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..1	??	Binding: ?? (required)		0..1	??	Binding: ?? (required)
value		0..1	??	Either @value or low/high should be present, but not both Date Format: YYYYMMDDHHMMSS.UUUU[+|-ZZzz]		0..1	??	Either @value or low/high should be present, but not both Date Format: YYYYMMDDHHMMSS.UUUU[+|-ZZzz]
operator		0..1	??	Binding: ?? (required)		0..1	??	Binding: ?? (required)
low	C	0..1	IVXB_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	C	0..1	IVXB_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..1	??	Binding: ?? (required)		0..1	??	Binding: ?? (required)
value		0..1	??	Date Format: YYYYMMDDHHMMSS.UUUU[+|-ZZzz]		0..1	??	Date Format: YYYYMMDDHHMMSS.UUUU[+|-ZZzz]
inclusive		0..1	??			0..1	??
center		0..1	TS			0..1	TS
width		0..1	PQ			0..1	PQ
high	C	0..1	IVXB_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	C	0..1	IVXB_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..1	??	Binding: ?? (required)		0..1	??	Binding: ?? (required)
value		0..1	??	Date Format: YYYYMMDDHHMMSS.UUUU[+|-ZZzz]		0..1	??	Date Format: YYYYMMDDHHMMSS.UUUU[+|-ZZzz]
inclusive		0..1	??			0..1	??
Documentation for this format