R4 Ballot #1 (Mixed Normative/Trial use) Current Build
This page was published as part of FHIR v3.3.0: R4 Ballot #1 : Mixed Normative/Trial use (First Normative ballot). It has been superceded by R4 . For a full list of available versions, see the Directory of published versions .

4.2.13.674 4.3.14.273 Code System http://hl7.org/fhir/type-derivation-rule

FHIR Infrastructure Work Group   Maturity Level : 5 N Normative (from v4.1.0) Use Context : Any
Normative Candidate Note: This page is candidate normative content for R4 in the Conformance Package . Once normative, it will lose it's Maturity Level, and breaking changes will no longer be made.

This is a code system defined by the FHIR project.

Summary

Defining URL: http://hl7.org/fhir/type-derivation-rule
Version: 4.1.0
Name: TypeDerivationRule
Title: TypeDerivationRule
Definition:

How a type relates to its baseDefinition.

Committee: FHIR Infrastructure Work Group
OID: 2.16.840.1.113883.4.642.1.674 (for OID based terminology systems)
Source Resource XML / JSON

This Code system is used in the following value sets:

How a type relates to its baseDefinition.

This code system http://hl7.org/fhir/type-derivation-rule defines the following codes:
Code Display Definition
specialization Specialization This definition defines a new type that adds additional elements to the base type type.
constraint Constraint This definition adds additional rules to an existing concrete type type.

 

See the full registry of value sets code systems defined as part of FHIR.


Explanation of the columns that may appear on this page:

Lvl Level A few code lists that FHIR defines are hierarchical - each code is assigned a level. See Code System for further information.
Source The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code The code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')
Display The display (used in the display element of a Coding ). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition An explanation of the meaning of the concept
Comments Additional notes about how to use the code