This page is part of the FHIR Specification (v3.2.0: R4 Ballot 1). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2
Financial Management Work Group | Maturity Level: 1 | Trial Use | Compartments: Not linked to any defined compartments |
Detailed Descriptions for the elements in the Contract resource.
Contract | |
Definition | A formal agreement between parties regarding the conduct of business, exchange of information or other matters. |
Control | 1..1 |
Contract.identifier | |
Definition | Unique identifier for this Contract or a derivative that references a Source Contract. |
Note | This is a business identifer, not a resource identifier (see discussion) |
Control | 0..1 |
Type | Identifier |
Requirements | 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. |
Summary | true |
Contract.status | |
Definition | The status of the resource instance. |
Control | 0..1 |
Terminology Binding | Contract Resource Status Codes (Required) |
Type | code |
Is Modifier | true |
Requirements | This is the Contract Business Workflow Status. |
Summary | true |
Comments | This element is labeled as a modifier because the status contains codes that mark the contract as not currently valid or active. |
Contract.contentDerivative | |
Definition | The minimal content derived from the basal information source at a specific stage in its lifecycle. |
Control | 0..1 |
Terminology Binding | Contract Content Derivation Codes (Example) |
Type | CodeableConcept |
Requirements | 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. |
Contract.issued | |
Definition | When this Contract was issued. |
Control | 0..1 |
Type | dateTime |
Requirements | The Contract issuance dateTime often precedes the Contract effective dateTime. |
Summary | true |
Contract.applies | |
Definition | Relevant time or time-period when this Contract is applicable. |
Control | 0..1 |
Type | Period |
Requirements | The dateTime upon which the Contract is binding. |
Summary | true |
Contract.subject | |
Definition | The target entity impacted by or of interest to parties to the agreement. |
Control | 0..* |
Type | Reference(Any) |
Requirements | 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. |
Alternate Names | Patient |
Summary | true |
Comments | 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. |
Contract.authority | |
Definition | 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. |
Control | 0..* |
Type | Reference(Organization) |
Requirements | The governance framework responsible for ensuring compliance with or enforcement of the contract or policy. |
Contract.domain | |
Definition | 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. |
Control | 0..* |
Type | Reference(Location) |
Requirements | The entities bound by governance to comply with the enforcement of contracts or policies by a recognized authority. |
Alternate Names | scope of governance jurisdiction |
Contract.type | |
Definition | Type of Contract such as an insurance policy, real estate contract, a will, power of attorny, Privacy or Security policy , trust framework agreement, etc. |
Control | 0..1 |
Terminology Binding | Contract Type Codes (Example) |
Type | CodeableConcept |
Summary | true |
Contract.subType | |
Definition | 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. |
Control | 0..* |
Terminology Binding | Contract Subtype Codes (Example) |
Type | CodeableConcept |
Summary | true |
Contract.term | |
Definition | One or more Contract Provisions, which may be related and conveyed as a group, and may contain nested groups. |
Control | 0..* |
Contract.term.identifier | |
Definition | Unique identifier for this particular Contract Provision. |
Note | This is a business identifer, not a resource identifier (see discussion) |
Control | 0..1 |
Type | Identifier |
Summary | true |
Contract.term.issued | |
Definition | When this Contract Provision was issued. |
Control | 0..1 |
Type | dateTime |
Summary | true |
Contract.term.applies | |
Definition | Relevant time or time-period when this Contract Provision is applicable. |
Control | 0..1 |
Type | Period |
Summary | true |
Contract.term.type | |
Definition | Type of Contract Provision such as specific requirements, purposes for actions, obligations, prohibitions, e.g. life time maximum benefit. |
Control | 0..1 |
Terminology Binding | Contract Term Type Codes (Example) |
Type | CodeableConcept |
Contract.term.subType | |
Definition | Subtype of this Contract Provision, e.g. life time maximum payment for a contract term for specific valued item, e.g. disability payment. |
Control | 0..1 |
Terminology Binding | Contract Term Subtype Codes (Example) |
Type | CodeableConcept |
Contract.term.offer | |
Definition | The matter of concern in the context of this provision of the agrement. |
Control | 1..1 |
Contract.term.offer.topic | |
Definition | 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). |
Control | 0..1 |
Type | Reference(Any) |
Requirements | 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. |
Summary | true |
Comments | 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. |
Contract.term.offer.type | |
Definition | Type of Contract Provision such as specific requirements, purposes for actions, obligations, prohibitions, e.g. life time maximum benefit. |
Control | 0..1 |
Terminology Binding | Contract Term Type Codes (Example) |
Type | CodeableConcept |
Contract.term.offer.decision | |
Definition | The type of decision made by a grantor with respect to an offer made by a grantee. |
Control | 0..1 |
Terminology Binding | ActConsentDirective (Extensible) |
Type | CodeableConcept |
Requirements | 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". |
Contract.term.offer.text | |
Definition | Human readable form of this Contract Offer. |
Control | 0..1 |
Type | string |
Contract.term.offer.linkId | |
Definition | The id of the clause or question text of the offer in the referenced questionnaire/response. |
Control | 0..1 |
Type | string |
Contract.term.asset | |
Definition | Contract Term Asset List. |
Control | 0..* |
Contract.term.asset.class | |
Definition | Resource Type, Profile, or CDA etc. |
Control | 0..1 |
Terminology Binding | Consent Content Class (Extensible) |
Type | Coding |
Contract.term.asset.code | |
Definition | Code in the content. |
Control | 0..1 |
Terminology Binding | Consent Content Codes (Example) |
Type | Coding |
Contract.term.asset.period | |
Definition | Time period of the asset. |
Control | 0..1 |
Type | Period |
Contract.term.asset.dataPeriod | |
Definition | Time period of the data for the asset. |
Control | 0..1 |
Type | Period |
Contract.term.asset.data | |
Definition | Data defined by this Asset. |
Control | 0..* |
Contract.term.asset.data.meaning | |
Definition | instance | related | dependents | authoredby. |
Control | 0..1 |
Terminology Binding | ContractDataMeaning (Required) |
Type | code |
Contract.term.asset.data.reference | |
Definition | The actual data reference. |
Control | 0..1 |
Type | Reference(Any) |
Contract.term.asset.valuedItem | |
Definition | Contract Valued Item List. |
Control | 0..* |
Contract.term.asset.valuedItem.entity[x] | |
Definition | Specific type of Contract Valued Item that may be priced. |
Control | 0..1 |
Type | CodeableConcept|Reference(Any) |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Contract.term.asset.valuedItem.identifier | |
Definition | Identifies a Contract Valued Item instance. |
Note | This is a business identifer, not a resource identifier (see discussion) |
Control | 0..1 |
Type | Identifier |
Contract.term.asset.valuedItem.effectiveTime | |
Definition | Indicates the time during which this Contract ValuedItem information is effective. |
Control | 0..1 |
Type | dateTime |
Contract.term.asset.valuedItem.quantity | |
Definition | Specifies the units by which the Contract Valued Item is measured or counted, and quantifies the countable or measurable Contract Valued Item instances. |
Control | 0..1 |
Type | SimpleQuantity |
Contract.term.asset.valuedItem.unitPrice | |
Definition | A Contract Valued Item unit valuation measure. |
Control | 0..1 |
Type | Money |
Contract.term.asset.valuedItem.factor | |
Definition | 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. |
Control | 0..1 |
Type | decimal |
Contract.term.asset.valuedItem.points | |
Definition | 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. |
Control | 0..1 |
Type | decimal |
Contract.term.asset.valuedItem.net | |
Definition | 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. |
Control | 0..1 |
Type | Money |
Contract.term.asset.securityLabel | |
Definition | A set of security labels that define which terms are controlled by this condition. |
Control | 0..* |
Terminology Binding | All Security Labels (Extensible) |
Type | Coding |
Summary | true |
Contract.term.agent | |
Definition | An actor taking a role in an activity for which it can be assigned some degree of responsibility for the activity taking place. |
Control | 0..* |
Requirements | An agent can be a person, an organization, software, device, or other entities that may be ascribed responsibility. |
Comments | 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. |
Contract.term.agent.actor | |
Definition | Who or what parties are assigned roles in this Contract. |
Control | 1..1 |
Type | Reference(Contract | Device | Group | Location | Organization | Patient | Practitioner | RelatedPerson | Substance) |
Contract.term.agent.role | |
Definition | Role type of agent assigned roles in this Contract. |
Control | 0..* |
Terminology Binding | Contract Actor Role Codes (Example) |
Type | CodeableConcept |
Contract.term.action | |
Definition | Action stipulated by this Contract Provision. |
Control | 0..* |
Terminology Binding | Contract Action Codes (Example) |
Type | CodeableConcept |
Requirements | If the Contract.topic references a Resource, which contains actions or activities, such as a Procedure to which a grantor is agreeing to receive from the grantee, then this element would likely not be populated. If the Resource referenced in the Contract.topic does not include an action such as a Device, then the Contract.action would likely be populated, for example with the actions "purchase and sale" the Device. |
Contract.term.actionReason | |
Definition | Reason or purpose for the action stipulated by this Contract Provision. |
Control | 0..* |
Terminology Binding | PurposeOfUse (Example) |
Type | CodeableConcept |
Contract.term.group | |
Definition | Nested group of Contract Provisions. |
Control | 0..* |
Type | See Contract.term |
Contract.signer | |
Definition | 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. |
Control | 0..* |
Requirements | 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. |
Comments | 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. |
Contract.signer.type | |
Definition | Role of this Contract signer, e.g. notary, grantee. |
Control | 1..1 |
Terminology Binding | Contract Signer Type Codes (Preferred) |
Type | Coding |
Contract.signer.party | |
Definition | Party which is a signator to this Contract. |
Control | 1..1 |
Type | Reference(Organization | Patient | Practitioner | RelatedPerson) |
Contract.signer.signature | |
Definition | Legally binding Contract DSIG signature contents in Base64. |
Control | 1..* |
Type | Signature |
Contract.friendly | |
Definition | 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. |
Control | 0..* |
Contract.friendly.content[x] | |
Definition | Human readable rendering of this Contract in a format and representation intended to enhance comprehension and ensure understandability. |
Control | 1..1 |
Type | Attachment|Reference(Composition | DocumentReference | QuestionnaireResponse) |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Contract.legal | |
Definition | List of Legal expressions or representations of this Contract. |
Control | 0..* |
Contract.legal.content[x] | |
Definition | Contract legal text in human renderable form. |
Control | 1..1 |
Type | Attachment|Reference(Composition | DocumentReference | QuestionnaireResponse) |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Contract.rule | |
Definition | List of Computable Policy Rule Language Representations of this Contract. |
Control | 0..1 |
Contract.rule.content[x] | |
Definition | Computable Contract conveyed using a policy rule language (e.g. XACML, DKAL, SecPal). |
Control | 1..1 |
Type | Attachment|Reference(DocumentReference) |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Contract.legallyBinding[x] | |
Definition | 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. |
Control | 0..1 |
Type | Attachment|Reference(Composition | DocumentReference | QuestionnaireResponse | Contract) |
[x] Note | See Choice of Data Types for further information about how to use [x] |