Effective Date Extension¶
| Canonical | ../StructureDefinition/effective-date |
|---|---|
| Status | draft · 1.26.0 |
| Base | Extension (constraint) |
| Context | StructureDefinition (element) |
| Source | FSH · JSON |
Which element carries THE effective date for this profile, as a precedence-ordered list of raw-FHIR paths -- or an explicit declaration that the profile has none. One date concept per resource, declared in the IG rather than guessed by each consumer.
Elements / Key elements
The working view: must-support, required, modifier and sliced elements from the effective (snapshot) definition.
| Element | Flags | Card. | Type | Description & Constraints |
|---|---|---|---|---|
| Extension | 0..* | Effective Date Invariants: ele-1, ext-1, effective-date-declares-exactly-one |
||
| extension:paths | S | 0..1 | Extension | The effective-date elements, most preferred first, separated by | iInvariants: ele-1, ext-1 |
| url | 1..1 | http://hl7.org/fhirpath/System.String | identifies the meaning of the extension i Fixed: paths |
|
| extension:none | S | 0..1 | Extension | True when the profile deliberately has no effective date i Invariants: ele-1, ext-1 |
| url | 1..1 | http://hl7.org/fhirpath/System.String | identifies the meaning of the extension i Fixed: none |
|
| url | 1..1 | http://hl7.org/fhirpath/System.String | identifies the meaning of the extension i Fixed: ../StructureDefinition/effective-date |