<del class="diff-old">
This
page
is
part
of
the
FHIR
Specification
(v0.0.82:
DSTU
1).
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:
R5
R4B
R4
R3
R2
Structuredefinition.profile.xml
Raw
XML
(
canonical
form
)
StructureDefinition
for
structuredefinition
Raw
XML


  
  
    
  
  
    
    
  
  
  
  
  
    
      
      
    
  
  
    
      
      
    
  
  
  
  
  
    
    
    
  
  
    
    
    
  
  
  
  
    
      
      
      A definition of a FHIR structure. This resource is used to describe the underlying resources,
       data types defined in FHIR, and also for describing extensions, and constraints on resources
       and data types.
      
      
      
      
      
        
      
      
        
        
        
        
      
      
        
        
        
        
      
      
        
        
        If the type is Resource or Type, the url has to start with &amp;quot;http://hl7.org/fhir/StructureDefini
        tion/&amp;quot; and the tail must match the name
        not(f:type/@value=(&apos;Resource&apos;, &apos;Type&apos;)) or f:url/@value=concat(&apos;http://hl7.org/fhir/StructureDefinit
        ion/&apos;, f:name/@value)
      
      
        
        
        
        
      
      
        
        
        In any snapshot or differential, all the elements except the first have to have a path
         that starts with the path of the first + &amp;quot;.&amp;quot;
        string-join(for $elementName in f:*[self::f:snapshot or self::f:differential]/f:element[position()&amp;g
        t;1]/f:path/@value return if (starts-with($elementName, concat($elementName/ancestor::f:element/paren
        t::f:*/f:element[1]/f:path/@value, &apos;.&apos;))) then &apos;&apos; else $elementName,&apos;&apos;)=&apos;&apos;
      
    
    
      
      
      The logical id of the resource, as used in the url for the resoure. Once assigned, this
       value never changes.
      The only time that a resource does not have an id is when it is being submitted to the
       server using a create operation. Bundles always have an id, though it is usually a generated
       UUID.
      
      
      
        
      
    
    
      
      
      The metadata about the resource. This is content that is maintained by the infrastructure.
       Changes to the content may not always be associated with version changes to the resource.
      
      
      
        
      
    
    
      
      
      A reference to a set of rules that were followed when the resource was constructed, and
       which must be understood when processing the content.
      Asserting this rule set restricts the content to be only understood by a limited set of
       trading partners. This inherently limits the usefulness of the data in the long term.
       However the existing health eco-system is highly fractured, and not yet ready to define,
       collect, and exchange data in a generally computable sense. Wherever possible, implementers
       and/or specification writers should avoid using this element as much as possible.
      
      
      
        
      
      
    
    
      
      
      
      Language is provided to support indexing and accessibility (typically, services such as
       text to speech use the language tag). The html language tag in the narrative applies 
       to the narrative. The language tag on the resource may be used to specify the language
       of other presentations generated from the data in the resource  Not all the content has
       to be in the base language. The Resource.language should not be assumed to apply to the
       narrative automatically. If a language is specified, it should it also be specified on
       the div element in the html (see rules in HTML5 for information about the relationship
       between xml:lang and the html lang attribute).
      
      
      
        
      
      
        
        
        
        
      
    
    
      
      
      A human-readable narrative that contains a summary of the resource, and may be used to
       represent the content of the resource to a human. The narrative need not encode all the
       structured data, but is required to contain sufficient detail to make it &amp;quot;clinically
       safe&amp;quot; for a human to just read the narrative. Resource definitions may define what
       content should be represented in the narrative to ensure clinical safety.
      Contained resources do not have narrative. Resources that are not contained SHOULD have
       a narrative.
      
      
      
      
      
      
      
        
      
      
      
        
        
      
    
    
      
      
      These resources do not have an independent existence apart from the resource that contains
       them - they cannot be identified independently, and nor can they have their own independent
       transaction scope.
      This should never be done when the content can be identified properly, as once identification
       is lost, it is extremely difficult (and context dependent) to restore it again.
      
      
      
      
      
      
        
      
      
        
        
      
    
    
      
      
      May be used to represent additional information that is not part of the basic definition
       of the resource. In order to make the use of extensions safe and manageable, there is
       a strict set of governance  applied to the definition and use of extensions. Though any
       implementer is allowed to define an extension, there is a set of requirements that SHALL
       be met as part of the definition of the extension.
      There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone.
      
      
      
      
      
        
      
      
        
        
      
    
    
      
      
      May be used to represent additional information that is not part of the basic definition
       of the resource, and that modifies the understanding of the element that contains it.
       Usually modifier elements provide negation or qualification. In order to make the use
       of extensions safe and manageable, there is a strict set of governance applied to the
       definition and use of extensions. Though any implementer is allowed to define an extension,
       there is a set of requirements that SHALL be met as part of the definition of the extension.
       Applications processing a resource are required to check for modifier extensions.
      There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone.
      
      
      
      
      
        
      
      
        
        
      
    
    
      
      
      An absolute URL at which this StructureDefinition is (or will be) published, and which
       is used to reference this StructureDefinition in extension urls and tag values in operational
       FHIR systems.
      So you can say, in a StructureDefinition, what the full extensions URLs should be. This
       is required to allow hosting StructureDefinitions on multiple different servers, and to
       allow for the editorial process.
      
      
      
      
      
      
      
        
      
      
    
    
      
      
      Formal identifier that is used to identify this StructureDefinition when it is represented
       in other formats, or referenced in a specification, model, design or an instance  (should
       be globally unique OID, UUID, or URI), (if it&apos;s not possible to use the literal URI).
      
      
      
      
        
      
      
      
        
        
      
    
    
      
      
      The identifier that is used to identify this version of the StructureDefinition when it
       is referenced in a specification, model, design or instance. This is an arbitrary value
       managed by the StructureDefinition author manually.
      
      There may be multiple resource versions of the StructureDefinition that have this same
       identifier. The resource version id will change for technical reasons, whereas the stated
       version number needs to be under the author&apos;s control.
      
      
      
        
      
      
      
        
        
      
    
    
      
      
      
      
      
      
      
        
      
      
    
    
      
      
      The content was developed with a focus and intent of supporting the contexts that are
       listed. These terms may be used to assist with indexing and searching of structure definitions.
      
      
      
      
        
      
      
      
        
        
        Indicates the countries, regions, disciplines and other aspects of use this artifact is
         targeted for use within
        
          
        
      
      
        
        COMPONENT, PROPERTY, TIME_ASPCT, SYSTEM, SCALE_TYP, METHOD_TYP, CLASS, CLASSTYPE, ORDER_OBS,
         DOCUMENT_SECTION, HL7_ATTACHMENT_STRUCTURE
      
    
    
      
      
      Defined so that applications can use this name when displaying the value of the extension
       to the user.
      Applications don&apos;t have to use this name, but can always fall back to it. In the absence
       of a value for this element, use the name.
      
      
      
        
      
      
    
    
      
      
      
      Usually an organization, but may be an individual. This item SHOULD be populated unless
       the information is available from context.
      Helps establish the &amp;quot;authority/credibility&amp;quot; of the structure definition.  May
       also allow for contact.
      
      
      
        
      
      
      
        
        
      
    
    
      
      
      
      
      
      
      
    
    
      
      
      
      
      
      
      
        
      
      
        
        
      
    
    
      
      
      May be used to represent additional information that is not part of the basic definition
       of the element. In order to make the use of extensions safe and manageable, there is a
       strict set of governance  applied to the definition and use of extensions. Though any
       implementer is allowed to define an extension, there is a set of requirements that SHALL
       be met as part of the definition of the extension.
      There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone.
      
      
      
      
      
        
      
      
        
        
      
    
    
      
      
      May be used to represent additional information that is not part of the basic definition
       of the element, and that modifies the understanding of the element that contains it. Usually
       modifier elements provide negation or qualification. In order to make the use of extensions
       safe and manageable, there is a strict set of governance applied to the definition and
       use of extensions. Though any implementer is allowed to define an extension, there is
       a set of requirements that SHALL be met as part of the definition of the extension. Applications
       processing a resource are required to check for modifier extensions.
      There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone.
      
      
      
      
      
      
        
      
      
        
        
      
    
    
      
      
      
      
      
      
      
        
      
      
    
    
      
      
      
      
      
      
        
      
      
    
    
      
      
      
      This field can be used for things such as why the StructureDefinition was written, comments
       about misuse, instructions for clinical use and interpretation, literature references,
       examples from the paper world, etc.  It is *not* a rendering of the StructureDefinition
       as conveyed in StructureDefinition.text. This item SHOULD be populated unless the information
       is available from context.
      
      
      
        
      
      
    
    
      
      
      
      This element does not describe the usage of the structure definition (that&apos;s done in comments),
       rather it&apos;s for traceability of *why* the element is either needed or why the constraints
       exist as they do.  This may be used to point to source materials or specifications that
       drove the structure of this data element.
      
      
      
        
      
    
    
      
      
      A copyright statement relating to the structure definition and/or its contents. Copyright
       statements are generally legal restrictions on the use and publishing of the details of
       the constraints and mappings.
      
      
      
      
      
        
      
    
    
      
      
      A set of terms from external terminologies that may be used to assist with indexing and
       searching of templates.
      
      
      
      
        
      
      
      
        
        
      
    
    
      
      
      
      
      
      
      
        
      
      
      
      
        
        
        
        
          
        
      
      
        
        
      
    
    
      
      
      This StructureDefinition was authored for testing purposes (or education/evaluation/marketing),
       and is not intended to be used for genuine usage.
      
      
      
      
        
      
      
      
        
        
      
    
    
      
      
      
      
      
      
        
      
      
    
    
      
      
      The version of the FHIR specification on which this StructureDefinition is based - this
       is the formal version of the specification, without the revision number, e.g. [publication].[major].
      [minor], which is 0.4.0 for this version.
      A StructureDefinition does not need to specify the target it applies to,as StructureDefinitions
       will often be valid across multiple versions of FHIR. FHIR tooling can determine whether
       a StructureDefinition is consistent with a particular StructureDefinition if desired.
      
      
      
        
      
      
    
    
      
      
      
      
      
      
        
        
        
        
      
    
    
      
      
      
      
      
      
      
        
      
      
        
        
      
    
    
      
      
      May be used to represent additional information that is not part of the basic definition
       of the element. In order to make the use of extensions safe and manageable, there is a
       strict set of governance  applied to the definition and use of extensions. Though any
       implementer is allowed to define an extension, there is a set of requirements that SHALL
       be met as part of the definition of the extension.
      There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone.
      
      
      
      
      
        
      
      
        
        
      
    
    
      
      
      May be used to represent additional information that is not part of the basic definition
       of the element, and that modifies the understanding of the element that contains it. Usually
       modifier elements provide negation or qualification. In order to make the use of extensions
       safe and manageable, there is a strict set of governance applied to the definition and
       use of extensions. Though any implementer is allowed to define an extension, there is
       a set of requirements that SHALL be met as part of the definition of the extension. Applications
       processing a resource are required to check for modifier extensions.
      There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone.
      
      
      
      
      
      
        
      
      
        
        
      
    
    
      
      
      
      The specification is described once, with general comments, and then specific mappings
       are made that reference this declaration.
      
      
      
        
      
    
    
      
      
      
      
      
      
      
        
      
      
    
    
      
      
      
      
      
      
        
      
      
    
    
      
      
      Comments about this mapping, including version notes, issues, scope limitations, and other
       important notes for usage.
      
      
      
        
      
    
    
      
      
      
      
      
      
        
      
      
      
        
        
        
        
          
        
      
    
    
      
      
      Whether structure this definition describes is abstract or not  - that is, whether an
       actual exchanged item can ever be of this type.
      Abstract Resources cannot be instantiated - a concrete sub-type must be used. Abstract
       datatypes and extensions cannot be used in an instance. Flagging a constraint structure
       as abstract conveys design intent but makes no difference to how the structure definition
       is handled. Note that inline declared elements that are given the type &amp;quot;Element&amp;quot;
       in the profile, but have children described, are anonymous concrete types that specialise
       Element.
      
      
      
        
      
      
    
    
      
      
      If this is an extension, Identifies the context within FHIR resources where the extension
       can be used.
      
      
      
        
      
      
      
      
        
        
        
        
          
        
      
    
    
      
      
      
      If the context is an element that can have multiple types, then use (e.g.) value[x] if
       the extension works on all choice types, or otherwise an enumeration of explicitly named
       elements if not. Note that a context of &amp;quot;string&amp;quot; doesn&apos;t mean that the extension
       can be used with one of the string patterns such as &amp;quot;id&amp;quot; etc.
      
      
      
        
      
      
      
    
    
      
      
      
      If differential constraints are specified in this structure, they are applied to the base
       in a &amp;quot;differential&amp;quot; fashion. If there is no base, then the differential constraints
       cannot be provided (snapshot only). Differential structures are useful for the editing
       perspective, and snapshot structures are suitable for operational use. The FHIR Project
       provides a number of tools/services to populate snaphots from differential constraints.
      
      
      
        
      
      
      
    
    
      
      
      A snapshot view is expressed in a stand alone form that can be used and interpreted without
       considering the base StructureDefinition.
      
      
      
      
        
        
        
        
      
      
        
        
        If a structure is a snapshot, then each element definition must have a formal definition,
         and cardinalities
        exists(f:base) or (count(f:element) = count(f:element[exists(f:definition) and exists(f:min)
         and exists(f:max)]))
      
    
    
      
      
      
      
      
      
      
        
      
      
        
        
      
    
    
      
      
      May be used to represent additional information that is not part of the basic definition
       of the element. In order to make the use of extensions safe and manageable, there is a
       strict set of governance  applied to the definition and use of extensions. Though any
       implementer is allowed to define an extension, there is a set of requirements that SHALL
       be met as part of the definition of the extension.
      There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone.
      
      
      
      
      
        
      
      
        
        
      
    
    
      
      
      May be used to represent additional information that is not part of the basic definition
       of the element, and that modifies the understanding of the element that contains it. Usually
       modifier elements provide negation or qualification. In order to make the use of extensions
       safe and manageable, there is a strict set of governance applied to the definition and
       use of extensions. Though any implementer is allowed to define an extension, there is
       a set of requirements that SHALL be met as part of the definition of the extension. Applications
       processing a resource are required to check for modifier extensions.
      There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone.
      
      
      
      
      
      
        
      
      
        
        
      
    
    
      
      
      
      
      
      
        
      
      
      
        
        
      
    
    
      
      
      A differential view is expressed relative to the base StructureDefinition - a statement
       of differences that it applies.
      
      
      
    
    
      
      
      
      
      
      
      
        
      
      
        
        
      
    
    
      
      
      May be used to represent additional information that is not part of the basic definition
       of the element. In order to make the use of extensions safe and manageable, there is a
       strict set of governance  applied to the definition and use of extensions. Though any
       implementer is allowed to define an extension, there is a set of requirements that SHALL
       be met as part of the definition of the extension.
      There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone.
      
      
      
      
      
        
      
      
        
        
      
    
    
      
      
      May be used to represent additional information that is not part of the basic definition
       of the element, and that modifies the understanding of the element that contains it. Usually
       modifier elements provide negation or qualification. In order to make the use of extensions
       safe and manageable, there is a strict set of governance applied to the definition and
       use of extensions. Though any implementer is allowed to define an extension, there is
       a set of requirements that SHALL be met as part of the definition of the extension. Applications
       processing a resource are required to check for modifier extensions.
      There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone.
      
      
      
      
      
      
        
      
      
        
        
      
    
    
      
      
      
      
      
      
        
      
      
        
        
      
    
  
  
    
      
      
      A definition of a FHIR structure. This resource is used to describe the underlying resources,
       data types defined in FHIR, and also for describing extensions, and constraints on resources
       and data types.
      
      
      
      
      
        
      
      
        
        
        
        
      
      
        
        
        
        
      
      
        
        
        If the type is Resource or Type, the url has to start with &amp;quot;http://hl7.org/fhir/StructureDefini
        tion/&amp;quot; and the tail must match the name
        not(f:type/@value=(&apos;Resource&apos;, &apos;Type&apos;)) or f:url/@value=concat(&apos;http://hl7.org/fhir/StructureDefinit
        ion/&apos;, f:name/@value)
      
      
        
        
        
        
      
      
        
        
        In any snapshot or differential, all the elements except the first have to have a path
         that starts with the path of the first + &amp;quot;.&amp;quot;
        string-join(for $elementName in f:*[self::f:snapshot or self::f:differential]/f:element[position()&amp;g
        t;1]/f:path/@value return if (starts-with($elementName, concat($elementName/ancestor::f:element/paren
        t::f:*/f:element[1]/f:path/@value, &apos;.&apos;))) then &apos;&apos; else $elementName,&apos;&apos;)=&apos;&apos;
      
    
    
      
      
      An absolute URL at which this StructureDefinition is (or will be) published, and which
       is used to reference this StructureDefinition in extension urls and tag values in operational
       FHIR systems.
      So you can say, in a StructureDefinition, what the full extensions URLs should be. This
       is required to allow hosting StructureDefinitions on multiple different servers, and to
       allow for the editorial process.
      
      
      
      
      
      
      
        
      
      
    
    
      
      
      Formal identifier that is used to identify this StructureDefinition when it is represented
       in other formats, or referenced in a specification, model, design or an instance  (should
       be globally unique OID, UUID, or URI), (if it&apos;s not possible to use the literal URI).
      
      
      
      
        
      
      
      
        
        
      
    
    
      
      
      The identifier that is used to identify this version of the StructureDefinition when it
       is referenced in a specification, model, design or instance. This is an arbitrary value
       managed by the StructureDefinition author manually.
      
      There may be multiple resource versions of the StructureDefinition that have this same
       identifier. The resource version id will change for technical reasons, whereas the stated
       version number needs to be under the author&apos;s control.
      
      
      
        
      
      
      
        
        
      
    
    
      
      
      
      
      
      
      
        
      
      
    
    
      
      
      The content was developed with a focus and intent of supporting the contexts that are
       listed. These terms may be used to assist with indexing and searching of structure definitions.
      
      
      
      
        
      
      
      
        
        
        Indicates the countries, regions, disciplines and other aspects of use this artifact is
         targeted for use within
        
          
        
      
      
        
        COMPONENT, PROPERTY, TIME_ASPCT, SYSTEM, SCALE_TYP, METHOD_TYP, CLASS, CLASSTYPE, ORDER_OBS,
         DOCUMENT_SECTION, HL7_ATTACHMENT_STRUCTURE
      
    
    
      
      
      Defined so that applications can use this name when displaying the value of the extension
       to the user.
      Applications don&apos;t have to use this name, but can always fall back to it. In the absence
       of a value for this element, use the name.
      
      
      
        
      
      
    
    
      
      
      
      Usually an organization, but may be an individual. This item SHOULD be populated unless
       the information is available from context.
      Helps establish the &amp;quot;authority/credibility&amp;quot; of the structure definition.  May
       also allow for contact.
      
      
      
        
      
      
      
        
        
      
    
    
      
      
      
      
      
      
      
    
    
      
      
      
      
      
      
      
        
      
      
    
    
      
      
      
      
      
      
        
      
      
    
    
      
      
      
      This field can be used for things such as why the StructureDefinition was written, comments
       about misuse, instructions for clinical use and interpretation, literature references,
       examples from the paper world, etc.  It is *not* a rendering of the StructureDefinition
       as conveyed in StructureDefinition.text. This item SHOULD be populated unless the information
       is available from context.
      
      
      
        
      
      
    
    
      
      
      
      This element does not describe the usage of the structure definition (that&apos;s done in comments),
       rather it&apos;s for traceability of *why* the element is either needed or why the constraints
       exist as they do.  This may be used to point to source materials or specifications that
       drove the structure of this data element.
      
      
      
        
      
    
    
      
      
      A copyright statement relating to the structure definition and/or its contents. Copyright
       statements are generally legal restrictions on the use and publishing of the details of
       the constraints and mappings.
      
      
      
      
      
        
      
    
    
      
      
      A set of terms from external terminologies that may be used to assist with indexing and
       searching of templates.
      
      
      
      
        
      
      
      
        
        
      
    
    
      
      
      
      
      
      
      
        
      
      
      
      
        
        
        
        
          
        
      
      
        
        
      
    
    
      
      
      This StructureDefinition was authored for testing purposes (or education/evaluation/marketing),
       and is not intended to be used for genuine usage.
      
      
      
      
        
      
      
      
        
        
      
    
    
      
      
      
      
      
      
        
      
      
    
    
      
      
      The version of the FHIR specification on which this StructureDefinition is based - this
       is the formal version of the specification, without the revision number, e.g. [publication].[major].
      [minor], which is 0.4.0 for this version.
      A StructureDefinition does not need to specify the target it applies to,as StructureDefinitions
       will often be valid across multiple versions of FHIR. FHIR tooling can determine whether
       a StructureDefinition is consistent with a particular StructureDefinition if desired.
      
      
      
        
      
      
    
    
      
      
      
      
      
      
        
        
        
        
      
    
    
      
      
      
      The specification is described once, with general comments, and then specific mappings
       are made that reference this declaration.
      
      
      
        
      
    
    
      
      
      
      
      
      
      
        
      
      
    
    
      
      
      
      
      
      
        
      
      
    
    
      
      
      Comments about this mapping, including version notes, issues, scope limitations, and other
       important notes for usage.
      
      
      
        
      
    
    
      
      
      
      
      
      
        
      
      
      
        
        
        
        
          
        
      
    
    
      
      
      Whether structure this definition describes is abstract or not  - that is, whether an
       actual exchanged item can ever be of this type.
      Abstract Resources cannot be instantiated - a concrete sub-type must be used. Abstract
       datatypes and extensions cannot be used in an instance. Flagging a constraint structure
       as abstract conveys design intent but makes no difference to how the structure definition
       is handled. Note that inline declared elements that are given the type &amp;quot;Element&amp;quot;
       in the profile, but have children described, are anonymous concrete types that specialise
       Element.
      
      
      
        
      
      
    
    
      
      
      If this is an extension, Identifies the context within FHIR resources where the extension
       can be used.
      
      
      
        
      
      
      
      
        
        
        
        
          
        
      
    
    
      
      
      
      If the context is an element that can have multiple types, then use (e.g.) value[x] if
       the extension works on all choice types, or otherwise an enumeration of explicitly named
       elements if not. Note that a context of &amp;quot;string&amp;quot; doesn&apos;t mean that the extension
       can be used with one of the string patterns such as &amp;quot;id&amp;quot; etc.
      
      
      
        
      
      
      
    
    
      
      
      
      If differential constraints are specified in this structure, they are applied to the base
       in a &amp;quot;differential&amp;quot; fashion. If there is no base, then the differential constraints
       cannot be provided (snapshot only). Differential structures are useful for the editing
       perspective, and snapshot structures are suitable for operational use. The FHIR Project
       provides a number of tools/services to populate snaphots from differential constraints.
      
      
      
        
      
      
      
    
    
      
      
      A snapshot view is expressed in a stand alone form that can be used and interpreted without
       considering the base StructureDefinition.
      
      
      
      
        
        
        
        
      
      
        
        
        If a structure is a snapshot, then each element definition must have a formal definition,
         and cardinalities
        exists(f:base) or (count(f:element) = count(f:element[exists(f:definition) and exists(f:min)
         and exists(f:max)]))
      
    
    
      
      
      
      
      
      
        
      
      
      
        
        
      
    
    
      
      
      A differential view is expressed relative to the base StructureDefinition - a statement
       of differences that it applies.
      
      
      
    
    
      
      
      
      
      
      
        
      
      
        
        
      
    
  
&lt;/StructureDefinition&gt;
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.
©
HL7.org
2011+.
FHIR
DSTU
(v0.4.0-4902)
generated
on
Fri,
Mar
27,
2015
00:23+1100.
Links:
What's
a
DSTU?
|
Version
History
|
Specification
Map
|
Compare
to
DSTU1
|
|
Propose
a
change
</del>