This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions

Example OperationDefinition/NamingSystem-translate-id (Narrative)

Terminology Infrastructure Work GroupMaturity Level: N/AStandards Status: InformativeCompartments: 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 translate-id operation as an OperationDefinition on NamingSystem. See the Operation documentation

URL: [base]/NamingSystem/$translate-id



The server parses the provided identifier to see what type it is (e.g. a URI, an OID as a URI, a plain OID, or a v2 table 0396 code). If the server can't tell what type of identifier it is, it can try it as multiple types. It is an error if more than one system matches the provided identifier

INsourceType1..1codeNaming System Identifier Type (Required)
INtargetType1..1codeNaming System Identifier Type (Required)

If preferredOnly = true then return only the preferred identifier, or if preferredOnly = false then return all available ids.


If 'date' is supplied return only ids that have a validity period that includes that date.


True if the identifier could be translated successfully.


The target identifer(s) of the requested type


Whether the target identifier is preferred.


The perioid when the target identifier is valid.

Servers handle this request by finding the provided identifier in their known naming systems, and returning the requested identifier type (NamingSystem.uniqueId.type).

If the server wishes, it can also look through all code systems and value sets it knows about when attempting to find the requested identifier



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.