Generated Narrative: StructureDefinition profile-Contract Name Flags Card. Type Description & Constraints Contract 0..* Contract(5.0.0) Legal Agreement #xD; meta #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:meta 0..1 Meta DSTU2: meta additional types URL: http://hl7.org/fhir/1.0/StructureDefinition/extension-Contract.meta #xD; text #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:text 0..1 (Complex) DSTU2: text additional types URL: http://hl7.org/fhir/1.0/StructureDefinition/extension-Contract.text #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:action 0..* CodeableConcept DSTU2: Contract Action (new) URL: http://hl7.org/fhir/1.0/StructureDefinition/extension-Contract.action Binding: ContractActionCodes (example): Detailed codes for the contract action. #xD; extension:actionReason 0..* CodeableConcept DSTU2: Contract Action Reason (new) URL: http://hl7.org/fhir/1.0/StructureDefinition/extension-Contract.actionReason Binding: http://terminology.hl7.org/ValueSet/v3-PurposeOfUse|2.0.0 (example): Detailed codes for the contract action reason. #xD; extension:role 0..* CodeableConcept DSTU2: Contract Actor Role (new) URL: http://hl7.org/fhir/1.0/StructureDefinition/extension-Contract.actor.role Binding: ContractActorRoleCodes (example): Detailed codes for the contract actor role. #xD; extension:valuedItem 0..* (Complex) DSTU2: Contract Valued Item (new) URL: http://hl7.org/fhir/1.0/StructureDefinition/extension-Contract.valuedItem #xD; extension:binding 0..1 Attachment, Reference(Cross-version Profile for DSTU2.Composition for use in FHIR R5(0.1.0) | Composition | Cross-version Profile for DSTU2.DocumentReference for use in FHIR R5(0.1.0) | DocumentReference | Cross-version Profile for DSTU2.QuestionnaireResponse for use in FHIR R5(0.1.0) | QuestionnaireResponse) DSTU2: Binding Contract (new) URL: http://hl7.org/fhir/1.0/StructureDefinition/extension-Contract.binding #xD; identifier #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:identifier 0..1 Identifier DSTU2: Contract identifier additional types URL: http://hl7.org/fhir/1.0/StructureDefinition/extension-Contract.identifier #xD; applies #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:applies 0..1 Period DSTU2: applies additional types URL: http://hl7.org/fhir/1.0/StructureDefinition/extension-Contract.applies #xD; subject #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:subject 0..* Reference(Resource) DSTU2: Subject of this Contract additional types URL: http://hl7.org/fhir/StructureDefinition/alternate-reference #xD; authority #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:authority 0..* Reference(Resource) DSTU2: authority additional types URL: http://hl7.org/fhir/StructureDefinition/alternate-reference #xD; domain #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:domain 0..* Reference(Resource) DSTU2: Domain in which this Contract applies additional types URL: http://hl7.org/fhir/StructureDefinition/alternate-reference #xD; author #xD; Slices for extension 1..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:entity 1..1 Reference(Resource) DSTU2: Contract Actor Type URL: http://hl7.org/fhir/StructureDefinition/alternate-reference #xD; term #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:actionReason 0..* CodeableConcept DSTU2: Contract Term Action Reason (new) URL: http://hl7.org/fhir/1.0/StructureDefinition/extension-Contract.term.actionReason Binding: http://terminology.hl7.org/ValueSet/v3-PurposeOfUse|2.0.0 (example): Detailed codes for the contract action reason. #xD; extension:actor 0..* (Complex) DSTU2: Contract Term Actor List (new) URL: http://hl7.org/fhir/1.0/StructureDefinition/extension-Contract.term.actor #xD; extension:valuedItem 0..* (Complex) DSTU2: Contract Term Valued Item (new) URL: http://hl7.org/fhir/1.0/StructureDefinition/extension-Contract.term.valuedItem #xD; identifier #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:identifier 0..1 Identifier DSTU2: Contract Term identifier additional types URL: http://hl7.org/fhir/1.0/StructureDefinition/extension-Contract.term.identifier #xD; applies #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:applies 0..1 Period DSTU2: applies additional types URL: http://hl7.org/fhir/1.0/StructureDefinition/extension-Contract.term.applies #xD; topicReference #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:alternateReference 0..1 Reference(Resource) DSTU2: Subject of this Contract Term additional types URL: http://hl7.org/fhir/StructureDefinition/alternate-reference #xD; signer #xD; party #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:party 0..1 Reference(Resource) DSTU2: party URL: http://hl7.org/fhir/StructureDefinition/alternate-reference #xD; signature #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:signature 0..1 string DSTU2: signature additional types URL: http://hl7.org/fhir/1.0/StructureDefinition/extension-Contract.signer.signature #xD; friendly #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:content 0..1 Attachment DSTU2: content additional types URL: http://hl7.org/fhir/1.0/StructureDefinition/extension-Contract.friendly.content #xD; contentReference #xD; Slices for extension Content/Rules for all slices #xD; extension:alternateReference 0..1 Reference(Resource) DSTU2: content additional types URL: http://hl7.org/fhir/StructureDefinition/alternate-reference #xD; legal #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:content 0..1 Attachment DSTU2: content additional types URL: http://hl7.org/fhir/1.0/StructureDefinition/extension-Contract.legal.content #xD; contentReference #xD; Slices for extension Content/Rules for all slices #xD; extension:alternateReference 0..1 Reference(Resource) DSTU2: content additional types URL: http://hl7.org/fhir/StructureDefinition/alternate-reference #xD; rule #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:content 0..1 Attachment DSTU2: content additional types URL: http://hl7.org/fhir/1.0/StructureDefinition/extension-Contract.rule.content #xD; contentReference #xD; Slices for extension Content/Rules for all slices #xD; extension:alternateReference 0..1 Reference(Resource) DSTU2: content additional types URL: http://hl7.org/fhir/StructureDefinition/alternate-reference #xD; Documentation for this format
Cross-version Profile for DSTU2.Contract for use in FHIR R5
This cross-version profile allows DSTU2 Contract content to be represented via FHIR R5 Contract resources.
Legally enforceable, formally recorded unilateral or bilateral directive i.e., a policy or agreement.
If the resource is contained in another resource, it SHALL NOT contain nested Resources
If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().ofType(canonical) | %resource.descendants().ofType(uri) | %resource.descendants().ofType(url))) or descendants().where(reference = '#').exists() or descendants().where(ofType(canonical) = '#').exists() or descendants().where(ofType(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
If a resource is contained in another resource, it SHALL NOT have a security label
When a resource has no narrative, only systems that fully understand the data can display the resource to a human safely. Including a human readable representation in the resource makes for a much more robust eco-system and cheaper handling of resources by intermediary systems. Some ecosystems restrict distribution of resources to only those systems that do fully understand the resources, and as a consequence implementers may believe that the narrative is superfluous. However experience shows that such eco-systems often open up to new participants over time.
A resource should have narrative for robust management
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.
The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
Must have either extensions or value[x], not both
DSTU2: `Contract.meta` additional types (Meta) additional types from child elements (lastUpdated, profile, security, tag, versionId)
Element `Contract.meta` is mapped to FHIR R5 element `Contract.meta` as `SourceIsBroaderThanTarget`. The mappings for `Contract.meta` do not cover the following types: Meta. The mappings for `Contract.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.
The version specific identifier, as it appears in the version portion of the URL. This value changes when the resource is created, updated, or deleted.
The server assigns this value, and ignores what the client specifies, except in the case that the server is imposing version integrity on updates/deletes.
When the resource last changed - e.g. when the version changed.
This element is generally omitted in instances submitted in a PUT or POST. Instead, it is populated in the response instance and when retrieving information using a GET. The server / resource manager sets this value; what a client provides is irrelevant. This is equivalent to the HTTP Last-Modified and SHOULD have the same value on a [read](http://hl7.org/fhir/R5/http.html#read) interaction.
Identifies where the resource comes from
A uri that identifies the source system of the resource. This provides a minimal amount of [Provenance](http://hl7.org/fhir/R5/provenance.html#) information that can be used to track or differentiate the source of information in the resource. The source may identify another FHIR server, document, message, database, etc.
The exact use of the source (and the possible implied Provenance.entity.role and agent.role) is left to implementer discretion. Only one nominated source is allowed; for additional provenance details, a full Provenance resource should be used. The source may correspond to Provenance.entity.what[x] or Provenance.agent.who[x], though it may be a more general or abstract reference. This element can be used to indicate where the current master source of a resource that has a canonical URL if the resource is no longer hosted at the canonical URL.
Profiles this resource claims to conform to
A list of profiles (references to [StructureDefinition](http://hl7.org/fhir/R5/structuredefinition.html#) resources) that this resource claims to conform to. The URL is a reference to [StructureDefinition.url](http://hl7.org/fhir/R5/structuredefinition-definitions.html#StructureDefinition.url).
It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set.
Security Labels applied to this resource
Security labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure.
The security labels can be updated without changing the stated version of the resource. The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored.
Security Labels from the Healthcare Privacy and Security Classification System.
Tags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource.
The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored.
Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
A set of rules under which this content was created
A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.
Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.
This element is labeled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies its meaning or interpretation
The base language in which the resource is written.
Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
Text summary of the resource, for human interpretation
A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.
Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
DSTU2: `Contract.text` additional types (Narrative) additional types from child elements (div, status)
Element `Contract.text` is mapped to FHIR R5 element `Contract.text` as `SourceIsBroaderThanTarget`. The mappings for `Contract.text` do not cover the following types: Narrative. The mappings for `Contract.text` do not cover the following types based on type expansion: div, status. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.
generated | extensions | additional | empty
The status of the narrative - whether it's entirely generated (from just the defined data or the extensions too), or whether a human authored it and it may contain additional data.
The actual narrative content, a stripped down version of XHTML.
The contents of the html element are an XHTML fragment containing only the basic html formatting elements described in chapters 7-11 and 15 of the HTML 4.0 standard, elements (either name or href), images and internally contained stylesheets. The XHTML content SHALL NOT contain a head, a body, external stylesheet references, scripts, forms, base/link/xlink, frames, iframes and objects.
The narrative SHALL contain only the basic html formatting elements and attributes described in chapters 7-11 (except section 4 of chapter 9) and 15 of the HTML 4.0 standard, elements (either name or href), images and internally contained style attributes
The narrative SHALL have some non-whitespace content
These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.
This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.
DSTU2: `Contract.action` (new:CodeableConcept)
Element `Contract.action` has a context of Contract based on following the parent source element upwards and mapping to `Contract`. Element `Contract.action` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
DSTU2: `Contract.actionReason` (new:CodeableConcept)
Element `Contract.actionReason` has a context of Contract based on following the parent source element upwards and mapping to `Contract`. Element `Contract.actionReason` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
DSTU2: `Contract.actor.role` (new:CodeableConcept)
Element `Contract.actor.role` has a context of Contract based on following the parent source element upwards and mapping to `Contract`. Element `Contract.actor.role` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
DSTU2: `Contract.valuedItem` (new:BackboneElement)
Element `Contract.valuedItem` has a context of Contract based on following the parent source element upwards and mapping to `Contract`. Element `Contract.valuedItem` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
DSTU2: `Contract.binding[x]` (new:Attachment, Reference(Composition,DocumentReference,QuestionnaireResponse))
Element `Contract.binding[x]` has a context of Contract based on following the parent source element upwards and mapping to `Contract`. Element `Contract.binding[x]` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R5/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the resource that contains them
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.
DSTU2: Contract identifier additional types
DSTU2: `Contract.identifier` additional types (Identifier) additional types from child elements (assigner, period, system, type, use, value)
Element `Contract.identifier` is mapped to FHIR R5 element `Contract.identifier` as `RelatedTo`. The mappings for `Contract.identifier` do not cover the following types: Identifier. The mappings for `Contract.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value.
usual | official | temp | secondary | old (If known)
Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.
Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.
This is labeled as "Is Modifier" because applications should not mistake a temporary id for a permanent one.
Identifies the purpose for this identifier, if known .
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.
This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.
Allows users to make use of identifiers when the identifier system is not known.
A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.
Establishes the namespace for the value - that is, an absolute URL that describes a set values that are unique.
Identifier.system is always case sensitive.
There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.
The portion of the identifier typically relevant to the user and which is unique within the context of the system.
If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the [http://hl7.org/fhir/StructureDefinition/rendered-value](http://hl7.org/fhir/extensions/StructureDefinition-rendered-value.html)). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)
Time period when id is/was valid for use
Time period during which identifier is/was valid for use.
Role.effectiveTime or implied by context
Organization that issued id (may be just text)
Organization that issued/manages the identifier.
The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
Canonical identifier for this contract, represented as a URI (globally unique).
Used in a domain that uses a supplied contract repository.
An absolute URI that is used to identify this contract when it is referenced in a specification, model, design, instance or a contract derivative; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which this plan definition is (or will be) published.
An edition identifier used for business purposes to label business significant variants.
Note - This is a business versionId, not a resource version id (see discussion at [Versioning](http://hl7.org/fhir/R5/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](http://hl7.org/fhir/R5/resource.html#bv-format).
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.
amended | appended | cancelled | disputed | entered-in-error | executable +
This element is labeled as a modifier because the status contains codes that mark the contract as not currently valid or active.
This is the Contract Business Workflow Status.
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
A code specifying the state of the resource instance.
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.
Detailed codes for the legal state of a contract.
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.
Content derived from the basal information
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.
This is an example set of Content Derivative type codes, which represent the minimal content derived from the basal information source.
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.
The Contract issuance dateTime often precedes the Contract effective dateTime.
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.
Relevant time or time-period when this Contract is applicable.
The dateTime upon which the Contract is binding.
Act.effectiveTime Definition: The clinically or operationally relevant time of an act, exclusive of administrative activity.
DSTU2: `Contract.applies` additional types (Period) additional types from child elements (end, start)
Element `Contract.applies` is mapped to FHIR R5 element `Contract.applies` as `SourceIsBroaderThanTarget`. The mappings for `Contract.applies` do not cover the following types: Period. The mappings for `Contract.applies` do not cover the following types based on type expansion: end, start.
The start of the period. The boundary is inclusive.
If the low element is missing, the meaning is that the low boundary is not known.
End time with inclusive boundary, if not ongoing
The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.
The end value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has an end value of 2012-02-03.
If the end of the period is missing, it means that the period is ongoing
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.
DSTU2: Subject of this Contract additional types
DSTU2: `Contract.subject` additional types from child elements (display, reference)
Element `Contract.subject` is mapped to FHIR R5 element `Contract.subject` as `SourceIsBroaderThanTarget`. The mappings for `Contract.subject` do not cover the following types based on type expansion: display, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `Contract.subject` with unmapped reference targets: Resource.
Literal reference, Relative, internal or absolute URL
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
Type the reference refers to (e.g. "Patient") - must be a resource in resources
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a known RESTful URL) or by resolving the target of the reference.
Aa resource (or, for logical models, the URI of the logical model).
Logical reference, when literal reference is not known
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the [http://hl7.org/fhir/StructureDefinition/additionalIdentifier](http://hl7.org/fhir/extensions/StructureDefinition-additionalIdentifier.html) extension.
Plain text narrative that identifies the resource in addition to the resource reference.
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
Authority under which this Contract has standing
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.
Organization Role. CONCEPT DOMAIN: OrganizationEntityType Description: Further classifies entities of EntityClass ORG.
DSTU2: `Contract.authority` additional types from child elements (display, reference)
Element `Contract.authority` is mapped to FHIR R5 element `Contract.authority` as `SourceIsBroaderThanTarget`. The mappings for `Contract.authority` do not cover the following types based on type expansion: display, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `Contract.authority` with unmapped reference targets: Organization.
A sphere of control governed by an authoritative jurisdiction, organization, or person
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.
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.
DSTU2: Domain in which this Contract applies additional types
DSTU2: `Contract.domain` additional types from child elements (display, reference)
Element `Contract.domain` is mapped to FHIR R5 element `Contract.domain` as `SourceIsBroaderThanTarget`. The mappings for `Contract.domain` do not cover the following types based on type expansion: display, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `Contract.domain` with unmapped reference targets: Location.
Sites in which the contract is complied with, exercised, or in force.
A natural language name identifying this Contract definition, derivative, or instance in any legal state. Provides additional information about its content. This name should be usable as an identifier for the module by machine processing applications such as code generation.
The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.
Support human navigation and code generation.
A short, descriptive, user-friendly title for this Contract definition, derivative, or instance in any legal state.
A more detailed or qualifying explanatory or alternate user-friendly title for this Contract definition, derivative, or instance in any legal state.
Alternative representation of the title for this Contract definition, derivative, or instance in any legal state., e.g., a domain specific contract number related to legislation.
The individual or organization that authored the Contract definition, derivative, or instance in any legal state.
Element `Contract.actor.entity` is mapped to FHIR R5 element `Contract.author` as `RelatedTo`. The standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `Contract.actor.entity` with unmapped reference targets: Contract, Device, Group, Location, Organization, Patient, Practitioner, RelatedPerson, Substance.
A 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.
Contractual areas of concern are very broad. This element supports narrowing the area of concern to more specific term topics within this Contract. Given the wide range of contract topics, implementers need to be cognizant of the business use case for which they are designing a FHIR Contract, and narrowly specify the topic being represented with respect to the Contract.type and any specializing Contract.subtype. The same topic, e.g., an asset such as a good or service, such as a real property, medical supply, insurance, information, a procedure or employment, or a manner of conduct, such adherence to a privacy, trust, or security policy, may be the topic of multiple types of contracts. One way to determine the Contract.topic is to answer the question: "What is the overall objective of this legal instrument?". The Contract.topic is described with more detail by the terms of the Contract.
May be used to focus the topic of a Contract definition, derivative, or instance in any legal state.
A high-level category for the legal instrument, whether constructed as a Contract definition, derivative, or instance in any legal state. Provides additional information about its content within the context of the Contract's scope to distinguish the kinds of systems that would be interested in the contract.
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.
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.
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.
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.
Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
Extensions that cannot be ignored even if unrecognized
May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
Precusory content structure and use, i.e., a boilerplate, template, application for a contract such as an insurance policy or benefits under a program, e.g., workers compensation.
Detailed codes for the definition of contracts.
Detailed codes for the additional definition of contracts.
The individual or organization that published the Contract precursor content.
The date (and optionally time) when the contract was last significantly changed. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the contract changes.
amended | appended | cancelled | disputed | entered-in-error | executable +.
Status of the publication of contract content.
A copyright statement relating to Contract precursor content. Copyright statements are generally legal restrictions on the use and publishing of the Contract precursor content.
One or more Contract Provisions, which may be related and conveyed as a group, and may contain nested groups.
RIM mechanism for grouping or nesting rules, which are likely Acts and Observations.
DSTU2: Contract Term Action Reason (new)
DSTU2: `Contract.term.actionReason` (new:CodeableConcept)
Element `Contract.term.actionReason` has a context of Contract.term based on following the parent source element upwards and mapping to `Contract`. Element `Contract.term.actionReason` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
DSTU2: `Contract.term.actor` (new:BackboneElement)
Element `Contract.term.actor` has a context of Contract.term based on following the parent source element upwards and mapping to `Contract`. Element `Contract.term.actor` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
DSTU2: `Contract.term.valuedItem` (new:BackboneElement)
Element `Contract.term.valuedItem` has a context of Contract.term based on following the parent source element upwards and mapping to `Contract`. Element `Contract.term.valuedItem` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
Unique identifier for this particular Contract Provision.
DSTU2: Contract Term identifier additional types
DSTU2: `Contract.term.identifier` additional types (Identifier) additional types from child elements (assigner, period, system, type, use, value)
Element `Contract.term.identifier` is mapped to FHIR R5 element `Contract.term.identifier` as `SourceIsBroaderThanTarget`. The mappings for `Contract.term.identifier` do not cover the following types: Identifier. The mappings for `Contract.term.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value.
When this Contract Provision was issued.
Relevant time or time-period when this Contract Provision is applicable.
DSTU2: `Contract.term.applies` additional types (Period) additional types from child elements (end, start)
Element `Contract.term.applies` is mapped to FHIR R5 element `Contract.term.applies` as `SourceIsBroaderThanTarget`. The mappings for `Contract.term.applies` do not cover the following types: Period. The mappings for `Contract.term.applies` do not cover the following types based on type expansion: end, start.
DSTU2: Subject of this Contract Term additional types
DSTU2: `Contract.term.subject` additional types from child elements (display, reference)
Element `Contract.term.subject` is mapped to FHIR R5 element `Contract.term.topic[x]` as `RelatedTo`. The mappings for `Contract.term.subject` do not cover the following types based on type expansion: display, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `Contract.term.subject` with unmapped reference targets: Resource. Source element `Contract.term.subject` has unmapped reference types. While the target element `Contract.term.topic[x]` is a choice type and does not allow extensions, the `alternate-reference` extension can be applied to Reference values within it.
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.
Detailed codes for the types of contract provisions.
Contract Term Type specific classification
A specialized legal clause or condition based on overarching contract type.
Detailed codes for the subtypes of contract provisions.
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.
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.
This security label protects the term and its contained provision elements.
Number used to link this term or term element to the applicable Security Label.
Security label privacy tag that specifies the level of confidentiality protection required for this term and/or term elements.
Security label privacy tag that specifies the applicable privacy and security policies governing this term and/or term elements.
Security label privacy tag that specifies 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.
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).
The Contract.topic may be an application for or offer of a policy or service (e.g., uri to a consent directive form or a health insurance policy), which becomes the Contract once accepted by both the grantor and grantee. The Contract Resource may function simply as the computable representation of the executed contract, which may be the attached to the Contract Resource as the “binding” or as the “friendly” electronic form. For example, a Contract Resource may be automatically populated with the values expressed in a related QuestionnaireResponse. However, the Contract Resource may be considered the legally binding contract if it is the only “executed” form of this contract, and includes the signatures as *The Contract Resource may function as the computable representation of an application or offer in a pre-executed Contract if the grantor has not entered any values. In this case, it is populated with values in a “legal” form of the application or offer or by the values in an associated Questionnaire. If the grantor has filled in the legal form or the associated Questionnaire Response, then these values are used to populate a pre-executed Contract Resource. If the Contract.topic is considered an application or offer, then the policy is often required to be attached as the “legal” basis for the application to ensure “informed consent” to the contract, and that any discrepancy between the application and the policy are interpreted against the policy. Implementers should check organizational and jurisdictional policies to determine the relationship among multiple representations of a contract pre- and post-execution.
In the context of a contract, the topic is the matter under consideration in regards to which specific rights, privileges, obligations, restrictions, and prohibitions are binding on any grantor and grantee parties upon the execution of the contract. Given the wide range of contract topics, implementers need to be cognizant of the business use case for which they are designing a FHIR Contract, and narrowly specify the topic being represented with respect to the Contract.type and any specializing Contract.subtype. The same topic, e.g., an asset such as a good or service, such as a real property, medical supply, insurance, information, a procedure or employment, or a manner of conduct, such adherence to a privacy, trust, or security policy, may be the topic of multiple types of contracts. One way to determine the Contract.topic is to answer the question: “What is the object of negotiation?” Answer: The Contract.topic, which may be described with more detail in the [0..*]Contract.valuedItem @ [0..1] Contract.valuedItem.entity[x] Definition: Specific type of Contract Valued Item that may be priced. CodeableConcept|Reference(Any) Contract.topic is “the what” that a grantor is exchanging with a grantee in return for some benefit. Contract.topic is “the what” to which any Contract.action is being applied for any stipulated Contract.action.reason. AContract.topic is “the what” governed by the execution of the contract to which any party’s rights, privileges, obligations, restrictions, and prohibitions apply.
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.
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".
The type of decision made by a grantor with respect to an offer made by a grantee.
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.
How the decision about a Contract was conveyed.
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.
Human readable form of this Contract Offer.
The id of the clause or question text of the offer in the referenced questionnaire/response.
.outboundRelationship[typeCode=DEFN].target[classCode=OBS, moodCode=DEFN].id
Security labels that protects the offer.
Target entity type about which the term may be concerned.
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 or instances that refer to it, and/or are owned by the offeree.
The class (type) of information a consent rule covers.
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.
Description of the quality and completeness of the asset that may be a factor in its valuation.
Type of Asset availability for use or ownership.
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.
Security labels that protects the asset.
COCT_RM440000UV09 ValuedItem classCode INVE
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.
COCT_RM440000UV09 ValuedItem effectiveTime
Specifies the units by which the Contract Valued Item is measured or counted, and quantifies the countable or measurable Contract Valued Item instances.
COCT_RM440000UV09 ValuedItem unitQuantity
Contract Valued Item fee, charge, or cost
A Contract Valued Item unit valuation measure.
COCT_RM440000UV09 ValuedItem unitPriceAmt
Contract Valued Item Price Scaling Factor
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.
COCT_RM440000UV09 ValuedItem factorNumber
Contract Valued Item Difficulty Scaling Factor
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.
COCT_RM440000UV09 ValuedItem pointNumber
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.
Id of the clause or question text related to the context of this valuedItem in the referenced form or QuestionnaireResponse.
Security Labels that define affected terms
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.
Several agents may be associated (i.e. has some responsibility for an activity) with an activity and vice-versa. For example, in cases of actions initiated by one user for other users, or in events that involve more than one user, hardware device, software, or system process. However, only one user may be the initiator/requestor for the event.
An agent can be a person, an organization, software, device, or other entities that may be ascribed responsibility.
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.
Activity or service obligation to be done or not done, performed or not performed, effectuated or not by this Contract term.
The entity the action is performed or not performed on or for.
Role type of agent assigned roles in this Contract.
Detailed codes for the contract actor role.
RoleClass, RoleCode, ParticipationType, ParticipationFunction codes
Reason or purpose for the action stipulated by this Contract Provision.
Detailed codes for the contract action reason.
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.
Id [identifier??] of the clause or question text related to this action in the referenced form or QuestionnaireResponse.
Encounter or Episode with primary association to the specified term activity.
Id [identifier??] of the clause or question text related to the requester of this action in the referenced form or QuestionnaireResponse.
Who or what initiated the action and has responsibility for its activation.
The type of individual that is desired or required to perform or not perform the action.
Codes for the types of action performer.
The type of role or competency of an individual desired or required to perform or not perform the action.
Codes for the role of the action performer.
Actor that wil execute (or not) 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.
Comments made about the term action made by the requester, performer, subject or other participants.
Security labels that protects the action.
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 Provenance.entity indicates the target that was changed in the update (see [Provenance.entity](http://hl7.org/fhir/R5/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.
Signers who are principal parties to the contract are bound by the Contract.activity related to the Contract.topic, and the Contract.term(s), which either extend or restrict the overall action on the topic by, for example, stipulating specific policies or obligations constraining actions, action reason, or agents with respect to some or all of the topic. For example, specifying how policies or obligations shall constrain actions and action reasons permitted or denied on all or a subset of the Contract.topic (e.g., all or a portion of property being transferred by the contract), agents (e.g., who can resell, assign interests, or alter the property being transferred by the contract), actions, and action reasons; or with respect to Contract.terms, stipulating, extending, or limiting the Contract.period of applicability or valuation of items under consideration.
The Contract.signer applies a signature to the Contract.binding referenced resource, which is the documentation that is the legal "source of truth". The Contract.signer may delegate, such as a legally recognized personal representative, or have a delegate assigned e.g., by a court of law, to actually sign the Contract, such as a trustee in the case of incompetence.
Role of this Contract signer, e.g. notary, grantee.
RoleClass, RoleCode, ParticipationType, ParticipationFunction class codes.
Party which is a signator to this Contract.
Element `Contract.signer.party` is mapped to FHIR R5 element `Contract.signer.party` as `RelatedTo`. The standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `Contract.signer.party` with unmapped reference targets: Organization, Patient, Practitioner, RelatedPerson.
Legally binding Contract DSIG signature contents in Base64.
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 1) 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.
DSTU2: `Contract.signer.signature` additional types (string) additional types from child elements (value)
Element `Contract.signer.signature` is mapped to FHIR R5 element `Contract.signer.signature` as `RelatedTo`. The mappings for `Contract.signer.signature` do not cover the following types: string. The mappings for `Contract.signer.signature` do not cover the following types based on type expansion: value.
Indication of the reason the entity signed the object(s)
An indication of the reason that the entity signed this document. This may be explicitly included as part of the signature information and can be used when determining accountability for various actions concerning the document.
Examples include attesting to: authorship, correct transcription, and witness of specific event. Also known as a "Commitment Type Indication".
An indication of the reason that an entity signed the object.
This should agree with the information in the signature.
A reference to an application-usable description of the identity that signed (e.g. the signature used their private key).
A reference to an application-usable description of the identity that is represented by the signature.
The party that can't sign. For example a child.
used when the signature is on behalf of a non-signer.
The technical format of the signed resources
A mime type that indicates the technical format of the target resources signed by the signature.
"xml", "json" and "ttl" are allowed, which describe the simple encodings described in the specification (and imply appropriate bundle support). Otherwise, mime types are legal here.
A mime type that indicates the technical format of the signature. Important mime types are application/signature+xml for X ML DigSig, application/jose for JWS, and image/* for a graphical image of a signature, etc.
The actual signature content (XML DigSig. JWS, picture, etc.)
The base64 encoding of the Signature content. When signature is not recorded electronically this element would be empty.
Where the signature type is an XML DigSig, the signed content is a FHIR Resource(s), the signature is of the XML form of the Resource(s) using XML-Signature (XMLDIG) "Detached Signature" form.
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.
DSTU2: `Contract.friendly.content[x]` additional types (Attachment)
Element `Contract.friendly.content[x]` is mapped to FHIR R5 element `Contract.friendly.content[x]` as `RelatedTo`. The mappings for `Contract.friendly.content[x]` do not cover the following types: Attachment. The target context `Contract.friendly.content[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Contract.friendly`. The standard extension `alternate-reference` has been mapped as PART of the representation of FHIR DSTU2 element `Contract.friendly.content[x]` with unmapped reference targets: Composition, DocumentReference, QuestionnaireResponse. Source element `Contract.friendly.content[x]` has unmapped reference types. While the target element `Contract.friendly.content[x]` is a choice type and does not allow extensions, the `alternate-reference` extension can be applied to Reference values within it.
Easily comprehended representation of this Contract
Human readable rendering of this Contract in a format and representation intended to enhance comprehension and ensure understandability.
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.
List of Legal expressions or representations of this Contract.
DSTU2: `Contract.legal.content[x]` additional types (Attachment)
Element `Contract.legal.content[x]` is mapped to FHIR R5 element `Contract.legal.content[x]` as `RelatedTo`. The mappings for `Contract.legal.content[x]` do not cover the following types: Attachment. The target context `Contract.legal.content[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Contract.legal`. The standard extension `alternate-reference` has been mapped as PART of the representation of FHIR DSTU2 element `Contract.legal.content[x]` with unmapped reference targets: Composition, DocumentReference, QuestionnaireResponse. Source element `Contract.legal.content[x]` has unmapped reference types. While the target element `Contract.legal.content[x]` is a choice type and does not allow extensions, the `alternate-reference` extension can be applied to Reference values within it.
Contract legal text in human renderable form.
Example: Act.text of an Act coded as with ActPrivacyLaw, ActPolicy code
List of Computable Policy Rule Language Representations of this Contract.
DSTU2: `Contract.rule.content[x]` additional types (Attachment) additional types from child elements (contentType, creation, data, hash, language, size, title, url, display, reference)
Element `Contract.rule.content[x]` is mapped to FHIR R5 element `Contract.rule.content[x]` as `RelatedTo`. The mappings for `Contract.rule.content[x]` do not cover the following types: Attachment. The mappings for `Contract.rule.content[x]` do not cover the following types based on type expansion: contentType, creation, data, display, hash, language, reference, size, title, url. The target context `Contract.rule.content[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Contract.rule`. The standard extension `alternate-reference` has been mapped as PART of the representation of FHIR DSTU2 element `Contract.rule.content[x]` with unmapped reference targets: DocumentReference. Source element `Contract.rule.content[x]` has unmapped reference types. While the target element `Contract.rule.content[x]` is a choice type and does not allow extensions, the `alternate-reference` extension can be applied to Reference values within it.
Computable Contract conveyed using a policy rule language (e.g. XACML, DKAL, SecPal).
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. 1. 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" 2. SHALL contain exactly one [1..1] @moodCode="DEF" (CodeSystem: 2.16.840.1.113883.5.1001 HL7ActMood) (CONF:14912) 3. 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. 4. 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 <entryRelationship typeCode="COMP"> <templateId root="2.16.840.1.113883.3.445.16" /> <observationMedia classCode="OBS" moodCode="EVN"> <value mediaType="text/xml" representation="TXT"> ... </value> </observationMedia> </entryRelationship>
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.
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.