type: resource-definitionsresource: Contract

Contract Definitions

Contract

Legal Agreement

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

Cardinality: 0..*

Mappings: workflow=Event; rim=FinancialContract; w5=financial.other

Contract.identifier

Contract number

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

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.

Cardinality: 0..*

Type: Identifier

Summary: true

Mappings: workflow=Event.identifier; rim=FinancialContract id

Contract.url

Basal definition

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

Comments: Used in a domain that uses a supplied contract repository.

Requirements: 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.

Cardinality: 0..1

Type: uri

Contract.version

Business edition

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

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.

Requirements: 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.

Cardinality: 0..1

Type: string

Summary: true

Contract.status

Definition: The status of the resource instance.

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

Requirements: This is the Contract Business Workflow Status.

Cardinality: 0..1

Type: code

Binding: required:contract-status

Summary: true

Is Modifier: true (Reason: This element is labeled as a modifier because it is a status element that contains status entered-in-error which means that the resource should not be treated as valid)

Mappings: workflow=Event.status; w5=FiveWs.status; rim=Act.status

Contract.legalState

Negotiation status

Definition: 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.

Requirements: 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.

Cardinality: 0..1

Type: CodeableConcept

Binding: extensible:contract-legalstate

Contract.instantiatesCanonical

Source Contract Definition

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

Cardinality: 0..1

Type: Reference(Contract)

Contract.instantiatesUri

External Contract Definition

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

Cardinality: 0..1

Type: uri

Contract.contentDerivative

Content derived from the basal information

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

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.

Cardinality: 0..1

Type: CodeableConcept

Binding: example:contract-content-derivative

Mappings: w5=FiveWs.what[x]; rim=Maps partially to several v3 codes: ActClass: REG (registration) Description: Represents the act of maintaining information about the registration of its associated registered subject. The subject can be either an Act or a Role, and includes subjects such as lab exam definitions, drug protocol definitions, prescriptions, persons, patients, practitioners, and equipment. The registration may have a unique identifier - separate from the unique identification of the subject - as well as a core set of related participations and act relationships that characterize the registration event and aid in the disposition of the subject information by a receiving system. Observation: VERIF (Verification) Description: An act which describes the process whereby a 'verifying party' validates either the existence of the Role attested to by some Credential or the actual Vetting act and its details. TRFR (transfer) Description: The act of transferring information without the intent of imparting understanding about a topic to the subject that is the recipient or holder of the transferred information where the participation association must be RCV or HLD. _ActDetectedIssueManagementCode [abstract term] Description: Codes dealing with the management of Detected Issue observations. _ActInformationAccessContextCode [abstract term] Description: Concepts conveying the context in which authorization given under jurisdictional law, by organizational policy, or by a patient consent directive permits the collection, access, use or disclosure of specified patient health information. _ActListCode [abstract term]vDescription: Provides codes associated with ActClass value of LIST (working list). RefusalReasonCode [abstract term] Description: Description: Identifies why a request to add (or activate) a record is being refused. Examples include the receiving system not able to match the identifier and find that record in the receiving system, having no permission, or a detected issue exists which precludes the requested action.

Contract.issued

When this Contract was issued

Definition: When this Contract was issued.

Requirements: The Contract issuance dateTime often precedes the Contract effective dateTime.

Cardinality: 0..1

Type: dateTime

Summary: true

Mappings: workflow=Event.recorded; rim=Act.availabilityTime. Definition: A time expression specifying when an Observation, Procedure, or other Act occurs, or, depending on the mood, is supposed to occur, scheduled to occur, etc. The activityTime includes the times of component actions (such as preparation and clean-up). For Procedures and SubstanceAdministrations, the activityTime can provide a needed administrative function by providing a more inclusive time to be anticipated in scheduling. UsageNotes:The activityTime is primarily of administrative rather than clinical use. The clinically relevant time is the effectiveTime. When an observation of a prior symptom is made, the activityTime describes the time the observation is made, as opposed to effectiveTime which is the time the symptom is reported to have occurred. Thus the activityTime may be entirely different from the effectiveTime of the same Act. However, even apart from clinical use cases, designers should first consider effectiveTime as the primary relevant time for an Act. ActivityTime indicates when an Act occurs, not when it is recorded.

Contract.applies

Effective time

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

Requirements: The dateTime upon which the Contract is binding.

Cardinality: 0..1

Type: Period

Summary: true

Mappings: workflow=Event.occurrence[x]; rim=Act.effectiveTime Definition: The clinically or operationally relevant time of an act, exclusive of administrative activity.

Contract.expirationType

Contract cessation cause

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

Cardinality: 0..1

Type: CodeableConcept

Binding: example:contract-expiration-type

Contract.subject

Contract Target Entity

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

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.

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.

Aliases: Patient

Cardinality: 0..*

Type: Reference(Resource)

Summary: true

Mappings: workflow=Event.subject; rim=RoleClass, RoleCode

Contract.authority

Authority under which this Contract has standing

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.

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

Cardinality: 0..*

Type: Reference(Organization)

Mappings: rim=Organization Role. CONCEPT DOMAIN: OrganizationEntityType Description: Further classifies entities of EntityClass ORG.

Contract.domain

A sphere of control governed by an authoritative jurisdiction, organization, or person

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.

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

Aliases: scope of governance jurisdiction

Cardinality: 0..*

Type: Reference(Location)

Mappings: rim=TERR (territory of authority) Description: Relates a place entity (player) as the region over which the scoper (typically an Organization) has certain authority (jurisdiction). For example, the Calgary Regional Health Authority (scoper) has authority over the territory "Region 4 of Alberta" (player) in matters of health. Entity Class = Place? A physical place or site with its containing structure. May be natural or man-made. The geographic position of a place might or might not be constant. CONCEPT DOMAIN: TerritoryEntityType Description: A territorial entity that may be cited as the body over which an agency exercises jurisdiction, or which defines a sphere in which a party has a particular responsibility. CONCEPT DOMAIN: OrganizationEntityType Description: Further classifies entities of EntityClass ORG.

Contract.site

Specific Location

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

Cardinality: 0..*

Type: Reference(Location)

Contract.name

Computer friendly designation

Definition: 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.

Comments: 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.

Requirements: Support human navigation and code generation.

Cardinality: 0..1

Type: string

Summary: true

Contract.title

Human Friendly name

Definition: A short, descriptive, user-friendly title for this Contract definition, derivative, or instance in any legal state.

Cardinality: 0..1

Type: string

Summary: true

Contract.subtitle

Subordinate Friendly name

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

Cardinality: 0..1

Type: string

Contract.alias

Acronym or short name

Definition: 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.

Cardinality: 0..*

Type: string

Contract.author

Source of Contract

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

Cardinality: 0..1

Type: Reference(Patient, Practitioner, PractitionerRole, Organization, RelatedPerson)

Contract.scope

Range of Legal Concerns

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

Cardinality: 0..1

Type: CodeableConcept

Binding: example:contract-scope

Contract.topic[x]

Focus of contract interest

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

Comments: 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.

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

Cardinality: 0..1

Type: CodeableConcept, Reference(Resource)

Contract.type

Legal instrument category

Definition: 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.

Cardinality: 0..1

Type: CodeableConcept

Binding: example:contract-type

Summary: true

Mappings: workflow=Event.code; w5=FiveWs.what[x]; rim=Maps to multiple ActClass and ActCode Concept Domains and Code Systems such as the following: In the ActClass Concept Domain: ActClassPolicy. In the ActCode Concept Domain: ActContractType, which generalizes ActFinancialContractType, ActCoverageType, ActBillingArrangementType. ActConsentType, which generalizes ActDataConsentType; ActFinancialParticipationConsentType; ActInformationAccessCode; AdvanceBeneficiaryNoticeType. ActPolicyType, which generalizes: ActPrivacyPolicyType, ActSensitivityPrivacyPolicyType, ActSecurityPolicyType. In the ActClass Code System: CNTRCT (contract) Description: An agreement of obligation between two or more parties that is subject to contractual law and enforcement, lwhich generalizes FCNTRCT (financial contract) and COV (coverage). POLICY (policy) - Description: A mandate, regulation, obligation, requirement, rule, or expectation unilaterally imposed by one party on: The activity of another party; the behavior of another party; or the manner in which an act is executed. LEAF CONCEPTS: JURISPOL (jurisdictional policy) Description:A mandate, regulation, obligation, requirement, rule, or expectation unilaterally imposed by a jurisdiction on: The activity of another party; the behavior of another party; or the manner in which an act is executed.Examples:A jurisdictional mandate regarding the prescribing and dispensing of a particular medication. A jurisdictional privacy or security regulation dictating the manner in which personal health information is disclosed. A jurisdictional requirement that certain services or health conditions are reported to a monitoring program, e.g., immunizations, methadone treatment, or cancer registries.ORGPOL (organizational policy)Examples:A clinical or research protocols imposed by a payer, a malpractice insurer, or an institution to which a provider must adhere. A mandate imposed by a denominational institution for a provider to provide or withhold certain information from the patient about treatment options.SCOPOL (scope of practice policy)Description:An ethical or clinical obligation, requirement, rule, or expectation imposed or strongly encouraged by organizations that oversee particular clinical domains or provider certification which define the boundaries within which a provider may practice and which may have legal basis or ramifications.Examples:An ethical obligation for a provider to fully inform a patient about all treatment options. An ethical obligation for a provider not to disclose personal health information that meets certain criteria, e.g., where disclosure might result in harm to the patient or another person. The set of health care services which a provider is credentialed or privileged to provide. STDPOL (standard of practice policy) Examples:A payer may require a prescribing provider to adhere to formulary guidelines. An institution may adopt clinical guidelines and protocols and implement these within its electronic health record and decision support systems. CONS (consent)Description: The Consent class represents informed consents and all similar medico-legal transactions between the patient (or his legal guardian) and the provider. Examples are informed consent for surgical procedures, informed consent for clinical trials, advanced beneficiary notice, against medical advice decline from service, release of information agreement, etc. The details of consents vary. Often an institution has a number of different consent forms for various purposes, including reminding the physician about the topics to mention. Such forms also include patient education material. In electronic medical record communication, consents thus are information-generating acts on their own and need to be managed similar to medical activities. Thus, Consent is modeled as a special class of Act. The "signatures" to the consent document are represented electronically through Participation instances to the consent object. Typically an informed consent has Participation.typeCode of "performer", the healthcare provider informing the patient, and "consenter", the patient or legal guardian. Some consent may associate a witness or a notary public (e.g., living wills, advanced directives). In consents where a healthcare provider is not required (e.g. living will), the performer may be the patient himself or a notary public.

Contract.subType

Subtype within the context of type

Definition: 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.

Cardinality: 0..*

Type: CodeableConcept

Binding: example:contract-subtype

Summary: true

Mappings: w5=FiveWs.what[x]; rim=Examples of Contract or Policy subtypes in ActCodes:_ActCoverageTypeCode Definition: Set of codes indicating the type of insurance policy or program that pays for the cost of benefits provided to covered parties. Generalizes: _ActInsurancePolicyCode; _ActInsuranceTypeCode; ActProgramTypeCode. _ActPolicyType Description:Types of policies that further specify the ActClassPolicy value set. Generalizes: _ActPrivacyPolicy; _ActPrivacyLaw; _InformationSensitivityPolicy; ActTrustPolicyType; SecurityPolicy. _ActInvoiceAdjudicationPaymentGroupCode Description: Codes representing adjustments to a Payment Advice such as retroactive, clawback, garnishee, etc., e.g. RECOV (recovery) Description: Retroactive adjustment such as fee rate adjustment due to contract negotiations.

Contract.contentDefinition

Contract precursor content

Definition: 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.

Cardinality: 0..1

Type: BackboneElement

Contract.contentDefinition.type

Content structure and use

Definition: 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.

Cardinality: 1..1

Type: CodeableConcept

Binding: example:contract-definition-type

Contract.contentDefinition.subType

Detailed Content Type Definition

Definition: Detailed Precusory content type.

Cardinality: 0..1

Type: CodeableConcept

Binding: example:contract-definition-subtype

Contract.contentDefinition.publisher

Publisher Entity

Definition: The individual or organization that published the Contract precursor content.

Cardinality: 0..1

Type: Reference(Practitioner, PractitionerRole, Organization)

Contract.contentDefinition.publicationDate

When published

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

Cardinality: 0..1

Type: dateTime

Contract.contentDefinition.publicationStatus

Cardinality: 1..1

Type: code

Binding: required:contract-publicationstatus

Contract.contentDefinition.copyright

Publication Ownership

Definition: A copyright statement relating to Contract precursor content. Copyright statements are notices of intellectual property ownership and can include restrictions on the use and publishing of the Contract precursor content.

Cardinality: 0..1

Type: markdown

Contract.term

Contract Term List

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

Cardinality: 0..*

Type: BackboneElement

Mappings: w5=FiveWs.what[x]; rim=RIM mechanism for grouping or nesting rules, which are likely Acts and Observations.

Contract.term.identifier

Contract Term Number

Definition: Unique identifier for this particular Contract Provision.

Cardinality: 0..1

Type: Identifier

Summary: true

Mappings: workflow=Event.identifier; rim=Act or Observation identifier.

Contract.term.issued

Contract Term Issue Date Time

Definition: When this Contract Provision was issued.

Cardinality: 0..1

Type: dateTime

Summary: true

Mappings: workflow=Event.recorded; w5=FiveWs.recorded; rim=Act availabilityTime

Contract.term.applies

Contract Term Effective Time

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

Cardinality: 0..1

Type: Period

Summary: true

Mappings: workflow=Event.occurrence[x]; w5=FiveWs.done[x]; rim=Act effectiveTime

Contract.term.topic[x]

Term Concern

Definition: The entity that the term applies to.

Cardinality: 0..1

Type: CodeableConcept, Reference(Resource)

Contract.term.type

Contract Term Type or Form

Definition: 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.

Cardinality: 0..1

Type: CodeableConcept

Binding: example:contract-term-type

Mappings: workflow=Event.code; w5=FiveWs.what[x]; rim=See Contract.term mapping.

Contract.term.subType

Contract Term Type specific classification

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

Cardinality: 0..1

Type: CodeableConcept

Binding: example:contract-term-subtype

Mappings: w5=FiveWs.what[x]; rim=See Contract.topic mapping.

Contract.term.text

Term Statement

Definition: Statement of a provision in a policy or a contract.

Cardinality: 0..1

Type: markdown

Summary: true

Contract.term.securityLabel

Protection for the Term

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

Comments: 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. 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. 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.

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.

Requirements: This security label protects the term and its contained provision elements.

Cardinality: 0..*

Type: BackboneElement

Contract.term.securityLabel.number

Link to Security Labels

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

Cardinality: 0..*

Type: unsignedInt

Contract.term.securityLabel.classification

Confidentiality Protection

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

Cardinality: 1..1

Type: Coding

Binding: example:contract-security-classification

Contract.term.securityLabel.category

Applicable Policy

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

Cardinality: 0..*

Type: Coding

Binding: example:contract-security-category

Contract.term.securityLabel.control

Handling Instructions

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

Cardinality: 0..*

Type: Coding

Binding: example:contract-security-control

Contract.term.offer

Context of the Contract term

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

Cardinality: 1..1

Type: BackboneElement

Mappings: rim=Document

Contract.term.offer.identifier

Offer business ID

Definition: Unique identifier for this particular Contract Provision.

Cardinality: 0..*

Type: Identifier

Contract.term.offer.party

Offer Recipient

Definition: Offer Recipient.

Cardinality: 0..*

Type: BackboneElement

Contract.term.offer.party.reference

Referenced entity

Definition: Participant in the offer.

Cardinality: 1..*

Type: Reference(Patient, RelatedPerson, Practitioner, PractitionerRole, Device, Group, Organization)

Contract.term.offer.party.role

Participant engagement type

Definition: How the party participates in the offer.

Cardinality: 1..1

Type: CodeableConcept

Binding: example:contract-party-role

Contract.term.offer.topic

Negotiable offer asset

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

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.

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.

Cardinality: 0..1

Type: Reference(Resource)

Summary: true

Mappings: rim=Includes many ActClass, ActCode, RoleClass, RoleCode, EntityClass, EntityCode, ParticipationType codes from HL7 concept domains and code systems. For example, RoleCode: HLD (held entity) Description: Entity that is currently in the possession of a holder (scoper), who holds, or uses it, usually based on some agreement with the owner. MANU (manufactured product) Description: Scoped by the manufacturer. OWN (owned entity) Description: An Entity (player) for which someone (scoper) is granted by law the right to call the material (player) his own. This entitles the scoper to make decisions about the disposition of that material. WRTE (warranteed product) Description: A role a product plays when a guarantee is given to the purchaser by the seller (scoping entity) stating that the product is reliable and free from known defects and that the seller will repair or replace defective parts within a given time limit and under certain conditions.

Contract.term.offer.type

Contract Offer Type or Form

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

Cardinality: 0..1

Type: CodeableConcept

Binding: example:contract-term-type

Mappings: w5=FiveWs.what[x]; rim=See Contract.term mapping.

Contract.term.offer.decision

Accepting party choice

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

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

Cardinality: 0..1

Type: CodeableConcept

Binding: extensible:v3-ActConsentDirective

Mappings: w5=FiveWs.what[x]; rim=ActCode: _ActConsentDirective [abstract term] Description: Specifies the type of agreement between one or more grantor and grantee in which rights and obligations related to one or more shared items of interest are allocated. Usage Note: Such agreements may be considered "consent directives" or "contracts" depending on the context, and are considered closely related or synonymous from a legal perspective.

Contract.term.offer.decisionMode

How decision is conveyed

Definition: How the decision about a Contract was conveyed.

Cardinality: 0..*

Type: CodeableConcept

Binding: example:contract-decision-mode

Contract.term.offer.answer

Response to offer text

Definition: Response to offer text.

Cardinality: 0..*

Type: BackboneElement

Contract.term.offer.answer.value[x]

The actual answer response

Definition: 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, warranty duration, or whether biospecimen may be used for further research.

Cardinality: 1..1

Type: boolean, decimal, integer, date, dateTime, time, string, uri, Attachment, Coding, Quantity, Reference(Resource)

Contract.term.offer.text

Human readable offer text

Definition: Human readable form of this Contract Offer.

Cardinality: 0..1

Type: string

Mappings: rim=Document.text

Contract.term.offer.linkId

Pointer to text

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

Cardinality: 0..*

Type: string

Mappings: rim=.outboundRelationship[typeCode=DEFN].target[classCode=OBS, moodCode=DEFN].id

Contract.term.offer.securityLabelNumber

Offer restriction numbers

Definition: Security labels that protects the offer.

Cardinality: 0..*

Type: unsignedInt

Contract.term.asset

Contract Term Asset List

Definition: Contract Term Asset List.

Cardinality: 0..*

Type: BackboneElement

Mappings: rim=FinancialContract.paymentTermsCode

Contract.term.asset.scope

Range of asset

Definition: Differentiates the kind of the asset .

Cardinality: 0..1

Type: CodeableConcept

Binding: example:contract-assetscope

Contract.term.asset.type

Asset category

Definition: Target entity type about which the term may be concerned.

Cardinality: 0..*

Type: CodeableConcept

Binding: example:contract-assettype

Contract.term.asset.typeReference

Associated entities

Definition: Associated entities.

Cardinality: 0..*

Type: Reference(Resource)

Contract.term.asset.subtype

Asset sub-category

Definition: May be a subtype or part of an offered asset.

Cardinality: 0..*

Type: CodeableConcept

Binding: example:contract-assetsubtype

Contract.term.asset.relationship

Kinship of the asset

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

Cardinality: 0..1

Type: Coding

Binding: extensible:consent-content-class

Mappings: rim=FinancialContract.code

Contract.term.asset.context

Circumstance of the asset

Definition: Circumstance of the asset.

Cardinality: 0..*

Type: BackboneElement

Contract.term.asset.context.reference

Creator,custodian or owner

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

Cardinality: 0..1

Type: Reference(Resource)

Contract.term.asset.context.code

Codeable asset context

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

Cardinality: 0..*

Type: CodeableConcept

Binding: example:contract-assetcontext

Contract.term.asset.context.text

Context description

Definition: Context description.

Cardinality: 0..1

Type: string

Contract.term.asset.condition

Quality desctiption of asset

Definition: Description of the quality and completeness of the asset that may be a factor in its valuation.

Cardinality: 0..1

Type: string

Contract.term.asset.periodType

Asset availability types

Definition: Type of Asset availability for use or ownership.

Cardinality: 0..*

Type: CodeableConcept

Binding: example:asset-availability

Mappings: rim=FinancialContract.code

Contract.term.asset.period

Time period of the asset

Definition: Asset relevant contractual time period.

Cardinality: 0..*

Type: Period

Mappings: rim=FinancialContract.activityTime

Contract.term.asset.usePeriod

Time period

Definition: Time period of asset use.

Cardinality: 0..*

Type: Period

Mappings: rim=FinancialContract.effectiveTime

Contract.term.asset.text

Asset clause or question text

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

Cardinality: 0..1

Type: string

Contract.term.asset.linkId

Pointer to asset text

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

Cardinality: 0..*

Type: string

Contract.term.asset.answer

Response to assets

Definition: Response to assets.

Cardinality: 0..*

Contract.term.asset.securityLabelNumber

Asset restriction numbers

Definition: Security labels that protects the asset.

Cardinality: 0..*

Type: unsignedInt

Contract.term.asset.valuedItem

Contract Valued Item List

Definition: Contract Valued Item List.

Cardinality: 0..*

Type: BackboneElement

Mappings: rim=COCT_RM440000UV09 ValuedItem classCode INVE

Contract.term.asset.valuedItem.entity[x]

Contract Valued Item Type

Definition: Specific type of Contract Valued Item that may be priced.

Cardinality: 0..1

Type: CodeableConcept, Reference(Resource)

Mappings: w5=FiveWs.what[x]; rim=COCT_RM440000UV09 ValuedItem code

Contract.term.asset.valuedItem.identifier

Contract Valued Item Number

Definition: Identifies a Contract Valued Item instance.

Cardinality: 0..1

Type: Identifier

Mappings: rim=COCT_RM440000UV09 ValuedItem id

Contract.term.asset.valuedItem.effectiveTime

Contract Valued Item Effective Tiem

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

Cardinality: 0..1

Type: dateTime

Mappings: w5=FiveWs.done[x]; rim=COCT_RM440000UV09 ValuedItem effectiveTime

Contract.term.asset.valuedItem.quantity

Count of Contract Valued Items

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

Cardinality: 0..1

Type: Quantity(SimpleQuantity)

Mappings: w5=FiveWs.what[x]; rim=COCT_RM440000UV09 ValuedItem unitQuantity

Contract.term.asset.valuedItem.unitPrice

Contract Valued Item fee, charge, or cost

Definition: A Contract Valued Item unit valuation measure.

Cardinality: 0..1

Type: Money

Mappings: w5=FiveWs.what[x]; rim=COCT_RM440000UV09 ValuedItem unitPriceAmt

Contract.term.asset.valuedItem.factor

Contract Valued Item Price Scaling 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.

Cardinality: 0..1

Type: decimal

Mappings: w5=FiveWs.what[x]; rim=COCT_RM440000UV09 ValuedItem factorNumber

Contract.term.asset.valuedItem.points

Contract Valued Item Difficulty Scaling Factor

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.

Cardinality: 0..1

Type: decimal

Mappings: w5=FiveWs.what[x]; rim=COCT_RM440000UV09 ValuedItem pointNumber

Contract.term.asset.valuedItem.net

Total Contract Valued Item Value

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.

Cardinality: 0..1

Type: Money

Mappings: w5=FiveWs.what[x]; rim=COCT_RM440000UV09 ValuedItem netAmt

Contract.term.asset.valuedItem.payment

Terms of valuation

Definition: Terms of valuation.

Cardinality: 0..1

Type: string

Contract.term.asset.valuedItem.paymentDate

When payment is due

Definition: When payment is due.

Cardinality: 0..1

Type: dateTime

Contract.term.asset.valuedItem.responsible

Who will make payment

Definition: Who will make payment.

Cardinality: 0..1

Type: Reference(Organization, Patient, Practitioner, PractitionerRole, RelatedPerson)

Contract.term.asset.valuedItem.recipient

Who will receive payment

Definition: Who will receive payment.

Cardinality: 0..1

Type: Reference(Organization, Patient, Practitioner, PractitionerRole, RelatedPerson)

Contract.term.asset.valuedItem.linkId

Pointer to specific item

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

Cardinality: 0..*

Type: string

Contract.term.asset.valuedItem.securityLabelNumber

Security Labels that define affected terms

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

Cardinality: 0..*

Type: unsignedInt

Contract.term.action

Entity being ascribed responsibility

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

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.

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

Cardinality: 0..*

Type: BackboneElement

Mappings: rim=Participation

Contract.term.action.doNotPerform

True if the term prohibits the action

Definition: True if the term prohibits the action.

Cardinality: 0..1

Type: boolean

Is Modifier: true (Reason: If true this element negates the specified action. For Example, instead of a dictate to perform an action, it is a dictate not to perform the action.)

Contract.term.action.type

Type or form of the action

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

Cardinality: 1..1

Type: CodeableConcept

Binding: example:contract-action

Mappings: workflow=Event.performer; rim=RIM Role, Participation Type classes

Contract.term.action.subject

Entity of the action

Definition: Entity of the action.

Cardinality: 0..*

Type: BackboneElement

Contract.term.action.subject.reference

Entity of the action

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

Cardinality: 1..*

Type: Reference(Patient, RelatedPerson, Practitioner, PractitionerRole, Device, Group, Organization)

Contract.term.action.subject.role

Role type of the agent

Definition: Role type of agent assigned roles in this Contract.

Cardinality: 0..1

Type: CodeableConcept

Binding: example:contract-actorrole

Mappings: rim=RoleClass, RoleCode, ParticipationType, ParticipationFunction codes

Contract.term.action.intent

Purpose for the Contract Term Action

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

Cardinality: 1..1

Type: CodeableConcept

Binding: example:v3-PurposeOfUse

Mappings: workflow=Event.reason; w5=FiveWs.why[x]; rim=Examples from ActReason Concept Domains: ActCoverageReason Description:Codes used to specify reasons or criteria relating to coverage provided under a policy or program. May be used to convey reasons pertaining to coverage contractual provisions, including criteria for eligibility, coverage limitations, coverage maximums, or financial participation required of covered parties. ActInformationPrivacyReason Description: The rationale or purpose for an act relating to the management of personal information, such as disclosing personal tax information for the purpose of complying with a court order. ClinicalResearchObservationReason Definition: Specifies the reason that a test was performed or observation collected in a clinical research study. SafetyInvestigationReportReasonType Description: Possible reasons generating a report providing information developed during the investigation of an adverse event or a product problem. ControlActReason Description: Indicates the motivation, cause or rationale of an Act which results in a trigger event. NonPerformanceReasonCode Description: The reason the action was not performed, e.g. why the medication was not taken. If an action was not performed, it is often clinically important to know why the action was not taken. RefusalReasonCode Description: Identifies why a request to add (or activate) a record is being refused. Examples include the receiving system not able to match the identifier and find that record in the receiving system, having no permission, or a detected issue exists which precludes the requested action.

Examples from HL7 ActReason Code System: QUALIMP (quality improvement) Description:Operational activities conducted for the purposes of improving the quality of an activity, product, or service. _PatientProfileQueryReasonCode Description: A collection of concepts identifying why the patient's profile is being queried. _ActInformationManagementReason Description:The rationale or purpose for an act relating to information management, such as archiving information for the purpose of complying with an enterprise data retention policy. _ActInvalidReason (ActInvalidReason) Description: Types of reasons why a substance is invalid for use. _NonPerformanceReasonCode Description: The reason the action wasn't performed, e.g. why the medication was not taken. If an action wasn"t performed, it is often clinically important to know why the action wasn"t taken.

Contract.term.action.linkId

Pointer to specific item

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

Cardinality: 0..*

Type: string

Contract.term.action.status

State of the action

Definition: Current state of the term action.

Cardinality: 1..1

Type: CodeableConcept

Binding: example:contract-actionstatus

Contract.term.action.context

Episode associated with action

Definition: Encounter or Episode with primary association to the specified term activity.

Cardinality: 0..1

Type: Reference(Encounter, EpisodeOfCare)

Contract.term.action.contextLinkId

Pointer to specific item

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

Cardinality: 0..*

Type: string

Contract.term.action.occurrence[x]

When action happens

Definition: When action happens.

Cardinality: 0..1

Type: dateTime, Period, Timing

Contract.term.action.requester

Who asked for action

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

Cardinality: 0..*

Type: Reference(Patient, RelatedPerson, Practitioner, PractitionerRole, Device, Group, Organization)

Contract.term.action.requesterLinkId

Pointer to specific item

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

Cardinality: 0..*

Type: string

Contract.term.action.performerType

Kind of service performer

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

Cardinality: 0..*

Type: CodeableConcept

Binding: example:participation-role-type

Contract.term.action.performerRole

Competency of the performer

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

Cardinality: 0..1

Type: CodeableConcept

Binding: example:security-role-type-example

Contract.term.action.performer

Actor that wil execute (or not) the action

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

Cardinality: 0..1

Type: Reference(RelatedPerson, Patient, Practitioner, PractitionerRole, CareTeam, Device, Substance, Organization, Location)

Contract.term.action.performerLinkId

Pointer to specific item

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

Cardinality: 0..*

Type: string

Contract.term.action.reason

Why is action (not) needed?

Definition: 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.

Cardinality: 0..*

Type: CodeableReference

Binding: example:v3-PurposeOfUse

Contract.term.action.reasonLinkId

Pointer to specific item

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

Cardinality: 0..*

Type: string

Contract.term.action.note

Comments about the action

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

Cardinality: 0..*

Type: Annotation

Contract.term.action.securityLabelNumber

Action restriction numbers

Definition: Security labels that protects the action.

Cardinality: 0..*

Type: unsignedInt

Contract.term.group

Nested Contract Term Group

Definition: Nested group of Contract Provisions.

Cardinality: 0..*

Mappings: w5=FiveWs.what[x]; rim=RIM Grouping or Nesting mechanisms

Contract.supportingInfo

Extra Information

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

Cardinality: 0..*

Type: Reference(Resource)

Contract.relevantHistory

Key event in Contract History

Definition: 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 Provenance.entity indicates the target that was changed in the update (see Provenance.entity).

Cardinality: 0..*

Type: Reference(Provenance)

Contract.signer

Contract Signatory

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.

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.

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.

Cardinality: 0..*

Type: BackboneElement

Mappings: rim=Participation

Contract.signer.type

Contract Signatory Role

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

Cardinality: 1..1

Type: Coding

Binding: preferred:contract-signer-type

Mappings: w5=FiveWs.actor; rim=RoleClass, RoleCode, ParticipationType, ParticipationFunction class codes.

Contract.signer.party

Contract Signatory Party

Definition: Party which is a signator to this Contract.

Cardinality: 1..1

Type: Reference(Organization, Patient, Practitioner, PractitionerRole, RelatedPerson)

Mappings: workflow=Event.performer.actor; w5=FiveWs.author; rim=Role Class

Contract.signer.signature

Contract Documentation Signature

Definition: Legally binding Contract DSIG signature contents in Base64.

Cardinality: 1..*

Type: Signature

Mappings: w5=FiveWs.author; rim=Participation.signatureCode :: CD (0..1) Definition: Whether the participant has attested participation through a signature, or whether such a signature is needed. Examples: A surgical Procedure act object (representing a procedure report) requires a signature of the performing and responsible surgeon, and possibly other participants; The participant intends to provide a signature. Participation.signatureText :: ED (0..1) Definition: A textual or multimedia depiction of the signature by which the participant endorses and accepts responsibility for his or her participation in the Act as specified in the Participation.typeCode. UsageNotes: The signature can be represented either inline or by reference according to the ED data type. Typical cases are

Paper-based signatures: the ED data type may refer to a document or other resource that can be retrieved through an electronic interface to a hardcopy archive. 2) Electronic signature: this attribute can represent virtually any electronic signature scheme. 3) Digital signature: this attribute can represent digital signatures by reference to a signature data block that is constructed in accordance to a digital signature standard, such as XML-DSIG, PKCS#7, PGP, etc. Examples: 1) An "author" participant assumes accountability for the truth of the Act statement to the best of his knowledge. 2) An information recipient only attests to the fact that he or she has received the information.

Contract.friendly

Contract Friendly Language

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.

Cardinality: 0..*

Type: BackboneElement

Mappings: w5=FiveWs.what[x]; rim=LanguageCommunication

Contract.friendly.content[x]

Easily comprehended representation of this Contract

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

Cardinality: 1..1

Type: Attachment, Reference(Composition, DocumentReference, QuestionnaireResponse)

Mappings: w5=FiveWs.what[x]; rim=Act.text Definition: A renderable textual or multimedia description (or reference to a description) of the complete information which would reasonably be expected to be displayed to a human reader conveyed by the Act.

Contract.legal

Contract Legal Language

Definition: List of Legal expressions or representations of this Contract.

Cardinality: 0..*

Type: BackboneElement

Mappings: w5=FiveWs.what[x]; rim=LanguageCommunication

Contract.legal.content[x]

Contract Legal Text

Definition: Contract legal text in human renderable form.

Cardinality: 1..1

Type: Attachment, Reference(Composition, DocumentReference, QuestionnaireResponse)

Mappings: w5=FiveWs.what[x]; rim=Example: Act.text of an Act coded as with ActPrivacyLaw, ActPolicy code

Contract.rule

Computable Contract Language

Definition: List of Computable Policy Rule Language Representations of this Contract.

Cardinality: 0..*

Type: BackboneElement

Mappings: w5=FiveWs.what[x]; rim=LanguageCommunication

Contract.rule.content[x]

Computable Contract Rules

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

Cardinality: 1..1

Type: Attachment, Reference(DocumentReference)

Mappings: w5=FiveWs.what[x]; rim=Computable Policy Consent [Observation: templateId 2.16.840.1.113883.3.445.16] This template is used to represent an alternative representation of the Privacy Consent Directive (e.g.,ODRL, XrML, XACML) as a computer-readable set of rules. An implementation may use any appropriate representations of the privacy consent in addition to the "ConsentDirectiveStructuredDefinition" which uses the Clinical Template structure to express the elements of a consent directive in an interoperable way.

SHALL contain exactly one [1..1] templateId ( CONF-CD-16 ) such that it a. SHALL contain exactly one [1..1] @root="2.16.840.1.113883.3.445.16"
SHALL contain exactly one [1..1] @moodCode="DEF" (CodeSystem: 2.16.840.1.113883.5.1001 HL7ActMood) (CONF:14912)
SHALL contain exactly one [1..1] code (CONF:9139)/@code="57016-8" Privacy Policy Acknowledgement Document (CodeSystem: 2.16.840.1.113883.6.1 LOINC) (CONF:9138) It specifies the LOINC code corresponding to "Privacy Policy Acknowledgement Document", it is fixed at this value.
SHOULD contain zero or more [0..*] value with @xsi:type="ANY" (CONF:9140) The value contains the computable representation of the policy. This may be a standard-based access control or attribute control based policy (See "References"). Computable Policy Consent example

Contract.legallyBinding[x]

Binding Contract

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.

Cardinality: 0..1

Type: Attachment, Reference(Composition, DocumentReference, QuestionnaireResponse, Contract)

Mappings: rim=DocumentCompletion code system AU (authenticated) Description: A completion status in which a document has been signed manually or electronically by one or more individuals who attest to its accuracy. No explicit determination is made that the assigned individual has performed the authentication. While the standard allows multiple instances of authentication, it would be typical to have a single instance of authentication, usually by the assigned individual.