$preferred-id

Fetch Preferred it

draftFHIR Core package4.3.0operation2 inputs1 output

This operation returns the preferred identifiers for identifiers, and terminologies. The operation takes 2 parameters:

  • a system identifier - either a URI, an OID, or a v2 table 0396 (other) code
  • a code for what kind of identifier is desired (URI, OID, v2 table 0396 identifier)

and returns either the requested identifier, or an HTTP errors response with an OperationOutcome because either the provided identifier was not recognized, or the requested identiifer type is not known.

The principle use of this operation is when converting between v2, CDA and FHIR Identifier/CX/II and CodeableConcepts/C(N/W)E/CD but the operation may also find use when converting metadata such as profiles.

Metadata

hl7.org/fhir
Canonical URL
http://hl7.org/fhir/OperationDefinition/NamingSystem-preferred-id
Code
$preferred-id
Kind
operation
Affects State
No
Publisher
HL7 (FHIR Project)

Invocation Context

Can be invoked at:
Type Level
Target Resources:
NamingSystem
Affects State:No

Implementation Notes

Servers handle this request by finding the provided identifier in their known naming systems, and returning the requested identifier type ([NamingSystem.uniqueId.type](namingsystem-definitions.html#NamingSystem.uniqueId.type)). If there are multiple possible identifiers of the specified type (e.g. multiple OIDs) the server returns an error. 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

Input Parameters (2)

NameTypeCard.Description
id*string1..1The server parses the provided id to see what type it is (mary 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
type*code
binding: required
1..1

Output Parameters (1)

NameTypeCard.Description
resultstring1..1OIDs are return as plain OIDs (not the URI form).

Additional Information

Version
4.3.0
Date
2022-05-28T12:47:40+10:00