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.

Invariants

Every rule in force on a conforming instance. This profile rows are stated here; inherited rows come from the base resource and are listed so that a constraint named on an element is findable. Invariant keys elsewhere on this page link into this table.

Key	Source	Severity	On	Rule
effective-date-declares-exactly-one	this profile	error	Extension	An effective-date declaration must say either which paths carry the date, or that there is deliberately none -- never both, and never neither. An empty declaration is indistinguishable from not declaring, which is the ambiguity this extension exists to remove. extension('paths').exists() xor extension('none').exists()
ele-1	inherited	error	Extension	All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ext-1	inherited	error	Extension	Must have either extensions or value[x], not both extension.exists() != value.exists()