Release 4 FHIR CI-Build

This page is part of the Continuous Integration Build of FHIR Specification (v4.0.1: R4 - Mixed Normative and STU ) in it's permanent home (it will always (will be available incorrect/inconsistent at this URL). The current version which supercedes this version is 5.0.0 . For a full list of available versions, see times).
See the Directory of published versions . Page versions: R5 R4B R4

Operation-namingsystem-preferred-id

Example OperationDefinition/NamingSystem-preferred-id (Narrative)

Maturity Level : N/A
FHIR Responsible Owner: Terminology Infrastructure Work Group Standards Status : Informative Compartments : Not linked to any No defined compartments

This is the narrative for the resource. See also the XML , JSON or Turtle format.

Fetch Preferred it OPERATION: Fetch Preferred it The official URL for

Note that this operation definition is: http://hl7.org/fhir/OperationDefinition/NamingSystem-preferred-id This operation returns is 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 formal definition 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 preferred-id operation as an OperationOutcome because either the provided identifier was not recognized, or OperationDefinition on NamingSystem. See the requested identiifer type is not known. Operation documentation

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.

Generated Narrative: OperationDefinition NamingSystem-preferred-id

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

Parameters

Use Name Scope Cardinality Type Binding Documentation
IN id 1..1 string

The server parses the provided id identifier to see what type it is (mary (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

IN type 1..1 code http://hl7.org/fhir/ValueSet/namingsystem-identifier-type|4.0.1 Naming System Identifier Type (Required)
IN date 0..1 dateTime

If specified, the operation will indicate what the preferred identifier was on the specified date. If not specified, the operation will provide the preferred identifier as of 'now'

OUT result 1..1 string

OIDs are return as plain OIDs (not the URI form).

Servers handle this request by finding the provided identifier in their known naming systems, and returning the requested identifier type ( NamingSystem.uniqueId.type ). If there are multiple possible identifiers is more than one identifier of the specified type (e.g. (for the specified date), then the 'preferred' identifier will be returned. If there is only one identifier, that identifier will be returned even if it is not preferred. If there are multiple OIDs) preferred identifiers or multiple identifiers with none marked as preferred, the server returns system MAY return an error. error or may list all identifiers applicable for that date and period.

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 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.