Legally enforceable, formally recorded unilateral or bilateral directive i.e., a policy or agreement.

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 its narrative along with other profiles, value sets, etc.

These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.

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.

An Extension

DSTU2: Contract.action (new:CodeableConcept)

Element Contract.action has a context of Contract based on following the parent source element upwards and mapping to Contract. Element Contract.action has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

DSTU2: Contract.actionReason (new:CodeableConcept)

Element Contract.actionReason has a context of Contract based on following the parent source element upwards and mapping to Contract. Element Contract.actionReason has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

DSTU2: Contract.actor.role (new:CodeableConcept)

Element Contract.actor.role has a context of Contract based on following the parent source element upwards and mapping to Contract. Element Contract.actor.role has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

DSTU2: Contract.valuedItem (new:BackboneElement)

Element Contract.valuedItem has a context of Contract based on following the parent source element upwards and mapping to Contract. Element Contract.valuedItem has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

DSTU2: Contract.binding[x] (new:Attachment, Reference(Composition,DocumentReference,QuestionnaireResponse))

Element Contract.binding[x] has a context of Contract based on following the parent source element upwards and mapping to Contract. Element Contract.binding[x] has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

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 managable, 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.

The status of the resource instance.

This element is labeled as a modifier because the status contains codes that mark the contract as not currently valid or active.

A code specifying the state of the resource instance.

This is the Contract Business Workflow Status.

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

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

DSTU2: Contract.text additional types (Narrative) additional types from child elements (div, status)

Element Contract.text is mapped to FHIR R5 element Contract.text as SourceIsBroaderThanTarget. The mappings for Contract.text do not cover the following types: Narrative. The mappings for Contract.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.

DSTU2: Contract.action (new:CodeableConcept)

Element Contract.action has a context of Contract based on following the parent source element upwards and mapping to Contract. Element Contract.action has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

DSTU2: Contract.actionReason (new:CodeableConcept)

Element Contract.actionReason has a context of Contract based on following the parent source element upwards and mapping to Contract. Element Contract.actionReason has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

DSTU2: Contract.actor.role (new:CodeableConcept)

Element Contract.actor.role has a context of Contract based on following the parent source element upwards and mapping to Contract. Element Contract.actor.role has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

DSTU2: Contract.valuedItem (new:BackboneElement)

Element Contract.valuedItem has a context of Contract based on following the parent source element upwards and mapping to Contract. Element Contract.valuedItem has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

DSTU2: Contract.binding[x] (new:Attachment, Reference(Composition,DocumentReference,QuestionnaireResponse))

Element Contract.binding[x] has a context of Contract based on following the parent source element upwards and mapping to Contract. Element Contract.binding[x] has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

DSTU2: Contract.identifier additional types (Identifier) additional types from child elements (assigner, period, system, type, use, value)

Element Contract.identifier is mapped to FHIR R5 element Contract.identifier as RelatedTo. The mappings for Contract.identifier do not cover the following types: Identifier. The mappings for Contract.identifier do not cover the following types based on type expansion: assigner, period, system, type, use, value.

DSTU2: Contract.applies additional types (Period) additional types from child elements (end, start)

Element Contract.applies is mapped to FHIR R5 element Contract.applies as SourceIsBroaderThanTarget. The mappings for Contract.applies do not cover the following types: Period. The mappings for Contract.applies do not cover the following types based on type expansion: end, start.

DSTU2: Contract.subject additional types from child elements (display, reference)

Element Contract.subject is mapped to FHIR R5 element Contract.subject as SourceIsBroaderThanTarget. The mappings for Contract.subject do not cover the following types based on type expansion: display, reference. The standard extension alternate-reference has been mapped as the representation of FHIR DSTU2 element Contract.subject with unmapped reference targets: Resource.

DSTU2: Contract.authority additional types from child elements (display, reference)

Element Contract.authority is mapped to FHIR R5 element Contract.authority as SourceIsBroaderThanTarget. The mappings for Contract.authority do not cover the following types based on type expansion: display, reference. The standard extension alternate-reference has been mapped as the representation of FHIR DSTU2 element Contract.authority with unmapped reference targets: Organization.

DSTU2: Contract.domain additional types from child elements (display, reference)

Element Contract.domain is mapped to FHIR R5 element Contract.domain as SourceIsBroaderThanTarget. The mappings for Contract.domain do not cover the following types based on type expansion: display, reference. The standard extension alternate-reference has been mapped as the representation of FHIR DSTU2 element Contract.domain with unmapped reference targets: Location.

DSTU2: Contract.actor.entity

Element Contract.actor.entity is mapped to FHIR R5 element Contract.author as RelatedTo. The standard extension alternate-reference has been mapped as the representation of FHIR DSTU2 element Contract.actor.entity with unmapped reference targets: Contract, Device, Group, Location, Organization, Patient, Practitioner, RelatedPerson, Substance.

DSTU2: Contract.term.actionReason (new:CodeableConcept)

Element Contract.term.actionReason has a context of Contract.term based on following the parent source element upwards and mapping to Contract. Element Contract.term.actionReason has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

DSTU2: Contract.term.actor (new:BackboneElement)

Element Contract.term.actor has a context of Contract.term based on following the parent source element upwards and mapping to Contract. Element Contract.term.actor has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

DSTU2: Contract.term.valuedItem (new:BackboneElement)

Element Contract.term.valuedItem has a context of Contract.term based on following the parent source element upwards and mapping to Contract. Element Contract.term.valuedItem has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

DSTU2: Contract.term.identifier additional types (Identifier) additional types from child elements (assigner, period, system, type, use, value)

Element Contract.term.identifier is mapped to FHIR R5 element Contract.term.identifier as SourceIsBroaderThanTarget. The mappings for Contract.term.identifier do not cover the following types: Identifier. The mappings for Contract.term.identifier do not cover the following types based on type expansion: assigner, period, system, type, use, value.

DSTU2: Contract.term.applies additional types (Period) additional types from child elements (end, start)

Element Contract.term.applies is mapped to FHIR R5 element Contract.term.applies as SourceIsBroaderThanTarget. The mappings for Contract.term.applies do not cover the following types: Period. The mappings for Contract.term.applies do not cover the following types based on type expansion: end, start.

DSTU2: Contract.term.subject additional types from child elements (display, reference)

Element Contract.term.subject is mapped to FHIR R5 element Contract.term.topic[x] as RelatedTo. The mappings for Contract.term.subject do not cover the following types based on type expansion: display, reference. The standard extension alternate-reference has been mapped as the representation of FHIR DSTU2 element Contract.term.subject with unmapped reference targets: Resource. Source element Contract.term.subject has unmapped reference types. While the target element Contract.term.topic[x] is a choice type and does not allow extensions, the alternate-reference extension can be applied to Reference values within it.

DSTU2: Contract.signer.party

Element Contract.signer.party is mapped to FHIR R5 element Contract.signer.party as RelatedTo. The standard extension alternate-reference has been mapped as the representation of FHIR DSTU2 element Contract.signer.party with unmapped reference targets: Organization, Patient, Practitioner, RelatedPerson.

DSTU2: Contract.signer.signature additional types (string) additional types from child elements (value)

Element Contract.signer.signature is mapped to FHIR R5 element Contract.signer.signature as RelatedTo. The mappings for Contract.signer.signature do not cover the following types: string. The mappings for Contract.signer.signature do not cover the following types based on type expansion: value.

DSTU2: Contract.friendly.content[x] additional types (Attachment)

Element Contract.friendly.content[x] is mapped to FHIR R5 element Contract.friendly.content[x] as RelatedTo. The mappings for Contract.friendly.content[x] do not cover the following types: Attachment. The target context Contract.friendly.content[x] is a choice-type element and cannot directly hold extensions. The context is moved up to parent element Contract.friendly. The standard extension alternate-reference has been mapped as PART of the representation of FHIR DSTU2 element Contract.friendly.content[x] with unmapped reference targets: Composition, DocumentReference, QuestionnaireResponse. Source element Contract.friendly.content[x] has unmapped reference types. While the target element Contract.friendly.content[x] is a choice type and does not allow extensions, the alternate-reference extension can be applied to Reference values within it.

DSTU2: Contract.friendly.content[x] additional types (Attachment)

Element Contract.friendly.content[x] is mapped to FHIR R5 element Contract.friendly.content[x] as RelatedTo. The mappings for Contract.friendly.content[x] do not cover the following types: Attachment. The target context Contract.friendly.content[x] is a choice-type element and cannot directly hold extensions. The context is moved up to parent element Contract.friendly. The standard extension alternate-reference has been mapped as PART of the representation of FHIR DSTU2 element Contract.friendly.content[x] with unmapped reference targets: Composition, DocumentReference, QuestionnaireResponse. Source element Contract.friendly.content[x] has unmapped reference types. While the target element Contract.friendly.content[x] is a choice type and does not allow extensions, the alternate-reference extension can be applied to Reference values within it.

DSTU2: Contract.legal.content[x] additional types (Attachment)

Element Contract.legal.content[x] is mapped to FHIR R5 element Contract.legal.content[x] as RelatedTo. The mappings for Contract.legal.content[x] do not cover the following types: Attachment. The target context Contract.legal.content[x] is a choice-type element and cannot directly hold extensions. The context is moved up to parent element Contract.legal. The standard extension alternate-reference has been mapped as PART of the representation of FHIR DSTU2 element Contract.legal.content[x] with unmapped reference targets: Composition, DocumentReference, QuestionnaireResponse. Source element Contract.legal.content[x] has unmapped reference types. While the target element Contract.legal.content[x] is a choice type and does not allow extensions, the alternate-reference extension can be applied to Reference values within it.

DSTU2: Contract.legal.content[x] additional types (Attachment)

Element Contract.legal.content[x] is mapped to FHIR R5 element Contract.legal.content[x] as RelatedTo. The mappings for Contract.legal.content[x] do not cover the following types: Attachment. The target context Contract.legal.content[x] is a choice-type element and cannot directly hold extensions. The context is moved up to parent element Contract.legal. The standard extension alternate-reference has been mapped as PART of the representation of FHIR DSTU2 element Contract.legal.content[x] with unmapped reference targets: Composition, DocumentReference, QuestionnaireResponse. Source element Contract.legal.content[x] has unmapped reference types. While the target element Contract.legal.content[x] is a choice type and does not allow extensions, the alternate-reference extension can be applied to Reference values within it.

DSTU2: Contract.rule.content[x] additional types (Attachment) additional types from child elements (contentType, creation, data, hash, language, size, title, url, display, reference)

Element Contract.rule.content[x] is mapped to FHIR R5 element Contract.rule.content[x] as RelatedTo. The mappings for Contract.rule.content[x] do not cover the following types: Attachment. The mappings for Contract.rule.content[x] do not cover the following types based on type expansion: contentType, creation, data, display, hash, language, reference, size, title, url. The target context Contract.rule.content[x] is a choice-type element and cannot directly hold extensions. The context is moved up to parent element Contract.rule. The standard extension alternate-reference has been mapped as PART of the representation of FHIR DSTU2 element Contract.rule.content[x] with unmapped reference targets: DocumentReference. Source element Contract.rule.content[x] has unmapped reference types. While the target element Contract.rule.content[x] is a choice type and does not allow extensions, the alternate-reference extension can be applied to Reference values within it.

DSTU2: Contract.rule.content[x] additional types (Attachment) additional types from child elements (contentType, creation, data, hash, language, size, title, url, display, reference)

Element Contract.rule.content[x] is mapped to FHIR R5 element Contract.rule.content[x] as RelatedTo. The mappings for Contract.rule.content[x] do not cover the following types: Attachment. The mappings for Contract.rule.content[x] do not cover the following types based on type expansion: contentType, creation, data, display, hash, language, reference, size, title, url. The target context Contract.rule.content[x] is a choice-type element and cannot directly hold extensions. The context is moved up to parent element Contract.rule. The standard extension alternate-reference has been mapped as PART of the representation of FHIR DSTU2 element Contract.rule.content[x] with unmapped reference targets: DocumentReference. Source element Contract.rule.content[x] has unmapped reference types. While the target element Contract.rule.content[x] is a choice type and does not allow extensions, the alternate-reference extension can be applied to Reference values within it.

Legally enforceable, formally recorded unilateral or bilateral directive i.e., a policy or agreement.

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

Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.

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

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

Element Contract.meta is mapped to FHIR R5 element Contract.meta as SourceIsBroaderThanTarget. The mappings for Contract.meta do not cover the following types: Meta. The mappings for Contract.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 element is generally omitted in instances submitted in a PUT or POST. Instead, it is populated in the response instance and when retrieving information using a GET. 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.

The exact use of the source (and the possible implied Provenance.entity.role and agent.role) is left to implementer discretion. Only one nominated source is allowed; for additional provenance details, a full Provenance resource should be used. The source may correspond to Provenance.entity.what[x] or Provenance.agent.who[x], though it may be a more general or abstract reference.

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.

Unless not suitable, these codes SHALL be taken from AllSecurityLabels
(extensible to http://hl7.org/fhir/ValueSet/security-labels|5.0.0)

Security Labels from the Healthcare Privacy and Security Classification System.

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.

Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".

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 its 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 for a human language

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 a 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

DSTU2: Contract.text additional types (Narrative) additional types from child elements (div, status)

Element Contract.text is mapped to FHIR R5 element Contract.text as SourceIsBroaderThanTarget. The mappings for Contract.text do not cover the following types: Narrative. The mappings for Contract.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.

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 status of a resource narrative.

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, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.

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.

An Extension

DSTU2: Contract.action (new:CodeableConcept)

Element Contract.action has a context of Contract based on following the parent source element upwards and mapping to Contract. Element Contract.action has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

DSTU2: Contract.actionReason (new:CodeableConcept)

Element Contract.actionReason has a context of Contract based on following the parent source element upwards and mapping to Contract. Element Contract.actionReason has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

DSTU2: Contract.actor.role (new:CodeableConcept)

Element Contract.actor.role has a context of Contract based on following the parent source element upwards and mapping to Contract. Element Contract.actor.role has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

DSTU2: Contract.valuedItem (new:BackboneElement)

Element Contract.valuedItem has a context of Contract based on following the parent source element upwards and mapping to Contract. Element Contract.valuedItem has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

DSTU2: Contract.binding[x] (new:Attachment, Reference(Composition,DocumentReference,QuestionnaireResponse))

Element Contract.binding[x] has a context of Contract based on following the parent source element upwards and mapping to Contract. Element Contract.binding[x] has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

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 managable, 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.

Unique identifier for this Contract or a derivative that references a Source Contract.

This is the business identifier of the contract content conveyed. It may be a derivative of the legally binding contract, in which case, the identifier of the basal contract is contained in the Contract.binding referenced Contract.

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

An Extension

DSTU2: Contract.identifier additional types (Identifier) additional types from child elements (assigner, period, system, type, use, value)

Element Contract.identifier is mapped to FHIR R5 element Contract.identifier as RelatedTo. The mappings for Contract.identifier do not cover the following types: Identifier. The mappings for Contract.identifier do not cover the following types based on type expansion: assigner, period, system, type, use, value.

The purpose of this identifier.

Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.

Identifies the purpose for this identifier, if known .

Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.

A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.

This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.

A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.

Allows users to make use of identifiers when the identifier system is not known.

Establishes the namespace for the value - that is, an absolute URL that describes a set values that are unique.

Identifier.system is always case sensitive.

There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.

The portion of the identifier typically relevant to the user and which is unique within the context of the system.

If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the http://hl7.org/fhir/StructureDefinition/rendered-value). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.

Time period during which identifier is/was valid for use.

Organization that issued/manages the identifier.

The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.

Canonical identifier for this contract, represented as a URI (globally unique).

Used in a domain that uses a supplied contract repository.

An absolute URI that is used to identify this contract when it is referenced in a specification, model, design, instance or a contract derivative; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which this plan definition is (or will be) published.

An edition identifier used for business purposes to label business significant variants.

Note - This is a business versionId, not a resource version id (see discussion at Versioning) Comments - There may be different contract 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 plan definition with the format [url]|[version]. The version SHOULD NOT contain a '#' - see Business Version.

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

The status of the resource instance.

This element is labeled as a modifier because the status contains codes that mark the contract as not currently valid or active.

A code specifying the state of the resource instance.

This is the Contract Business Workflow Status.

Legal states of the formation of a legal instrument, which is a formally executed written document that can be formally attributed to its author, records and formally expresses a legally enforceable act, process, or contractual duty, obligation, or right, and therefore evidences that act, process, or agreement.

Detailed codes for the legal state of a contract.

The legal state of a contract follows a prescribed flow as defined by the legal community and these state may be indepenedent of the workflow state.

The URL pointing to a FHIR-defined Contract Definition that is adhered to in whole or part by this Contract.

The URL pointing to an externally maintained definition that is adhered to in whole or in part by this Contract.

The minimal content derived from the basal information source at a specific stage in its lifecycle.

This is an example set of Content Derivative type codes, which represent the minimal content derived from the basal information source.

In the context of a contract, the information source of the content derivative shall be the information referenced by the contract.binding. The Contract Resource may function simply as the computable representation of the executed contract, which may be the attached to the Contract Resource as the “binding” or as the “friendly” electronic form. For example, a Contract Resource may be automatically populated with the values expressed in a related QuestionnaireResponse. However, the Contract Resource may be considered the legally binding contract if it is the only “executed” form of this contract, and includes the signatures as *The Contract Resource may function as the computable representation of an application or offer in a pre-executed Contract if the grantor has not entered any values. In this case, it is populated with values in a “legal” form of the application or offer or by the values in an associated Questionnaire. If the grantor has filled in the legal form or the associated Questionnaire Response, then these values are used to populate a pre-executed Contract Resource. If the Contract.topic is considered an application or offer, then the policy is often required to be attached as the “legal” basis for the application to ensure “informed consent” to the contract, and that any discrepancy between the application and the policy are interpreted against the policy. Implementers should check organizational and jurisdictional policies to determine the relationship among multiple representations of a contract pre- and post-execution.

When this Contract was issued.

The Contract issuance dateTime often precedes the Contract effective dateTime.

Relevant time or time-period when this Contract is applicable.

The dateTime upon which the Contract is binding.

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

An Extension

DSTU2: Contract.applies additional types (Period) additional types from child elements (end, start)

Element Contract.applies is mapped to FHIR R5 element Contract.applies as SourceIsBroaderThanTarget. The mappings for Contract.applies do not cover the following types: Period. The mappings for Contract.applies do not cover the following types based on type expansion: end, start.

The start of the period. The boundary is inclusive.

If the low element is missing, the meaning is that the low boundary is not known.

The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.

The end value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has an end value of 2012-02-03.

Event resulting in discontinuation or termination of this Contract instance by one or more parties to the contract.

Codes for the Cessation of Contracts.

The target entity impacted by or of interest to parties to the agreement.

The Contract.subject is an entity that has some role with respect to the Contract.topic and Contract.topic.term, which is of focal interest to the parties to the contract and likely impacted in a significant way by the Contract.action/Contract.action.reason and the Contract.term.action/Contract.action.reason. In many cases, the Contract.subject is a Contract.signer if the subject is an adult; has a legal interest in the contract; and incompetent to participate in the contract agreement.

The Contract.subject is an entity that has some role with respect to the Contract.topic and Contract.topic.term, which is of focal interest to the parties to the contract and likely impacted in a significant way by the Contract.action/Contract.action.reason and the Contract.term.action/Contract.action.reason. In many cases, the Contract.subject is a Contract.signer if the subject is an adult; has a legal interest in the contract; and incompetent to participate in the contract agreement.

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

An Extension

DSTU2: Contract.subject additional types from child elements (display, reference)

Element Contract.subject is mapped to FHIR R5 element Contract.subject as SourceIsBroaderThanTarget. The mappings for Contract.subject do not cover the following types based on type expansion: display, reference. The standard extension alternate-reference has been mapped as the representation of FHIR DSTU2 element Contract.subject with unmapped reference targets: Resource.

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 known RESTful URL) or by resolving the target of the reference.

Unless not suitable, these codes SHALL be taken from ResourceType
(extensible to http://hl7.org/fhir/ValueSet/resource-types|5.0.0)

Aa resource (or, for logical models, the URI of the logical model).

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).

This element only allows for a single identifier. In the case where additional identifers are required, use the http://hl7.org/fhir/StructureDefinition/additionalIdentifier extension.

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.

A formally or informally recognized grouping of people, principals, organizations, or jurisdictions formed for the purpose of achieving some form of collective action such as the promulgation, administration and enforcement of contracts and policies.

The governance framework responsible for ensuring compliance with or enforcement of the contract or policy.

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

An Extension

DSTU2: Contract.authority additional types from child elements (display, reference)

Element Contract.authority is mapped to FHIR R5 element Contract.authority as SourceIsBroaderThanTarget. The mappings for Contract.authority do not cover the following types based on type expansion: display, reference. The standard extension alternate-reference has been mapped as the representation of FHIR DSTU2 element Contract.authority with unmapped reference targets: Organization.

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 known RESTful URL) or by resolving the target of the reference.

Unless not suitable, these codes SHALL be taken from ResourceType
(extensible to http://hl7.org/fhir/ValueSet/resource-types|5.0.0)

Aa resource (or, for logical models, the URI of the logical model).

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).

This element only allows for a single identifier. In the case where additional identifers are required, use the http://hl7.org/fhir/StructureDefinition/additionalIdentifier extension.

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.

Recognized governance framework or system operating with a circumscribed scope in accordance with specified principles, policies, processes or procedures for managing rights, actions, or behaviors of parties or principals relative to resources.

The entities bound by governance to comply with the enforcement of contracts or policies by a recognized authority.

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

An Extension

DSTU2: Contract.domain additional types from child elements (display, reference)

Element Contract.domain is mapped to FHIR R5 element Contract.domain as SourceIsBroaderThanTarget. The mappings for Contract.domain do not cover the following types based on type expansion: display, reference. The standard extension alternate-reference has been mapped as the representation of FHIR DSTU2 element Contract.domain with unmapped reference targets: Location.

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 known RESTful URL) or by resolving the target of the reference.

Unless not suitable, these codes SHALL be taken from ResourceType
(extensible to http://hl7.org/fhir/ValueSet/resource-types|5.0.0)

Aa resource (or, for logical models, the URI of the logical model).

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).

This element only allows for a single identifier. In the case where additional identifers are required, use the http://hl7.org/fhir/StructureDefinition/additionalIdentifier extension.

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.

Sites in which the contract is complied with, exercised, or in force.

A natural language name identifying this Contract definition, derivative, or instance in any legal state. Provides additional information about its content. 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 this Contract definition, derivative, or instance in any legal state.

A more detailed or qualifying explanatory or alternate user-friendly title for this Contract definition, derivative, or instance in any legal state.

Alternative representation of the title for this Contract definition, derivative, or instance in any legal state., e.g., a domain specific contract number related to legislation.

The individual or organization that authored the Contract definition, derivative, or instance in any legal state.

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

An Extension

DSTU2: Contract.actor.entity

Element Contract.actor.entity is mapped to FHIR R5 element Contract.author as RelatedTo. The standard extension alternate-reference has been mapped as the representation of FHIR DSTU2 element Contract.actor.entity with unmapped reference targets: Contract, Device, Group, Location, Organization, Patient, Practitioner, RelatedPerson, Substance.

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 known RESTful URL) or by resolving the target of the reference.

Unless not suitable, these codes SHALL be taken from ResourceType
(extensible to http://hl7.org/fhir/ValueSet/resource-types|5.0.0)

Aa resource (or, for logical models, the URI of the logical model).

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).

This element only allows for a single identifier. In the case where additional identifers are required, use the http://hl7.org/fhir/StructureDefinition/additionalIdentifier extension.

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.

A selector of legal concerns for this Contract definition, derivative, or instance in any legal state.

Codes for the range of legal concerns.

Narrows the range of legal concerns to focus on the achievement of specific contractual objectives.

Contractual areas of concern are very broad. This element supports narrowing the area of concern to more specific term topics within this Contract. Given the wide range of contract topics, implementers need to be cognizant of the business use case for which they are designing a FHIR Contract, and narrowly specify the topic being represented with respect to the Contract.type and any specializing Contract.subtype. The same topic, e.g., an asset such as a good or service, such as a real property, medical supply, insurance, information, a procedure or employment, or a manner of conduct, such adherence to a privacy, trust, or security policy, may be the topic of multiple types of contracts. One way to determine the Contract.topic is to answer the question: "What is the overall objective of this legal instrument?". The Contract.topic is described with more detail by the terms of the Contract.

May be used to focus the topic of a Contract definition, derivative, or instance in any legal state.

A high-level category for the legal instrument, whether constructed as a Contract definition, derivative, or instance in any legal state. Provides additional information about its content within the context of the Contract's scope to distinguish the kinds of systems that would be interested in the contract.

List of overall contract codes.

Sub-category for the Contract that distinguishes the kinds of systems that would be interested in the Contract within the context of the Contract's scope.

Detailed codes within the above.

Precusory content developed with a focus and intent of supporting the formation a Contract instance, which may be associated with and transformable into a Contract.

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 managable, 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 managable, 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.

Precusory content structure and use, i.e., a boilerplate, template, application for a contract such as an insurance policy or benefits under a program, e.g., workers compensation.

Detailed codes for the definition of contracts.

Detailed Precusory content type.

Detailed codes for the additional definition of contracts.

The individual or organization that published the Contract precursor content.

The date (and optionally time) when the contract was last significantly changed. 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 contract changes.

amended | appended | cancelled | disputed | entered-in-error | executable +.

Status of the publication of contract content.

A copyright statement relating to Contract precursor content. Copyright statements are generally legal restrictions on the use and publishing of the Contract precursor content.

One or more Contract Provisions, which may be related and conveyed as a group, and may contain nested groups.

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

An Extension

DSTU2: Contract.term.actionReason (new:CodeableConcept)

Element Contract.term.actionReason has a context of Contract.term based on following the parent source element upwards and mapping to Contract. Element Contract.term.actionReason has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

DSTU2: Contract.term.actor (new:BackboneElement)