FHIR Release 3 (STU) R4 Ballot #2 (Mixed Normative/Trial use)

This page is part of the FHIR Specification (v3.0.2: STU 3). (v3.5.0: R4 Ballot #2). 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: R5 R4B R4 R3

7.7.11 7.8.1 Resource StructureMap - Operations

FHIR Infrastructure Work Group Maturity Level : 2   Trial Use Compartments : Not linked to any defined compartments

This resource has 1 operation associated with it:

$transform Model Instance Transformation

For more information about operations, including how they are invoked, see Operations .

7.7.11.1 Model Instance Transformation The transform operation takes input content, applies a structure map transform, and then returns the output. The official URL for this operation definition is http://hl7.org/fhir/OperationDefinition/StructureMap-transform Formal Definition (as a OperationDefinition ). URL: [base]/StructureMap/$transform URL: [base]/StructureMap/[id]/$transform This is an idempotent operation In Parameters: Name Cardinality Type Binding Profile Documentation source 0..1 uri The structure map to apply. This is only needed if the operation is invoked at the resource level. If the $transform operation is invoked on a particular structure map, this will be ignored by the server content 1..1 Resource The logical content to transform Out Parameters: Name Cardinality Type Binding Profile Documentation return 1..1 Resource 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 7.7.11.1.1 Examples Transform input model (Request): POST [base]/StructureMap/example/$tansform Content-Type: text/xml <classA xmlns="http://example.org"> <test>value</test> </class> Response: HTTP/1.1 200 OK Content-Type: application/xml [other headers] <message xmlns="http://example.org/other"> <testValue value="value"/> </message>