R4 Ballot #1 (Mixed Normative/Trial use) Release 4

This page is part of the FHIR Specification (v3.3.0: (v4.0.1: R4 Ballot 2). - Mixed Normative and STU ) in it's permanent home (it will always be available at this URL). The current version which supercedes this version is 5.0.0 . For a full list of available versions, see the Directory of published versions . Page versions: R4B R4 R3 R2

2.27.1 2.28.1 Element - Detailed Descriptions

FHIR Infrastructure Work Group Maturity Level : 5 Normative Ballot Standards Status : Normative
Normative Candidate Note:
This page is candidate normative content for R4 in has been approved as part of an ANSI standard. See the Infrastructure Package . Once normative, it will lose it's Maturity Level, and breaking changes will no longer be made. for further details.

2.27.1.1 2.28.1.1 Element

Element
Standards Status This element has a standards status of "Normative" which is different to the status of the whole resource
Definition

Base definition for all elements in a resource.

Control Cardinality 1..1 0..*
Invariants :
Defined on this element
ele-1 : Rule All FHIR elements must have a @value or children ( expression hasValue() | or (children().count() > id.count()), xpath: @value|f:*|h:div) id.count())
Affect this element
Element.id
Definition

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

Control Cardinality 0..1
Type string
Element.extension
Definition

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 manageable, 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.

Control Cardinality 0..*
Type Extension
Alternate Names extensions; user content
Comments

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.