FHIR Mapping Language (FML)
0.1.0 - STU 1 International flag

FHIR Mapping Language (FML), published by HL7 International / FHIR Infrastructure. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/mapping-language-ig/ and changes regularly. See the Directory of published versions

OperationDefinition: Model Instance Transformation

Official URL: http://hl7.org/fhir/build/OperationDefinition/StructureMap-transform Version: 0.1.0
Standards status: Trial-use Maturity Level: 2 Computable Name: Transform

The transform operation takes input content, applies a structure map transform, and then returns the output.

Last updated: 2021-01-05 10:01:24+1100

URL: [base]/StructureMap/$transform

URL: [base]/StructureMap/[id]/$transform

Parameters

UseNameScopeCardinalityTypeBindingDocumentation
INsourcetype0..1uri

The structure map to apply. This is only needed if the operation is invoked at the resource level and no structureMap has been provided. If the $transform operation is invoked on a particular structure map, this will be ignored by the server

INsourceMap0..1StructureMap

The structure map to apply. This is only needed when the operation is invoked at the resource level and no URI has been provided.

INsupportingMap0..*StructureMap

StructureMap resources that support the source map. If a source URL is provided, the map can be provided in this parameter (or it can be provided as sourceMap).

INsrcMap0..*string

The same as structureMap, but the resource is provided in the mapping language rather than as a structureMap.

INcontent1..1Resource

The logical content to transform

OUTreturn1..1Resource

The result of the transform

The input and return are specified as 'Resources'. In most usage of the $transform operation, either the input or return content is not a valid FHIR resource. In these cases, the return type is actually a Binary resource. For this operation, the Binary resources may be encoded directly, using a mime-type, as shown in the example. Note: this specification does not yet address the means by which the servers may know the correct mime types for the various content involved