diff --git a/source/datatypes/elementdefinition.xml b/source/datatypes/elementdefinition.xml index 80243b24278..2e877b57cb4 100644 --- a/source/datatypes/elementdefinition.xml +++ b/source/datatypes/elementdefinition.xml @@ -984,7 +984,7 @@ y - Name for element to display with or prompt for element + String to display with or prompt for element A single preferred label which is the text to display beside the element indicating its meaning or to use to prompt for the element in a user display or form. See also the extension [[[http://hl7.org/fhir/StructureDefinition/elementdefinition-question]]] @@ -1016,7 +1016,7 @@ Corresponding codes in terminologies A code that has the same meaning as the element in a particular terminology. Links the meaning of an element to an external terminology, and is very useful for searching and indexing - The concept SHALL be properly aligned with the data element definition and other constraints, as defined in the code system, including relationships, of any code listed here. Where multiple codes exist in a terminology that could correspond to the data element, the most granular code(s) should be selected, so long as they are not more restrictive than the data element itself. The mappings may be used to provide more or less granular or structured equivalences in the code system + The concept SHALL be properly aligned with the data element definition and other constraints, as defined in the code system, including relationships, of any code listed here. Where multiple codes exist in a terminology that could correspond to the data element, the most granular code(s) should be selected, so long as they are not more restrictive than the data element itself. The mappings may be used to provide more or less granular or structured equivalences in the code system. This is used for both mapping to formal terminologies as well as to informal collections of data elements provided they can be treated as a 'system' (i.e. a single namespace with a canonical URI). For mappings to more complex structures not identifiable with a single id, use the ElementDefinition.mapping structure. ./code (root or translation) OM1.7 @@ -2904,7 +2904,7 @@ Map element to another set of definitions Identifies a concept from an external specification that roughly corresponds to this element Provides guidance to implementers familiar with or converting content from other specifications - Mappings are not necessarily specific enough for safe translation + Mappings are not necessarily specific enough for safe translation. Note that ElementDefinition.code can provide a mapping to terminologies or other simple data element collections. N/A (MIF territory) diff --git a/source/datatypes/meta.xml b/source/datatypes/meta.xml index 06a38ca5ffd..b238ef82359 100644 --- a/source/datatypes/meta.xml +++ b/source/datatypes/meta.xml @@ -599,7 +599,7 @@ When the resource version last changed When the resource last changed - e.g. when the version changed - This element is generally omitted in instances submitted in a PUT or POST. Instead, it is populated in the response instance and when retrieving information using a GET. The server / resource manager sets this value; what a client provides is irrelevant. This is equivalent to the HTTP Last-Modified and SHOULD have the same value on a [read](http.html#read) interaction + This element is generally omitted in instances submitted in a PUT or POST. Instead, it is populated in the response instance and when retrieving information using a GET. The server / resource manager sets this value; what a client provides is irrelevant. This is equivalent to the HTTP Last-Modified and SHOULD have the same value on a [read](http.html#read) interaction. There may be situations where the returned data elements might change *without* any change to the lastUpdated element. For example, if a server returns a code and its corresponding display by using a foreign-key reference to the code system, updates to the code system that affect the display name might not be reflected in the lastUpdated value of the resource holding the code. It is also possible that an underlying record might be updated in a way that isn't actually surfaced in the FHIR resource (e.g. changing non-exposed metadata) that would cause lastUpdated to change even when there is no apparent change in the data.