DSTU2 Ballot Source

This page is part of the FHIR Specification (v0.5.0: DSTU 2 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: R4 R3 R2

V3-IdentifierScope.xml

Raw XML (canonical form)

Description: Codes to specify the scope in which the identifier applies to the object with which it is associated, and used in the datatype property II.

Raw XML

<ValueSet xmlns="http://hl7.org/fhir">
  <id value="v3-IdentifierScope"/>
  <meta>
    <lastUpdated value="2015-03-23T00:00:00.000+11:00"/>
    <profile value="http://hl7.org/fhir/StructureDefinition/valueset-shareable-definition"/>
  </meta>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><!-- Snipped for brevity --></div>
  </text>
  <extension url="http://hl7.org/fhir/StructureDefinition/valueset-oid">
    <valueUri value="urn:oid:2.16.840.1.113883.1.11.20276"/>
  </extension>
  <url value="http://hl7.org/fhir/v3/vs/IdentifierScope"/>
  <version value="2015-03-23"/>
  <name value="v3 Code System IdentifierScope"/>
  <publisher value="HL7, Inc"/>
  <contact>
    <telecom>
      <system value="url"/>
      <value value="http://hl7.org"/>
    </telecom>
  </contact>
  <description value="  Description: Codes to specify the scope in which the identifier applies to the object
     with which it is associated, and used in the datatype property II."/>
  <status value="active"/>
  <experimental value="false"/>
  <date value="2015-03-23"/>
  <define>
    <extension url="http://hl7.org/fhir/StructureDefinition/valueset-oid">
      <valueUri value="urn:oid:2.16.840.1.113883.5.1116"/>
    </extension>
    <system value="http://hl7.org/fhir/v3/IdentifierScope"/>
    <caseSensitive value="true"/>
    <concept>
      <code value="BUSN"/>
      <abstract value="false"/>
      <display value="Business Identifier"/>
      <definition value="Description: An identifier whose scope is defined by the business practices associated
         with the object. In contrast to the other scope identifiers, the scope of the use of the
         id is not necessarily restricted to a single object, but may be reused for other objects
         closely associated with the object due to business practice."/>
    </concept>
    <concept>
      <code value="OBJ"/>
      <abstract value="false"/>
      <display value="Object Identifier"/>
      <definition value="Description: The identifier associated with a particular object. It remains consistent
         as the object undergoes state transitions."/>
    </concept>
    <concept>
      <code value="VER"/>
      <abstract value="false"/>
      <display value="Version Identifier"/>
      <definition value="Description: An identifier that references a particular object as it existed at a given
         point in time. The identifier SHALL change with each state transition on the object. I.e.
         The version identifier of an object prior to a 'suspend' state transition is distinct
         from the identifier of the object after the state transition. Each version identifier
         can be tied to exactly one ControlAct event which brought that version into being (though
         the control act may never be instantiated).                                          
                     NOTE: Applications that do not support versioning of objects must ignore and
         not persist these ids to avoid confusion resulting from leaving the same identifier on
         an object that undergoes changes."/>
    </concept>
    <concept>
      <code value="VW"/>
      <abstract value="false"/>
      <display value="View Specific Identifier"/>
      <definition value="Description: An identifier that references a particular object as it existed at a given
         point in time. The identifier SHALL change with each state transition on the object. 
                                                             Example The version identifier of
         an object prior to a 'suspend' state transition is distinct from the identifier of the
         object after the state transition. Each version identifier can be tied to exactly one
         ControlAct event which brought that version into being (though the control act may never
         be instantiated).                                                       NOTE: Applications
         that do not support versioning of objects must ignore and not persist these ids to avoid
         confusion resulting from leaving the same identifier on an object that undergoes changes."/>
    </concept>
  </define>
</ValueSet>

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.