A set of rules of how a particular interoperability or standards problem is solved - typically through the use of FHIR resources. This resource is used to gather all the parts of an implementation guide into a logical whole and to publish a computable definition of all the parts.

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.

Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.

May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

An absolute URI that is used to identify this implementation guide 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 implementation guide is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the implementation guide is stored on different servers.

Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version.

The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in Technical and Business Versions.

In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the meta.source element to indicate where the current master source of the resource can be found.

Allows the implementation guide to be referenced by a single globally unique identifier. This is required to allow hosting Implementation Guides on multiple different servers, and to allow for the editorial process.

A natural language name identifying the implementation guide. This name should be usable as an identifier for the module by machine processing applications such as code generation.

The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.

Support human navigation and code generation.

The status of this implementation guide. Enables tracking the life-cycle of the content.

Allows filtering of implementation guides that are appropriate for use versus not.

The lifecycle status of an artifact.

The NPM package name for this Implementation Guide, used in the NPM package distribution, which is the primary mechanism by which FHIR based tooling manages IG dependencies. This value must be globally unique, and should be assigned with care.

Many (if not all) IG publishing tools will require that this element be present. For implementation guides published through HL7 or the FHIR foundation, the FHIR product director assigns package IDs.

The version(s) of the FHIR specification that this ImplementationGuide targets - e.g. describes how to use. The value of this element is the formal version of the specification, without the revision number, e.g. [publication].[major].[minor], which is 4.3.0. for this version.

Most implementation guides target a single version - e.g. they describe how to use a particular version, and the profiles and examples etc are valid for that version. But some implementation guides describe how to use multiple different versions of FHIR to solve the same problem, or in concert with each other. Typically, the requirement to support multiple versions arises as implementation matures and different implementation communities are stuck at different versions by regulation or market dynamics.

All published FHIR Versions.

STU3: ImplementationGuide.meta additional types (Meta) additional types from child elements (lastUpdated, profile, security, tag, versionId)

Element ImplementationGuide.meta is mapped to FHIR R4B element ImplementationGuide.meta as SourceIsBroaderThanTarget. The mappings for ImplementationGuide.meta do not cover the following types: Meta. The mappings for ImplementationGuide.meta do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.

STU3: ImplementationGuide.text additional types (Narrative) additional types from child elements (div, status)

Element ImplementationGuide.text is mapped to FHIR R4B element ImplementationGuide.text as SourceIsBroaderThanTarget. The mappings for ImplementationGuide.text do not cover the following types: Narrative. The mappings for ImplementationGuide.text do not cover the following types based on type expansion: div, status. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded in formation is added later.

STU3: ImplementationGuide.contact additional types (ContactDetail) additional types from child elements (name, telecom)

Element ImplementationGuide.contact is mapped to FHIR R4B element ImplementationGuide.contact as SourceIsBroaderThanTarget. The mappings for ImplementationGuide.contact do not cover the following types: ContactDetail. The mappings for ImplementationGuide.contact do not cover the following types based on type expansion: name, telecom. May be a web site, an email address, a telephone number, etc.

STU3: ImplementationGuide.useContext additional types (UsageContext) additional types from child elements (code, value[x])

Element ImplementationGuide.useContext is mapped to FHIR R4B element ImplementationGuide.useContext as SourceIsBroaderThanTarget. The mappings for ImplementationGuide.useContext do not cover the following types: UsageContext. The mappings for ImplementationGuide.useContext do not cover the following types based on type expansion: code, value[x]. When multiple useContexts are specified, there is no expectation whether all or any of the contexts apply.

STU3: ImplementationGuide.dependency.type (new:code)

Element ImplementationGuide.dependency.type has a context of ImplementationGuide.dependsOn based on following the parent source element upwards and mapping to ImplementationGuide. Element ImplementationGuide.dependency.type has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). For information about processing included guides, see [Including Guides]{implementationguide.html#include}.

STU3: ImplementationGuide.global.type additional codes

Element ImplementationGuide.global.type is mapped to FHIR R4B element ImplementationGuide.global.type as RelatedTo. The mappings for ImplementationGuide.global.type do not allow expression of the necessary codes, per the bindings on the source and target. The type must match that of the profile that is referred to, but is made explicit here as a denormalization so that a system processing the implementation guide resource knows which resources the profile applies to even if the profile itself is not available.

STU3: ImplementationGuide.global.profile additional types (Reference(http://hl7.org/fhir/StructureDefinition/StructureDefinition)) additional types from child elements (display, identifier, reference)

Element ImplementationGuide.global.profile is mapped to FHIR R4B element ImplementationGuide.global.profile as SourceIsBroaderThanTarget. The mappings for ImplementationGuide.global.profile do not cover the following types: Reference. The mappings for ImplementationGuide.global.profile do not cover the following types based on type expansion: display, identifier, reference.

STU3: ImplementationGuide.package.resource.acronym (new:string)

Element ImplementationGuide.package.resource.acronym has a context of ImplementationGuide.definition.resource based on following the parent source element upwards and mapping to ImplementationGuide. Element ImplementationGuide.package.resource.acronym has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). This is used when generating schematrons from profiles, for example, but has other uses. Publishing tooling may autogenerate this value, but a human assigned value is more useful. This value must be unique within an implementation guide (across included guides as well).

STU3: ImplementationGuide.package.resource.exampleFor additional types (Reference(http://hl7.org/fhir/StructureDefinition/StructureDefinition)) additional types from child elements (display, identifier, reference)

Element ImplementationGuide.package.resource.exampleFor is mapped to FHIR R4B element ImplementationGuide.definition.resource.example[x] as RelatedTo. The mappings for ImplementationGuide.package.resource.exampleFor do not cover the following types: Reference. The mappings for ImplementationGuide.package.resource.exampleFor do not cover the following types based on type expansion: display, identifier, reference. The target context ImplementationGuide.definition.resource.example[x] is a choice-type element and cannot directly hold extensions. The context is moved up to parent element ImplementationGuide.definition.resource. Examples:

• StructureDefinition -> Any
• ValueSet -> expansion
• OperationDefinition -> Parameters
• Questionnaire -> QuestionnaireResponse.

STU3: ImplementationGuide.package.resource.source[x] additional types (uri) additional types from child elements (value, display, identifier, reference)

Element ImplementationGuide.package.resource.source[x] is mapped to FHIR R4B element ImplementationGuide.definition.resource.reference as SourceIsBroaderThanTarget. The mappings for ImplementationGuide.package.resource.source[x] do not cover the following types: uri. The mappings for ImplementationGuide.package.resource.source[x] do not cover the following types based on type expansion: display, identifier, reference, value. The standard extension alternate-reference has been mapped as PART of the representation of FHIR STU3 element ImplementationGuide.package.resource.source[x] with unmapped reference targets: Resource. Usually this is a relative URL that locates the resource within the implementation guide. If you authoring an implementation guide, and will publish it using the FHIR publication tooling, use a URI that may point to a resource, or to one of various alternative representations (e.g. spreadsheet). The tooling will convert this when it publishes it.

STU3: ImplementationGuide.package.resource.source[x] additional types (uri) additional types from child elements (value, display, identifier, reference)

Element ImplementationGuide.package.resource.source[x] is mapped to FHIR R4B element ImplementationGuide.definition.resource.reference as SourceIsBroaderThanTarget. The mappings for ImplementationGuide.package.resource.source[x] do not cover the following types: uri. The mappings for ImplementationGuide.package.resource.source[x] do not cover the following types based on type expansion: display, identifier, reference, value. The standard extension alternate-reference has been mapped as PART of the representation of FHIR STU3 element ImplementationGuide.package.resource.source[x] with unmapped reference targets: Resource. Usually this is a relative URL that locates the resource within the implementation guide. If you authoring an implementation guide, and will publish it using the FHIR publication tooling, use a URI that may point to a resource, or to one of various alternative representations (e.g. spreadsheet). The tooling will convert this when it publishes it.

STU3: ImplementationGuide.page.kind (new:code)

Element ImplementationGuide.page.kind has a context of ImplementationGuide.manifest.page based on following the parent source element upwards and mapping to ImplementationGuide. Element ImplementationGuide.page.kind has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).

STU3: ImplementationGuide.page.type (new:code)

Element ImplementationGuide.page.type has a context of ImplementationGuide.manifest.page based on following the parent source element upwards and mapping to ImplementationGuide. Element ImplementationGuide.page.type has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).

STU3: ImplementationGuide.page.package (new:string)

Element ImplementationGuide.page.package has a context of ImplementationGuide.manifest.page based on following the parent source element upwards and mapping to ImplementationGuide. Element ImplementationGuide.page.package has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).

STU3: ImplementationGuide.page.format (new:code)

Element ImplementationGuide.page.format has a context of ImplementationGuide.manifest.page based on following the parent source element upwards and mapping to ImplementationGuide. Element ImplementationGuide.page.format has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). This is primarily for the publishing tool, that will convert all pages to html format. HTML pages are pre-processed, see xxxx.

STU3: ImplementationGuide.page.page (new:ImplementationGuide.page)

Element ImplementationGuide.page.page has a context of ImplementationGuide.manifest.page based on following the parent source element upwards and mapping to ImplementationGuide. Element ImplementationGuide.page.page has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). The implementation guide breadcrumbs are generated from this structure.

A set of rules of how a particular interoperability or standards problem is solved - typically through the use of FHIR resources. This resource is used to gather all the parts of an implementation guide into a logical whole and to publish a computable definition of all the parts.

The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

The only time that a resource does not have an id is when it is being submitted to the server using a create operation.

The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

STU3: ImplementationGuide.meta additional types (Meta) additional types from child elements (lastUpdated, profile, security, tag, versionId)

Element ImplementationGuide.meta is mapped to FHIR R4B element ImplementationGuide.meta as SourceIsBroaderThanTarget. The mappings for ImplementationGuide.meta do not cover the following types: Meta. The mappings for ImplementationGuide.meta do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.

The version specific identifier, as it appears in the version portion of the URL. This value changes when the resource is created, updated, or deleted.

The server assigns this value, and ignores what the client specifies, except in the case that the server is imposing version integrity on updates/deletes.

When the resource last changed - e.g. when the version changed.

This value is always populated except when the resource is first being created. The server / resource manager sets this value; what a client provides is irrelevant. This is equivalent to the HTTP Last-Modified and SHOULD have the same value on a read interaction.

A uri that identifies the source system of the resource. This provides a minimal amount of Provenance information that can be used to track or differentiate the source of information in the resource. The source may identify another FHIR server, document, message, database, etc.

In the provenance resource, this corresponds to Provenance.entity.what[x]. The exact use of the source (and the implied Provenance.entity.role) is left to implementer discretion. Only one nominated source is allowed; for additional provenance details, a full Provenance resource should be used.

This element can be used to indicate where the current master source of a resource that has a canonical URL if the resource is no longer hosted at the canonical URL.

A list of profiles (references to StructureDefinition resources) that this resource claims to conform to. The URL is a reference to StructureDefinition.url.

It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set.

Security labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure.

The security labels can be updated without changing the stated version of the resource. The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored.

Tags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource.

The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored.

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.

Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.

The base language in which the resource is written.

Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).

IETF language tag

A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.

Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

STU3: ImplementationGuide.text additional types (Narrative) additional types from child elements (div, status)

Element ImplementationGuide.text is mapped to FHIR R4B element ImplementationGuide.text as SourceIsBroaderThanTarget. The mappings for ImplementationGuide.text do not cover the following types: Narrative. The mappings for ImplementationGuide.text do not cover the following types based on type expansion: div, status. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded in formation is added later.

The status of the narrative - whether it's entirely generated (from just the defined data or the extensions too), or whether a human authored it and it may contain additional data.

The actual narrative content, a stripped down version of XHTML.

The contents of the html element are an XHTML fragment containing only the basic html formatting elements described in chapters 7-11 and 15 of the HTML 4.0 standard, <a> elements (either name or href), images and internally contained stylesheets. The XHTML content SHALL NOT contain a head, a body, external stylesheet references, scripts, forms, base/link/xlink, frames, iframes and objects.

These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.

This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.

May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

An absolute URI that is used to identify this implementation guide 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 implementation guide is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the implementation guide is stored on different servers.

Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version.

The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in Technical and Business Versions.

In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the meta.source element to indicate where the current master source of the resource can be found.

Allows the implementation guide to be referenced by a single globally unique identifier. This is required to allow hosting Implementation Guides on multiple different servers, and to allow for the editorial process.

The identifier that is used to identify this version of the implementation guide when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the implementation guide 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.

There may be different implementation guide instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the implementation guide with the format [url]|[version].

A natural language name identifying the implementation guide. This name should be usable as an identifier for the module by machine processing applications such as code generation.

The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.

Support human navigation and code generation.

A short, descriptive, user-friendly title for the implementation guide.

This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.

The status of this implementation guide. Enables tracking the life-cycle of the content.

Allows filtering of implementation guides that are appropriate for use versus not.

The lifecycle status of an artifact.

A Boolean value to indicate that this implementation guide is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage.

Allows filtering of implementation guides that are appropriate for use versus not.

Enables experimental content to be developed following the same lifecycle that would be used for a production-level implementation guide.

The date (and optionally time) when the implementation guide 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 implementation guide changes.

Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the implementation guide. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.

The name of the organization or individual that published the implementation guide.

Usually an organization but may be an individual. The publisher (or steward) of the implementation guide is the organization or individual primarily responsible for the maintenance and upkeep of the implementation guide. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the implementation guide. This item SHOULD be populated unless the information is available from context.

Helps establish the "authority/credibility" of the implementation guide. May also allow for contact.

Contact details to assist a user in finding and communicating with the publisher.

May be a web site, an email address, a telephone number, etc.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

STU3: ImplementationGuide.contact additional types (ContactDetail) additional types from child elements (name, telecom)

Element ImplementationGuide.contact is mapped to FHIR R4B element ImplementationGuide.contact as SourceIsBroaderThanTarget. The mappings for ImplementationGuide.contact do not cover the following types: ContactDetail. The mappings for ImplementationGuide.contact do not cover the following types based on type expansion: name, telecom. May be a web site, an email address, a telephone number, etc.

The name of an individual to contact.

If there is no named individual, the telecom information is for the organization as a whole.

The contact details for the individual (if a name was provided) or the organization.

A free text natural language description of the implementation guide from a consumer's perspective.

This description can be used to capture details such as why the implementation guide was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the implementation guide as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the implementation guide is presumed to be the predominant language in the place the implementation guide was created).

The content was developed with a focus and intent of supporting the contexts that are listed. These 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 implementation guide instances.

When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.

Assist in searching for appropriate content.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

STU3: ImplementationGuide.useContext additional types (UsageContext) additional types from child elements (code, value[x])

Element ImplementationGuide.useContext is mapped to FHIR R4B element ImplementationGuide.useContext as SourceIsBroaderThanTarget. The mappings for ImplementationGuide.useContext do not cover the following types: UsageContext. The mappings for ImplementationGuide.useContext do not cover the following types based on type expansion: code, value[x]. When multiple useContexts are specified, there is no expectation whether all or any of the contexts apply.

A code that identifies the type of context being specified by this usage context.

A value that defines the context specified in this context of use. The interpretation of the value is defined by the code.

A legal or geographic region in which the implementation guide is intended to be used.

It may be possible for the implementation guide to be used in jurisdictions other than those for which it was originally designed or intended.

Countries and regions within which this artifact is targeted for use.

A copyright statement relating to the implementation guide and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the implementation guide.

Consumers must be able to determine any legal restrictions on the use of the implementation guide and/or its content.

The NPM package name for this Implementation Guide, used in the NPM package distribution, which is the primary mechanism by which FHIR based tooling manages IG dependencies. This value must be globally unique, and should be assigned with care.

Many (if not all) IG publishing tools will require that this element be present. For implementation guides published through HL7 or the FHIR foundation, the FHIR product director assigns package IDs.

The license that applies to this Implementation Guide, using an SPDX license code, or 'not-open-source'.

The license that applies to an Implementation Guide (using an SPDX license Identifiers, or 'not-open-source'). The binding is required but new SPDX license Identifiers are allowed to be used (https://spdx.org/licenses/).

The version(s) of the FHIR specification that this ImplementationGuide targets - e.g. describes how to use. The value of this element is the formal version of the specification, without the revision number, e.g. [publication].[major].[minor], which is 4.3.0. for this version.

Most implementation guides target a single version - e.g. they describe how to use a particular version, and the profiles and examples etc are valid for that version. But some implementation guides describe how to use multiple different versions of FHIR to solve the same problem, or in concert with each other. Typically, the requirement to support multiple versions arises as implementation matures and different implementation communities are stuck at different versions by regulation or market dynamics.

All published FHIR Versions.

Another implementation guide that this implementation depends on. Typically, an implementation guide uses value sets, profiles etc.defined in other implementation guides.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

STU3: ImplementationGuide.dependency.type (new:code)

Element ImplementationGuide.dependency.type has a context of ImplementationGuide.dependsOn based on following the parent source element upwards and mapping to ImplementationGuide. Element ImplementationGuide.dependency.type has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). For information about processing included guides, see [Including Guides]{implementationguide.html#include}.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

A canonical reference to the Implementation guide for the dependency.

Usually, A canonical reference to the implementation guide is the same as the master location at which the implementation guide is published.

The NPM package name for the Implementation Guide that this IG depends on.

The version of the IG that is depended on, when the correct version is required to understand the IG correctly.

This follows the syntax of the NPM packaging version field - see [[reference]].

A set of profiles that all resources covered by this implementation guide must conform to.

See Default Profiles for a discussion of which resources are 'covered' by an implementation guide.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

The type of resource that all instances must conform to.

The type must match that of the profile that is referred to but is made explicit here as a denormalization so that a system processing the implementation guide resource knows which resources the profile applies to even if the profile itself is not available.

One of the resource types defined as part of this version of FHIR.

unique id for the element within a resource (for internal references)

An Extension

STU3: ImplementationGuide.global.type additional codes

Element ImplementationGuide.global.type is mapped to FHIR R4B element ImplementationGuide.global.type as RelatedTo. The mappings for ImplementationGuide.global.type do not allow expression of the necessary codes, per the bindings on the source and target. The type must match that of the profile that is referred to, but is made explicit here as a denormalization so that a system processing the implementation guide resource knows which resources the profile applies to even if the profile itself is not available.

Primitive value for code

A reference to the profile that all instances must conform to.

unique id for the element within a resource (for internal references)

An Extension

STU3: ImplementationGuide.global.profile additional types (Reference(http://hl7.org/fhir/StructureDefinition/StructureDefinition)) additional types from child elements (display, identifier, reference)

Element ImplementationGuide.global.profile is mapped to FHIR R4B element ImplementationGuide.global.profile as SourceIsBroaderThanTarget. The mappings for ImplementationGuide.global.profile do not cover the following types: Reference. The mappings for ImplementationGuide.global.profile do not cover the following types based on type expansion: display, identifier, reference.

Primitive value for canonical

The information needed by an IG publisher tool to publish the whole implementation guide.

Principally, this consists of information abuot source resource and file locations, and build parameters and templates.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

A logical group of resources. Logical groups can be used when building pages.

Groupings are arbitrary sub-divisions of content. Typically, they are used to help build Table of Contents automatically.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

The human-readable title to display for the package of resources when rendering the implementation guide.

Human readable text describing the package.

A resource that is part of the implementation guide. Conformance resources (value set, structure definition, capability statements etc.) are obvious candidates for inclusion, but any kind of resource can be included as an example resource.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

STU3: ImplementationGuide.package.resource.acronym (new:string)

Element ImplementationGuide.package.resource.acronym has a context of ImplementationGuide.definition.resource based on following the parent source element upwards and mapping to ImplementationGuide. Element ImplementationGuide.package.resource.acronym has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). This is used when generating schematrons from profiles, for example, but has other uses. Publishing tooling may autogenerate this value, but a human assigned value is more useful. This value must be unique within an implementation guide (across included guides as well).

STU3: ImplementationGuide.package.resource.exampleFor additional types (Reference(http://hl7.org/fhir/StructureDefinition/StructureDefinition)) additional types from child elements (display, identifier, reference)

Element ImplementationGuide.package.resource.exampleFor is mapped to FHIR R4B element ImplementationGuide.definition.resource.example[x] as RelatedTo. The mappings for ImplementationGuide.package.resource.exampleFor do not cover the following types: Reference. The mappings for ImplementationGuide.package.resource.exampleFor do not cover the following types based on type expansion: display, identifier, reference. The target context ImplementationGuide.definition.resource.example[x] is a choice-type element and cannot directly hold extensions. The context is moved up to parent element ImplementationGuide.definition.resource. Examples:

• StructureDefinition -> Any
• ValueSet -> expansion
• OperationDefinition -> Parameters
• Questionnaire -> QuestionnaireResponse.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Where this resource is found.

Usually this is a relative URL that locates the resource within the implementation guide. If you authoring an implementation guide, and will publish it using the FHIR publication tooling, use a URI that may point to a resource, or to one of various alternative representations (e.g. spreadsheet). The tooling will convert this when it publishes it.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

STU3: ImplementationGuide.package.resource.source[x] additional types (uri) additional types from child elements (value, display, identifier, reference)

Element ImplementationGuide.package.resource.source[x] is mapped to FHIR R4B element ImplementationGuide.definition.resource.reference as SourceIsBroaderThanTarget. The mappings for ImplementationGuide.package.resource.source[x] do not cover the following types: uri. The mappings for ImplementationGuide.package.resource.source[x] do not cover the following types based on type expansion: display, identifier, reference, value. The standard extension alternate-reference has been mapped as PART of the representation of FHIR STU3 element ImplementationGuide.package.resource.source[x] with unmapped reference targets: Resource. Usually this is a relative URL that locates the resource within the implementation guide. If you authoring an implementation guide, and will publish it using the FHIR publication tooling, use a URI that may point to a resource, or to one of various alternative representations (e.g. spreadsheet). The tooling will convert this when it publishes it.

STU3: ImplementationGuide.package.resource.source[x] additional types (uri) additional types from child elements (value, display, identifier, reference)

Element ImplementationGuide.package.resource.source[x] is mapped to FHIR R4B element ImplementationGuide.definition.resource.reference as SourceIsBroaderThanTarget. The mappings for ImplementationGuide.package.resource.source[x] do not cover the following types: uri. The mappings for ImplementationGuide.package.resource.source[x] do not cover the following types based on type expansion: display, identifier, reference, value. The standard extension alternate-reference has been mapped as PART of the representation of FHIR STU3 element ImplementationGuide.package.resource.source[x] with unmapped reference targets: Resource. Usually this is a relative URL that locates the resource within the implementation guide. If you authoring an implementation guide, and will publish it using the FHIR publication tooling, use a URI that may point to a resource, or to one of various alternative representations (e.g. spreadsheet). The tooling will convert this when it publishes it.

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.

The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).

This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.

An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

Indicates the FHIR Version(s) this artifact is intended to apply to. If no versions are specified, the resource is assumed to apply to all the versions stated in ImplementationGuide.fhirVersion.

The resource SHALL be valid against all the versions it is specified to apply to. If the resource referred to is a StructureDefinition, the fhirVersion stated in the StructureDefinition cannot disagree with the version specified here; the specified versions SHALL include the version specified by the StructureDefinition, and may include additional versions using the applicable-version extension.

All published FHIR Versions.

A human assigned name for the resource. All resources SHOULD have a name, but the name may be extracted from the resource (e.g. ValueSet.name).

A description of the reason that a resource has been included in the implementation guide.

This is mostly used with examples to explain why it is present (though they can have extensive comments in the examples).

If true or a reference, indicates the resource is an example instance. If a reference is present, indicates that the example is an example of the specified profile.

Examples:

• StructureDefinition -> Any
• ValueSet -> expansion
• OperationDefinition -> Parameters
• Questionnaire -> QuestionnaireResponse.

Reference to the id of the grouping this resource appears in.

This must correspond to a package.id element within this implementation guide.

A page / section in the implementation guide. The root page is the implementation guide home page.

Pages automatically become sections if they have sub-pages. By convention, the home page is called index.html.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

The source address for the page.

The publishing tool will autogenerate source for list (source = n/a) and inject included implementations for include (source = uri of guide to include).

A short title used to represent this page in navigational structures such as table of contents, bread crumbs, etc.

A code that indicates how the page is generated.

A code that indicates how the page is generated.

Nested Pages/Sections under this page.

The implementation guide breadcrumbs are generated from this structure.

Defines how IG is built by tools.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

apply | path-resource | path-pages | path-tx-cache | expansion-parameter | rule-broken-links | generate-xml | generate-json | generate-turtle | html-template.

Code of parameter that is input to the guide.

Value for named type.

A template for building resources.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Type of template specified.

The source location for the template.

The scope in which the template applies.

Information about an assembled implementation guide, created by the publication tooling.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

A pointer to official web page, PDF or other rendering of the implementation guide.

A resource that is part of the implementation guide. Conformance resources (value set, structure definition, capability statements etc.) are obvious candidates for inclusion, but any kind of resource can be included as an example resource.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.