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

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.

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

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.

Used in a domain that uses a supplied contract repository.

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

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.

Note - This is a business versionId, not a resource version id (see discussion http://hl7.org/fhir/2022Sep/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]. The version SHOULD NOT contain a '#' - see Business Version.

The status of the resource instance.

This is the Contract Business Workflow Status.

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

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.

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.

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.

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

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.

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.

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.

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.

Support human navigation and 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.

A short, descriptive, user-friendly title for this Contract definition, derivative, or instance in any legal state.t giving additional information about its content.

An explanatory or alternate user-friendly title for this Contract definition, derivative, or instance in any legal state.t giving additional information about its content.

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.

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

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

Requirement: May be used to focus the topic of a Contract definition, derivative, or instance in any legal state. Comment: 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.

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.

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.

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.

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 Precusory content type.

The individual or organization that published the Contract precursor content.

The date (and optionally time) when the contract was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the contract changes.

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

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 identifier for this particular Contract Provision.

When this Contract Provision was issued.

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

The entity that the term applies to.

A legal clause or condition contained within a contract that requires one or both parties to perform a particular requirement by some specified time or prevents one or both parties from performing a particular requirement by some specified time.

A specialized legal clause or condition based on overarching contract type.

Statement of a provision in a policy or a contract.

Security labels that protect the handling of information about the term and its elements, which may be specifically identified..

Requirement - Within a Contract, a security label may apply to the one to many nested group of terms or to a term, whether inside a group or a singleton. This security label protects the term and its contained provision elements. The security label on the entire set of term provision elements may be different from the security labels on a contained offer, asset, valuedItem, or data such as sensitive information, and must be the high water mark of all security labels within the term. Rationale is that a labelled term, which may be disaggregated from the Contract, and must persist the label on the term and on contained elements within other contexts. Requirement - If more than one policy dictates a level of confidentiality of the term, then each applicable policy may be represented by a security label specific to its requirements. Comment - A Security Label is comprised of 1..1 confidentiality code and 0..* other security label codes (aka "privacy tags". A Security Label is metadata assigned (aka "tagged") to Resources and Resource elements, which specify the confidentiality and sensitivity of the Resource or element and their related attributes, the purposes for which tagged items may be collected, access, used or disclosed, any limitation on the type of entities authorized to engage in permitted purposes, and handling instructions that obligate or prohibit certain actions on the tagged items.

Number used to link this term or term element to the applicable Security Label.

Security label privacy tag that species the level of confidentiality protection required for this term and/or term elements.

Security label privacy tag that species the applicable privacy and security policies governing this term and/or term elements.

Security label privacy tag that species the manner in which term and/or term elements are to be protected.

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

Unique identifier for this particular Contract Provision.

Offer Recipient.

Participant in the offer.

How the party participates in the offer.

The owner of an asset has the residual control rights over the asset: the right to decide all usages of the asset in any way not inconsistent with a prior contract, custom, or law (Hart, 1995, p. 30).

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.

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.

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

Type of choice made by accepting party with respect to an offer made by an offeror/ grantee.

In some policy or contract contexts, the "offer" is made by an offeror wishing to be the "grantee" of the offer topic by the grantor. From this perspective, the grantor is the "offeree".

How the decision about a Contract was conveyed.

Response to offer text.

Response to an offer clause or question text, which enables selection of values to be agreed to, e.g., the period of participation, the date of occupancy of a rental, warrently duration, or whether biospecimen may be used for further research.

Human readable form of this Contract Offer.

The id of the clause or question text of the offer in the referenced questionnaire/response.

Security labels that protects the offer.

Contract Term Asset List.

Differentiates the kind of the asset .

Target entity type about which the term may be concerned.

Associated entities.

May be a subtype or part of an offered asset.

Specifies the applicability of the term to an asset resource instance, and instances it refers to orinstances that refer to it, and/or are owned by the offeree.

Circumstance of the asset.

Asset context reference may include the creator, custodian, or owning Person or Organization (e.g., bank, repository), location held, e.g., building, jurisdiction.

Coded representation of the context generally or of the Referenced entity, such as the asset holder type or location.

Context description.

Description of the quality and completeness of the asset that imay be a factor in its valuation.

Type of Asset availability for use or ownership.

Asset relevant contractual time period.

Time period of asset use.

Clause or question text (Prose Object) concerning the asset in a linked form, such as a QuestionnaireResponse used in the formation of the contract.

Id [identifier??] of the clause or question text about the asset in the referenced form or QuestionnaireResponse.

Response to assets.

Security labels that protects the asset.

Contract Valued Item List.

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.

Terms of valuation.

When payment is due.

Who will make payment.

Who will receive payment.

Id of the clause or question text related to the context of this valuedItem in the referenced form or QuestionnaireResponse.

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

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

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

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.

True if the term prohibits the action.

Activity or service obligation to be done or not done, performed or not performed, effectuated or not by this Contract term.

Entity of the action.

The entity the action is performed or not performed on or for.

Role type of agent assigned roles in this Contract.

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

Id [identifier??] of the clause or question text related to this action in the referenced form or QuestionnaireResponse.

Current state of the term action.

Encounter or Episode with primary association to specified term activity.

Id [identifier??] of the clause or question text related to the requester of this action in the referenced form or QuestionnaireResponse.

When action happens.

Who or what initiated the action and has responsibility for its activation.

Id [identifier??] of the clause or question text related to the requester of this action in the referenced form or QuestionnaireResponse.

The type of individual that is desired or required to perform or not perform the action.

The type of role or competency of an individual desired or required to perform or not perform the action.

Indicates who or what is being asked to perform (or not perform) the ction.

Id [identifier??] of the clause or question text related to the reason type or reference of this action in the referenced form or QuestionnaireResponse.

Rationale for the action to be performed or not performed. Describes why the action is permitted or prohibited. Either a coded concept, or another resource whose existence justifies permitting or not permitting this action.

Id [identifier??] of the clause or question text related to the reason type or reference of this action in the referenced form or QuestionnaireResponse.

Comments made about the term action made by the requester, performer, subject or other participants.

Security labels that protects the action.

Nested group of Contract Provisions.

Information that may be needed by/relevant to the performer in their execution of this term action.

Links to Provenance records for past versions of this Contract definition, derivative, or instance, which identify key state transitions or updates that are likely to be relevant to a user looking at the current version of the Contract. The Provence.entity indicates the target that was changed in the update. http://hl7.org/fhir/2022Sep/provenance-definitions.html#Provenance.entity.

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.

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.

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.

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

Party which is a signator to this Contract.

Legally binding Contract DSIG signature contents in Base64.

The "patient friendly language" versionof the Contract in whole or in parts. "Patient friendly language" means the representation of the Contract and Contract Provisions in a manner that is readily accessible and understandable by a layperson in accordance with best practices for communication styles that ensure that those agreeing to or signing the Contract understand the roles, actions, obligations, responsibilities, and implication of the agreement.

Human readable rendering of this Contract in a format and representation intended to enhance comprehension and ensure understandability.

List of Legal expressions or representations of this Contract.

Contract legal text in human renderable form.

List of Computable Policy Rule Language Representations of this Contract.

Computable Contract conveyed using a policy rule language (e.g. XACML, DKAL, SecPal).

Legally binding Contract: This is the signed and legally recognized representation of the Contract, which is considered the "source of truth" and which would be the basis for legal action related to enforcement of this Contract.