Generated Narrative: StructureDefinition ee-health-declaration-category Name Flags Card. Type Description & Constraints Extension 0..* Extension Tervise deklaratsiooni kasutusala #xD; extension 1..* Extension Extension #xD; Slices for extension Content/Rules for all slices #xD; extension:category 1..1 Extension Kasutusala #xD; extension 0..0 Extension #xD; url 1..1 uri "category" #xD; value[x] 1..1 Coding Value of extension Binding: Läbivaatuse tüüp (required) #xD; extension:effectivePeriod S 0..1 Extension Kehtivusperiood #xD; extension 0..0 Extension #xD; url 1..1 uri "effectivePeriod" #xD; value[x] 1..1 Period Value of extension #xD; start 1..1 dateTime Starting time with inclusive boundary #xD; end 1..1 dateTime End time with inclusive boundary, if not ongoing #xD; url 1..1 uri "https://fhir.ee/hdecl/StructureDefinition/ee-health-declaration-category" #xD; value[x] 0..0 Value of extension #xD; Documentation for this format
Tervise deklaratsiooni kasutusala ja selle kehtivuse periood
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
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).
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.
The start of the period. The boundary is inclusive.
If the low element is missing, the meaning is that the low boundary is not known.
End time with inclusive boundary, if not ongoing
The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.
The end value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has an end value of 2012-02-03.
If the end of the period is missing, it means that the period is ongoing