A formal agreement between parties regarding the conduct of business, exchange of information or other matters.

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.

Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element.

This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.

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

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

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.

R4: Contract.topic[x] additional types (CodeableConcept) additional types from child elements (coding, text)

Element Contract.topic[x] is mapped to FHIR STU3 element Contract.topic as RelatedTo. The mappings for Contract.topic[x] do not cover the following types: CodeableConcept. The mappings for Contract.topic[x] do not cover the following types based on type expansion: coding, text.

R4: Contract.url (new:uri)

Element Contract.url has a context of Contract.agent based on following the parent source element upwards and mapping to Contract. Element Contract.url has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Used in a domain that uses a supplied contract repository.

R4: Contract.version (new:string)

Element Contract.version has a context of Contract.agent based on following the parent source element upwards and mapping to Contract. Element Contract.version has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Note - This is a business versionId, not a resource version id (see discussion http://build.fhir.org/resource.html#versions) 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].

R4: Contract.legalState (new:CodeableConcept)

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

R4: Contract.instantiatesCanonical (new:Reference(Contract))

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

R4: Contract.instantiatesUri (new:uri)

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

R4: Contract.expirationType (new:CodeableConcept)

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

R4: Contract.site (new:Reference(Location))

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

R4: Contract.name (new:string)

Element Contract.name has a context of Contract.agent based on following the parent source element upwards and mapping to Contract. Element Contract.name has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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.

R4: Contract.title (new:string)

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

R4: Contract.subtitle (new:string)

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

R4: Contract.alias (new:string)

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

R4: Contract.scope (new:CodeableConcept)

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

R4: Contract.contentDefinition (new:BackboneElement)

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

R4: Contract.supportingInfo (new:Reference(Resource))

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

R4: Contract.relevantHistory (new:Reference(Provenance))

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

R4: Contract.legallyBinding[x] (new:Attachment, Reference(Composition,DocumentReference,QuestionnaireResponse,Contract))

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

R4: Contract.author

Element Contract.author is mapped to FHIR STU3 element Contract.agent.actor as RelatedTo. The standard extension alternate-reference has been mapped as the representation of FHIR R4 element Contract.author with unmapped reference targets: PractitionerRole.

R4: Contract.signer.party

Element Contract.signer.party is mapped to FHIR STU3 element Contract.signer.party as SourceIsBroaderThanTarget. The standard extension alternate-reference has been mapped as the representation of FHIR R4 element Contract.signer.party with unmapped reference targets: PractitionerRole.

R4: Contract.term.offer (new:BackboneElement)

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

R4: Contract.term.offer.answer (new:BackboneElement)

Element Contract.term.offer.answer is part of an existing definition because parent element Contract.term.offer requires a cross-version extension. Element Contract.term.offer.answer has a context of Contract.term based on following the parent source element upwards and mapping to Contract. Element Contract.term.offer.answer has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R4: Contract.term.asset (new:BackboneElement)

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

R4: Contract.term.asset.answer (new:Contract.term.offer.answer)

Element Contract.term.asset.answer is part of an existing definition because parent element Contract.term.asset requires a cross-version extension. Element Contract.term.asset.answer has a context of Contract.term based on following the parent source element upwards and mapping to Contract. Element Contract.term.asset.answer has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R4: Contract.term.topic[x] additional types (CodeableConcept) additional types from child elements (coding, text)

Element Contract.term.topic[x] is mapped to FHIR STU3 element Contract.term.topic as RelatedTo. The mappings for Contract.term.topic[x] do not cover the following types: CodeableConcept. The mappings for Contract.term.topic[x] do not cover the following types based on type expansion: coding, text.

R4: Contract.term.action.doNotPerform (new:boolean)

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

R4: Contract.term.action.type (new:CodeableConcept)

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

R4: Contract.term.action.subject (new:BackboneElement)

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

R4: Contract.term.action.intent (new:CodeableConcept)

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

R4: Contract.term.action.linkId (new:string)

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

R4: Contract.term.action.status (new:CodeableConcept)

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

R4: Contract.term.action.context (new:Reference(Encounter,EpisodeOfCare))

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

R4: Contract.term.action.contextLinkId (new:string)

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

R4: Contract.term.action.occurrence[x] (new:dateTime, Period, Timing)

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

R4: Contract.term.action.requester (new:Reference(Patient,RelatedPerson,Practitioner,PractitionerRole,Device,Group,Organization))

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

R4: Contract.term.action.requesterLinkId (new:string)

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

R4: Contract.term.action.performerType (new:CodeableConcept)

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

R4: Contract.term.action.performerRole (new:CodeableConcept)

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

R4: Contract.term.action.performer (new:Reference(RelatedPerson,Patient,Practitioner,PractitionerRole,CareTeam,Device,Substance,Organization,Location))

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

R4: Contract.term.action.performerLinkId (new:string)

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

R4: Contract.term.action.reasonCode (new:CodeableConcept)

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

R4: Contract.term.action.reasonReference (new:Reference(Condition,Observation,DiagnosticReport,DocumentReference,Questionnaire,QuestionnaireResponse))

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

R4: Contract.term.action.reason (new:string)

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

R4: Contract.term.action.reasonLinkId (new:string)

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

R4: Contract.term.action.note (new:Annotation)

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

R4: Contract.term.action.securityLabelNumber (new:unsignedInt)

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

R4: Contract.term.securityLabel.number (new:unsignedInt)

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

R4: Contract.term.securityLabel.classification (new:Coding)

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

R4: Contract.term.securityLabel.category (new:Coding)

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

R4: Contract.term.securityLabel.control (new:Coding)

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

A formal agreement between parties regarding the conduct of business, exchange of information or other matters.

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 may not always be associated with version changes to the resource.

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.

Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element.

This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.

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

A human language.

A human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "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 in formation is added later.

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

This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again.

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

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

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

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

Unique identifier for this Contract.

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.

When this Contract was issued.

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

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.

The matter of concern in the context of this agreement.

The Contract.topic may be an application for or offer of a policy or service (e.g., uri to a consent directive form or a health insurance policy), which becomes the Contract once accepted by both the grantor and grantee. 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.

In the context of a contract, the topic is the matter under consideration in regards to which specific rights, privileges, obligations, restrictions, and prohibitions are binding on any grantor and grantee parties upon the execution of the 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 object of negotiation?” Answer: The Contract.topic, which may be described with more detail in the [0..*]Contract.valuedItem @ [0..1] Contract.valuedItem.entity[x] Definition: Specific type of Contract Valued Item that may be priced. CodeableConcept|Reference(Any) Contract.topic is “the what” that a grantor is exchanging with a grantee in return for some benefit. Contract.topic is “the what” to which any Contract.action is being applied for any stipulated Contract.action.reason. AContract.topic is “the what” governed by the execution of the contract to which any party’s rights, privileges, obligations, restrictions, and prohibitions apply.

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

An Extension

R4: Contract.topic[x] additional types (CodeableConcept) additional types from child elements (coding, text)

Element Contract.topic[x] is mapped to FHIR STU3 element Contract.topic as RelatedTo. The mappings for Contract.topic[x] do not cover the following types: CodeableConcept. The mappings for Contract.topic[x] do not cover the following types based on type expansion: coding, text.

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.

An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity 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.

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.

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.

Type of Contract such as an insurance policy, real estate contract, a will, power of attorny, Privacy or Security policy , trust framework agreement, etc.

List of overall contract codes.

More specific type or specialization of an overarching or more general contract such as auto insurance, home owner insurance, prenupial agreement, Advanced-Directive, or privacy consent.

Detailed codes within the above.

Action stipulated by this Contract.

Detailed codes for the contract action.

Reason for action stipulated by this Contract.

Detailed codes for the contract action reason.

The type of decision made by a grantor with respect to an offer made by a grantee.

The type of decision made by a grantor with respect to an offer made by a grantee.

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.

A set of security labels that define which resources are controlled by this consent. If more than one label is specified, all resources must have all the specified labels.

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

Security Labels from the Healthcare Privacy and Security Classification System.

An actor taking a role in an activity for which it can be assigned some degree of responsibility for the activity taking place.

Several agents may be associated (i.e. has some responsibility for an activity) with an activity and vice-versa. For example, in cases of actions initiated by one user for other users, or in events that involve more than one user, hardware device, software, or system process. However, only one user may be the initiator/requestor for the event.

An agent can be a person, an organization, software, device, or other entities that may be ascribed responsibility.

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

An Extension

R4: Contract.url (new:uri)

Element Contract.url has a context of Contract.agent based on following the parent source element upwards and mapping to Contract. Element Contract.url has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Used in a domain that uses a supplied contract repository.

R4: Contract.version (new:string)

Element Contract.version has a context of Contract.agent based on following the parent source element upwards and mapping to Contract. Element Contract.version has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Note - This is a business versionId, not a resource version id (see discussion http://build.fhir.org/resource.html#versions) 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].

R4: Contract.legalState (new:CodeableConcept)

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

R4: Contract.instantiatesCanonical (new:Reference(Contract))

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

R4: Contract.instantiatesUri (new:uri)

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

R4: Contract.expirationType (new:CodeableConcept)

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

R4: Contract.site (new:Reference(Location))

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

R4: Contract.name (new:string)

Element Contract.name has a context of Contract.agent based on following the parent source element upwards and mapping to Contract. Element Contract.name has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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.

R4: Contract.title (new:string)

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

R4: Contract.subtitle (new:string)

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

R4: Contract.alias (new:string)

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

R4: Contract.scope (new:CodeableConcept)

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

R4: Contract.contentDefinition (new:BackboneElement)

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

R4: Contract.supportingInfo (new:Reference(Resource))

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

R4: Contract.relevantHistory (new:Reference(Provenance))

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

R4: Contract.legallyBinding[x] (new:Attachment, Reference(Composition,DocumentReference,QuestionnaireResponse,Contract))

Element Contract.legallyBinding[x] has a context of Contract.agent based on following the parent source element upwards and mapping to Contract. Element Contract.legallyBinding[x] has no mapping targets in FHIR STU3. 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 element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

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

Who or what parties are assigned roles in this 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

R4: Contract.author

Element Contract.author is mapped to FHIR STU3 element Contract.agent.actor as RelatedTo. The standard extension alternate-reference has been mapped as the representation of FHIR R4 element Contract.author with unmapped reference targets: PractitionerRole.

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.

An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity 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.

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.

Role type of agent assigned roles in this Contract.

Detailed codes for the contract actor role.

Parties with legal standing in the Contract, including the principal parties, the grantor(s) and grantee(s), which are any person or organization bound by the contract, and any ancillary parties, which facilitate the execution of the contract such as a notary or witness.

Signers who are principal parties to the contract are bound by the Contract.activity related to the Contract.topic, and the Contract.term(s), which either extend or restrict the overall action on the topic by, for example, stipulating specific policies or obligations constraining actions, action reason, or agents with respect to some or all of the topic. For example, specifying how policies or obligations shall constrain actions and action reasons permitted or denied on all or a subset of the Contract.topic (e.g., all or a portion of property being transferred by the contract), agents (e.g., who can resell, assign interests, or alter the property being transferred by the contract), actions, and action reasons; or with respect to Contract.terms, stipulating, extending, or limiting the Contract.period of applicability or valuation of items under consideration.

The Contract.signer applies a signature to the Contract.binding referenced resource, which is the documentation that is the legal "source of truth". The Contract.signer may delegate, such as a legally recognized personal representative, or have a delegate assigned e.g., by a court of law, to actually sign the Contract, such as a trustee in the case of incompetence.

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. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

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

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

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

Role of this Contract signer, e.g. notary, grantee.

List of parties who may be signing.

Party which is a signator to this 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

R4: Contract.signer.party

Element Contract.signer.party is mapped to FHIR STU3 element Contract.signer.party as SourceIsBroaderThanTarget. The standard extension alternate-reference has been mapped as the representation of FHIR R4 element Contract.signer.party with unmapped reference targets: PractitionerRole.

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.

An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity 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.

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.

Legally binding Contract DSIG signature contents in Base64.

Contract Valued Item List.

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. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

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

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

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

Specific type of Contract Valued Item that may be priced.

Identifies a Contract Valued Item instance.

Indicates the time during which this Contract ValuedItem information is effective.

Specifies the units by which the Contract Valued Item is measured or counted, and quantifies the countable or measurable Contract Valued Item instances.

A Contract Valued Item unit valuation measure.

A real number that represents a multiplier used in determining the overall value of the Contract Valued Item delivered. The concept of a Factor allows for a discount or surcharge multiplier to be applied to a monetary amount.

An amount that expresses the weighting (based on difficulty, cost and/or resource intensiveness) associated with the Contract Valued Item delivered. The concept of Points allows for assignment of point values for a Contract Valued Item, such that a monetary amount can be assigned to each point.

Expresses the product of the Contract Valued Item unitQuantity and the unitPriceAmt. For example, the formula: unit Quantity * unit Price (Cost per Point) * factor Number * points = net Amount. Quantity, factor and points are assumed to be 1 if not supplied.

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

R4: Contract.term.offer (new:BackboneElement)

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

R4: Contract.term.offer.answer (new:BackboneElement)

Element Contract.term.offer.answer is part of an existing definition because parent element Contract.term.offer requires a cross-version extension. Element Contract.term.offer.answer has a context of Contract.term based on following the parent source element upwards and mapping to Contract. Element Contract.term.offer.answer has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R4: Contract.term.asset (new:BackboneElement)

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

R4: Contract.term.asset.answer (new:Contract.term.offer.answer)

Element Contract.term.asset.answer is part of an existing definition because parent element Contract.term.asset requires a cross-version extension. Element Contract.term.asset.answer has a context of Contract.term based on following the parent source element upwards and mapping to Contract. Element Contract.term.asset.answer has no mapping targets in FHIR STU3. 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 element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

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

Unique identifier for this particular Contract Provision.

When this Contract Provision was issued.

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

Type of Contract Provision such as specific requirements, purposes for actions, obligations, prohibitions, e.g. life time maximum benefit.

Detailed codes for the types of contract provisions.

Subtype of this Contract Provision, e.g. life time maximum payment for a contract term for specific valued item, e.g. disability payment.

Detailed codes for the subtypes of contract provisions.

The matter of concern in the context of this provision of the agrement.

The Contract.term.topic, as a Contract Resource subpart, is handled in the same manner as the Contract Resource as discussed above.

A contract term topic is typically about a portion of the contract topic which has additional or specialized rights, privileges, obligations, restrictions, and prohibitions that are binding on any grantor and grantee parties upon the execution of the contract. Contract.term.topic may be described in more detail in the [0..*] Contract.term.valuedItem @[0..1] Contract.term.valuedItem [x] Definition: Specific type of Contract Provision Valued Item that may be priced. CodeableConcept|Reference(Any) [See Contract.topic Requirements for further elaboration on this requirement.].

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

An Extension

R4: Contract.term.topic[x] additional types (CodeableConcept) additional types from child elements (coding, text)

Element Contract.term.topic[x] is mapped to FHIR STU3 element Contract.term.topic as RelatedTo. The mappings for Contract.term.topic[x] do not cover the following types: CodeableConcept. The mappings for Contract.term.topic[x] do not cover the following types based on type expansion: coding, text.

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.

An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity 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.

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.

Action stipulated by this Contract Provision.

Detailed codes for the contract action.

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

An Extension

R4: Contract.term.action.type (new:CodeableConcept)

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

R4: Contract.term.action.subject (new:BackboneElement)

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

R4: Contract.term.action.intent (new:CodeableConcept)

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

R4: Contract.term.action.linkId (new:string)

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

R4: Contract.term.action.status (new:CodeableConcept)

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

R4: Contract.term.action.context (new:Reference(Encounter,EpisodeOfCare))

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

R4: Contract.term.action.contextLinkId (new:string)

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

R4: Contract.term.action.occurrence[x] (new:dateTime, Period, Timing)

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

R4: Contract.term.action.requester (new:Reference(Patient,RelatedPerson,Practitioner,PractitionerRole,Device,Group,Organization))

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

R4: Contract.term.action.requesterLinkId (new:string)

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

R4: Contract.term.action.performerType (new:CodeableConcept)

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

R4: Contract.term.action.performerRole (new:CodeableConcept)

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

R4: Contract.term.action.performer (new:Reference(RelatedPerson,Patient,Practitioner,PractitionerRole,CareTeam,Device,Substance,Organization,Location))

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

R4: Contract.term.action.performerLinkId (new:string)

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

R4: Contract.term.action.reasonCode (new:CodeableConcept)

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

R4: Contract.term.action.reasonReference (new:Reference(Condition,Observation,DiagnosticReport,DocumentReference,Questionnaire,QuestionnaireResponse))

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

R4: Contract.term.action.reason (new:string)

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

R4: Contract.term.action.reasonLinkId (new:string)

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

R4: Contract.term.action.note (new:Annotation)

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

R4: Contract.term.action.securityLabelNumber (new:unsignedInt)

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

A reference to a code defined by a terminology system.

Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.

Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings.

A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.

Very often the text is the same as a displayName of one of the codings.

The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.

Reason or purpose for the action stipulated by this Contract Provision.

Detailed codes for the contract action reason.

A set of security labels that define which terms are controlled by this condition.

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

Security Labels from the Healthcare Privacy and Security Classification System.

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

An Extension

R4: Contract.term.securityLabel.number (new:unsignedInt)

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

R4: Contract.term.securityLabel.classification (new:Coding)

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

R4: Contract.term.securityLabel.category (new:Coding)

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

R4: Contract.term.securityLabel.control (new:Coding)

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

The identification of the code system that defines the meaning of the symbol in the code.

The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should de-reference to some definition that establish the system clearly and unambiguously.

Need to be unambiguous about the source of the definition of the symbol.

The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.

Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.

A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

Need to refer to a particular code in the system.

A representation of the meaning of the code in the system, following the rules of the system.

Need to be able to carry a human-readable meaning of the code for readers that do not know the system.