R4 Ballot #1 (Mixed Normative/Trial use) Release 4

This page is part of the FHIR Specification (v3.3.0: (v4.0.1: R4 Ballot 2). - Mixed Normative and STU ) in it's permanent home (it will always be available at this URL). 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

5.3 Resource StructureDefinition - Content

FHIR Infrastructure Work Group Maturity Level : 5 N   Normative (from v4.0.0) Security Category : Anonymous Compartments : Not linked to any defined compartments
Normative Candidate Note:
This page is candidate normative content for R4 in has been approved as part of an ANSI standard. See the Conformance Package . Once normative, it will lose it's Maturity Level, and breaking changes will no longer be made. for further details.

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.3.1 Scope and Usage

The StructureDefinition resource describes a structure - a set of data element definitions, and their associated rules of usage. These structure definitions are used to describe both the content defined in the FHIR specification itself - Resources, data types, the underlying infrastructural types, and also are used to describe how these structures are used in implementations. This allows the definitions of the structures to be shared and published through repositories of structure definitions, compared with each other, and used as the basis for code, report and UI generation.

Note that as part of the specification itself, a full set of structure definitions for all resources and data types is published.

5.3.2 Boundaries and Relationships

  • StructureDefinitions are used by CapabilityStatement instances for specifying how resources are used
  • StructureDefinitions use Value Sets to specify the content of coded elements

5.3.3 Background and Context

Implementers should be familiar with the background and concepts described in Profiling FHIR before working with this resource.

5.3.3.1 Metadata

The StructureDefinition resource has a set of metadata that is mostly shared with the Value Set , CapabilityStatement and other infrastructure resources. The metadata describes the structure and helps find the structure when registered in profile repositories.

url The identifier that is used to identify this structure when it is referenced in a specification, model, design or an instance. This URL is where the structure can be accessed
identifier Other identifiers that are used to identify this structure
version

The identifier that is used to identify this version of the structure when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the structure author manually and the value should be a timestamp.

Note that there may be multiple resource versions of the structure that have this same identifier. The resource will have updates that create new versions for technical reasons, whereas the stated version number needs to be under the author's control

name A Computer=ready Computer-ready name (e.g. a token) that identifies the structure - suitable for code generation generation. Note that this name (and other names relevant for code generation, including element & slice names, codes etc) may collide with reserved words in the relevant target language, and code generators will need to handle this
title A free text natural language name identifying the structure
status The status of the structure allows filtering of StructureDefinitions that are appropriate for use vs. not. See the Status Codes
experimental This structure was authored for testing purposes (or education/evaluation/marketing), and is not intended for genuine usage
date The date this version of the structure was published
publisher Details of the individual or organization who accepts responsibility for publishing the structure. This helps establish the "authority/credibility" of the structure.
telecom contact Contact details to assist a user in finding and communicating with the publisher
description A free text natural language description of the structure and its use
requirements purpose The Scope and Usage that Why this structure was created to meet - what the intent of it is
code useContext & Jurisdiction Computable details about purpose and scope of use
keyword A set of terms from external terminologies that may be used to assist with indexing and searching of profiles status The status of the structure allows filtering of profiles that are appropriate for use vs. not. See the Status Codes experimental This structure was authored for testing purposes (or education/evaluation/marketing), and is not intended for genuine usage StructureDefinitionss
date copyright The date this version of the structure was published Use and/or publishing restrictions
fhirVersion The version of the FHIR specification on which this structure is based. It is not necessary to specify the version, as most profiles SructureDefinitions are valid across multiple versions, and the validity of a structure against a particular version of FHIR can easily be checked by tooling.
type The type the structure describes.
contextType & context For extensions, the types of contexts in which the extension can be used (resources, datatypes, or extensions). context For extensions, the specific types of resources or data types on which the extension can be used. For further details, see Defining Extensions

Notes:

  • The name and title of the structure is are not required to be globally unique, but the name amd title should have some scoping information (e.g. AcmeAllergies / Acme Inc. (USA), Allergy List)
  • Multiple codes keywords may be assigned to the structure. These may either describe the structure, the focus of the structure or both. They are solely to help find the structure by searching for structured concepts
  • The 3 status codes (draft, active, and retired) are the codes that are relevant to structure consumers. Authors may wish to use the authoring-status extension to track the life cycle of a structure as it is prepared

This resource is referenced by DataRequirement , ElementDefinition , Meta , ParameterDefinition , ActivityDefinition , CapabilityStatement , GraphDefinition , ImplementationGuide , MessageDefinition , OperationDefinition , StructureMap itself and TerminologyCapabilities StructureMap

5.3.4 Resource Content

Structure

?!
Name Flags Card. Type Description & Constraints doco
. . StructureDefinition I N DomainResource Structural Definition
+ In any snapshot or differential, no label, code or requirements on Warning: Name should be usable as an element without a "." in the path (e.g. identifier for the first element) module by machine processing applications such as code generation
+ Custom types can only Rule: Element paths must be used in logical models unique unless the structure is a constraint
+ All Rule: If the first element definitions must have unique ids (snapshot) in a differential has no "." in the path and it's not a logical model, it has no type
+ Context Invariants can only Rule: If the structure is not abstract, then there SHALL be used for extensions a baseDefinition
+ All element definitions Rule: If the structure defines an extension then the structure must have unique ids (diff) context information
+ element.base cannot appear if there is Rule: A structure must have either a differential, or a snapshot (or both)
+ Rule: In any snapshot or differential, no base label, code or requirements on an element without a "." in the structure definition path (e.g. the first element)
+ Rule: If there's a type, its content must match the path name in the first element of a snapshot
+ Rule: All element definitions must have an id
+ Element paths must be unique Rule: The first element in a snapshot has no type unless the structure model is a constraint logical model.
+ Default values Rule: All element definitions must have unique ids (snapshot)
+ Rule: All element definitions must have unique ids (diff)
+ Rule: Context Invariants can only be specified on logical models used for extensions
+ If the structure describes a base Resource or Type, the URL has to start with "http://hl7.org/fhir/StructureDefinition/" and the tail must match the id Rule: FHIR Specification models only use FHIR defined types
+ A structure must have either a differential, or a snapshot (or both) Rule: Default values can only be specified on specializations
+ If the structure defines an extension then the structure must Rule: FHIR Specification models never have context information default values
+ If the structure is not abstract, then there SHALL be a baseDefinition Rule: No slice name on root
Elements defined in Ancestors: id , meta , implicitRules , language , text , contained , extension , modifierExtension
. . . url Σ 1..1 uri Canonical identifier for this structure definition, represented as a URI (globally unique)
. . . identifier Σ 0..* Identifier Additional identifier for the structure definition
. . . version Σ 0..1 string Business version of the structure definition
. . . name Σ I 1..1 string Name for this structure definition (computer friendly)
. . . title Σ 0..1 string Name for this structure definition (human friendly)
. . . status ?! Σ 1..1 code draft | active | retired | unknown
PublicationStatus ( Required )
. . . experimental Σ 0..1 boolean For testing purposes, not real usage
. . . date Σ 0..1 dateTime Date last changed
. . . publisher Σ 0..1 string Name of the publisher (organization or individual)
. . . contact Σ 0..* ContactDetail Contact details for the publisher
. . . description 0..1 markdown Natural language description of the structure definition
. . . useContext Σ TU 0..* UsageContext The context that the content is intended to support
. . . jurisdiction Σ 0..* CodeableConcept Intended jurisdiction for structure definition (if applicable)
Jurisdiction ValueSet ( Extensible )
. . . purpose 0..1 markdown Why this structure definition is defined
. . . copyright 0..1 markdown Use and/or publishing restrictions
. . . keyword Σ 0..* Coding Assist with indexing and finding
Structure Definition Use Codes / Keywords ( Example Extensible )
. . . fhirVersion Σ 0..1 id code FHIR Version this StructureDefinition targets
All Published FHIR versions FHIRVersion ( Required )
. . . mapping I 0..* BackboneElement External specification that the content is mapped to
+ Rule: Must have at least a name or a uri (or both)
. . . . identity 1..1 id Internal id when this mapping is used
. . . . uri I 0..1 uri Identifies what this mapping refers to
. . . . name I 0..1 string Names what this mapping refers to
. . . . comment 0..1 string Versions, Issues, Scope limitations etc.
. . . kind Σ 1..1 code primitive-type | complex-type | resource | logical
StructureDefinitionKind ( Required )
. . . abstract Σ 1..1 boolean Whether the structure is abstract
. . . context Σ I 0..* BackboneElement If an extension, where it can be used in instances
. . . . type Σ 1..1 code fhirpath | element | extension
ExtensionContextType ( Required )
. . . . expression Σ 1..1 string Where the extension can be used in instances
. . . contextInvariant Σ I 0..* string FHIRPath invariants - when the extension can be used
. . . type Σ I 1..1 uri Type defined or constrained by this structure
FHIRDefinedType ( Extensible )
. . . baseDefinition Σ I 0..1 canonical ( StructureDefinition ) Definition that this type is constrained/specialized from
. . . derivation Σ 0..1 code specialization | constraint - How relates to base definition
TypeDerivationRule ( Required )
. . . snapshot I 0..1 BackboneElement Snapshot view of the structure
+ The first Rule: Each element definition in a snapshot has no type must have a formal definition and cardinalities
+ In any snapshot, all the Rule: All snapshot elements must be in start with the StructureDefinition's specified type, and must have a base definition type for non-logical models, or with the same type name for logical models
+ Each element definition in a Rule: All snapshot elements must have a formal base definition and cardinalities
. . . . element I 1..* ElementDefinition Definition of elements in the resource (if no StructureDefinition)
+ Rule: provide either a binding reference or a description (or both)
. . . differential I 0..1 BackboneElement Differential view of the structure
+ If the first element in a differential has no "." in the path, it has no type + Rule: No slicing on the root element
+ Rule: In any differential, all the elements must be in start with the StructureDefinition's specified type for non-logical models, or with the same type name for logical models
. . . . element 1..* ElementDefinition Definition of elements in the resource (if no StructureDefinition)

doco Documentation for this format

UML Diagram ( Legend )

StructureDefinition ( DomainResource ) An absolute URI that is used to identify this structure definition when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this structure definition is (or will be) published published. This URL can be the target of a canonical reference. It SHALL remain the same when the structure definition is stored on different servers url : uri [1..1] A formal identifier that is used to identify this structure definition when it is represented in other formats, or referenced in a specification, model, design or an instance identifier : Identifier [0..*] The identifier that is used to identify this version of the structure definition when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the structure definition author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence version : string [0..1] A natural language name identifying the structure definition. This name should be usable as an identifier for the module by machine processing applications such as code generation name : string [1..1] A short, descriptive, user-friendly title for the structure definition title : string [0..1] The status of this structure definition. Enables tracking the life-cycle of the content (this element modifies the meaning of other elements) status : code [1..1] « The lifecycle status of an artifact. (Strength=Required) PublicationStatus ! » A Boolean value to indicate that this structure definition is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage (this element modifies the meaning of other elements) experimental : boolean [0..1] The date (and optionally time) when the structure definition was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the structure definition changes date : dateTime [0..1] The name of the organization or individual that published the structure definition publisher : string [0..1] Contact details to assist a user in finding and communicating with the publisher contact : ContactDetail [0..*] A free text natural language description of the structure definition from a consumer's perspective description : markdown [0..1] The content was developed with a focus and intent of supporting the contexts that are listed. These terms contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate structure definition instances useContext : UsageContext [0..*] A legal or geographic region in which the structure definition is intended to be used jurisdiction : CodeableConcept [0..*] « Countries and regions within which this artifact is targeted for use use. (Strength=Extensible) Jurisdiction ValueSet + » Explanation of why this structure definition is needed and why it has been designed as it has purpose : markdown [0..1] 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 structure definition copyright : markdown [0..1] A set of key words or terms from external terminologies that may be used to assist with indexing and searching of templates nby describing the use of this structure definition, or the content it describes keyword : Coding [0..*] « Codes for the meaning of the defined structure (SNOMED CT and LOINC codes, as an example). (Strength=Example) (Strength=Extensible) Structure Definition DefinitionUseCodes ?? + » 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 3.3.0 4.0.1. for this version fhirVersion : id code [0..1] « All published FHIR Versions Versions. (Strength=Required) All Published FHIR versions FHIRVersion ! » Defines the kind of structure that this definition is describing kind : code [1..1] « Defines the type of structure that a definition is describing. (Strength=Required) StructureDefinitionKind ! » Whether structure this definition describes is abstract or not - that is, whether the structure is not intended to be instantiated. For Resources and Data types, abstract types will never be exchanged between systems abstract : boolean [1..1] A set of rules as FHIRPath Invariants about when the extension can be used (e.g. co-occurrence variants for the extension). All the rules must be true contextInvariant : string [0..*] The type this structure describes. If the derivation kind is 'specialization' then this is the master definition for a type, and there is always one of these (a data type, an extension, a resource, including abstract ones). Otherwise the structure definition is a constraint on the stated type (and in this case, the type cannot be an abstract type). References are URLs that are relative to http://hl7.org/fhir/StructureDefinition e.g. "string" is a reference to http://hl7.org/fhir/StructureDefinition/string. Absolute URLs are only allowed in logical models type : uri [1..1] « Either a resource or a data type, including logical model types types. (Strength=Extensible) FHIRDefinedType + » An absolute URI that is the base structure from which this type is derived, either by specialization or constraint baseDefinition : canonical [0..1] « StructureDefinition » How the type relates to the baseDefinition derivation : code [0..1] « How a type relates to its baseDefinition. (Strength=Required) TypeDerivationRule ! » Mapping An Internal id that is used to identify this mapping set when specific mappings are made identity : id [1..1] An absolute URI that identifies the specification that this mapping is expressed to uri : uri [0..1] A name for the specification that is being mapped to name : string [0..1] Comments about this mapping, including version notes, issues, scope limitations, and other important notes for usage comment : string [0..1] Context Defines how to interpret the expression that defines what the context of the extension is type : code [1..1] « How an extension context is interpreted. (Strength=Required) ExtensionContextType ! » An expression that defines where an extension can be used in resources expression : string [1..1] Snapshot Captures constraints on each element within the resource element : ElementDefinition [1..*] Differential Captures constraints on each element within the resource element : ElementDefinition [1..*] An external specification that the content is mapped to mapping [0..*] Identifies the types of resource or data type elements to which the extension can be applied context [0..*] A snapshot view is expressed in a standalone form that can be used and interpreted without considering the base StructureDefinition snapshot [0..1] A differential view is expressed relative to the base StructureDefinition - a statement of differences that it applies differential [0..1]

XML Template 

<StructureDefinition xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <

 <url value="[uri]"/><!-- 1..1 Canonical identifier for this structure definition, represented as a URI (globally unique) -->

 <identifier><!-- 0..* Identifier Additional identifier for the structure definition --></identifier>
 <version value="[string]"/><!-- 0..1 Business version of the structure definition -->
 <

 <name value="[string]"/><!-- ?? 1..1 Name for this structure definition (computer friendly) -->

 <title value="[string]"/><!-- 0..1 Name for this structure definition (human friendly) -->
 <status value="[code]"/><!-- 1..1 draft | active | retired | unknown -->
 <

 <experimental value="[boolean]"/><!-- 0..1 For testing purposes, not real usage -->

 <date value="[dateTime]"/><!-- 0..1 Date last changed -->
 <publisher value="[string]"/><!-- 0..1 Name of the publisher (organization or individual) -->
 <contact><!-- 0..* ContactDetail Contact details for the publisher --></contact>
 <description value="[markdown]"/><!-- 0..1 Natural language description of the structure definition -->
 <</useContext>

 <useContext><!-- 0..* UsageContext The context that the content is intended to support --></useContext>

 <jurisdiction><!-- 0..* CodeableConcept Intended jurisdiction for structure definition (if applicable) --></jurisdiction>
 <purpose value="[markdown]"/><!-- 0..1 Why this structure definition is defined -->
 <copyright value="[markdown]"/><!-- 0..1 Use and/or publishing restrictions -->
 <</keyword>
 <

 <keyword><!-- 0..* Coding Assist with indexing and finding --></keyword>
 <fhirVersion value="[code]"/><!-- 0..1 FHIR Version this StructureDefinition targets -->

 <mapping>  <!-- 0..* External specification that the content is mapped to -->
  <identity value="[id]"/><!-- 1..1 Internal id when this mapping is used -->
  <uri value="[uri]"/><!-- ?? 0..1 Identifies what this mapping refers to -->
  <name value="[string]"/><!-- ?? 0..1 Names what this mapping refers to -->
  <comment value="[string]"/><!-- 0..1 Versions, Issues, Scope limitations etc. -->
 </mapping>
 <kind value="[code]"/><!-- 1..1 primitive-type | complex-type | resource | logical -->
 <abstract value="[boolean]"/><!-- 1..1 Whether the structure is abstract -->
 <context>  <!-- ?? 0..* If an extension, where it can be used in instances -->
  <type value="[code]"/><!-- 1..1 fhirpath | element | extension -->
  <expression value="[string]"/><!-- 1..1 Where the extension can be used in instances -->
 </context>
 <contextInvariant value="[string]"/><!-- ?? 0..* FHIRPath invariants - when the extension can be used -->
 <type value="[uri]"/><!-- ?? 1..1 Type defined or constrained by this structure -->
 <baseDefinition><!-- ?? 0..1 canonical(StructureDefinition) Definition that this type is constrained/specialized from --></baseDefinition>
 <derivation value="[code]"/><!-- 0..1 specialization | constraint - How relates to base definition -->
 <snapshot>  <!-- ?? 0..1 Snapshot view of the structure -->
  <element><!-- ?? 1..* ElementDefinition Definition of elements in the resource (if no StructureDefinition) --></element>
 </snapshot>
 <differential>  <!-- ?? 0..1 Differential view of the structure -->
  <element><!-- 1..* ElementDefinition Definition of elements in the resource (if no StructureDefinition) --></element>
 </differential>
</StructureDefinition>

JSON Template 

{doco
  "resourceType" : "StructureDefinition",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "

  "url" : "<uri>", // R!  Canonical identifier for this structure definition, represented as a URI (globally unique)

  "identifier" : [{ Identifier }], // Additional identifier for the structure definition
  "version" : "<string>", // Business version of the structure definition
  "

  "name" : "<string>", // C? R!  Name for this structure definition (computer friendly)

  "title" : "<string>", // Name for this structure definition (human friendly)
  "status" : "<code>", // R!  draft | active | retired | unknown
  "

  "experimental" : <boolean>, // For testing purposes, not real usage

  "date" : "<dateTime>", // Date last changed
  "publisher" : "<string>", // Name of the publisher (organization or individual)
  "contact" : [{ ContactDetail }], // Contact details for the publisher
  "description" : "<markdown>", // Natural language description of the structure definition
  "

  "useContext" : [{ UsageContext }], // The context that the content is intended to support

  "jurisdiction" : [{ CodeableConcept }], // Intended jurisdiction for structure definition (if applicable)
  "purpose" : "<markdown>", // Why this structure definition is defined
  "copyright" : "<markdown>", // Use and/or publishing restrictions
  "
  "

  "keyword" : [{ Coding }], // Assist with indexing and finding
  "fhirVersion" : "<code>", // FHIR Version this StructureDefinition targets

  "mapping" : [{ // External specification that the content is mapped to
    "identity" : "<id>", // R!  Internal id when this mapping is used
    "uri" : "<uri>", // C? Identifies what this mapping refers to
    "name" : "<string>", // C? Names what this mapping refers to
    "comment" : "<string>" // Versions, Issues, Scope limitations etc.
  }],
  "kind" : "<code>", // R!  primitive-type | complex-type | resource | logical
  "abstract" : <boolean>, // R!  Whether the structure is abstract
  "context" : [{ // C? If an extension, where it can be used in instances
    "type" : "<code>", // R!  fhirpath | element | extension
    "expression" : "<string>" // R!  Where the extension can be used in instances
  }],
  "contextInvariant" : ["<string>"], // C? FHIRPath invariants - when the extension can be used
  "type" : "<uri>", // C? R!  Type defined or constrained by this structure
  "

  "baseDefinition" : { canonical(StructureDefinition) }, // C? Definition that this type is constrained/specialized from

  "derivation" : "<code>", // specialization | constraint - How relates to base definition
  "snapshot" : { // C? Snapshot view of the structure
    "element" : [{ ElementDefinition }] // C? R!  Definition of elements in the resource (if no StructureDefinition)
  },
  "differential" : { // C? Differential view of the structure
    "element" : [{ ElementDefinition }] // R!  Definition of elements in the resource (if no StructureDefinition)
  }
}

Turtle Template 

@prefix fhir: <http://hl7.org/fhir/> .doco


[ a fhir:StructureDefinition;
  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from Resource: .id, .meta, .implicitRules, and .language
  # from DomainResource: .text, .contained, .extension, and .modifierExtension
  fhir:

  fhir:StructureDefinition.url [ uri ]; # 1..1 Canonical identifier for this structure definition, represented as a URI (globally unique)

  fhir:StructureDefinition.identifier [ Identifier ], ... ; # 0..* Additional identifier for the structure definition
  fhir:StructureDefinition.version [ string ]; # 0..1 Business version of the structure definition
  fhir:StructureDefinition.name [ string ]; # 1..1 Name for this structure definition (computer friendly)
  fhir:StructureDefinition.title [ string ]; # 0..1 Name for this structure definition (human friendly)
  fhir:StructureDefinition.status [ code ]; # 1..1 draft | active | retired | unknown
  fhir:

  fhir:StructureDefinition.experimental [ boolean ]; # 0..1 For testing purposes, not real usage

  fhir:StructureDefinition.date [ dateTime ]; # 0..1 Date last changed
  fhir:StructureDefinition.publisher [ string ]; # 0..1 Name of the publisher (organization or individual)
  fhir:StructureDefinition.contact [ ContactDetail ], ... ; # 0..* Contact details for the publisher
  fhir:StructureDefinition.description [ markdown ]; # 0..1 Natural language description of the structure definition
  fhir:

  fhir:StructureDefinition.useContext [ UsageContext ], ... ; # 0..* The context that the content is intended to support

  fhir:StructureDefinition.jurisdiction [ CodeableConcept ], ... ; # 0..* Intended jurisdiction for structure definition (if applicable)
  fhir:StructureDefinition.purpose [ markdown ]; # 0..1 Why this structure definition is defined
  fhir:StructureDefinition.copyright [ markdown ]; # 0..1 Use and/or publishing restrictions
  fhir:
  fhir:

  fhir:StructureDefinition.keyword [ Coding ], ... ; # 0..* Assist with indexing and finding
  fhir:StructureDefinition.fhirVersion [ code ]; # 0..1 FHIR Version this StructureDefinition targets

  fhir:StructureDefinition.mapping [ # 0..* External specification that the content is mapped to
    fhir:StructureDefinition.mapping.identity [ id ]; # 1..1 Internal id when this mapping is used
    fhir:StructureDefinition.mapping.uri [ uri ]; # 0..1 Identifies what this mapping refers to
    fhir:StructureDefinition.mapping.name [ string ]; # 0..1 Names what this mapping refers to
    fhir:StructureDefinition.mapping.comment [ string ]; # 0..1 Versions, Issues, Scope limitations etc.
  ], ...;
  fhir:StructureDefinition.kind [ code ]; # 1..1 primitive-type | complex-type | resource | logical
  fhir:StructureDefinition.abstract [ boolean ]; # 1..1 Whether the structure is abstract
  fhir:StructureDefinition.context [ # 0..* If an extension, where it can be used in instances
    fhir:StructureDefinition.context.type [ code ]; # 1..1 fhirpath | element | extension
    fhir:StructureDefinition.context.expression [ string ]; # 1..1 Where the extension can be used in instances
  ], ...;
  fhir:StructureDefinition.contextInvariant [ string ], ... ; # 0..* FHIRPath invariants - when the extension can be used
  fhir:StructureDefinition.type [ uri ]; # 1..1 Type defined or constrained by this structure
  fhir:StructureDefinition.baseDefinition [ canonical(StructureDefinition) ]; # 0..1 Definition that this type is constrained/specialized from
  fhir:StructureDefinition.derivation [ code ]; # 0..1 specialization | constraint - How relates to base definition
  fhir:StructureDefinition.snapshot [ # 0..1 Snapshot view of the structure
    fhir:StructureDefinition.snapshot.element [ ElementDefinition ], ... ; # 1..* Definition of elements in the resource (if no StructureDefinition)
  ];
  fhir:StructureDefinition.differential [ # 0..1 Differential view of the structure
    fhir:StructureDefinition.differential.element [ ElementDefinition ], ... ; # 1..* Definition of elements in the resource (if no StructureDefinition)
  ];
]

Changes since R3

StructureDefinition
StructureDefinition.status
  • Change value set from http://hl7.org/fhir/ValueSet/publication-status to http://hl7.org/fhir/ValueSet/publication-status|4.0.1
StructureDefinition.experimental
  • No longer marked as Modifier
StructureDefinition.keyword
  • Add Binding http://hl7.org/fhir/ValueSet/definition-use (extensible)
StructureDefinition.fhirVersion
  • Type changed from id to code
  • Add Binding http://hl7.org/fhir/ValueSet/fhir-versions http://hl7.org/fhir/ValueSet/FHIR-version|4.0.1 (required)
StructureDefinition.kind
  • Change value set from http://hl7.org/fhir/ValueSet/structure-definition-kind to http://hl7.org/fhir/ValueSet/structure-definition-kind|4.0.1
StructureDefinition.context
  • Type changed from string to BackboneElement
StructureDefinition.context.type
  • Added Mandatory Element
StructureDefinition.context.expression
  • Added Mandatory Element
StructureDefinition.type
  • Type changed from code to uri
StructureDefinition.baseDefinition
  • Type changed from uri to canonical canonical(StructureDefinition)
StructureDefinition.derivation
  • Change value set from http://hl7.org/fhir/ValueSet/type-derivation-rule to http://hl7.org/fhir/ValueSet/type-derivation-rule|4.0.1
StructureDefinition.contextType
  • deleted

See the Full Difference for further information

This analysis is available as XML or JSON .

See R2 <--> R3 <--> R4 Conversion Maps (status = 248 206 tests that all execute ok. 60 4 fail round-trip testing and 145 206 r3 resources are invalid (441 (0 errors). ). Note: these have note yet been updated to be R3 to R4 )

Structure

?!
Name Flags Card. Type Description & Constraints doco
. . StructureDefinition I N DomainResource Structural Definition
+ In any snapshot or differential, no label, code or requirements on Warning: Name should be usable as an element without a "." in the path (e.g. identifier for the first element) module by machine processing applications such as code generation
+ Custom types can only Rule: Element paths must be used in logical models unique unless the structure is a constraint
+ All Rule: If the first element definitions must have unique ids (snapshot) in a differential has no "." in the path and it's not a logical model, it has no type
+ Context Invariants can only Rule: If the structure is not abstract, then there SHALL be used for extensions a baseDefinition
+ All element definitions Rule: If the structure defines an extension then the structure must have unique ids (diff) context information
+ element.base cannot appear if there is Rule: A structure must have either a differential, or a snapshot (or both)
+ Rule: In any snapshot or differential, no base label, code or requirements on an element without a "." in the structure definition path (e.g. the first element)
+ Rule: If there's a type, its content must match the path name in the first element of a snapshot
+ Rule: All element definitions must have an id
+ Element paths must be unique Rule: The first element in a snapshot has no type unless the structure model is a constraint logical model.
+ Default values Rule: All element definitions must have unique ids (snapshot)
+ Rule: All element definitions must have unique ids (diff)
+ Rule: Context Invariants can only be specified on logical models used for extensions
+ If the structure describes a base Resource or Type, the URL has to start with "http://hl7.org/fhir/StructureDefinition/" and the tail must match the id Rule: FHIR Specification models only use FHIR defined types
+ A structure must have either a differential, or a snapshot (or both) Rule: Default values can only be specified on specializations
+ If the structure defines an extension then the structure must Rule: FHIR Specification models never have context information default values
+ If the structure is not abstract, then there SHALL be a baseDefinition Rule: No slice name on root
Elements defined in Ancestors: id , meta , implicitRules , language , text , contained , extension , modifierExtension
. . . url Σ 1..1 uri Canonical identifier for this structure definition, represented as a URI (globally unique)
. . . identifier Σ 0..* Identifier Additional identifier for the structure definition
. . . version Σ 0..1 string Business version of the structure definition
. . . name Σ I 1..1 string Name for this structure definition (computer friendly)
. . . title Σ 0..1 string Name for this structure definition (human friendly)
. . . status ?! Σ 1..1 code draft | active | retired | unknown
PublicationStatus ( Required )
. . . experimental Σ 0..1 boolean For testing purposes, not real usage
. . . date Σ 0..1 dateTime Date last changed
. . . publisher Σ 0..1 string Name of the publisher (organization or individual)
. . . contact Σ 0..* ContactDetail Contact details for the publisher
. . . description 0..1 markdown Natural language description of the structure definition
. . . useContext Σ TU 0..* UsageContext The context that the content is intended to support
. . . jurisdiction Σ 0..* CodeableConcept Intended jurisdiction for structure definition (if applicable)
Jurisdiction ValueSet ( Extensible )
. . . purpose 0..1 markdown Why this structure definition is defined
. . . copyright 0..1 markdown Use and/or publishing restrictions
. . . keyword Σ 0..* Coding Assist with indexing and finding
Structure Definition Use Codes / Keywords ( Example Extensible )
. . . fhirVersion Σ 0..1 id code FHIR Version this StructureDefinition targets
All Published FHIR versions FHIRVersion ( Required )
. . . mapping I 0..* BackboneElement External specification that the content is mapped to
+ Rule: Must have at least a name or a uri (or both)
. . . . identity 1..1 id Internal id when this mapping is used
. . . . uri I 0..1 uri Identifies what this mapping refers to
. . . . name I 0..1 string Names what this mapping refers to
. . . . comment 0..1 string Versions, Issues, Scope limitations etc.
. . . kind Σ 1..1 code primitive-type | complex-type | resource | logical
StructureDefinitionKind ( Required )
. . . abstract Σ 1..1 boolean Whether the structure is abstract
. . . context Σ I 0..* BackboneElement If an extension, where it can be used in instances
. . . . type Σ 1..1 code fhirpath | element | extension
ExtensionContextType ( Required )
. . . . expression Σ 1..1 string Where the extension can be used in instances
. . . contextInvariant Σ I 0..* string FHIRPath invariants - when the extension can be used
. . . type Σ I 1..1 uri Type defined or constrained by this structure
FHIRDefinedType ( Extensible )
. . . baseDefinition Σ I 0..1 canonical ( StructureDefinition ) Definition that this type is constrained/specialized from
. . . derivation Σ 0..1 code specialization | constraint - How relates to base definition
TypeDerivationRule ( Required )
. . . snapshot I 0..1 BackboneElement Snapshot view of the structure
+ The first Rule: Each element definition in a snapshot has no type must have a formal definition and cardinalities
+ In any snapshot, all the Rule: All snapshot elements must be in start with the StructureDefinition's specified type, and must have a base definition type for non-logical models, or with the same type name for logical models
+ Each element definition in a Rule: All snapshot elements must have a formal base definition and cardinalities
. . . . element I 1..* ElementDefinition Definition of elements in the resource (if no StructureDefinition)
+ Rule: provide either a binding reference or a description (or both)
. . . differential I 0..1 BackboneElement Differential view of the structure
+ If the first element in a differential has no "." in the path, it has no type + Rule: No slicing on the root element
+ Rule: In any differential, all the elements must be in start with the StructureDefinition's specified type for non-logical models, or with the same type name for logical models
. . . . element 1..* ElementDefinition Definition of elements in the resource (if no StructureDefinition)

doco Documentation for this format

UML Diagram ( Legend )

StructureDefinition ( DomainResource ) An absolute URI that is used to identify this structure definition when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this structure definition is (or will be) published published. This URL can be the target of a canonical reference. It SHALL remain the same when the structure definition is stored on different servers url : uri [1..1] A formal identifier that is used to identify this structure definition when it is represented in other formats, or referenced in a specification, model, design or an instance identifier : Identifier [0..*] The identifier that is used to identify this version of the structure definition when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the structure definition author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence version : string [0..1] A natural language name identifying the structure definition. This name should be usable as an identifier for the module by machine processing applications such as code generation name : string [1..1] A short, descriptive, user-friendly title for the structure definition title : string [0..1] The status of this structure definition. Enables tracking the life-cycle of the content (this element modifies the meaning of other elements) status : code [1..1] « The lifecycle status of an artifact. (Strength=Required) PublicationStatus ! » A Boolean value to indicate that this structure definition is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage (this element modifies the meaning of other elements) experimental : boolean [0..1] The date (and optionally time) when the structure definition was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the structure definition changes date : dateTime [0..1] The name of the organization or individual that published the structure definition publisher : string [0..1] Contact details to assist a user in finding and communicating with the publisher contact : ContactDetail [0..*] A free text natural language description of the structure definition from a consumer's perspective description : markdown [0..1] The content was developed with a focus and intent of supporting the contexts that are listed. These terms contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate structure definition instances useContext : UsageContext [0..*] A legal or geographic region in which the structure definition is intended to be used jurisdiction : CodeableConcept [0..*] « Countries and regions within which this artifact is targeted for use use. (Strength=Extensible) Jurisdiction ValueSet + » Explanation of why this structure definition is needed and why it has been designed as it has purpose : markdown [0..1] 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 structure definition copyright : markdown [0..1] A set of key words or terms from external terminologies that may be used to assist with indexing and searching of templates nby describing the use of this structure definition, or the content it describes keyword : Coding [0..*] « Codes for the meaning of the defined structure (SNOMED CT and LOINC codes, as an example). (Strength=Example) (Strength=Extensible) Structure Definition DefinitionUseCodes ?? + » 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 3.3.0 4.0.1. for this version fhirVersion : id code [0..1] « All published FHIR Versions Versions. (Strength=Required) All Published FHIR versions FHIRVersion ! » Defines the kind of structure that this definition is describing kind : code [1..1] « Defines the type of structure that a definition is describing. (Strength=Required) StructureDefinitionKind ! » Whether structure this definition describes is abstract or not - that is, whether the structure is not intended to be instantiated. For Resources and Data types, abstract types will never be exchanged between systems abstract : boolean [1..1] A set of rules as FHIRPath Invariants about when the extension can be used (e.g. co-occurrence variants for the extension). All the rules must be true contextInvariant : string [0..*] The type this structure describes. If the derivation kind is 'specialization' then this is the master definition for a type, and there is always one of these (a data type, an extension, a resource, including abstract ones). Otherwise the structure definition is a constraint on the stated type (and in this case, the type cannot be an abstract type). References are URLs that are relative to http://hl7.org/fhir/StructureDefinition e.g. "string" is a reference to http://hl7.org/fhir/StructureDefinition/string. Absolute URLs are only allowed in logical models type : uri [1..1] « Either a resource or a data type, including logical model types types. (Strength=Extensible) FHIRDefinedType + » An absolute URI that is the base structure from which this type is derived, either by specialization or constraint baseDefinition : canonical [0..1] « StructureDefinition » How the type relates to the baseDefinition derivation : code [0..1] « How a type relates to its baseDefinition. (Strength=Required) TypeDerivationRule ! » Mapping An Internal id that is used to identify this mapping set when specific mappings are made identity : id [1..1] An absolute URI that identifies the specification that this mapping is expressed to uri : uri [0..1] A name for the specification that is being mapped to name : string [0..1] Comments about this mapping, including version notes, issues, scope limitations, and other important notes for usage comment : string [0..1] Context Defines how to interpret the expression that defines what the context of the extension is type : code [1..1] « How an extension context is interpreted. (Strength=Required) ExtensionContextType ! » An expression that defines where an extension can be used in resources expression : string [1..1] Snapshot Captures constraints on each element within the resource element : ElementDefinition [1..*] Differential Captures constraints on each element within the resource element : ElementDefinition [1..*] An external specification that the content is mapped to mapping [0..*] Identifies the types of resource or data type elements to which the extension can be applied context [0..*] A snapshot view is expressed in a standalone form that can be used and interpreted without considering the base StructureDefinition snapshot [0..1] A differential view is expressed relative to the base StructureDefinition - a statement of differences that it applies differential [0..1]

XML Template 

<StructureDefinition xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <

 <url value="[uri]"/><!-- 1..1 Canonical identifier for this structure definition, represented as a URI (globally unique) -->

 <identifier><!-- 0..* Identifier Additional identifier for the structure definition --></identifier>
 <version value="[string]"/><!-- 0..1 Business version of the structure definition -->
 <

 <name value="[string]"/><!-- ?? 1..1 Name for this structure definition (computer friendly) -->

 <title value="[string]"/><!-- 0..1 Name for this structure definition (human friendly) -->
 <status value="[code]"/><!-- 1..1 draft | active | retired | unknown -->
 <

 <experimental value="[boolean]"/><!-- 0..1 For testing purposes, not real usage -->

 <date value="[dateTime]"/><!-- 0..1 Date last changed -->
 <publisher value="[string]"/><!-- 0..1 Name of the publisher (organization or individual) -->
 <contact><!-- 0..* ContactDetail Contact details for the publisher --></contact>
 <description value="[markdown]"/><!-- 0..1 Natural language description of the structure definition -->
 <</useContext>

 <useContext><!-- 0..* UsageContext The context that the content is intended to support --></useContext>

 <jurisdiction><!-- 0..* CodeableConcept Intended jurisdiction for structure definition (if applicable) --></jurisdiction>
 <purpose value="[markdown]"/><!-- 0..1 Why this structure definition is defined -->
 <copyright value="[markdown]"/><!-- 0..1 Use and/or publishing restrictions -->
 <</keyword>
 <

 <keyword><!-- 0..* Coding Assist with indexing and finding --></keyword>
 <fhirVersion value="[code]"/><!-- 0..1 FHIR Version this StructureDefinition targets -->

 <mapping>  <!-- 0..* External specification that the content is mapped to -->
  <identity value="[id]"/><!-- 1..1 Internal id when this mapping is used -->
  <uri value="[uri]"/><!-- ?? 0..1 Identifies what this mapping refers to -->
  <name value="[string]"/><!-- ?? 0..1 Names what this mapping refers to -->
  <comment value="[string]"/><!-- 0..1 Versions, Issues, Scope limitations etc. -->
 </mapping>
 <kind value="[code]"/><!-- 1..1 primitive-type | complex-type | resource | logical -->
 <abstract value="[boolean]"/><!-- 1..1 Whether the structure is abstract -->
 <context>  <!-- ?? 0..* If an extension, where it can be used in instances -->
  <type value="[code]"/><!-- 1..1 fhirpath | element | extension -->
  <expression value="[string]"/><!-- 1..1 Where the extension can be used in instances -->
 </context>
 <contextInvariant value="[string]"/><!-- ?? 0..* FHIRPath invariants - when the extension can be used -->
 <type value="[uri]"/><!-- ?? 1..1 Type defined or constrained by this structure -->
 <baseDefinition><!-- ?? 0..1 canonical(StructureDefinition) Definition that this type is constrained/specialized from --></baseDefinition>
 <derivation value="[code]"/><!-- 0..1 specialization | constraint - How relates to base definition -->
 <snapshot>  <!-- ?? 0..1 Snapshot view of the structure -->
  <element><!-- ?? 1..* ElementDefinition Definition of elements in the resource (if no StructureDefinition) --></element>
 </snapshot>
 <differential>  <!-- ?? 0..1 Differential view of the structure -->
  <element><!-- 1..* ElementDefinition Definition of elements in the resource (if no StructureDefinition) --></element>
 </differential>
</StructureDefinition>

JSON Template 

{doco
  "resourceType" : "StructureDefinition",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "

  "url" : "<uri>", // R!  Canonical identifier for this structure definition, represented as a URI (globally unique)

  "identifier" : [{ Identifier }], // Additional identifier for the structure definition
  "version" : "<string>", // Business version of the structure definition
  "

  "name" : "<string>", // C? R!  Name for this structure definition (computer friendly)

  "title" : "<string>", // Name for this structure definition (human friendly)
  "status" : "<code>", // R!  draft | active | retired | unknown
  "

  "experimental" : <boolean>, // For testing purposes, not real usage

  "date" : "<dateTime>", // Date last changed
  "publisher" : "<string>", // Name of the publisher (organization or individual)
  "contact" : [{ ContactDetail }], // Contact details for the publisher
  "description" : "<markdown>", // Natural language description of the structure definition
  "

  "useContext" : [{ UsageContext }], // The context that the content is intended to support

  "jurisdiction" : [{ CodeableConcept }], // Intended jurisdiction for structure definition (if applicable)
  "purpose" : "<markdown>", // Why this structure definition is defined
  "copyright" : "<markdown>", // Use and/or publishing restrictions
  "
  "

  "keyword" : [{ Coding }], // Assist with indexing and finding
  "fhirVersion" : "<code>", // FHIR Version this StructureDefinition targets

  "mapping" : [{ // External specification that the content is mapped to
    "identity" : "<id>", // R!  Internal id when this mapping is used
    "uri" : "<uri>", // C? Identifies what this mapping refers to
    "name" : "<string>", // C? Names what this mapping refers to
    "comment" : "<string>" // Versions, Issues, Scope limitations etc.
  }],
  "kind" : "<code>", // R!  primitive-type | complex-type | resource | logical
  "abstract" : <boolean>, // R!  Whether the structure is abstract
  "context" : [{ // C? If an extension, where it can be used in instances
    "type" : "<code>", // R!  fhirpath | element | extension
    "expression" : "<string>" // R!  Where the extension can be used in instances
  }],
  "contextInvariant" : ["<string>"], // C? FHIRPath invariants - when the extension can be used
  "type" : "<uri>", // C? R!  Type defined or constrained by this structure
  "

  "baseDefinition" : { canonical(StructureDefinition) }, // C? Definition that this type is constrained/specialized from

  "derivation" : "<code>", // specialization | constraint - How relates to base definition
  "snapshot" : { // C? Snapshot view of the structure
    "element" : [{ ElementDefinition }] // C? R!  Definition of elements in the resource (if no StructureDefinition)
  },
  "differential" : { // C? Differential view of the structure
    "element" : [{ ElementDefinition }] // R!  Definition of elements in the resource (if no StructureDefinition)
  }
}

Turtle Template 

@prefix fhir: <http://hl7.org/fhir/> .doco


[ a fhir:StructureDefinition;
  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from Resource: .id, .meta, .implicitRules, and .language
  # from DomainResource: .text, .contained, .extension, and .modifierExtension
  fhir:

  fhir:StructureDefinition.url [ uri ]; # 1..1 Canonical identifier for this structure definition, represented as a URI (globally unique)

  fhir:StructureDefinition.identifier [ Identifier ], ... ; # 0..* Additional identifier for the structure definition
  fhir:StructureDefinition.version [ string ]; # 0..1 Business version of the structure definition
  fhir:StructureDefinition.name [ string ]; # 1..1 Name for this structure definition (computer friendly)
  fhir:StructureDefinition.title [ string ]; # 0..1 Name for this structure definition (human friendly)
  fhir:StructureDefinition.status [ code ]; # 1..1 draft | active | retired | unknown
  fhir:

  fhir:StructureDefinition.experimental [ boolean ]; # 0..1 For testing purposes, not real usage

  fhir:StructureDefinition.date [ dateTime ]; # 0..1 Date last changed
  fhir:StructureDefinition.publisher [ string ]; # 0..1 Name of the publisher (organization or individual)
  fhir:StructureDefinition.contact [ ContactDetail ], ... ; # 0..* Contact details for the publisher
  fhir:StructureDefinition.description [ markdown ]; # 0..1 Natural language description of the structure definition
  fhir:

  fhir:StructureDefinition.useContext [ UsageContext ], ... ; # 0..* The context that the content is intended to support

  fhir:StructureDefinition.jurisdiction [ CodeableConcept ], ... ; # 0..* Intended jurisdiction for structure definition (if applicable)
  fhir:StructureDefinition.purpose [ markdown ]; # 0..1 Why this structure definition is defined
  fhir:StructureDefinition.copyright [ markdown ]; # 0..1 Use and/or publishing restrictions
  fhir:
  fhir:

  fhir:StructureDefinition.keyword [ Coding ], ... ; # 0..* Assist with indexing and finding
  fhir:StructureDefinition.fhirVersion [ code ]; # 0..1 FHIR Version this StructureDefinition targets

  fhir:StructureDefinition.mapping [ # 0..* External specification that the content is mapped to
    fhir:StructureDefinition.mapping.identity [ id ]; # 1..1 Internal id when this mapping is used
    fhir:StructureDefinition.mapping.uri [ uri ]; # 0..1 Identifies what this mapping refers to
    fhir:StructureDefinition.mapping.name [ string ]; # 0..1 Names what this mapping refers to
    fhir:StructureDefinition.mapping.comment [ string ]; # 0..1 Versions, Issues, Scope limitations etc.
  ], ...;
  fhir:StructureDefinition.kind [ code ]; # 1..1 primitive-type | complex-type | resource | logical
  fhir:StructureDefinition.abstract [ boolean ]; # 1..1 Whether the structure is abstract
  fhir:StructureDefinition.context [ # 0..* If an extension, where it can be used in instances
    fhir:StructureDefinition.context.type [ code ]; # 1..1 fhirpath | element | extension
    fhir:StructureDefinition.context.expression [ string ]; # 1..1 Where the extension can be used in instances
  ], ...;
  fhir:StructureDefinition.contextInvariant [ string ], ... ; # 0..* FHIRPath invariants - when the extension can be used
  fhir:StructureDefinition.type [ uri ]; # 1..1 Type defined or constrained by this structure
  fhir:StructureDefinition.baseDefinition [ canonical(StructureDefinition) ]; # 0..1 Definition that this type is constrained/specialized from
  fhir:StructureDefinition.derivation [ code ]; # 0..1 specialization | constraint - How relates to base definition
  fhir:StructureDefinition.snapshot [ # 0..1 Snapshot view of the structure
    fhir:StructureDefinition.snapshot.element [ ElementDefinition ], ... ; # 1..* Definition of elements in the resource (if no StructureDefinition)
  ];
  fhir:StructureDefinition.differential [ # 0..1 Differential view of the structure
    fhir:StructureDefinition.differential.element [ ElementDefinition ], ... ; # 1..* Definition of elements in the resource (if no StructureDefinition)
  ];
]

Changes since DSTU2 Release 3

StructureDefinition
StructureDefinition.status
  • Change value set from http://hl7.org/fhir/ValueSet/publication-status to http://hl7.org/fhir/ValueSet/publication-status|4.0.1
StructureDefinition.experimental
  • No longer marked as Modifier
StructureDefinition.keyword
  • Add Binding http://hl7.org/fhir/ValueSet/definition-use (extensible)
StructureDefinition.fhirVersion
  • Type changed from id to code
  • Add Binding http://hl7.org/fhir/ValueSet/fhir-versions http://hl7.org/fhir/ValueSet/FHIR-version|4.0.1 (required)
StructureDefinition.kind
  • Change value set from http://hl7.org/fhir/ValueSet/structure-definition-kind to http://hl7.org/fhir/ValueSet/structure-definition-kind|4.0.1
StructureDefinition.context
  • Type changed from string to BackboneElement
StructureDefinition.context.type
  • Added Mandatory Element
StructureDefinition.context.expression
  • Added Mandatory Element
StructureDefinition.type
  • Type changed from code to uri
StructureDefinition.baseDefinition
  • Type changed from uri to canonical canonical(StructureDefinition)
StructureDefinition.derivation
  • Change value set from http://hl7.org/fhir/ValueSet/type-derivation-rule to http://hl7.org/fhir/ValueSet/type-derivation-rule|4.0.1
StructureDefinition.contextType
  • deleted

See the Full Difference for further information

This analysis is available as XML or JSON .

See R2 <--> R3 <--> R4 Conversion Maps (status = 248 206 tests that all execute ok. 60 4 fail round-trip testing and 145 206 r3 resources are invalid (441 (0 errors). ). Note: these have note yet been updated to be R3 to R4 )

 

Alternate See the Profiles & Extensions and the alternate definitions: Master Definition XML + JSON , XML Schema / Schematron + JSON Schema , ShEx (for Turtle ) + see the extensions & the dependency analysis

5.3.4.1 Terminology Bindings

Path Definition Type Reference
StructureDefinition.status The lifecycle status of an artifact. Required PublicationStatus
StructureDefinition.jurisdiction Countries and regions within which this artifact is targeted for use use. Extensible Jurisdiction ValueSet
StructureDefinition.keyword Codes for the meaning of the defined structure (SNOMED CT and LOINC codes, as an example). Example Extensible Structure Definition Codes DefinitionUseCodes
StructureDefinition.fhirVersion All published FHIR Versions Versions. Required All Published FHIR versions FHIRVersion
StructureDefinition.kind Defines the type of structure that a definition is describing. Required StructureDefinitionKind
StructureDefinition.context.type How an extension context is interpreted. Required ExtensionContextType
StructureDefinition.type Either a resource or a data type, including logical model types types. Extensible FHIRDefinedType
StructureDefinition.derivation How a type relates to its baseDefinition. Required TypeDerivationRule

5.3.4.2 Constraints

sdf-12 : element.base cannot appear if there is no base on the structure definition ( expression : snapshot.exists() implies (snapshot.element.base.exists() = baseDefinition.exists()) ) sdf-15a : On StructureDefinition.differential: If the sdf-2 : On StructureDefinition.mapping: Must have at least a name or a uri (or both) ( expression on StructureDefinition.mapping: name.exists() or uri.exists() ) sdf-4 : If the structure is not abstract, then there SHALL be a baseDefinition ( expression : abstract = true or baseDefinition.exists() ) sdf-8a : On StructureDefinition.differential: In any differential, all the elements must be in the specified type ( expression on StructureDefinition.differential: element.first().path.startsWith(%resource.type) and element.tail().all(path.startsWith(%resource.type&'.')) )
id Level Location Description Expression
sdf-0 Warning (base) Name should be usable as an identifier for the module by machine processing applications such as code generation name.matches('[A-Z]([A-Za-z0-9_]){0,254}')
sdf-1 : Rule (base) Element paths must be unique unless the structure is a constraint ( expression : derivation = 'constraint' or snapshot.element.select(path).isDistinct() )
sdf-15a Rule (base) If the first element in a differential has no "." in the path and it's not a logical model, it has no type (kind!='logical' and differential.element.first().path.contains('.').not()) implies differential.element.first().type.empty()
sdf-2 Rule StructureDefinition.mapping Must have at least a name or a uri (or both) name.exists() or uri.exists()
sdf-3 Rule StructureDefinition.snapshot Each element definition in a snapshot must have a formal definition and cardinalities element.all(definition.exists() and min.exists() and max.exists())
sdf-4 Rule (base) If the structure is not abstract, then there SHALL be a baseDefinition abstract = true or baseDefinition.exists()
sdf-5 Rule (base) If the structure defines an extension then the structure must have context information type != 'Extension' or derivation = 'specialization' or (context.exists())
sdf-6 Rule (base) A structure must have either a differential, or a snapshot (or both) snapshot.exists() or differential.exists()
sdf-8 Rule StructureDefinition.snapshot All snapshot elements must start with the StructureDefinition's specified type for non-logical models, or with the same type name for logical models (%resource.kind = 'logical' or element.first().path = %resource.type) and element.tail().all(path.startsWith(%resource.snapshot.element.first().path&'.'))
sdf-10 : On StructureDefinition.snapshot.element: Rule StructureDefinition.snapshot.element provide either a binding reference or a description (or both) ( expression on StructureDefinition.snapshot.element: binding.empty() or binding.valueSet.exists() or binding.description.exists() )
sdf-11 : Rule (base) If there's a type, its content must match the path name in the first element of a snapshot ( expression : kind != 'logical' implies snapshot.empty() or snapshot.element.first().path = type )
sdf-14 : Rule (base) All element definitions must have an id ( expression : snapshot.element.all(id.exists()) and differential.element.all(id.exists()) )
sdf-15 : On StructureDefinition.snapshot: The first element in a snapshot has no type ( expression Rule on StructureDefinition.snapshot: element.first().type.empty() ) (base) The first element in a differential has no "." in the path, it snapshot has no type ( expression unless model is a logical model. on StructureDefinition.differential: element.first().path.contains('.').not() kind!='logical' implies element.first().type.empty() snapshot.element.first().type.empty() )
sdf-16 : Rule (base) All element definitions must have unique ids (snapshot) ( expression : snapshot.element.all(id) snapshot.element.all(id.exists()) and snapshot.element.id.trace('ids').isDistinct() )
sdf-17 : Rule (base) All element definitions must have unique ids (diff) ( expression : differential.element.all(id) differential.element.all(id.exists()) and differential.element.id.trace('ids').isDistinct() )
sdf-18 : Rule (base) Context Invariants can only be used for extensions ( expression : contextInvariant.exists() implies type = 'Extension' )
sdf-19 : Custom types can only be used in logical Rule (base) FHIR Specification models ( expression only use FHIR defined types : kind = 'logical' or (differential.element.type.code.all(hasValue() url.startsWith('http://hl7.org/fhir/StructureDefinition') implies matches('^[a-zA-Z0-9]+$')) (differential.element.type.code.all(matches('^[a-zA-Z0-9]+$') or matches('^http:\\/\\/hl7\\.org\\/fhirpath\\/System\\.[A-Z][A-Za-z]+$')) and snapshot.element.type.code.all(hasValue() implies matches('^[a-zA-Z0-9]+$'))) snapshot.element.type.code.all(matches('^[a-zA-Z0-9\\.]+$') or matches('^http:\\/\\/hl7\\.org\\/fhirpath\\/System\\.[A-Z][A-Za-z]+$'))) )
sdf-20 : On StructureDefinition.differential: Rule StructureDefinition.differential No slicing on the root element ( expression on StructureDefinition.differential: element.where(path.contains('.').not()).slicing.empty() )
sdf-21 : Rule (base) Default values can only be specified on logical models ( expression specializations : (snapshot.element.defaultValue.exists() or differential.element.defaultValue.exists()) differential.element.defaultValue.exists() implies ((kind = 'logical') and (derivation = 'specialization')) 'specialization') )
sdf-3 : On StructureDefinition.snapshot: Each element definition in a snapshot must have a formal definition and cardinalities ( expression sdf-22 Rule on StructureDefinition.snapshot: (base) FHIR Specification models never have default values element.all(definition.exists() and min.exists() url.startsWith('http://hl7.org/fhir/StructureDefinition') implies (snapshot.element.defaultValue.empty() and max.exists()) differential.element.defaultValue.empty()) )
sdf-5 : If the structure defines an extension then the structure must have context information ( expression sdf-23 : type != 'Extension' or derivation = 'specialization' or (context.exists()) ) sdf-6 : A structure must have either a differential, or a snapshot (or both) ( expression Rule (base) No slice name on root : snapshot.exists() or differential.exists() (snapshot | differential).element.all(path.contains('.').not() implies sliceName.empty()) )
sdf-7 : If the structure describes a base Resource or Type, sdf-8a Rule StructureDefinition.differential In any differential, all the URL has to elements must start with "http://hl7.org/fhir/StructureDefinition/" and the tail must match StructureDefinition's specified type for non-logical models, or with the id ( expression same type name for logical models : (derivation (%resource.kind = 'constraint') 'logical' or (kind = 'logical') element.first().path.startsWith(%resource.type)) and (element.tail().empty() or (url = 'http://hl7.org/fhir/StructureDefinition/'+id) element.tail().all(path.startsWith(%resource.differential.element.first().path.replaceMatches('\\..*','')&'.'))) )
sdf-8 : On StructureDefinition.snapshot: In any snapshot, all the sdf-8b Rule StructureDefinition.snapshot All snapshot elements must be in the specified type, and must have a base definition ( expression on StructureDefinition.snapshot: element.first().path = %resource.type and element.tail().all(path.startsWith(%resource.type&'.')) and element.all(base.exists()) )
sdf-9 : Rule (base) In any snapshot or differential, no label, code or requirements on an element without a "." in the path (e.g. the first element) ( expression : children().element.where(path.contains('.').not()).label.empty() and children().element.where(path.contains('.').not()).code.empty() and children().element.where(path.contains('.').not()).requirements.empty() )

5.3.5 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 specialization profile 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 profiling a resource and only one type is specified, the name of the element is changed to include the type instead of '[x]'.
  • 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 is operator .
  • For XPath constraints, the prefix "f" should be used for "http://hl7.org/fhir", and "h" for "http://www.w3.org/1999/xhtml". XPath constraints are written against the XML representation
  • The condition element is used to assert that a constraint defined on another element affects the allowed cardinality of this element.

5.3.5.1 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 , constrainedType 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)
  "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",
  "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",
  "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",
  "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",
  "baseDefinition": "http://hl7.org/fhir/StructureDefinition/Composition"
}
  5. Base Extension (a standard data type) (example: Extension - XML , JSON ): 
    {
  "resourceType": "StructureDefinition",
  "url": "http://hl7.org/fhir/StructureDefinition/Extension",
  "name": "Extension",
  "kind": "datatype",
  "baseDefinition": "http://hl7.org/fhir/StructureDefinition/Element"
}
  6. 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",
  "baseDefinition": "http://hl7.org/fhir/StructureDefinition/Extension"
}
  7. 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",
  "baseDefinition": "http://hl7.org/fhir/us/core/StructureDefinition/us-core-race"
}

On this list, structure definitions of type 1, 3, and 5 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.3.5.2 Rules for Constrained Types

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

5.3.5.3 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
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
Mapping to NCPDP SCRIPT 10.6 Formal URL: http://ncpdp.org/SCRIPT10_6
FiveWs Pattern Mapping Formal URL: http://hl7.org/fhir/fivews
BRIDG 5.1 Mapping Formal URL: https://bridgmodel.nci.nih.gov
FHIR Composition Formal URL: http://hl7.org/fhir/composition
IHE Structured Data Capture Formal URL: http://siframework.org/ihe-sdc-profile
Canadian Dental Association eclaims standard Formal URL: http://www.cda-adc.ca/en/services/cdanet/
SNOMED CT Concept Domain Binding Formal URL: 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
R3-ReferalRequest Mapping Formal URL: http://hl7.org/fhir/rr
HL7 v2 Mapping Formal URL: http://hl7.org/v2
RIM Mapping Formal URL: http://hl7.org/v3
ISO 11179 Formal URL: 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.

SNOMED CT Attribute Binding Formal URL: http://snomed.info/sct 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 Mapping to Quality Improvement Domain Analysis Model Formal URL: http://hl7.org/qidam
DICOM Tag Mapping Formal URL: http://nema.org/dicom
MDMI Referent Index Mapping Formal URL: http://github.com/MDMI/ReferentIndexContent
V3 Pharmacy Dispense RMIM Formal URL: http://www.hl7.org/v3/PORX_RM020070UV
XDS metadata equivalent Formal URL: http://ihe.net/xds
Equivalent CAP Code Formal URL: http://cap.org/ecc
CDA (R2) Formal URL: http://hl7.org/v3/cda
Quality Improvement and Clinical Knowledge (QUICK) Formal URL: http://siframework.org/cqf
FHIR DocumentReference Formal URL: http://hl7.org/fhir/documentreference
Canadian Pharmacy Associaiton eclaims standard Formal URL: http://www.pharmacists.ca/
UDI Mapping Formal URL: http://fda.gov/UDI

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 Formal URL: http://www.healthit.gov/quality-data-model
FHIR AuditEvent Mapping Formal URL: http://hl7.org/fhir/auditevent
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:

  • 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
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.3.5.4 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.3.6 Search Parameters

Search parameters for 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 TU token Whether the structure is abstract StructureDefinition.abstract
base TU reference Definition that this type is constrained/specialized from StructureDefinition.baseDefinition
( StructureDefinition )
base-path TU token Path that identifies the base element StructureDefinition.snapshot.element.base.path | StructureDefinition.differential.element.base.path
context TU token A use context assigned to the structure definition (StructureDefinition.useContext.value as CodeableConcept)
context-quantity TU quantity A quantity- or range-valued use context assigned to the structure definition (StructureDefinition.useContext.value as Quantity) | (StructureDefinition.useContext.value as Range)
context-type TU token A type of use context assigned to the structure definition StructureDefinition.useContext.code
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.as(Quantity) | value.as(Range)
context-type-value TU composite A use context type and value assigned to the structure definition On StructureDefinition.useContext:
  context-type: code
  context: value.as(CodeableConcept)
date TU date The structure definition publication date StructureDefinition.date
derivation TU token specialization | constraint - How relates to base definition StructureDefinition.derivation
description TU string The description of the structure definition StructureDefinition.description
experimental TU token For testing purposes, not real usage StructureDefinition.experimental
ext-context TU token The system is the URL for the context-type: e.g. http://hl7.org/fhir/extension-context-type#element|CodeableConcept.text StructureDefinition.context StructureDefinition.context.type
identifier TU token External identifier for the structure definition StructureDefinition.identifier
jurisdiction TU token Intended jurisdiction for the structure definition StructureDefinition.jurisdiction
keyword TU token A code for the profile StructureDefinition StructureDefinition.keyword
kind TU token primitive-type | complex-type | resource | logical StructureDefinition.kind
name TU string Computationally friendly name of the structure definition StructureDefinition.name
path TU token A path that is constrained in the profile StructureDefinition StructureDefinition.snapshot.element.path | StructureDefinition.differential.element.path
publisher TU string Name of the publisher of the structure definition StructureDefinition.publisher
status TU token The current status of the structure definition StructureDefinition.status
title TU string The human-friendly name of the structure definition StructureDefinition.title
type TU uri Type defined or constrained by this structure StructureDefinition.type
url TU uri The uri that identifies the structure definition StructureDefinition.url
valueset TU reference A vocabulary binding reference StructureDefinition.snapshot.element.binding.valueSet
( ValueSet )
version TU token The business version of the structure definition StructureDefinition.version