This page is part of the FHIR Specification (v5.0.0: R5 - STU). This is the current published version in it's permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3
FHIR Infrastructure Work Group | Maturity Level: 4 | Trial Use | Use Context: Country: World |
Official URL: http://hl7.org/fhir/ValueSet/map-transform
|
Version: 5.0.0 | |||
draft as of 2020-12-28 | Computable Name: StructureMapTransform | |||
Flags: Immutable | OID: 2.16.840.1.113883.4.642.3.681 |
This value set is used in the following places:
How data is copied/created.
http://hl7.org/fhir/map-transform
This expansion generated 26 Mar 2023
This value set contains 17 concepts
Expansion based on Structure Map Transform v5.0.0 (CodeSystem)
Code | System | Display | Definition |
create | http://hl7.org/fhir/map-transform | create | create(type : string) - type is passed through to the application on the standard API, and must be known by it. |
copy | http://hl7.org/fhir/map-transform | copy | copy(source). |
truncate | http://hl7.org/fhir/map-transform | truncate | truncate(source, length) - source must be stringy type. |
escape | http://hl7.org/fhir/map-transform | escape | escape(source, fmt1, fmt2) - change source from one kind of escaping to another (plain, java, xml, json). note that this is for when the string itself is escaped. |
cast | http://hl7.org/fhir/map-transform | cast | cast(source, type?) - cast (convert) source from one type to another. Target type can be left as implicit if there is one and only one target type known. The default namespace for the type is 'FHIR' (see FHIRPath type specifiers ) |
append | http://hl7.org/fhir/map-transform | append | append(source...) - source is element or string. |
translate | http://hl7.org/fhir/map-transform | translate | translate(source, uri_of_map) - use the translate operation. |
reference | http://hl7.org/fhir/map-transform | reference | reference(source : object) - return a string that references the provided tree properly. |
dateOp | http://hl7.org/fhir/map-transform | dateOp | Perform a date operation. Parameters to be documented. |
uuid | http://hl7.org/fhir/map-transform | uuid | Generate a random UUID (in lowercase). No Parameters. |
pointer | http://hl7.org/fhir/map-transform | pointer | Return the appropriate string to put in a reference that refers to the resource provided as a parameter. |
evaluate | http://hl7.org/fhir/map-transform | evaluate | Execute the supplied FHIRPath expression and use the value returned by that. |
cc | http://hl7.org/fhir/map-transform | cc | Create a CodeableConcept. Parameters = (text) or (system. Code[, display]). |
c | http://hl7.org/fhir/map-transform | c | Create a Coding. Parameters = (system. Code[, display]). |
qty | http://hl7.org/fhir/map-transform | qty | Create a quantity. Parameters = (text) or (value, unit, [system, code]) where text is the natural representation e.g. [comparator]value[space]unit. |
id | http://hl7.org/fhir/map-transform | id | Create an identifier. Parameters = (system, value[, type]) where type is a code from the identifier type value set. |
cp | http://hl7.org/fhir/map-transform | cp | Create a contact details. Parameters = (value) or (system, value). If no system is provided, the system should be inferred from the content of the value. |
See the full registry of value sets defined as part of FHIR.
Explanation of the columns that may appear on this page:
Lvl | A few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - 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 |