Page Status: draft updated 2025-05-07
Contract
Information domain hvo-agreement, where this resource is represented as Avtal
Page index
Introduction
The Contract resource holds information about an agreement which entails rights and obligations for the associated parties.
Regarding information about how the "must support"-property is used in the Swedish National Catalog of Organization, Offerings and Contracts, please refer to the page Profiles.
Overview
HVOContract (Contract) | C | Contract | |
id | S Σ | 0..1 | string |
meta | Σ | 0..1 | Meta |
implicitRules | Σ ?! | 0..1 | uri |
language | 0..1 | codeBinding | |
text | 0..1 | Narrative | |
contained | 0..* | Resource | |
extension | C | 0..* | Extension |
additionalRelationship | S C | 0..* | Extension(Complex) |
id | 0..1 | string | |
extension | C | 2..* | Extension |
additionalRelationship | S C | 1..1 | Extension |
id | 0..1 | string | |
extension | C | 0..0 | Extension |
url | S | 1..1 | uriAuto Value |
value[x] | S | 1..1 | |
valueReference | Reference(HVOContract) | ||
type | S C | 1..1 | Extension |
id | 0..1 | string | |
extension | C | 0..0 | Extension |
url | S | 1..1 | uriAuto Value |
value[x] | S | 1..1 | Binding |
valueCoding | Coding | ||
id | 0..1 | string | |
extension | C | 0..* | Extension |
system | S Σ | 1..1 | uri |
version | Σ | 0..1 | string |
code | S Σ | 1..1 | code |
display | Σ | 0..1 | string |
userSelected | Σ | 0..1 | boolean |
url | 1..1 | uriAuto Value | |
value[x] | 0..0 | ||
modifierExtension | ?! C | 0..* | Extension |
identifier | S Σ | 1..* | Identifier |
id | 0..1 | string | |
extension | C | 0..* | Extension |
use | Σ ?! | 0..1 | codeBinding |
type | Σ | 0..1 | CodeableConceptBinding |
system | S Σ | 1..1 | uri |
value | S Σ | 1..1 | string |
period | Σ | 0..1 | Period |
assigner | Σ | 0..1 | Reference(Organization) |
url | 0..1 | uri | |
version | Σ | 0..1 | string |
status | Σ ?! | 0..1 | codeBinding |
legalState | 0..1 | CodeableConceptBinding | |
instantiatesCanonical | 0..1 | Reference(Contract) | |
instantiatesUri | 0..1 | uri | |
contentDerivative | 0..1 | CodeableConcept | |
issued | Σ | 0..1 | dateTime |
applies | S Σ | 1..1 | Period |
id | 0..1 | string | |
extension | C | 0..* | Extension |
start | S Σ C | 1..1 | dateTime |
end | S Σ C | 0..1 | dateTime |
expirationType | 0..1 | CodeableConcept | |
subject | S Σ | 0..* | Reference(HVOOrganizationAffiliation) |
authority | 0..* | Reference(Organization) | |
domain | 0..* | Reference(Location) | |
site | 0..* | Reference(Location) | |
name | Σ | 0..1 | string |
title | Σ | 0..1 | string |
subtitle | 0..1 | string | |
alias | 0..* | string | |
author | 0..1 | Reference(Patient | Practitioner | PractitionerRole | Organization) | |
scope | 0..1 | CodeableConcept | |
topic[x] | 0..1 | ||
topicCodeableConcept | CodeableConcept | ||
topicReference | Reference(Resource) | ||
type | S Σ | 0..1 | CodeableConceptBinding |
id | 0..1 | string | |
extension | C | 0..* | Extension |
coding | S Σ | 1..1 | Coding |
id | 0..1 | string | |
extension | C | 0..* | Extension |
system | S Σ | 1..1 | uri |
version | Σ | 0..1 | string |
code | S Σ | 1..1 | code |
display | Σ | 0..1 | string |
userSelected | Σ | 0..1 | boolean |
text | Σ | 0..1 | string |
subType | S Σ | 0..1 | CodeableConceptBinding |
id | 0..1 | string | |
extension | C | 0..* | Extension |
coding | S Σ | 1..1 | Coding |
id | 0..1 | string | |
extension | C | 0..* | Extension |
system | S Σ | 1..1 | uri |
version | Σ | 0..1 | string |
code | S Σ | 1..1 | code |
display | Σ | 0..1 | string |
userSelected | Σ | 0..1 | boolean |
text | Σ | 0..1 | string |
contentDefinition | 0..1 | BackboneElement | |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
type | 1..1 | CodeableConcept | |
subType | 0..1 | CodeableConcept | |
publisher | 0..1 | Reference(Practitioner | PractitionerRole | Organization) | |
publicationDate | 0..1 | dateTime | |
publicationStatus | 1..1 | codeBinding | |
copyright | 0..1 | markdown | |
term | S | 0..1 | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
identifier | Σ | 0..1 | Identifier |
issued | Σ | 0..1 | dateTime |
applies | Σ | 0..1 | Period |
topic[x] | 0..1 | ||
topicCodeableConcept | CodeableConcept | ||
topicReference | Reference(Resource) | ||
type | 0..1 | CodeableConcept | |
subType | 0..1 | CodeableConcept | |
text | S Σ | 1..1 | string |
securityLabel | 0..* | BackboneElement | |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
number | 0..* | unsignedInt | |
classification | 1..1 | Coding | |
category | 0..* | Coding | |
control | 0..* | Coding | |
offer | S | 1..1 | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
identifier | 0..* | Identifier | |
party | 0..* | BackboneElement | |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
reference | 1..* | Reference(Patient | RelatedPerson | Practitioner | PractitionerRole | Device | Group | Organization) | |
role | 1..1 | CodeableConcept | |
topic | Σ | 0..1 | Reference(Resource) |
type | 0..1 | CodeableConcept | |
decision | 0..1 | CodeableConceptBinding | |
decisionMode | 0..* | CodeableConcept | |
answer | 0..* | BackboneElement | |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
value[x] | 1..1 | ||
valueBoolean | boolean | ||
valueDecimal | decimal | ||
valueInteger | integer | ||
valueDate | date | ||
valueDateTime | dateTime | ||
valueTime | time | ||
valueString | string | ||
valueUri | uri | ||
valueAttachment | Attachment | ||
valueCoding | Coding | ||
valueQuantity | Quantity | ||
valueReference | Reference(Resource) | ||
text | S | 0..1 | string |
linkId | 0..* | string | |
securityLabelNumber | 0..* | unsignedInt | |
asset | 0..* | BackboneElement | |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
scope | 0..1 | CodeableConcept | |
type | 0..* | CodeableConcept | |
typeReference | 0..* | Reference(Resource) | |
subtype | 0..* | CodeableConcept | |
relationship | 0..1 | CodingBinding | |
context | 0..* | BackboneElement | |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
reference | 0..1 | Reference(Resource) | |
code | 0..* | CodeableConcept | |
text | 0..1 | string | |
condition | 0..1 | string | |
periodType | 0..* | CodeableConcept | |
period | 0..* | Period | |
usePeriod | 0..* | Period | |
text | 0..1 | string | |
linkId | 0..* | string | |
answer | 0..* | see (answer) | |
securityLabelNumber | 0..* | unsignedInt | |
valuedItem | 0..* | BackboneElement | |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
entity[x] | 0..1 | ||
entityCodeableConcept | CodeableConcept | ||
entityReference | Reference(Resource) | ||
identifier | 0..1 | Identifier | |
effectiveTime | 0..1 | dateTime | |
quantity | 0..1 | SimpleQuantity | |
unitPrice | 0..1 | Money | |
factor | 0..1 | decimal | |
points | 0..1 | decimal | |
net | 0..1 | Money | |
payment | 0..1 | string | |
paymentDate | 0..1 | dateTime | |
responsible | 0..1 | Reference(Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | |
recipient | 0..1 | Reference(Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | |
linkId | 0..* | string | |
securityLabelNumber | 0..* | unsignedInt | |
action | 0..* | BackboneElement | |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
doNotPerform | ?! | 0..1 | boolean |
type | 1..1 | CodeableConcept | |
subject | 0..* | BackboneElement | |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
reference | 1..* | Reference(Patient | RelatedPerson | Practitioner | PractitionerRole | Device | Group | Organization) | |
role | 0..1 | CodeableConcept | |
intent | 1..1 | CodeableConcept | |
linkId | 0..* | string | |
status | 1..1 | CodeableConcept | |
context | 0..1 | Reference(Encounter | EpisodeOfCare) | |
contextLinkId | 0..* | string | |
occurrence[x] | 0..1 | ||
occurrenceDateTime | dateTime | ||
occurrencePeriod | Period | ||
occurrenceTiming | Timing | ||
requester | 0..* | Reference(Patient | RelatedPerson | Practitioner | PractitionerRole | Device | Group | Organization) | |
requesterLinkId | 0..* | string | |
performerType | 0..* | CodeableConcept | |
performerRole | 0..1 | CodeableConcept | |
performer | 0..1 | Reference(RelatedPerson | Patient | Practitioner | PractitionerRole | CareTeam | Device | Substance | Organization | Location) | |
performerLinkId | 0..* | string | |
reasonCode | 0..* | CodeableConcept | |
reasonReference | 0..* | Reference(Condition | Observation | DiagnosticReport | DocumentReference | Questionnaire | QuestionnaireResponse) | |
reason | 0..* | string | |
reasonLinkId | 0..* | string | |
note | 0..* | Annotation | |
securityLabelNumber | 0..* | unsignedInt | |
group | 0..* | see (term) | |
supportingInfo | 0..* | Reference(Resource) | |
relevantHistory | 0..* | Reference(Provenance) | |
signer | 0..* | BackboneElement | |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
type | 1..1 | CodingBinding | |
party | 1..1 | Reference(Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | |
signature | 1..* | Signature | |
friendly | 0..* | BackboneElement | |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
content[x] | 1..1 | ||
contentAttachment | Attachment | ||
contentReference | Reference(Composition | DocumentReference | QuestionnaireResponse) | ||
legal | S | 0..1 | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
content[x] | 1..1 | ||
contentReference | Reference(Composition | DocumentReference | QuestionnaireResponse) | ||
contentAttachment | S | 1..1 | Attachment |
id | 0..1 | string | |
extension | C | 0..* | Extension |
contentType | Σ | 0..1 | codeBinding |
language | Σ | 0..1 | codeBinding |
data | 0..1 | base64Binary | |
url | S Σ | 1..1 | url |
size | Σ | 0..1 | unsignedInt |
hash | Σ | 0..1 | base64Binary |
title | Σ | 0..1 | string |
creation | Σ | 0..1 | dateTime |
rule | 0..* | BackboneElement | |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
content[x] | 1..1 | ||
contentAttachment | Attachment | ||
contentReference | Reference(DocumentReference) | ||
legallyBinding[x] | 0..1 | ||
legallyBindingAttachment | Attachment | ||
legallyBindingReference | Reference(Composition | DocumentReference | QuestionnaireResponse | Contract) |
Contract | |||
Short | Legal Agreement | ||
Definition | Legally enforceable, formally recorded unilateral or bilateral directive i.e., a policy or agreement. | ||
Cardinality | 0..* | ||
Constraints |
| ||
Mappings |
| ||
Contract.id | |||
Short | Logical id of this artifact | ||
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. | ||
Cardinality | 0..1 | ||
Type | string | ||
Must Support | True | ||
Summary | True | ||
Comments | The only time that a resource does not have an id is when it is being submitted to the server using a create operation. | ||
Contract.meta | |||
Short | Metadata about the resource | ||
Definition | 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. | ||
Cardinality | 0..1 | ||
Type | Meta | ||
Summary | True | ||
Constraints |
| ||
Contract.implicitRules | |||
Short | A set of rules under which this content was created | ||
Definition | 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. | ||
Cardinality | 0..1 | ||
Type | uri | ||
Modifier | True | ||
Summary | True | ||
Comments | 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 it's narrative along with other profiles, value sets, etc. | ||
Constraints |
| ||
Contract.language | |||
Short | Language of the resource content | ||
Definition | The base language in which the resource is written. | ||
Cardinality | 0..1 | ||
Type | code | ||
Binding | A human language.
| ||
Comments | 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). | ||
Constraints |
| ||
Contract.text | |||
Short | Text summary of the resource, for human interpretation | ||
Definition | 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. | ||
Cardinality | 0..1 | ||
Type | Narrative | ||
Alias | narrative, html, xhtml, display | ||
Comments | Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later. | ||
Constraints |
| ||
Mappings |
| ||
Contract.contained | |||
Short | Contained, inline Resources | ||
Definition | These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. | ||
Cardinality | 0..* | ||
Type | Resource | ||
Alias | inline resources, anonymous resources, contained resources | ||
Comments | 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. | ||
Mappings |
| ||
Contract.extension | |||
Short | Additional content defined by implementations | ||
Definition | May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
Cardinality | 0..* | ||
Type | Extension | ||
Alias | extensions, user content | ||
Comments | 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. | ||
Slicing | Unordered, Open, by url(Value) | ||
Constraints |
| ||
Mappings |
| ||
Contract.extension:additionalRelationship | |||
Short | Optional Extensions Element | ||
Definition | Extension for Contract to supply information about relationships between contracts. | ||
Cardinality | 0..* | ||
Type | Extension(Complex) | ||
Must Support | True | ||
Alias | extensions, user content | ||
Comments | 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. | ||
Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
Constraints |
| ||
Mappings |
| ||
Contract.extension:additionalRelationship.id | |||
Short | Unique id for inter-element referencing | ||
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
Cardinality | 0..1 | ||
Type | string | ||
Mappings |
| ||
Contract.extension:additionalRelationship.extension | |||
Short | Additional content defined by implementations | ||
Definition | 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 manageable, 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. | ||
Cardinality | 2..* | ||
Type | Extension | ||
Alias | extensions, user content | ||
Comments | 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. | ||
Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
Constraints |
| ||
Mappings |
| ||
Contract.extension:additionalRelationship.extension:additionalRelationship | |||
Short | Additional content defined by implementations | ||
Definition | 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 manageable, 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. | ||
Cardinality | 1..1 | ||
Type | Extension | ||
Must Support | True | ||
Alias | extensions, user content | ||
Comments | 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. | ||
Constraints |
| ||
Mappings |
| ||
Contract.extension:additionalRelationship.extension:additionalRelationship.id | |||
Short | Unique id for inter-element referencing | ||
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
Cardinality | 0..1 | ||
Type | string | ||
Mappings |
| ||
Contract.extension:additionalRelationship.extension:additionalRelationship.extension | |||
Short | Additional content defined by implementations | ||
Definition | 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 manageable, 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. | ||
Cardinality | 0..0 | ||
Type | Extension | ||
Alias | extensions, user content | ||
Comments | 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. | ||
Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
Constraints |
| ||
Mappings |
| ||
Contract.extension:additionalRelationship.extension:additionalRelationship.url | |||
Short | identifies the meaning of the extension | ||
Definition | Source of the definition for the extension code - a logical name or a URL. | ||
Cardinality | 1..1 | ||
Type | uri | ||
Must Support | True | ||
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. | ||
Auto Value | additionalRelationship | ||
Mappings |
| ||
Contract.extension:additionalRelationship.extension:additionalRelationship.value[x] | |||
Short | Value of extension | ||
Definition | Value of extension - must be one of a constrained set of the data types (see Extensibility for a list). | ||
Cardinality | 1..1 | ||
Type | Reference(HVOContract) | ||
Must Support | True | ||
Constraints |
| ||
Mappings |
| ||
Contract.extension:additionalRelationship.extension:type | |||
Short | Code for the type of relationship between contracts. | ||
Definition | 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 manageable, 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. | ||
Cardinality | 1..1 | ||
Type | Extension | ||
Must Support | True | ||
Alias | extensions, user content | ||
Comments | 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. | ||
Constraints |
| ||
Mappings |
| ||
Contract.extension:additionalRelationship.extension:type.id | |||
Short | Unique id for inter-element referencing | ||
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
Cardinality | 0..1 | ||
Type | string | ||
Mappings |
| ||
Contract.extension:additionalRelationship.extension:type.extension | |||
Short | Additional content defined by implementations | ||
Definition | 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 manageable, 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. | ||
Cardinality | 0..0 | ||
Type | Extension | ||
Alias | extensions, user content | ||
Comments | 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. | ||
Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
Constraints |
| ||
Mappings |
| ||
Contract.extension:additionalRelationship.extension:type.url | |||
Short | identifies the meaning of the extension | ||
Definition | Source of the definition for the extension code - a logical name or a URL. | ||
Cardinality | 1..1 | ||
Type | uri | ||
Must Support | True | ||
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. | ||
Auto Value | type | ||
Mappings |
| ||
Contract.extension:additionalRelationship.extension:type.value[x] | |||
Short | Value of extension | ||
Definition | Value of extension - must be one of a constrained set of the data types (see Extensibility for a list). | ||
Cardinality | 1..1 | ||
Type | Coding | ||
Binding | |||
Must Support | True | ||
Constraints |
| ||
Mappings |
| ||
Contract.extension:additionalRelationship.extension:type.value[x].id | |||
Short | Unique id for inter-element referencing | ||
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
Cardinality | 0..1 | ||
Type | string | ||
Mappings |
| ||
Contract.extension:additionalRelationship.extension:type.value[x].extension | |||
Short | Additional content defined by implementations | ||
Definition | 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 manageable, 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. | ||
Cardinality | 0..* | ||
Type | Extension | ||
Alias | extensions, user content | ||
Comments | 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. | ||
Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
Constraints |
| ||
Mappings |
| ||
Contract.extension:additionalRelationship.extension:type.value[x].system | |||
Short | Identity of the terminology system | ||
Definition | The identification of the code system that defines the meaning of the symbol in the code. | ||
Cardinality | 1..1 | ||
Type | uri | ||
Must Support | True | ||
Summary | True | ||
Requirements | Need to be unambiguous about the source of the definition of the symbol. | ||
Comments | The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously. | ||
Constraints |
| ||
Mappings |
| ||
Contract.extension:additionalRelationship.extension:type.value[x].version | |||
Short | Version of the system - if relevant | ||
Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. | ||
Cardinality | 0..1 | ||
Type | string | ||
Summary | True | ||
Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. | ||
Constraints |
| ||
Mappings |
| ||
Contract.extension:additionalRelationship.extension:type.value[x].code | |||
Short | Symbol in syntax defined by the system | ||
Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). | ||
Cardinality | 1..1 | ||
Type | code | ||
Must Support | True | ||
Summary | True | ||
Requirements | Need to refer to a particular code in the system. | ||
Constraints |
| ||
Mappings |
| ||
Contract.extension:additionalRelationship.extension:type.value[x].display | |||
Short | Representation defined by the system | ||
Definition | A representation of the meaning of the code in the system, following the rules of the system. | ||
Cardinality | 0..1 | ||
Type | string | ||
Summary | True | ||
Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. | ||
Constraints |
| ||
Mappings |
| ||
Contract.extension:additionalRelationship.extension:type.value[x].userSelected | |||
Short | If this coding was chosen directly by the user | ||
Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). | ||
Cardinality | 0..1 | ||
Type | boolean | ||
Summary | True | ||
Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. | ||
Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. | ||
Constraints |
| ||
Mappings |
| ||
Contract.extension:additionalRelationship.url | |||
Short | identifies the meaning of the extension | ||
Definition | Source of the definition for the extension code - a logical name or a URL. | ||
Cardinality | 1..1 | ||
Type | uri | ||
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. | ||
Auto Value | http://electronichealth.se/fhir/hvo/StructureDefinition/HVOContractAdditionalRelationshipExtension | ||
Mappings |
| ||
Contract.extension:additionalRelationship.value[x] | |||
Short | Value of extension | ||
Definition | Value of extension - must be one of a constrained set of the data types (see Extensibility for a list). | ||
Cardinality | 0..0 | ||
Type | base64Binary, boolean, canonical(), code, date, dateTime, decimal, id, instant, integer, markdown, oid, positiveInt, string, time, unsignedInt, uri, url, uuid, Address, Age, Annotation, Attachment, CodeableConcept, Coding, ContactPoint, Count, Distance, Duration, HumanName, Identifier, Money, Period, Quantity, Range, Ratio, Reference(), SampledData, Signature, Timing, ContactDetail, Contributor, DataRequirement, Expression, ParameterDefinition, RelatedArtifact, TriggerDefinition, UsageContext, Dosage, Meta | ||
Constraints |
| ||
Mappings |
| ||
Contract.modifierExtension | |||
Short | Extensions that cannot be ignored | ||
Definition | 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 manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||
Cardinality | 0..* | ||
Type | Extension | ||
Modifier | True | ||
Alias | extensions, user content | ||
Requirements | 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. | ||
Comments | 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. | ||
Constraints |
| ||
Mappings |
| ||
Contract.identifier | |||
Short | Contract number | ||
Definition | Unique identifier for this Contract or a derivative that references a Source Contract. | ||
Cardinality | 1..* | ||
Type | Identifier | ||
Must Support | True | ||
Summary | True | ||
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. | ||
Constraints |
| ||
Mappings |
| ||
Contract.identifier.id | |||
Short | Unique id for inter-element referencing | ||
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
Cardinality | 0..1 | ||
Type | string | ||
Mappings |
| ||
Contract.identifier.extension | |||
Short | Additional content defined by implementations | ||
Definition | 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 manageable, 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. | ||
Cardinality | 0..* | ||
Type | Extension | ||
Alias | extensions, user content | ||
Comments | 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. | ||
Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
Constraints |
| ||
Mappings |
| ||
Contract.identifier.use | |||
Short | usual | official | temp | secondary | old (If known) | ||
Definition | The purpose of this identifier. | ||
Cardinality | 0..1 | ||
Type | code | ||
Binding | Identifies the purpose for this identifier, if known . | ||
Modifier | True | ||
Summary | True | ||
Requirements | Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. | ||
Comments | Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. | ||
Constraints |
| ||
Mappings |
| ||
Contract.identifier.type | |||
Short | Description of identifier | ||
Definition | A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. | ||
Cardinality | 0..1 | ||
Type | CodeableConcept | ||
Binding | A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. | ||
Summary | True | ||
Requirements | Allows users to make use of identifiers when the identifier system is not known. | ||
Comments | 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. | ||
Constraints |
| ||
Mappings |
| ||
Contract.identifier.system | |||
Short | The namespace for the identifier value | ||
Definition | Establishes the namespace for the value - that is, a URL that describes a set values that are unique. | ||
Cardinality | 1..1 | ||
Type | uri | ||
Must Support | True | ||
Summary | True | ||
Requirements | 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. | ||
Comments | Identifier.system is always case sensitive. | ||
Constraints |
| ||
Examples | Generalhttp://www.acme.com/identifiers/patient | ||
Mappings |
| ||
Contract.identifier.value | |||
Short | The value that is unique | ||
Definition | The portion of the identifier typically relevant to the user and which is unique within the context of the system. | ||
Cardinality | 1..1 | ||
Type | string | ||
Must Support | True | ||
Summary | True | ||
Comments | 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 Rendered Value extension. 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. | ||
Constraints |
| ||
Examples | General123456 | ||
Mappings |
| ||
Contract.identifier.period | |||
Short | Time period when id is/was valid for use | ||
Definition | Time period during which identifier is/was valid for use. | ||
Cardinality | 0..1 | ||
Type | Period | ||
Summary | True | ||
Constraints |
| ||
Mappings |
| ||
Contract.identifier.assigner | |||
Short | Organization that issued id (may be just text) | ||
Definition | Organization that issued/manages the identifier. | ||
Cardinality | 0..1 | ||
Type | Reference(Organization) | ||
Summary | True | ||
Comments | 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. | ||
Constraints |
| ||
Mappings |
| ||
Contract.url | |||
Short | Basal definition | ||
Definition | Canonical identifier for this contract, represented as a URI (globally unique). | ||
Cardinality | 0..1 | ||
Type | uri | ||
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. | ||
Comments | Used in a domain that uses a supplied contract repository. | ||
Constraints |
| ||
Contract.version | |||
Short | Business edition | ||
Definition | An edition identifier used for business purposes to label business significant variants. | ||
Cardinality | 0..1 | ||
Type | string | ||
Summary | True | ||
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. | ||
Comments | Note - This is a business versionId, not a resource version id (see discussion http://build.fhir.org/resource.html#versions) Comments - There may be different contract instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the plan definition with the format [url]|[version]. | ||
Constraints |
| ||
Contract.status | |||
Short | amended | appended | cancelled | disputed | entered-in-error | executable | executed | negotiable | offered | policy | rejected | renewed | revoked | resolved | terminated | ||
Definition | The status of the resource instance. | ||
Cardinality | 0..1 | ||
Type | code | ||
Binding | A code specifying the state of the resource instance. | ||
Modifier | True | ||
Summary | True | ||
Requirements | This is the Contract Business Workflow Status. | ||
Comments | This element is labeled as a modifier because the status contains codes that mark the contract as not currently valid or active. | ||
Constraints |
| ||
Mappings |
| ||
Contract.legalState | |||
Short | 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. | ||
Cardinality | 0..1 | ||
Type | CodeableConcept | ||
Binding | Detailed codes for the legal state of a contract. | ||
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. | ||
Constraints |
| ||
Contract.instantiatesCanonical | |||
Short | 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) | ||
Constraints |
| ||
Contract.instantiatesUri | |||
Short | 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 | ||
Constraints |
| ||
Contract.contentDerivative | |||
Short | Content derived from the basal information | ||
Definition | The minimal content derived from the basal information source at a specific stage in its lifecycle. | ||
Cardinality | 0..1 | ||
Type | CodeableConcept | ||
Binding | This is an example set of Content Derivative type codes, which represent the minimal content derived from the basal information source. | ||
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. | ||
Constraints |
| ||
Mappings |
| ||
Contract.issued | |||
Short | When this Contract was issued | ||
Definition | When this Contract was issued. | ||
Cardinality | 0..1 | ||
Type | dateTime | ||
Summary | True | ||
Requirements | The Contract issuance dateTime often precedes the Contract effective dateTime. | ||
Constraints |
| ||
Mappings |
| ||
Contract.applies | |||
Short | Effective time | ||
Definition | Relevant time or time-period when this Contract is applicable. | ||
Cardinality | 1..1 | ||
Type | Period | ||
Must Support | True | ||
Summary | True | ||
Requirements | The dateTime upon which the Contract is binding. | ||
Constraints |
| ||
Mappings |
| ||
Contract.applies.id | |||
Short | Unique id for inter-element referencing | ||
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
Cardinality | 0..1 | ||
Type | string | ||
Mappings |
| ||
Contract.applies.extension | |||
Short | Additional content defined by implementations | ||
Definition | 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 manageable, 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. | ||
Cardinality | 0..* | ||
Type | Extension | ||
Alias | extensions, user content | ||
Comments | 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. | ||
Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
Constraints |
| ||
Mappings |
| ||
Contract.applies.start | |||
Short | The moment the contract becomes valid and has legal force | ||
Definition | The start of the period. The boundary is inclusive. | ||
Cardinality | 1..1 | ||
Type | dateTime | ||
Must Support | True | ||
Summary | True | ||
Comments | If the low element is missing, the meaning is that the low boundary is not known. | ||
Conditions | The cardinality or value of this element may be affected by these constraints: per-1 | ||
Constraints |
| ||
Mappings |
| ||
Contract.applies.end | |||
Short | The moment the contract stops being valid. Do not use if not known. | ||
Definition | 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. | ||
Cardinality | 0..1 | ||
Type | dateTime | ||
Must Support | True | ||
Summary | True | ||
Comments | The high 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. | ||
Meaning when missing | If the end of the period is missing, it means that the period is ongoing | ||
Conditions | The cardinality or value of this element may be affected by these constraints: per-1 | ||
Constraints |
| ||
Mappings |
| ||
Contract.expirationType | |||
Short | 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 | Codes for the Cessation of Contracts. | ||
Constraints |
| ||
Contract.subject | |||
Short | Contract Target Entity | ||
Definition | The target entity impacted by or of interest to parties to the agreement. | ||
Cardinality | 0..* | ||
Type | Reference(HVOOrganizationAffiliation) | ||
Must Support | True | ||
Summary | True | ||
Alias | Patient | ||
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. | ||
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. | ||
Constraints |
| ||
Mappings |
| ||
Contract.authority | |||
Short | 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. | ||
Cardinality | 0..* | ||
Type | Reference(Organization) | ||
Requirements | The governance framework responsible for ensuring compliance with or enforcement of the contract or policy. | ||
Constraints |
| ||
Mappings |
| ||
Contract.domain | |||
Short | 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. | ||
Cardinality | 0..* | ||
Type | Reference(Location) | ||
Alias | scope of governance jurisdiction | ||
Requirements | The entities bound by governance to comply with the enforcement of contracts or policies by a recognized authority. | ||
Constraints |
| ||
Mappings |
| ||
Contract.site | |||
Short | Specific Location | ||
Definition | Sites in which the contract is complied with, exercised, or in force. | ||
Cardinality | 0..* | ||
Type | Reference(Location) | ||
Constraints |
| ||
Contract.name | |||
Short | 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. | ||
Cardinality | 0..1 | ||
Type | string | ||
Summary | True | ||
Requirements | Support human navigation and 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. | ||
Constraints |
| ||
Contract.title | |||
Short | Human Friendly name | ||
Definition | A short, descriptive, user-friendly title for this Contract definition, derivative, or instance in any legal state.t giving additional information about its content. | ||
Cardinality | 0..1 | ||
Type | string | ||
Summary | True | ||
Constraints |
| ||
Contract.subtitle | |||
Short | Subordinate Friendly name | ||
Definition | An explanatory or alternate user-friendly title for this Contract definition, derivative, or instance in any legal state.t giving additional information about its content. | ||
Cardinality | 0..1 | ||
Type | string | ||
Constraints |
| ||
Contract.alias | |||
Short | 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 | ||
Constraints |
| ||
Contract.author | |||
Short | 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) | ||
Constraints |
| ||
Contract.scope | |||
Short | 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 | Codes for the range of legal concerns. | ||
Constraints |
| ||
Contract.topic[x] | |||
Short | Focus of contract interest | ||
Definition | Narrows the range of legal concerns to focus on the achievement of specific contractual objectives. | ||
Cardinality | 0..1 | ||
Type | CodeableConcept, Reference(Resource) | ||
Requirements | Requirement: May be used to focus the topic of a Contract definition, derivative, or instance in any legal state. Comment: Contractual areas of concern are very broad. This element supports narrowing the area of concern to more specific term topics within this Contract. Given the wide range of contract topics, implementers need to be cognizant of the business use case for which they are designing a FHIR Contract, and narrowly specify the topic being represented with respect to the Contract.type and any specializing Contract.subtype. The same topic, e.g., an asset such as a good or service, such as a real property, medical supply, insurance, information, a procedure or employment, or a manner of conduct, such adherence to a privacy, trust, or security policy, may be the topic of multiple types of contracts. One way to determine the Contract.topic is to answer the question: “What is the overall objective of this legal instrument. The Contract.topic is described with more detail by the terms of the Contract. | ||
Constraints |
| ||
Contract.type | |||
Short | Code for the domain(s) in which the services that the contract applies to have been procured | ||
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 | List of overall contract codes. | ||
Must Support | True | ||
Summary | True | ||
Constraints |
| ||
Mappings |
| ||
Contract.type.id | |||
Short | Unique id for inter-element referencing | ||
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
Cardinality | 0..1 | ||
Type | string | ||
Mappings |
| ||
Contract.type.extension | |||
Short | Additional content defined by implementations | ||
Definition | 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 manageable, 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. | ||
Cardinality | 0..* | ||
Type | Extension | ||
Alias | extensions, user content | ||
Comments | 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. | ||
Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
Constraints |
| ||
Mappings |
| ||
Contract.type.coding | |||
Short | Code defined by a terminology system | ||
Definition | A reference to a code defined by a terminology system. | ||
Cardinality | 1..1 | ||
Type | Coding | ||
Must Support | True | ||
Summary | True | ||
Requirements | Allows for alternative encodings within a code system, and translations to other code systems. | ||
Comments | Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. | ||
Constraints |
| ||
Mappings |
| ||
Contract.type.coding.id | |||
Short | Unique id for inter-element referencing | ||
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
Cardinality | 0..1 | ||
Type | string | ||
Mappings |
| ||
Contract.type.coding.extension | |||
Short | Additional content defined by implementations | ||
Definition | 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 manageable, 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. | ||
Cardinality | 0..* | ||
Type | Extension | ||
Alias | extensions, user content | ||
Comments | 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. | ||
Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
Constraints |
| ||
Mappings |
| ||
Contract.type.coding.system | |||
Short | Identity of the terminology system | ||
Definition | The identification of the code system that defines the meaning of the symbol in the code. | ||
Cardinality | 1..1 | ||
Type | uri | ||
Must Support | True | ||
Summary | True | ||
Requirements | Need to be unambiguous about the source of the definition of the symbol. | ||
Comments | The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously. | ||
Constraints |
| ||
Mappings |
| ||
Contract.type.coding.version | |||
Short | Version of the system - if relevant | ||
Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. | ||
Cardinality | 0..1 | ||
Type | string | ||
Summary | True | ||
Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. | ||
Constraints |
| ||
Mappings |
| ||
Contract.type.coding.code | |||
Short | Symbol in syntax defined by the system | ||
Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). | ||
Cardinality | 1..1 | ||
Type | code | ||
Must Support | True | ||
Summary | True | ||
Requirements | Need to refer to a particular code in the system. | ||
Constraints |
| ||
Mappings |
| ||
Contract.type.coding.display | |||
Short | Representation defined by the system | ||
Definition | A representation of the meaning of the code in the system, following the rules of the system. | ||
Cardinality | 0..1 | ||
Type | string | ||
Summary | True | ||
Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. | ||
Constraints |
| ||
Mappings |
| ||
Contract.type.coding.userSelected | |||
Short | If this coding was chosen directly by the user | ||
Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). | ||
Cardinality | 0..1 | ||
Type | boolean | ||
Summary | True | ||
Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. | ||
Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. | ||
Constraints |
| ||
Mappings |
| ||
Contract.type.text | |||
Short | Plain text representation of the concept | ||
Definition | A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. | ||
Cardinality | 0..1 | ||
Type | string | ||
Summary | True | ||
Requirements | The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. | ||
Comments | Very often the text is the same as a displayName of one of the codings. | ||
Constraints |
| ||
Mappings |
| ||
Contract.subType | |||
Short | Section of law in which a procurement has been done or an task has been delivered. | ||
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..1 | ||
Type | CodeableConcept | ||
Binding | Detailed codes within the above. | ||
Must Support | True | ||
Summary | True | ||
Constraints |
| ||
Mappings |
| ||
Contract.subType.id | |||
Short | Unique id for inter-element referencing | ||
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
Cardinality | 0..1 | ||
Type | string | ||
Mappings |
| ||
Contract.subType.extension | |||
Short | Additional content defined by implementations | ||
Definition | 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 manageable, 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. | ||
Cardinality | 0..* | ||
Type | Extension | ||
Alias | extensions, user content | ||
Comments | 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. | ||
Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
Constraints |
| ||
Mappings |
| ||
Contract.subType.coding | |||
Short | Code defined by a terminology system | ||
Definition | A reference to a code defined by a terminology system. | ||
Cardinality | 1..1 | ||
Type | Coding | ||
Must Support | True | ||
Summary | True | ||
Requirements | Allows for alternative encodings within a code system, and translations to other code systems. | ||
Comments | Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. | ||
Constraints |
| ||
Mappings |
| ||
Contract.subType.coding.id | |||
Short | Unique id for inter-element referencing | ||
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
Cardinality | 0..1 | ||
Type | string | ||
Mappings |
| ||
Contract.subType.coding.extension | |||
Short | Additional content defined by implementations | ||
Definition | 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 manageable, 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. | ||
Cardinality | 0..* | ||
Type | Extension | ||
Alias | extensions, user content | ||
Comments | 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. | ||
Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
Constraints |
| ||
Mappings |
| ||
Contract.subType.coding.system | |||
Short | Identity of the terminology system | ||
Definition | The identification of the code system that defines the meaning of the symbol in the code. | ||
Cardinality | 1..1 | ||
Type | uri | ||
Must Support | True | ||
Summary | True | ||
Requirements | Need to be unambiguous about the source of the definition of the symbol. | ||
Comments | The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously. | ||
Constraints |
| ||
Mappings |
| ||
Contract.subType.coding.version | |||
Short | Version of the system - if relevant | ||
Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. | ||
Cardinality | 0..1 | ||
Type | string | ||
Summary | True | ||
Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. | ||
Constraints |
| ||
Mappings |
| ||
Contract.subType.coding.code | |||
Short | Symbol in syntax defined by the system | ||
Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). | ||
Cardinality | 1..1 | ||
Type | code | ||
Must Support | True | ||
Summary | True | ||
Requirements | Need to refer to a particular code in the system. | ||
Constraints |
| ||
Mappings |
| ||
Contract.subType.coding.display | |||
Short | Representation defined by the system | ||
Definition | A representation of the meaning of the code in the system, following the rules of the system. | ||
Cardinality | 0..1 | ||
Type | string | ||
Summary | True | ||
Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. | ||
Constraints |
| ||
Mappings |
| ||
Contract.subType.coding.userSelected | |||
Short | If this coding was chosen directly by the user | ||
Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). | ||
Cardinality | 0..1 | ||
Type | boolean | ||
Summary | True | ||
Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. | ||
Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. | ||
Constraints |
| ||
Mappings |
| ||
Contract.subType.text | |||
Short | Plain text representation of the concept | ||
Definition | A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. | ||
Cardinality | 0..1 | ||
Type | string | ||
Summary | True | ||
Requirements | The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. | ||
Comments | Very often the text is the same as a displayName of one of the codings. | ||
Constraints |
| ||
Mappings |
| ||
Contract.contentDefinition | |||
Short | 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 | ||
Constraints |
| ||
Contract.contentDefinition.id | |||
Short | Unique id for inter-element referencing | ||
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
Cardinality | 0..1 | ||
Type | string | ||
Mappings |
| ||
Contract.contentDefinition.extension | |||
Short | Additional content defined by implementations | ||
Definition | 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 manageable, 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. | ||
Cardinality | 0..* | ||
Type | Extension | ||
Alias | extensions, user content | ||
Comments | 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. | ||
Constraints |
| ||
Mappings |
| ||
Contract.contentDefinition.modifierExtension | |||
Short | Extensions that cannot be ignored even if unrecognized | ||
Definition | 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 manageable, 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). | ||
Cardinality | 0..* | ||
Type | Extension | ||
Modifier | True | ||
Summary | True | ||
Alias | extensions, user content, modifiers | ||
Requirements | 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. | ||
Comments | 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. | ||
Constraints |
| ||
Mappings |
| ||
Contract.contentDefinition.type | |||
Short | 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 | Detailed codes for the definition of contracts. | ||
Constraints |
| ||
Contract.contentDefinition.subType | |||
Short | Detailed Content Type Definition | ||
Definition | Detailed Precusory content type. | ||
Cardinality | 0..1 | ||
Type | CodeableConcept | ||
Binding | Detailed codes for the additional definition of contracts. | ||
Constraints |
| ||
Contract.contentDefinition.publisher | |||
Short | Publisher Entity | ||
Definition | The individual or organization that published the Contract precursor content. | ||
Cardinality | 0..1 | ||
Type | Reference(Practitioner | PractitionerRole | Organization) | ||
Constraints |
| ||
Contract.contentDefinition.publicationDate | |||
Short | When published | ||
Definition | The date (and optionally time) when the contract was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the contract changes. | ||
Cardinality | 0..1 | ||
Type | dateTime | ||
Constraints |
| ||
Contract.contentDefinition.publicationStatus | |||
Short | amended | appended | cancelled | disputed | entered-in-error | executable | executed | negotiable | offered | policy | rejected | renewed | revoked | resolved | terminated | ||
Definition | amended | appended | cancelled | disputed | entered-in-error | executable | executed | negotiable | offered | policy | rejected | renewed | revoked | resolved | terminated. | ||
Cardinality | 1..1 | ||
Type | code | ||
Binding | Status of the publication of contract content. | ||
Constraints |
| ||
Contract.contentDefinition.copyright | |||
Short | Publication Ownership | ||
Definition | A copyright statement relating to Contract precursor content. Copyright statements are generally legal restrictions on the use and publishing of the Contract precursor content. | ||
Cardinality | 0..1 | ||
Type | markdown | ||
Constraints |
| ||
Contract.term | |||
Short | 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..1 | ||
Type | BackboneElement | ||
Must Support | True | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.id | |||
Short | Unique id for inter-element referencing | ||
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
Cardinality | 0..1 | ||
Type | string | ||
Mappings |
| ||
Contract.term.extension | |||
Short | Additional content defined by implementations | ||
Definition | 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 manageable, 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. | ||
Cardinality | 0..* | ||
Type | Extension | ||
Alias | extensions, user content | ||
Comments | 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. | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.modifierExtension | |||
Short | Extensions that cannot be ignored even if unrecognized | ||
Definition | 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 manageable, 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). | ||
Cardinality | 0..* | ||
Type | Extension | ||
Modifier | True | ||
Summary | True | ||
Alias | extensions, user content, modifiers | ||
Requirements | 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. | ||
Comments | 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. | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.identifier | |||
Short | Contract Term Number | ||
Definition | Unique identifier for this particular Contract Provision. | ||
Cardinality | 0..1 | ||
Type | Identifier | ||
Summary | True | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.issued | |||
Short | Contract Term Issue Date Time | ||
Definition | When this Contract Provision was issued. | ||
Cardinality | 0..1 | ||
Type | dateTime | ||
Summary | True | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.applies | |||
Short | Contract Term Effective Time | ||
Definition | Relevant time or time-period when this Contract Provision is applicable. | ||
Cardinality | 0..1 | ||
Type | Period | ||
Summary | True | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.topic[x] | |||
Short | Term Concern | ||
Definition | The entity that the term applies to. | ||
Cardinality | 0..1 | ||
Type | CodeableConcept, Reference(Resource) | ||
Constraints |
| ||
Contract.term.type | |||
Short | 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 | Detailed codes for the types of contract provisions. | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.subType | |||
Short | Contract Term Type specific classification | ||
Definition | A specialized legal clause or condition based on overarching contract type. | ||
Cardinality | 0..1 | ||
Type | CodeableConcept | ||
Binding | Detailed codes for the subtypes of contract provisions. | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.text | |||
Short | Textual description of relevant contract specific conditions and texts which are not represented elsewhere, for example in organization affiliations and the services they include | ||
Definition | Statement of a provision in a policy or a contract. | ||
Cardinality | 1..1 | ||
Type | string | ||
Must Support | True | ||
Summary | True | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.securityLabel | |||
Short | Protection for the Term | ||
Definition | Security labels that protect the handling of information about the term and its elements, which may be specifically identified.. | ||
Cardinality | 0..* | ||
Type | BackboneElement | ||
Requirements | Requirement - Within a Contract, a security label may apply to the one to many nested group of terms or to a term, whether inside a group or a singleton. This security label protects the term and its contained provision elements. The security label on the entire set of term provision elements may be different from the security labels on a contained offer, asset, valuedItem, or data such as sensitive information, and must be the high water mark of all security labels within the term. Rationale is that a labelled term, which may be disaggregated from the Contract, and must persist the label on the term and on contained elements within other contexts. Requirement - If more than one policy dictates a level of confidentiality of the term, then each applicable policy may be represented by a security label specific to its requirements. Comment - A Security Label is comprised of 1..1 confidentiality code and 0..* other security label codes (aka "privacy tags". A Security Label is metadata assigned (aka "tagged") to Resources and Resource elements, which specify the confidentiality and sensitivity of the Resource or element and their related attributes, the purposes for which tagged items may be collected, access, used or disclosed, any limitation on the type of entities authorized to engage in permitted purposes, and handling instructions that obligate or prohibit certain actions on the tagged items. | ||
Constraints |
| ||
Contract.term.securityLabel.id | |||
Short | Unique id for inter-element referencing | ||
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
Cardinality | 0..1 | ||
Type | string | ||
Mappings |
| ||
Contract.term.securityLabel.extension | |||
Short | Additional content defined by implementations | ||
Definition | 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 manageable, 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. | ||
Cardinality | 0..* | ||
Type | Extension | ||
Alias | extensions, user content | ||
Comments | 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. | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.securityLabel.modifierExtension | |||
Short | Extensions that cannot be ignored even if unrecognized | ||
Definition | 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 manageable, 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). | ||
Cardinality | 0..* | ||
Type | Extension | ||
Modifier | True | ||
Summary | True | ||
Alias | extensions, user content, modifiers | ||
Requirements | 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. | ||
Comments | 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. | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.securityLabel.number | |||
Short | Link to Security Labels | ||
Definition | Number used to link this term or term element to the applicable Security Label. | ||
Cardinality | 0..* | ||
Type | unsignedInt | ||
Constraints |
| ||
Contract.term.securityLabel.classification | |||
Short | Confidentiality Protection | ||
Definition | Security label privacy tag that species the level of confidentiality protection required for this term and/or term elements. | ||
Cardinality | 1..1 | ||
Type | Coding | ||
Binding | Codes for confidentiality protection. | ||
Constraints |
| ||
Contract.term.securityLabel.category | |||
Short | Applicable Policy | ||
Definition | Security label privacy tag that species the applicable privacy and security policies governing this term and/or term elements. | ||
Cardinality | 0..* | ||
Type | Coding | ||
Binding | Codes for policy category. | ||
Constraints |
| ||
Contract.term.securityLabel.control | |||
Short | Handling Instructions | ||
Definition | Security label privacy tag that species the manner in which term and/or term elements are to be protected. | ||
Cardinality | 0..* | ||
Type | Coding | ||
Binding | Codes for handling instructions. | ||
Constraints |
| ||
Contract.term.offer | |||
Short | Context of the Contract term | ||
Definition | The matter of concern in the context of this provision of the agrement. | ||
Cardinality | 1..1 | ||
Type | BackboneElement | ||
Must Support | True | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.offer.id | |||
Short | Unique id for inter-element referencing | ||
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
Cardinality | 0..1 | ||
Type | string | ||
Mappings |
| ||
Contract.term.offer.extension | |||
Short | Additional content defined by implementations | ||
Definition | 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 manageable, 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. | ||
Cardinality | 0..* | ||
Type | Extension | ||
Alias | extensions, user content | ||
Comments | 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. | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.offer.modifierExtension | |||
Short | Extensions that cannot be ignored even if unrecognized | ||
Definition | 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 manageable, 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). | ||
Cardinality | 0..* | ||
Type | Extension | ||
Modifier | True | ||
Summary | True | ||
Alias | extensions, user content, modifiers | ||
Requirements | 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. | ||
Comments | 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. | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.offer.identifier | |||
Short | Offer business ID | ||
Definition | Unique identifier for this particular Contract Provision. | ||
Cardinality | 0..* | ||
Type | Identifier | ||
Constraints |
| ||
Contract.term.offer.party | |||
Short | Offer Recipient | ||
Definition | Offer Recipient. | ||
Cardinality | 0..* | ||
Type | BackboneElement | ||
Constraints |
| ||
Contract.term.offer.party.id | |||
Short | Unique id for inter-element referencing | ||
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
Cardinality | 0..1 | ||
Type | string | ||
Mappings |
| ||
Contract.term.offer.party.extension | |||
Short | Additional content defined by implementations | ||
Definition | 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 manageable, 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. | ||
Cardinality | 0..* | ||
Type | Extension | ||
Alias | extensions, user content | ||
Comments | 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. | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.offer.party.modifierExtension | |||
Short | Extensions that cannot be ignored even if unrecognized | ||
Definition | 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 manageable, 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). | ||
Cardinality | 0..* | ||
Type | Extension | ||
Modifier | True | ||
Summary | True | ||
Alias | extensions, user content, modifiers | ||
Requirements | 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. | ||
Comments | 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. | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.offer.party.reference | |||
Short | Referenced entity | ||
Definition | Participant in the offer. | ||
Cardinality | 1..* | ||
Type | Reference(Patient | RelatedPerson | Practitioner | PractitionerRole | Device | Group | Organization) | ||
Constraints |
| ||
Contract.term.offer.party.role | |||
Short | Participant engagement type | ||
Definition | How the party participates in the offer. | ||
Cardinality | 1..1 | ||
Type | CodeableConcept | ||
Binding | Codes for offer participant roles. | ||
Constraints |
| ||
Contract.term.offer.topic | |||
Short | 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). | ||
Cardinality | 0..1 | ||
Type | Reference(Resource) | ||
Summary | True | ||
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. | ||
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. | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.offer.type | |||
Short | 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 | Detailed codes for the types of contract provisions. | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.offer.decision | |||
Short | Accepting party choice | ||
Definition | Type of choice made by accepting party with respect to an offer made by an offeror/ grantee. | ||
Cardinality | 0..1 | ||
Type | CodeableConcept | ||
Binding | The type of decision made by a grantor with respect to an offer made by a 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". | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.offer.decisionMode | |||
Short | How decision is conveyed | ||
Definition | How the decision about a Contract was conveyed. | ||
Cardinality | 0..* | ||
Type | CodeableConcept | ||
Binding | Codes for conveying a decision. | ||
Constraints |
| ||
Contract.term.offer.answer | |||
Short | Response to offer text | ||
Definition | Response to offer text. | ||
Cardinality | 0..* | ||
Type | BackboneElement | ||
Constraints |
| ||
Contract.term.offer.answer.id | |||
Short | Unique id for inter-element referencing | ||
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
Cardinality | 0..1 | ||
Type | string | ||
Mappings |
| ||
Contract.term.offer.answer.extension | |||
Short | Additional content defined by implementations | ||
Definition | 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 manageable, 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. | ||
Cardinality | 0..* | ||
Type | Extension | ||
Alias | extensions, user content | ||
Comments | 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. | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.offer.answer.modifierExtension | |||
Short | Extensions that cannot be ignored even if unrecognized | ||
Definition | 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 manageable, 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). | ||
Cardinality | 0..* | ||
Type | Extension | ||
Modifier | True | ||
Summary | True | ||
Alias | extensions, user content, modifiers | ||
Requirements | 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. | ||
Comments | 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. | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.offer.answer.value[x] | |||
Short | 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, warrently 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) | ||
Constraints |
| ||
Contract.term.offer.text | |||
Short | Textual description of option to prolong the contracts validity, if possible | ||
Definition | Human readable form of this Contract Offer. | ||
Cardinality | 0..1 | ||
Type | string | ||
Must Support | True | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.offer.linkId | |||
Short | Pointer to text | ||
Definition | The id of the clause or question text of the offer in the referenced questionnaire/response. | ||
Cardinality | 0..* | ||
Type | string | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.offer.securityLabelNumber | |||
Short | Offer restriction numbers | ||
Definition | Security labels that protects the offer. | ||
Cardinality | 0..* | ||
Type | unsignedInt | ||
Constraints |
| ||
Contract.term.asset | |||
Short | Contract Term Asset List | ||
Definition | Contract Term Asset List. | ||
Cardinality | 0..* | ||
Type | BackboneElement | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.asset.id | |||
Short | Unique id for inter-element referencing | ||
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
Cardinality | 0..1 | ||
Type | string | ||
Mappings |
| ||
Contract.term.asset.extension | |||
Short | Additional content defined by implementations | ||
Definition | 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 manageable, 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. | ||
Cardinality | 0..* | ||
Type | Extension | ||
Alias | extensions, user content | ||
Comments | 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. | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.asset.modifierExtension | |||
Short | Extensions that cannot be ignored even if unrecognized | ||
Definition | 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 manageable, 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). | ||
Cardinality | 0..* | ||
Type | Extension | ||
Modifier | True | ||
Summary | True | ||
Alias | extensions, user content, modifiers | ||
Requirements | 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. | ||
Comments | 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. | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.asset.scope | |||
Short | Range of asset | ||
Definition | Differentiates the kind of the asset . | ||
Cardinality | 0..1 | ||
Type | CodeableConcept | ||
Binding | Codes for scoping an asset. | ||
Constraints |
| ||
Contract.term.asset.type | |||
Short | Asset category | ||
Definition | Target entity type about which the term may be concerned. | ||
Cardinality | 0..* | ||
Type | CodeableConcept | ||
Binding | Condes for the type of an asset. | ||
Constraints |
| ||
Contract.term.asset.typeReference | |||
Short | Associated entities | ||
Definition | Associated entities. | ||
Cardinality | 0..* | ||
Type | Reference(Resource) | ||
Constraints |
| ||
Contract.term.asset.subtype | |||
Short | Asset sub-category | ||
Definition | May be a subtype or part of an offered asset. | ||
Cardinality | 0..* | ||
Type | CodeableConcept | ||
Binding | Condes for the sub-type of an asset. | ||
Constraints |
| ||
Contract.term.asset.relationship | |||
Short | Kinship of the asset | ||
Definition | Specifies the applicability of the term to an asset resource instance, and instances it refers to orinstances that refer to it, and/or are owned by the offeree. | ||
Cardinality | 0..1 | ||
Type | Coding | ||
Binding | The class (type) of information a consent rule covers. | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.asset.context | |||
Short | Circumstance of the asset | ||
Definition | Circumstance of the asset. | ||
Cardinality | 0..* | ||
Type | BackboneElement | ||
Constraints |
| ||
Contract.term.asset.context.id | |||
Short | Unique id for inter-element referencing | ||
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
Cardinality | 0..1 | ||
Type | string | ||
Mappings |
| ||
Contract.term.asset.context.extension | |||
Short | Additional content defined by implementations | ||
Definition | 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 manageable, 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. | ||
Cardinality | 0..* | ||
Type | Extension | ||
Alias | extensions, user content | ||
Comments | 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. | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.asset.context.modifierExtension | |||
Short | Extensions that cannot be ignored even if unrecognized | ||
Definition | 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 manageable, 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). | ||
Cardinality | 0..* | ||
Type | Extension | ||
Modifier | True | ||
Summary | True | ||
Alias | extensions, user content, modifiers | ||
Requirements | 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. | ||
Comments | 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. | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.asset.context.reference | |||
Short | 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) | ||
Constraints |
| ||
Contract.term.asset.context.code | |||
Short | 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 | Codes for the context of the asset. | ||
Constraints |
| ||
Contract.term.asset.context.text | |||
Short | Context description | ||
Definition | Context description. | ||
Cardinality | 0..1 | ||
Type | string | ||
Constraints |
| ||
Contract.term.asset.condition | |||
Short | Quality desctiption of asset | ||
Definition | Description of the quality and completeness of the asset that imay be a factor in its valuation. | ||
Cardinality | 0..1 | ||
Type | string | ||
Constraints |
| ||
Contract.term.asset.periodType | |||
Short | Asset availability types | ||
Definition | Type of Asset availability for use or ownership. | ||
Cardinality | 0..* | ||
Type | CodeableConcept | ||
Binding | Codes for asset availability. | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.asset.period | |||
Short | Time period of the asset | ||
Definition | Asset relevant contractual time period. | ||
Cardinality | 0..* | ||
Type | Period | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.asset.usePeriod | |||
Short | Time period | ||
Definition | Time period of asset use. | ||
Cardinality | 0..* | ||
Type | Period | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.asset.text | |||
Short | 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 | ||
Constraints |
| ||
Contract.term.asset.linkId | |||
Short | 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 | ||
Constraints |
| ||
Contract.term.asset.answer | |||
Short | Response to assets | ||
Definition | Response to assets. | ||
Cardinality | 0..* | ||
Type | see (answer) | ||
Constraints |
| ||
Contract.term.asset.securityLabelNumber | |||
Short | Asset restriction numbers | ||
Definition | Security labels that protects the asset. | ||
Cardinality | 0..* | ||
Type | unsignedInt | ||
Constraints |
| ||
Contract.term.asset.valuedItem | |||
Short | Contract Valued Item List | ||
Definition | Contract Valued Item List. | ||
Cardinality | 0..* | ||
Type | BackboneElement | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.asset.valuedItem.id | |||
Short | Unique id for inter-element referencing | ||
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
Cardinality | 0..1 | ||
Type | string | ||
Mappings |
| ||
Contract.term.asset.valuedItem.extension | |||
Short | Additional content defined by implementations | ||
Definition | 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 manageable, 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. | ||
Cardinality | 0..* | ||
Type | Extension | ||
Alias | extensions, user content | ||
Comments | 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. | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.asset.valuedItem.modifierExtension | |||
Short | Extensions that cannot be ignored even if unrecognized | ||
Definition | 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 manageable, 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). | ||
Cardinality | 0..* | ||
Type | Extension | ||
Modifier | True | ||
Summary | True | ||
Alias | extensions, user content, modifiers | ||
Requirements | 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. | ||
Comments | 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. | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.asset.valuedItem.entity[x] | |||
Short | Contract Valued Item Type | ||
Definition | Specific type of Contract Valued Item that may be priced. | ||
Cardinality | 0..1 | ||
Type | CodeableConcept, Reference(Resource) | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.asset.valuedItem.identifier | |||
Short | Contract Valued Item Number | ||
Definition | Identifies a Contract Valued Item instance. | ||
Cardinality | 0..1 | ||
Type | Identifier | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.asset.valuedItem.effectiveTime | |||
Short | Contract Valued Item Effective Tiem | ||
Definition | Indicates the time during which this Contract ValuedItem information is effective. | ||
Cardinality | 0..1 | ||
Type | dateTime | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.asset.valuedItem.quantity | |||
Short | 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 | SimpleQuantity | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.asset.valuedItem.unitPrice | |||
Short | Contract Valued Item fee, charge, or cost | ||
Definition | A Contract Valued Item unit valuation measure. | ||
Cardinality | 0..1 | ||
Type | Money | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.asset.valuedItem.factor | |||
Short | 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 | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.asset.valuedItem.points | |||
Short | 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 | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.asset.valuedItem.net | |||
Short | 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 | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.asset.valuedItem.payment | |||
Short | Terms of valuation | ||
Definition | Terms of valuation. | ||
Cardinality | 0..1 | ||
Type | string | ||
Constraints |
| ||
Contract.term.asset.valuedItem.paymentDate | |||
Short | When payment is due | ||
Definition | When payment is due. | ||
Cardinality | 0..1 | ||
Type | dateTime | ||
Constraints |
| ||
Contract.term.asset.valuedItem.responsible | |||
Short | Who will make payment | ||
Definition | Who will make payment. | ||
Cardinality | 0..1 | ||
Type | Reference(Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | ||
Constraints |
| ||
Contract.term.asset.valuedItem.recipient | |||
Short | Who will receive payment | ||
Definition | Who will receive payment. | ||
Cardinality | 0..1 | ||
Type | Reference(Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | ||
Constraints |
| ||
Contract.term.asset.valuedItem.linkId | |||
Short | 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 | ||
Constraints |
| ||
Contract.term.asset.valuedItem.securityLabelNumber | |||
Short | 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 | ||
Constraints |
| ||
Contract.term.action | |||
Short | 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. | ||
Cardinality | 0..* | ||
Type | BackboneElement | ||
Requirements | An agent can be a person, an organization, software, device, or other entities that may be ascribed responsibility. | ||
Comments | Several agents may be associated (i.e. has some responsibility for an activity) with an activity and vice-versa. For example, in cases of actions initiated by one user for other users, or in events that involve more than one user, hardware device, software, or system process. However, only one user may be the initiator/requestor for the event. | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.action.id | |||
Short | Unique id for inter-element referencing | ||
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
Cardinality | 0..1 | ||
Type | string | ||
Mappings |
| ||
Contract.term.action.extension | |||
Short | Additional content defined by implementations | ||
Definition | 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 manageable, 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. | ||
Cardinality | 0..* | ||
Type | Extension | ||
Alias | extensions, user content | ||
Comments | 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. | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.action.modifierExtension | |||
Short | Extensions that cannot be ignored even if unrecognized | ||
Definition | 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 manageable, 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). | ||
Cardinality | 0..* | ||
Type | Extension | ||
Modifier | True | ||
Summary | True | ||
Alias | extensions, user content, modifiers | ||
Requirements | 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. | ||
Comments | 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. | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.action.doNotPerform | |||
Short | True if the term prohibits the action | ||
Definition | True if the term prohibits the action. | ||
Cardinality | 0..1 | ||
Type | boolean | ||
Modifier | True | ||
Constraints |
| ||
Contract.term.action.type | |||
Short | 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 | Detailed codes for the contract action. | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.action.subject | |||
Short | Entity of the action | ||
Definition | Entity of the action. | ||
Cardinality | 0..* | ||
Type | BackboneElement | ||
Constraints |
| ||
Contract.term.action.subject.id | |||
Short | Unique id for inter-element referencing | ||
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
Cardinality | 0..1 | ||
Type | string | ||
Mappings |
| ||
Contract.term.action.subject.extension | |||
Short | Additional content defined by implementations | ||
Definition | 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 manageable, 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. | ||
Cardinality | 0..* | ||
Type | Extension | ||
Alias | extensions, user content | ||
Comments | 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. | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.action.subject.modifierExtension | |||
Short | Extensions that cannot be ignored even if unrecognized | ||
Definition | 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 manageable, 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). | ||
Cardinality | 0..* | ||
Type | Extension | ||
Modifier | True | ||
Summary | True | ||
Alias | extensions, user content, modifiers | ||
Requirements | 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. | ||
Comments | 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. | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.action.subject.reference | |||
Short | 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) | ||
Constraints |
| ||
Contract.term.action.subject.role | |||
Short | Role type of the agent | ||
Definition | Role type of agent assigned roles in this Contract. | ||
Cardinality | 0..1 | ||
Type | CodeableConcept | ||
Binding | Detailed codes for the contract actor role. | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.action.intent | |||
Short | Purpose for the Contract Term Action | ||
Definition | Reason or purpose for the action stipulated by this Contract Provision. | ||
Cardinality | 1..1 | ||
Type | CodeableConcept | ||
Binding | Detailed codes for the contract action reason. | ||
Constraints |
| ||
Mappings |
| ||
Contract.term.action.linkId | |||
Short | 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 | ||
Constraints |
| ||
Contract.term.action.status | |||
Short | State of the action | ||
Definition | Current state of the term action. | ||
Cardinality | 1..1 | ||
Type | CodeableConcept | ||
Binding | Codes for the status of an term action. | ||
Constraints |
| ||
Contract.term.action.context | |||
Short | Episode associated with action | ||
Definition | Encounter or Episode with primary association to specified term activity. | ||
Cardinality | 0..1 | ||
Type | Reference(Encounter | EpisodeOfCare) | ||
Constraints |
| ||
Contract.term.action.contextLinkId | |||
Short | 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 | ||
Constraints |
| ||
Contract.term.action.occurrence[x] | |||
Short | When action happens | ||
Definition | When action happens. | ||
Cardinality | 0..1 | ||
Type | dateTime, Period, Timing | ||
Constraints |
| ||
Contract.term.action.requester | |||
Short | 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) | ||
Constraints |
| ||
Contract.term.action.requesterLinkId | |||
Short | 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 | ||
Constraints |
| ||
Contract.term.action.performerType | |||
Short | 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 | Codes for the types of action perfomer. | ||
Constraints |
| ||
Contract.term.action.performerRole | |||
Short | 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 | Codes for the role of the action performer. | ||
Constraints |
| ||
Contract.term.action.performer | |||
Short | 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) | ||
Constraints |
| ||
Contract.term.action.performerLinkId | |||
Short | 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 | ||
Constraints |
| ||
Contract.term.action.reasonCode | |||
Short | Why is action (not) needed? | ||
Definition | Rationale for the action to be performed or not performed. Describes why the action is permitted or prohibited. | ||
Cardinality | 0..* | ||
Type | CodeableConcept | ||
Binding | Detailed codes for the contract action reason. | ||
Constraints |
| ||
Contract.term.action.reasonReference | |||
Short | Why is action (not) needed? | ||
Definition | Indicates another resource whose existence justifies permitting or not permitting this action. | ||
Cardinality | 0..* | ||
Type | Reference(Condition | Observation | DiagnosticReport | DocumentReference | Questionnaire | QuestionnaireResponse) | ||
Constraints |
| ||
Contract.term.action.reason | |||
Short | Why action is to be performed | ||
Definition | Describes why the action is to be performed or not performed in textual form. | ||
Cardinality | 0..* | ||
Type | string | ||
Constraints |
| ||
Contract.term.action.reasonLinkId | |||
Short | 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 | ||
Constraints |
| ||
Contract.term.action.note | |||
Short | Comments about the action | ||
Definition | Comments made about the term action made by the requester, performer, subject or other participants. | ||
Cardinality | 0..* | ||
Type | Annotation | ||
Constraints |
| ||
Contract.term.action.securityLabelNumber | |||
Short | Action restriction numbers | ||
Definition | Security labels that protects the action. | ||
Cardinality | 0..* | ||
Type | unsignedInt | ||
Constraints |
| ||
Contract.term.group | |||
Short | Nested Contract Term Group | ||
Definition | Nested group of Contract Provisions. | ||
Cardinality | 0..* | ||
Type | see (term) | ||
Constraints |
| ||
Mappings |
| ||
Contract.supportingInfo | |||
Short | 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) | ||
Constraints |
| ||
Contract.relevantHistory | |||
Short | 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 Provence.entity indicates the target that was changed in the update. http://build.fhir.org/provenance-definitions.html#Provenance.entity. | ||
Cardinality | 0..* | ||
Type | Reference(Provenance) | ||
Constraints |
| ||
Contract.signer | |||
Short | 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. | ||
Cardinality | 0..* | ||
Type | BackboneElement | ||
Requirements | The Contract.signer applies a signature to the Contract.binding referenced resource, which is the documentation that is the legal "source of truth". The Contract.signer may delegate, such as a legally recognized personal representative, or have a delegate assigned e.g., by a court of law, to actually sign the Contract, such as a trustee in the case of incompetence. | ||
Comments | Signers who are principal parties to the contract are bound by the Contract.activity related to the Contract.topic, and the Contract.term(s), which either extend or restrict the overall action on the topic by, for example, stipulating specific policies or obligations constraining actions, action reason, or agents with respect to some or all of the topic. For example, specifying how policies or obligations shall constrain actions and action reasons permitted or denied on all or a subset of the Contract.topic (e.g., all or a portion of property being transferred by the contract), agents (e.g., who can resell, assign interests, or alter the property being transferred by the contract), actions, and action reasons; or with respect to Contract.terms, stipulating, extending, or limiting the Contract.period of applicability or valuation of items under consideration. | ||
Constraints |
| ||
Mappings |
| ||
Contract.signer.id | |||
Short | Unique id for inter-element referencing | ||
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
Cardinality | 0..1 | ||
Type | string | ||
Mappings |
| ||
Contract.signer.extension | |||
Short | Additional content defined by implementations | ||
Definition | 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 manageable, 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. | ||
Cardinality | 0..* | ||
Type | Extension | ||
Alias | extensions, user content | ||
Comments | 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. | ||
Constraints |
| ||
Mappings |
| ||
Contract.signer.modifierExtension | |||
Short | Extensions that cannot be ignored even if unrecognized | ||
Definition | 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 manageable, 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). | ||
Cardinality | 0..* | ||
Type | Extension | ||
Modifier | True | ||
Summary | True | ||
Alias | extensions, user content, modifiers | ||
Requirements | 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. | ||
Comments | 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. | ||
Constraints |
| ||
Mappings |
| ||
Contract.signer.type | |||
Short | Contract Signatory Role | ||
Definition | Role of this Contract signer, e.g. notary, grantee. | ||
Cardinality | 1..1 | ||
Type | Coding | ||
Binding | List of parties who may be signing. | ||
Constraints |
| ||
Mappings |
| ||
Contract.signer.party | |||
Short | Contract Signatory Party | ||
Definition | Party which is a signator to this Contract. | ||
Cardinality | 1..1 | ||
Type | Reference(Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | ||
Constraints |
| ||
Mappings |
| ||
Contract.signer.signature | |||
Short | Contract Documentation Signature | ||
Definition | Legally binding Contract DSIG signature contents in Base64. | ||
Cardinality | 1..* | ||
Type | Signature | ||
Constraints |
| ||
Mappings |
| ||
Contract.friendly | |||
Short | 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 | ||
Constraints |
| ||
Mappings |
| ||
Contract.friendly.id | |||
Short | Unique id for inter-element referencing | ||
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
Cardinality | 0..1 | ||
Type | string | ||
Mappings |
| ||
Contract.friendly.extension | |||
Short | Additional content defined by implementations | ||
Definition | 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 manageable, 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. | ||
Cardinality | 0..* | ||
Type | Extension | ||
Alias | extensions, user content | ||
Comments | 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. | ||
Constraints |
| ||
Mappings |
| ||
Contract.friendly.modifierExtension | |||
Short | Extensions that cannot be ignored even if unrecognized | ||
Definition | 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 manageable, 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). | ||
Cardinality | 0..* | ||
Type | Extension | ||
Modifier | True | ||
Summary | True | ||
Alias | extensions, user content, modifiers | ||
Requirements | 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. | ||
Comments | 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. | ||
Constraints |
| ||
Mappings |
| ||
Contract.friendly.content[x] | |||
Short | 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) | ||
Constraints |
| ||
Mappings |
| ||
Contract.legal | |||
Short | URL to website containing the contract | ||
Definition | List of Legal expressions or representations of this Contract. | ||
Cardinality | 0..1 | ||
Type | BackboneElement | ||
Must Support | True | ||
Constraints |
| ||
Mappings |
| ||
Contract.legal.id | |||
Short | Unique id for inter-element referencing | ||
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
Cardinality | 0..1 | ||
Type | string | ||
Mappings |
| ||
Contract.legal.extension | |||
Short | Additional content defined by implementations | ||
Definition | 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 manageable, 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. | ||
Cardinality | 0..* | ||
Type | Extension | ||
Alias | extensions, user content | ||
Comments | 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. | ||
Constraints |
| ||
Mappings |
| ||
Contract.legal.modifierExtension | |||
Short | Extensions that cannot be ignored even if unrecognized | ||
Definition | 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 manageable, 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). | ||
Cardinality | 0..* | ||
Type | Extension | ||
Modifier | True | ||
Summary | True | ||
Alias | extensions, user content, modifiers | ||
Requirements | 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. | ||
Comments | 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. | ||
Constraints |
| ||
Mappings |
| ||
Contract.legal.content[x] | |||
Short | Contract Legal Text | ||
Definition | Contract legal text in human renderable form. | ||
Cardinality | 1..1 | ||
Type | Attachment, Reference(Composition | DocumentReference | QuestionnaireResponse) | ||
Slicing | Unordered, Open, by $this(Type) | ||
Constraints |
| ||
Mappings |
| ||
Contract.legal.content[x]:contentAttachment | |||
Short | Contract Legal Text | ||
Definition | Contract legal text in human renderable form. | ||
Cardinality | 1..1 | ||
Type | Attachment | ||
Must Support | True | ||
Constraints |
| ||
Mappings |
| ||
Contract.legal.content[x]:contentAttachment.id | |||
Short | Unique id for inter-element referencing | ||
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
Cardinality | 0..1 | ||
Type | string | ||
Mappings |
| ||
Contract.legal.content[x]:contentAttachment.extension | |||
Short | Additional content defined by implementations | ||
Definition | 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 manageable, 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. | ||
Cardinality | 0..* | ||
Type | Extension | ||
Alias | extensions, user content | ||
Comments | 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. | ||
Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
Constraints |
| ||
Mappings |
| ||
Contract.legal.content[x]:contentAttachment.contentType | |||
Short | Mime type of the content, with charset etc. | ||
Definition | Identifies the type of the data in the attachment and allows a method to be chosen to interpret or render the data. Includes mime type parameters such as charset where appropriate. | ||
Cardinality | 0..1 | ||
Type | code | ||
Binding | The mime type of an attachment. Any valid mime type is allowed. | ||
Summary | True | ||
Requirements | Processors of the data need to be able to know how to interpret the data. | ||
Constraints |
| ||
Examples | Generaltext/plain; charset=UTF-8, image/png | ||
Mappings |
| ||
Contract.legal.content[x]:contentAttachment.language | |||
Short | Human language of the content (BCP-47) | ||
Definition | The human language of the content. The value can be any valid value according to BCP 47. | ||
Cardinality | 0..1 | ||
Type | code | ||
Binding | A human language.
| ||
Summary | True | ||
Requirements | Users need to be able to choose between the languages in a set of attachments. | ||
Constraints |
| ||
Examples | Generalen-AU | ||
Mappings |
| ||
Contract.legal.content[x]:contentAttachment.data | |||
Short | Data inline, base64ed | ||
Definition | The actual data of the attachment - a sequence of bytes, base64 encoded. | ||
Cardinality | 0..1 | ||
Type | base64Binary | ||
Requirements | The data needs to able to be transmitted inline. | ||
Comments | The base64-encoded data SHALL be expressed in the same character set as the base resource XML or JSON. | ||
Constraints |
| ||
Mappings |
| ||
Contract.legal.content[x]:contentAttachment.url | |||
Short | Uri where the data can be found | ||
Definition | A location where the data can be accessed. | ||
Cardinality | 1..1 | ||
Type | url | ||
Must Support | True | ||
Summary | True | ||
Requirements | The data needs to be transmitted by reference. | ||
Comments | If both data and url are provided, the url SHALL point to the same content as the data contains. Urls may be relative references or may reference transient locations such as a wrapping envelope using cid: though this has ramifications for using signatures. Relative URLs are interpreted relative to the service url, like a resource reference, rather than relative to the resource itself. If a URL is provided, it SHALL resolve to actual data. | ||
Constraints |
| ||
Examples | Generalhttp://www.acme.com/logo-small.png | ||
Mappings |
| ||
Contract.legal.content[x]:contentAttachment.size | |||
Short | Number of bytes of content (if url provided) | ||
Definition | The number of bytes of data that make up this attachment (before base64 encoding, if that is done). | ||
Cardinality | 0..1 | ||
Type | unsignedInt | ||
Summary | True | ||
Requirements | Representing the size allows applications to determine whether they should fetch the content automatically in advance, or refuse to fetch it at all. | ||
Comments | The number of bytes is redundant if the data is provided as a base64binary, but is useful if the data is provided as a url reference. | ||
Constraints |
| ||
Mappings |
| ||
Contract.legal.content[x]:contentAttachment.hash | |||
Short | Hash of the data (sha-1, base64ed) | ||
Definition | The calculated hash of the data using SHA-1. Represented using base64. | ||
Cardinality | 0..1 | ||
Type | base64Binary | ||
Summary | True | ||
Requirements | Included so that applications can verify that the contents of a location have not changed due to technical failures (e.g., storage rot, transport glitch, incorrect version). | ||
Comments | The hash is calculated on the data prior to base64 encoding, if the data is based64 encoded. The hash is not intended to support digital signatures. Where protection against malicious threats a digital signature should be considered, see Provenance.signature for mechanism to protect a resource with a digital signature. | ||
Constraints |
| ||
Mappings |
| ||
Contract.legal.content[x]:contentAttachment.title | |||
Short | Label to display in place of the data | ||
Definition | A label or set of text to display in place of the data. | ||
Cardinality | 0..1 | ||
Type | string | ||
Summary | True | ||
Requirements | Applications need a label to display to a human user in place of the actual data if the data cannot be rendered or perceived by the viewer. | ||
Constraints |
| ||
Examples | GeneralOfficial Corporate Logo | ||
Mappings |
| ||
Contract.legal.content[x]:contentAttachment.creation | |||
Short | Date attachment was first created | ||
Definition | The date that the attachment was first created. | ||
Cardinality | 0..1 | ||
Type | dateTime | ||
Summary | True | ||
Requirements | This is often tracked as an integrity issue for use of the attachment. | ||
Constraints |
| ||
Mappings |
| ||
Contract.rule | |||
Short | Computable Contract Language | ||
Definition | List of Computable Policy Rule Language Representations of this Contract. | ||
Cardinality | 0..* | ||
Type | BackboneElement | ||
Constraints |
| ||
Mappings |
| ||
Contract.rule.id | |||
Short | Unique id for inter-element referencing | ||
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
Cardinality | 0..1 | ||
Type | string | ||
Mappings |
| ||
Contract.rule.extension | |||
Short | Additional content defined by implementations | ||
Definition | 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 manageable, 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. | ||
Cardinality | 0..* | ||
Type | Extension | ||
Alias | extensions, user content | ||
Comments | 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. | ||
Constraints |
| ||
Mappings |
| ||
Contract.rule.modifierExtension | |||
Short | Extensions that cannot be ignored even if unrecognized | ||
Definition | 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 manageable, 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). | ||
Cardinality | 0..* | ||
Type | Extension | ||
Modifier | True | ||
Summary | True | ||
Alias | extensions, user content, modifiers | ||
Requirements | 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. | ||
Comments | 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. | ||
Constraints |
| ||
Mappings |
| ||
Contract.rule.content[x] | |||
Short | Computable Contract Rules | ||
Definition | Computable Contract conveyed using a policy rule language (e.g. XACML, DKAL, SecPal). | ||
Cardinality | 1..1 | ||
Type | Attachment, Reference(DocumentReference) | ||
Constraints |
| ||
Mappings |
| ||
Contract.legallyBinding[x] | |||
Short | 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) | ||
Constraints |
| ||
Mappings |
|
Details
Validation rules
Rule ID | Element | Description | Expression | Error | Severity |
---|---|---|---|---|---|
applies.start, applies.end | The format is YYYY-MM-DD{Thh:mm:ss+zz:zz}, e.g. 1905-08-23 or 2015-02-07T13:28:17-05:00. If hours and minutes are specified, a timezone offset SHALL be populated. The time "24:00" is not allowed. Reference: HL7 dateTime datatype definition | ||||
per-1 | applies | If present, start SHALL have a lower value than end | start.hasValue().not() or end.hasValue().not() or (start <= end) |
Error |
Supported operations
HTTP methods
Operation | Supported | Comment |
---|---|---|
Search (GET, POST) | yes | Only GET |
Insert (POST) | no | See Bundle - HVOContractTransactionBundle for creating HVOContracts |
Update (PUT) | no | See Bundle - HVOContractTransactionBundle for updating HVOContracts |
Delete (DEL) | no | |
Operation (GET, POST) | no |
Query operations
Supported Queries
GET .../Contract?[parameters]
Parameter options:
_id=[LogicalId]
returns the Contract with the Logical IDterm-text:contains=[Description]
returns a Bundle of Contracts which term-texts contain the supplied Description
Include & reverse includes
Supported usage of include and revinclude. This kind of search returns a bundle of both the base resource and the related resources specified in the parameter.
GET .../Contract?[parameters]&[includes]
Include options that can be chained using "&":
_include=Contract:subject
includes the related HVOOrganizationAffiliations&_include:iterate=OrganizationAffiliation:service
includes the HVOServices related to the HVOOrganizationAffiliation&_include:iterate=HealthcareService:organization
includes the HVOOrganizationalUnit which provides the HVOService
&_include:iterate=OrganizationAffiliation:primary-organization
includes the HVOOrganization which assigned the tasks of the HVOOrganizationAffiliation&_include:iterate=OrganizationAffiliation:participating-organization
includes the HVOOrganization which have been assigned the tasks of the HVOOrganizationAffiliation
Search parameters
Parameter | Description | Comment |
---|---|---|
_id | Logical ID (UUID) of a Contract. | |
_include | Subject resource to include in the response. | See HL7 Include other resources for more information. |
_revinclude | Related resources of the specified type to include in the response. | See HL7 Include other resources for more information. |
term-text:contains | Search query of the description of a Contract |