This page is part of the Continuous Integration Build of FHIR Specification (v5.0.0: R5 - STU ). This is the current published version in it's permanent home (it will always (will be available incorrect/inconsistent at this URL). For a full list of available versions, see times).
See the Directory of published versions . Page versions: R5 R4B R4 R3 R2

• Content
• Examples Detailed Descriptions
• Detailed Descriptions Search Params
• Mappings
• Operations Examples
• Search Params Operations
• Profiles
• Extensions
R4 Conversions

5.4 Resource StructureDefinition - Content

Responsible Owner: FHIR Infrastructure Work Group

Maturity Level : N   Normative (from v4.0.0)

Security Category : Anonymous

Compartments : No defined compartments

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.

5.4.4 References to this Resource

• Resource References: ActivityDefinition , CapabilityStatement , DataRequirement , ElementDefinition , GraphDefinition ImplementationGuide ... Show 8 more , ImplementationGuide , MessageDefinition , Meta , OperationDefinition , ParameterDefinition , PlanDefinition , RequestOrchestration , itself , and StructureMap and TestScript
• Extension References: CapabilityStatement Declared Profile , Coding Conformance , Default Type , Pattern Dependent Profiles , Questionnaire Reference Profile Inherit Obligations ... Show 2 8 more , Obligations Profile , Pattern , Preferred Value Alternatives , Profile Mapping Extension , Questionnaire Reference Profile , StructureDefinition Compiles Complies With Profile , StructureDefinition Implements and StructureDefinition Dependent Profiles Imposes Profile

5.4.5 Resource Content

 

Additional definitions: Master Definition XML + JSON , XML Schema / Schematron + JSON Schema , ShEx (for Turtle ) , the spreadsheet version & the dependency analysis

5.4.5.1 Terminology Bindings

Path	ValueSet	Type	Documentation
StructureDefinition.versionAlgorithm[x]	VersionAlgorithm	Extensible	Indicates the mechanism used to compare versions to determine which is more current.
StructureDefinition.status	PublicationStatus	Required	The lifecycle status of an artifact.
StructureDefinition.jurisdiction	JurisdictionValueSet	Extensible	This value set defines a base set of codes for country, country subdivision and region for indicating where a resource is intended to be used. Note: The codes for countries and country subdivisions are taken from ISO 3166 while the codes for "supra-national" regions are from UN Standard country or area codes for statistical use (M49) .
StructureDefinition.keyword	DefinitionUseCodes (a valid code from Structure Definition Use Codes / Keywords )	Extensible	Structure Definition Use Codes / Keywords
StructureDefinition.fhirVersion	FHIRVersion	Required	All published FHIR Versions.
StructureDefinition.kind	StructureDefinitionKind	Required	Defines the type of structure that a definition is describing.
StructureDefinition.context.type	ExtensionContextType	Required	How an extension context is interpreted.
StructureDefinition.type	FHIRTypes (a valid code from All FHIR Types )	Extensible	All FHIR types
StructureDefinition.derivation	TypeDerivationRule	Required	How a type relates to its baseDefinition.

5.4.5.2 Constraints

5.4.6 Interpretation Notes:

• A structure is represented as a flat list of elements. The element.path provides the overall structure.
• Differentials in constraints need only specify elements that they are making rules about. Other elements can be inferred as defined in the base resource
• Elements specified in the differential (and all elements in the snapshot) must be ordered as such:
  • Elements from the baseDefinition appear before new elements in a StructureDefinition with derivation 'specialization'
  • Elements must be in the same order as the baseDefinition, and child elements appear in depth-first order.
  • Unsliced descendants of sliced elements appear before slices
• element.short , element.formal , element.comments and element.mapping provide the specific definition for the field in a specific context.
• element.type is used to specify which types may be used for this element. If there is more than one type, the element offers a choice of types and must have a name that terminates in "[x]". (Note: when substituting [x] with a specific data type, always capitalize the first letter. Choice types are always camel-case. Ex: "effectiveDateTime" is correct, "effectivedateTime" is NOT correct.)
• When using XPath to define constraints about the relationship between the contents of the narrative and the contents of the data elements, the element against which the rule is expressed is the one against which the error or warning will be reported by a validator.
• When expression constraints are placed on elements that offer a choice of types, the expression has to select the type to which it applies using the FHIRPath as operator .
• The condition element is used to assert that a constraint defined on another element affects the allowed cardinality of this element.

5.4.6.1 StructureDefinition Root Elements

The very first element in a snapshot (the one with an element id of just the type name) defines characteristics that apply to the type as a whole. Some of these characteristics affect the constraints that can hold on an element that references the type. For example, if the root element cardinality is 0..1 , then an element declared to be of that type cannot have a maximum cardinality greater than 1. (This is often used when defining extensions to indicate that multiple extension repetitions of that type are not allowed within a single element.)

In some cases, there can be redundancy between content defined on the root element and that defined on the StructureDefinition itself. For example, ElementDefinition has 'definition' while StructureDefinition has 'description'. These may have the same content put both places, though technically the 'definition' is text that describes what the type 'means', while 'description' is broader and may talk a bit about what the resource/data type/profile is for, in addition to its meaning.

5.4.6.2 Different Uses for StructureDefinition

The base structure definition is used in a number of different ways to support the FHIR specification. The various uses of the StructureDefinition are controlled by the elements kind , type , base , and url , using this basic pattern:

{
  "url": the identity of this structure definition,
  "kind": (primitive-type | complex-type | resource | logical),
  "type": the type being constrained (if it's a constraint)
  "abstract" : {true | false},
  "baseDefinition": the structure definition from which this is derived
}

This list shows a number of examples, with links to real examples for each:

1. Base definition of a data type (example: Quantity - XML , JSON ):
   

   {
     "resourceType": "StructureDefinition",
     "url": "http://hl7.org/fhir/StructureDefinition/Quantity",
     "name": "Quantity",
     "kind": "complex-type",
     "abstract" : false,
     "baseDefinition": "http://hl7.org/fhir/StructureDefinition/Element"
   }
   

2. A constrained data type (example: Money - XML , JSON ):
   

   {
     "resourceType": "StructureDefinition",
     "url": "http://hl7.org/fhir/StructureDefinition/Money",
     "name": "Money",
     "kind": "complex-type",
     "type": "Quantity",
     "abstract" : false,
     "baseDefinition": "http://hl7.org/fhir/StructureDefinition/Quantity"
   }
   

3. Base definition of a resource (example: Patient - XML , JSON ):
   

   {
     "resourceType": "StructureDefinition",
     "url": "http://hl7.org/fhir/StructureDefinition/Patient",
     "name": "Patient",
     "kind": "resource",
     "abstract" : false,
     "baseDefinition": "http://hl7.org/fhir/StructureDefinition/DomainResource"
   }
   

4. Constraint on a resource (example: Clinical Document Profile for Composition - XML , JSON ): { "resourceType": "StructureDefinition", "url": "http://hl7.org/fhir/StructureDefinition/clinicaldocument", "name": "Clinical Document Profile for Composition", "kind": "resource", "type": "Composition", "abstract" : false, "baseDefinition": "http://hl7.org/fhir/StructureDefinition/Composition" } Base Extension (a standard data type) (example: Extension - XML , JSON ):
   

   {
     "resourceType": "StructureDefinition",
     "url": "http://hl7.org/fhir/StructureDefinition/Extension",
     "name": "Extension",
     "kind": "complex-type",
     "abstract" : false,
     "baseDefinition": "http://hl7.org/fhir/StructureDefinition/Element"
   }
   

5. A defined Extension (example: Extension Data Absent Reason - XML , JSON ):
   

   {
     "resourceType": "StructureDefinition",
     "url": "http://hl7.org/fhir/StructureDefinition/data-absent-reason",
     "name": "Data Absent Reason",
     "kind": "complex-type",
     "type": "Extension",
     "abstract" : false,
     "baseDefinition": "http://hl7.org/fhir/StructureDefinition/Extension"
   }
   

6. A constraint on a defined extension (no examples currently defined):
   

   {
     "resourceType": "StructureDefinition",
     "url": "http://example.org/fhir/StructureDefinition/race",
     "name": "Race codes used by institution (a subset of meaningful use codes)",
     "kind": "complex-type",
     "type": "Extension",
     "abstract" : false,
     "abstract" : false,
   
     "baseDefinition": "http://hl7.org/fhir/us/core/StructureDefinition/us-core-race"
   }
   

7. A base abstract Resource (see e.g. Resource ):
   

   {
     "resourceType": "StructureDefinition",
     "url": "http://hl7.org/fhir/StructureDefinition/Resource",
     "name": "Resource",
     "kind": "resource",
     "type": "Resource",
     "abstract" : true,
     "baseDefinition": "http://hl7.org/fhir/us/core/StructureDefinition/Base"
   }
   

8. An interface defined in the base specification (see e.g. CanonicalResource ):
   

   {
     "resourceType": "StructureDefinition",
     "url": "http://hl7.org/fhir/StructureDefinition/CanonicalResource",
     "name": "CanonicalResource",
     "kind": "resource",
     "type": "CanonicalResource",
     "abstract" : true,
     "baseDefinition": "http://hl7.org/fhir/us/core/StructureDefinition/DomainResource"
   }
   

9. A logical model (see e.g. Definition ):
   

   {
     "resourceType": "StructureDefinition",
     "url": "http://hl7.org/fhir/StructureDefinition/Definition",
     "name": "Definition",
     "kind": "logical",
     "type": "Definition",
     "abstract" : false,
     "baseDefinition": "http://hl7.org/fhir/us/core/StructureDefinition/Base"
   }
   

On this list, structure definitions of type 1, 3, 5 and 8 - 9 can only be defined by the FHIR specification itself. The other kinds of structure definitions are (or may be) created by the specification but can also be defined by other implementers.

5.4.6.3 Rules for Constrained Types

When the structure is a constraint ( derivation = constraint ), see Extending and Restricting Resources for the rules that apply.

5.4.6.4 Common Mapping Targets

Structures are able to map elements to concepts in other definition systems. Generally, these are used to map the elements to local implementation models, data paths, and concepts. However they are also used to map to other standards and published terminologies. These are the standard URIs used for common targets of the mapping:

Name	Details
Logical Mapping	Formal URL: http://hl7.org/fhir/logical These mappings map logical models to their conceptual equivalents in FHIR. One example of their use is to map from the CDA and V2 coded data types to CodeableConcept and Coding so that the validator can validate them on a terminology server
ClinicalTrials.gov Mapping	Formal URL: http://clinicaltrials.gov
Workflow Pattern	Formal URL: http://hl7.org/fhir/workflow
CDISC Define XML 2.0 metadata standard	Formal URL: http://www.cdisc.org/define-xml
FHIR Consent FiveWs Pattern Mapping	Formal URL: http://hl7.org/fhir/consent http://hl7.org/fhir/fivews
BRIDG 5.1 Mapping to NCPDP SCRIPT 10.6	Formal URL: http://ncpdp.org/SCRIPT10_6 https://bridgmodel.nci.nih.gov
FiveWs Pattern IDMP Mapping	Formal URL: http://hl7.org/fhir/fivews https://www.iso.org/obp/ui/#iso:std:iso:11615
BRIDG 5.1 Bluetooth Technology	Formal URL: https://www.bluetooth.com
R3-ReferalRequest Mapping	Formal URL: https://bridgmodel.nci.nih.gov http://hl7.org/fhir/rr
HL7 V2 Mapping	Formal URL: http://hl7.org/v2 The mappings provided in this tab are indicative of how HL7 v2 fields relate to HL7 FHIR Composition attributes in this resource, but is not complete and without critical HL7 v2 context. The HL7 v2-FHIR Implementation guide, located here , provides additional guidance on transforming an HL7 v2 message to FHIR resources for FHIR R4 and FHIR R6.
RIM Mapping	Formal URL: http://hl7.org/fhir/composition http://hl7.org/v3
IDMP MDMI Referent Index Mapping	Formal URL: https://www.iso.org/obp/ui/#iso:std:iso:11615 http://github.com/MDMI/ReferentIndexContent
IHE Structured Data Capture ISBT 128 Codes	Formal URL: http://siframework.org/ihe-sdc-profile https://www.isbt128.org/uri/
IDMP Mapping (Substance) Quality Improvement and Clinical Knowledge (QUICK)	Formal URL: https://www.iso.org/obp/ui/#iso:std:iso:11238 http://siframework.org/cqf
Canadian Dental Pharmacy Association eclaims standard	Formal URL: http://www.cda-adc.ca/en/services/cdanet/ http://www.pharmacists.ca/
SNOMED CT Concept Domain Binding UDI Mapping	Formal URL: http://snomed.info/conceptdomain http://fda.gov/UDI Concept domain bindings link UDI is a resource unique numeric or an element to alphanumeric code that consists of two parts: (1) a set device identifier (DI), a mandatory, fixed portion of SNOMED CT concepts a UDI that represent identifies the intended semantics of labeler and the instances (whether specific version or not SNOMED CT is used to encode that data element). This set model of concepts is represented using a SNOMED CT expression constraint. Note device, and (2) a production identifier (PI), a conditional, variable portion of a UDI that identifies one or more of the 'Concept domain binding' may be following when included on the label of a superset device: (2a) the lot or batch number within which a device was manufactured; (2b) the serial number of a specific device; (2c) the 'value set binding'. expiration date of a specific device; (2d) the date a specific device was manufactured; (2e) the distinct identification code required by §1271.290(c) for a human cell, tissue, or cellular and tissue-based product (HCT/P) regulated as a device.
Quality Data Model	Formal URL: http://www.healthit.gov/quality-data-model
IHE Data Element Exchange (DEX)	Formal URL: http://ihe.net/data-element-exchange
SNOMED CT Attribute Binding	Formal URL: http://snomed.org/attributebinding Attribute bindings link coded data elements in FHIR resources to a corresponding attribute in the SNOMED CT concept model. These bindings help to support: Quality checking FHIR resources by ensuring that (a) clarifying the intended semantics meaning of the instances matches the valid range of data element Quality checking the alignment between FHIR resource design and any corresponding SNOMED CT attribute, and (b) the intended value set is appropriate for the intended semantics of the instances concept model Semantic checking Composition and decomposition of data instances by helping to detect potential inconsistencies caused by overlap between indicating the semantics incorporated in two SNOMED CT concept domains model attribute whose value may be used to decompose a precoordinated concept into this data element
R3-ReferalRequest vCard Mapping	Formal URL: http://hl7.org/fhir/rr http://w3.org/vcard
HL7 V2 Open EHR Archetype Mapping	Formal URL: http://hl7.org/v2 http://openehr.org
RIM Mapping ServD	Formal URL: http://hl7.org/v3 http://www.omg.org/spec/ServD/1.0/
ISO/IEEE 11073-10207 FHIR Provenance Mapping	Formal URL: urn:iso:std:iso:11073:10207 http://hl7.org/fhir/provenance
ISO 11179 FHIR Consent Mapping	Formal URL: http://metadata-standards.org/11179/ http://hl7.org/fhir/consent These mappings are included to indicate where properties of the data elements defined by the FHIR specification relate to similar fields in the ISO 11179 specification.
Mapping to Quality Improvement Domain Analysis Model NCPDP SCRIPT 10.6	Formal URL: http://hl7.org/qidam http://ncpdp.org/SCRIPT10_6
Interface Pattern FHIR Composition	Formal URL: http://hl7.org/fhir/interface http://hl7.org/fhir/composition
DICOM Tag Mapping IHE Structured Data Capture	Formal URL: http://nema.org/dicom http://siframework.org/ihe-sdc-profile
MDMI Referent Index IDMP Mapping (Substance)	Formal URL: http://github.com/MDMI/ReferentIndexContent https://www.iso.org/obp/ui/#iso:std:iso:11238
V3 Pharmacy Dispense RMIM Canadian Dental Association eclaims standard	Formal URL: http://www.hl7.org/v3/PORX_RM020070UV http://www.cda-adc.ca/en/services/cdanet/
XDS metadata equivalent	Formal URL: http://ihe.net/xds https://profiles.ihe.net/ITI/TF/Volume3
ISBT 128 Codes SNOMED CT Concept Domain Binding	Formal URL: https://www.isbt128.org/uri/ http://snomed.info/conceptdomain Concept domain bindings link a resource or an element to a set of SNOMED CT concepts that represent the intended semantics of the instances (whether or not SNOMED CT is used to encode that data element). This set of concepts is represented using a SNOMED CT expression constraint. Note that the 'Concept domain binding' may be a superset of the 'value set binding'. These bindings help to support: Quality checking FHIR resources by ensuring that (a) the intended semantics of the instances matches the valid range of the corresponding SNOMED CT attribute, and (b) the intended value set is appropriate for the intended semantics of the instances Semantic checking of data instances by helping to detect potential inconsistencies caused by overlap between the semantics incorporated in two concept domains
Equivalent CAP Code ISO/IEEE 11073-10207: Domain Information and Service Model for Service-Oriented Point-of-Care Medical Device Communication	Formal URL: http://cap.org/ecc urn:iso:std:iso:11073:10207
CDA (R2) ISO 11179	Formal URL: http://hl7.org/v3/cda http://metadata-standards.org/11179/ These mappings are included to indicate where properties of the data elements defined by the FHIR specification relate to similar fields in the ISO 11179 specification.
Quality Improvement and Clinical Knowledge (QUICK) ISO/IEEE 11073-10206: Personal health device communication--Abstract content information model	Formal URL: http://siframework.org/cqf urn:iso:std:iso:11073:10206
FHIR DocumentReference Mapping to Quality Improvement Domain Analysis Model	Formal URL: http://hl7.org/fhir/documentreference http://hl7.org/qidam
ISO/IEEE 11073-10201 Interface Pattern	Formal URL: urn:iso:std:iso:11073:10201 http://hl7.org/fhir/interface
Canadian V3 Pharmacy Association eclaims standard Dispense RMIM	Formal URL: http://www.pharmacists.ca/ http://www.hl7.org/v3/PORX_RM020070UV
UDI DICOM Tag Mapping	Formal URL: http://fda.gov/UDI http://nema.org/dicom
Equivalent CAP Code	Formal URL: http://cap.org/ecc UDI is a unique numeric or alphanumeric code that consists of two parts: (1) a device identifier (DI), a mandatory, fixed portion of a UDI that identifies the labeler and the specific version or model of a device, and (2) a production identifier (PI), a conditional, variable portion of a UDI that identifies one or more of the following when included on the label of a device: (2a) the lot or batch number within which a device was manufactured; (2b) the serial number of a specific device; (2c) the expiration date of a specific device; (2d) the date a specific device was manufactured; (2e) the distinct identification code required by §1271.290(c) for a human cell, tissue, or cellular and tissue-based product (HCT/P) regulated as a device.
Quality Data Model CDA (R2)	Formal URL: http://www.healthit.gov/quality-data-model http://hl7.org/v3/cda
FHIR AuditEvent DICOM Tag Mapping	Formal URL: http://hl7.org/fhir/auditevent https://dicomstandard.org/current
IHE Data Element Exchange (DEX) FHIR DocumentReference	Formal URL: http://ihe.net/data-element-exchange http://hl7.org/fhir/documentreference
SNOMED CT Attribute Binding ISO/IEEE 11073-10201: Domain Information Model	Formal URL: http://snomed.org/attributebinding urn:iso:std:iso:11073:10201
Attribute bindings link coded data elements in FHIR resources to a corresponding attribute in the SNOMED CT concept model. These bindings help to support: clarifying the intended meaning of the data element Quality checking the alignment between FHIR resource design and any coresponding SNOMED CT concept model Composition and decomposition of data instances by indicating the SNOMED CT concept model attribute whose value may be used to decompose a precoordinated concept into this data element AuditEvent Mapping	Formal URL: http://hl7.org/fhir/auditevent
W3C PROV	Formal URL: http://www.w3.org/ns/prov The provenance resource is based on known practices in the HL7 implementation space, particularly those found in the v2 EVN segment, the v3 ControlAct Wrapper, the CDA header, and IHE ATNA. The conceptual model underlying the design is the W3C provenance Specification . Though the content and format of the resource is designed to meet specific requirements for FHIR, all the parts of the resource are formally mapped to the PROV-O specification, and FHIR resources can be transformed to their W3C PROV equivalent.
Ontological RIM Mapping	Formal URL: http://hl7.org/orim
LOINC code for the element	Formal URL: http://loinc.org
vCard Mapping Formal URL: http://w3.org/vcard Open EHR Archetype Mapping Formal URL: http://openehr.org ServD Formal URL: http://www.omg.org/spec/ServD/1.0/ FHIR Provenance Mapping Formal URL: http://hl7.org/fhir/provenance iCalendar	Formal URL: http://ietf.org/rfc/2445

5.4.6.5 Logical Models

StructureDefinitions are used to define the basic structures of FHIR: data types, resources, extensions, and profiles. The same definition structure can also be used to define any arbitrary structures that are a directed acyclic graph with typed nodes, where the primitive types are those defined by the FHIR specification.

This technique has many uses:

• Describing any arbitrary content model
• Describing existing HL7 content models (e.g. v2, CDA) using FHIR
• Describing common design patterns used in FHIR
• Defining a content model to support the mapping language

5.4.6.6 Using StructureDefinitions to Define Additional Resource

Additional resources are defined by StructureDefinition resources, following these rules:

• The canonical URL of the definition is in some other canonical space than http://hl7.org/fhir
• The fhirVersion SHALL be 6.0.0 or a subsequent published version of FHIR
• The kind SHALL be resource
• abstract SHALL be false
• The type SHALL match the canonical URL exactly
• The baseDefinition SHALL be a direct reference to one of the abstract resources published by this specification ( Resource or DomainResource ). Resources MAY also use the implements extension to indicate adherence to the CanonicalResource or MetadataResource Interfaces
• The derivation SHALL be specialization
• The root of the element path SHALL be the tail of the canonical URL
• The root of the element SHOULD be the name assigned by HL7 to the resource
• The compartments for the resource are defined by using the (yet to be published) extension http://hl7.org/fhir/StructureDefinition/additional-resource-compartment

Here is an example with other properties removed:

{
  "resourceType" : "StructureDefinition",
  "url" : "http://hl7.org/fhir/uv/sql-on-fhir/StructureDefinition/ViewDefinition",
  "fhirVersion" : "6.0.0",
  "kind" : "resource",
  "abstract" : false,
  "type" : "http://hl7.org/fhir/uv/sql-on-fhir/StructureDefinition/ViewDefinition",
  "baseDefinition" : "http://hl7.org/fhir/StructureDefinition/CanonicalResource",
  "derivation" : "specialization",
  "differential" : {
    "element" : [{
      "path" : "ViewDefinition",
      // snip
    }]
  }
}

Once defined, additional resources are profiled like any other resource.

See general note to balloters about Additional resources

5.4.7 Search Parameters

Search parameters for this resource. See also the full list of search parameters for this resource , and check the Extensions registry for search parameters on extensions related to this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.

Name	Type	Description	Expression	In Common
abstract	token	Whether the structure is abstract	StructureDefinition.abstract
base	reference	Definition that this type is constrained/specialized from	StructureDefinition.baseDefinition ( StructureDefinition )
base-path	token	Path that identifies the base element	StructureDefinition.snapshot.element.base.path | StructureDefinition.differential.element.base.path
context	token	A use context assigned to the structure definition	(StructureDefinition.useContext.value.ofType(CodeableConcept))	30 24 Resources
context-quantity	quantity	A quantity- or range-valued use context assigned to the structure definition	(StructureDefinition.useContext.value.ofType(Quantity)) | (StructureDefinition.useContext.value.ofType(Range))	30 24 Resources
context-type TU	token	A type of use context assigned to the structure definition	StructureDefinition.useContext.code	30 24 Resources
context-type-quantity TU	composite	A use context type and quantity- or range-based value assigned to the structure definition	On StructureDefinition.useContext:   context-type: code   context-quantity: value.ofType(Quantity) | value.ofType(Range)	30 24 Resources
context-type-value TU	composite	A use context type and value assigned to the structure definition	On StructureDefinition.useContext:   context-type: code   context: value.ofType(CodeableConcept)	30 24 Resources
date	date	The structure definition publication date	StructureDefinition.date	30 25 Resources
derivation	token	specialization | constraint - How relates to base definition	StructureDefinition.derivation
description	string	The description of the structure definition	StructureDefinition.description	28 23 Resources
experimental	token	For testing purposes, not real usage Whether the StructureDefinition is experimental	StructureDefinition.experimental
ext-context	composite	An extension context assigned to the structure definition	On StructureDefinition.context:   ext-context-type: type   ext-context-expression: expression
ext-context-expression	token	An expression of extension context assigned to the structure definition	StructureDefinition.context.expression
ext-context-type	token	A type of extension context assigned to the structure definition	StructureDefinition.context.type
identifier	token	External identifier for the structure definition	StructureDefinition.identifier	34 28 Resources
jurisdiction	token	Intended jurisdiction for Jurisdiction of the authority that maintains the the structure definition	StructureDefinition.jurisdiction	26 21 Resources
keyword XD	token	A code for the StructureDefinition	StructureDefinition.keyword
kind	token	primitive-type | complex-type | resource | logical	StructureDefinition.kind
name	string	Computationally friendly name of the structure definition	StructureDefinition.name	26 23 Resources
path	token	A path that is constrained in the StructureDefinition	StructureDefinition.snapshot.element.path | StructureDefinition.differential.element.path
publisher	string	Name of the publisher of the structure definition	StructureDefinition.publisher	30 25 Resources
status	token	The current status of the structure definition	StructureDefinition.status	35 28 Resources
title	string	The human-friendly name of the structure definition	StructureDefinition.title	27 23 Resources
type	uri	Type defined or constrained by this structure	StructureDefinition.type
url	uri	The uri that identifies the structure definition	StructureDefinition.url	34 29 Resources
valueset	reference	A vocabulary binding reference	StructureDefinition.snapshot.element.binding.valueSet ( ValueSet )
version	token	The business version of the structure definition	StructureDefinition.version	30 26 Resources