This page is part of the FHIR Specification (v5.0.0: R5 - STU). This is the current published version. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4
FHIR Infrastructure Work Group | Maturity Level: N/A | Standards Status: Informative | Compartments: No defined compartments |
This is the narrative for the resource. See also the XML, JSON or Turtle format.
Note that this is the formal definition for the convert operation as an OperationDefinition on Resource. See the Operation documentation
URL: [base]/$convert
Parameters
Use | Name | Scope | Cardinality | Type | Binding | Documentation |
IN | resource | 1..1 | Resource | The resource that is to be converted | ||
OUT | return | 1..1 | Resource | The resource after conversion |
While the primary use of this operation is simple - converting a resource from one format to another, there are many potential uses including:
These variants would all be associated with parameters that define and control these kind of conversions, though such parameters are not defined at this time. In the absence of any parameters, simple format conversion is all that will occur.
For this reason, implementers should be aware that:
return
resource type may be different from the resource
parameter resource type (for example, it might be a bundle)Implementers are encouraged to provide feedback to HL7 about their use of this operation
Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.