Generated Narrative: StructureDefinition relative-date Name Flags Card. Type Description & Constraints Extension 0..1 Extension Relative Date Criteria #xD; Slices for extension Content/Rules for all slices #xD; extension:targetReference 1..1 Extension Specific event that the date is relative to #xD; extension 0..0 #xD; url 1..1 uri "targetReference" #xD; value[x] 1..1 Reference() Value of extension #xD; extension:targetCode 1..1 Extension Kind of event that the date is relative to #xD; extension 0..0 #xD; url 1..1 uri "targetCode" #xD; value[x] 1..1 CodeableConcept Value of extension #xD; extension:targetPath 0..1 Extension Relative to which element on the event #xD; extension 0..0 #xD; url 1..1 uri "targetPath" #xD; value[x] 1..1 string Value of extension #xD; extension:relationship XD 0..1 Extension before-start | before | before-end | concurrent-with-start | concurrent | concurrent-with-end | after-start | after | after-end #xD; extension 0..0 #xD; url 1..1 uri "relationship" #xD; value[x] 1..1 code Value of extension Binding: ActionRelationshipType (preferred) #xD; extension:offset 1..1 Extension Duration before or after the event #xD; extension 0..0 #xD; url 1..1 uri "offset" #xD; value[x] 1..1 Value of extension #xD; valueDuration Duration #xD; valueRange Range #xD; url 1..1 uri "http://hl7.org/fhir/StructureDefinition/relative-date" #xD; value[x] 0..0 #xD; Documentation for this format
Specifies that a date is relative to some event. The event happens [Duration] after [Event].
NOTE: This extension will be deprecated in favor of the new relative-time extension once the RelativeTime data type on which it is based is generally available.
This extension is used when a precise date is not known, but rather, the date will be relative to some future event (e.g. Do this 2 weeks after an operation).
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
Must have either extensions or value[x], not both
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Specific event that the date is relative to
The specific event that the date(time) is relative to - e.g. an Encounter, an Observation, a Procedure, etc.
Source of the definition for the extension code - a logical name or a URL.
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R5/extensibility.html) for a list).
Kind of event that the date is relative to
The generic type of event that the date(time) is relative to.
If present alongside targetReference, the kind of event is within the specified event - e.g. admission or discharge in an encounter, enrollment or start of therapy in a study, etc.
The path to the element of the target that specifies the anchoring date or timeframe for the relative date.
The specified path SHALL be a FHIRPath resolveable on the specified type of the DataRequirement. The path must resolve to an element of type date, dateTime, Period, Schedule, or Timing. The `reference` plus the `targetPath` provides a fully computable anchor (e.g. `Patient.birthDate` or `ResearchSubject.progress.where(milestone.coding.where(system=x and code=y).exists()).startDate)`, while `targetCode` gives something that is more meaningful to a user (e.g. 'age', 'startOfTreatment'). Often there might be utility in having both.
This element is deprecated, the relationship of the event to the target is captured by offset.
before-start | before | before-end | concurrent-with-start | concurrent | concurrent-with-end | after-start | after | after-end
[Deprecated] Defines the relationship between the event and the date.
Defines the types of relationships between actions.
The duration before or after the event that the element on which this extension appears is asserted to be.
a negative offset indicates a duration 'prior' to the event. E.g. "3 days prior to patient death". A positive offset indicates a duration 'after' the event. E.g. "27 years after birth - i.e. Age 27". An offset of 0 indicates occurrence simultaneous with the referenced event. E.g. "Started therapy immediately on admission".