Generated Narrative: StructureDefinition profile-Contract Name Flags Card. Type Description & Constraints Contract 0..* Contract Legal Agreement #xD; topic #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:topic 0..1 CodeableConcept R4: Focus of contract interest additional types URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.topic #xD; agent #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:url 0..1 uri R4: Basal definition (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.url #xD; extension:version 0..1 string R4: Business edition (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.version #xD; extension:legalState 0..1 CodeableConcept R4: Negotiation status (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.legalState Binding: R4ContractLegalstateForR3 (0.1.0) (extensible): Detailed codes for the legal state of a contract. #xD; extension:instantiatesCanonical 0..1 Reference(Cross-version Profile for R4.Contract for use in FHIR STU3(0.1.0) | Contract) R4: Source Contract Definition (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.instantiatesCanonical #xD; extension:instantiatesUri 0..1 uri R4: External Contract Definition (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.instantiatesUri #xD; extension:expirationType 0..1 CodeableConcept R4: Contract cessation cause (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.expirationType Binding: R4ContractExpirationTypeForR3 (0.1.0) (example): Codes for the Cessation of Contracts. #xD; extension:site 0..* Reference(Cross-version Profile for R4.Location for use in FHIR STU3(0.1.0) | Location) R4: Specific Location (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.site #xD; extension:name 0..1 string R4: Computer friendly designation (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.name #xD; extension:title 0..1 string R4: Human Friendly name (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.title #xD; extension:subtitle 0..1 string R4: Subordinate Friendly name (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.subtitle #xD; extension:alias 0..* string R4: Acronym or short name (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.alias #xD; extension:scope 0..1 CodeableConcept R4: Range of Legal Concerns (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.scope Binding: R4ContractScopeForR3 (0.1.0) (example): Codes for the range of legal concerns. #xD; extension:contentDefinition 0..1 (Complex) R4: Contract precursor content (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.contentDefinition #xD; extension:supportingInfo 0..* Reference(Cross-version Profile for R4.Resource for use in FHIR STU3(0.1.0) | Resource) R4: Extra Information (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.supportingInfo #xD; extension:relevantHistory 0..* Reference(Cross-version Profile for R4.Provenance for use in FHIR STU3(0.1.0) | Provenance) R4: Key event in Contract History (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.relevantHistory #xD; extension:legallyBinding 0..1 Attachment, Reference(Cross-version Profile for R4.Composition for use in FHIR STU3(0.1.0) | Composition | Cross-version Profile for R4.DocumentReference for use in FHIR STU3(0.1.0) | DocumentReference | Cross-version Profile for R4.QuestionnaireResponse for use in FHIR STU3(0.1.0) | QuestionnaireResponse | Cross-version Profile for R4.Contract for use in FHIR STU3(0.1.0) | Contract) R4: Binding Contract (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.legallyBinding #xD; actor #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:author 0..1 ?gen-e1? [CanonicalType[http://hl7.org/fhir/StructureDefinition/alternate-reference]] R4: Source of Contract URL: http://hl7.org/fhir/StructureDefinition/alternate-reference #xD; signer #xD; party #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:party 0..1 ?gen-e1? [CanonicalType[http://hl7.org/fhir/StructureDefinition/alternate-reference]] R4: party URL: http://hl7.org/fhir/StructureDefinition/alternate-reference #xD; term #xD; Slices for extension 1..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:offer 1..1 (Complex) R4: Context of the Contract term (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.term.offer #xD; extension:answer 0..* (Complex) R4: Response to offer text (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.term.offer.answer #xD; extension:asset 0..* (Complex) R4: Contract Term Asset List (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.term.asset #xD; extension:answer 0..* (Complex) R4: Response to assets (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.term.offer.answer #xD; topic #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:topic 0..1 CodeableConcept R4: Term Concern additional types URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.term.topic #xD; action #xD; Slices for modifierExtension 0..* Slice: Unordered, Open by value:url #xD; modifierExtension:doNotPerform 0..1 boolean R4: True if the term prohibits the action (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.term.action.doNotPerform #xD; Slices for extension 3..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:type 1..1 CodeableConcept R4: Type or form of the action (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.term.action.type Binding: Contract Action Codes (example): Detailed codes for the contract action. #xD; extension:subject 0..* (Complex) R4: Entity of the action (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.term.action.subject #xD; extension:intent 1..1 CodeableConcept R4: Purpose for the Contract Term Action (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.term.action.intent Binding: R4V3PurposeOfUseForR3 (0.1.0) (example): Detailed codes for the contract action reason. #xD; extension:linkId 0..* string R4: Pointer to specific item (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.term.action.linkId #xD; extension:status 1..1 CodeableConcept R4: State of the action (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.term.action.status Binding: R4ContractActionstatusForR3 (0.1.0) (example): Codes for the status of an term action. #xD; extension:context 0..1 Reference(Cross-version Profile for R4.Encounter for use in FHIR STU3(0.1.0) | Encounter | Cross-version Profile for R4.EpisodeOfCare for use in FHIR STU3(0.1.0) | EpisodeOfCare) R4: Episode associated with action (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.term.action.context #xD; extension:contextLinkId 0..* string R4: Pointer to specific item (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.term.action.contextLinkId #xD; extension:occurrence 0..1 dateTime, Period, Timing R4: When action happens (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.term.action.occurrence #xD; extension:requester 0..* Reference(Cross-version Profile for R4.Patient for use in FHIR STU3(0.1.0) | Patient | Cross-version Profile for R4.RelatedPerson for use in FHIR STU3(0.1.0) | RelatedPerson | Cross-version Profile for R4.Practitioner for use in FHIR STU3(0.1.0) | Practitioner | Cross-version Profile for R4.PractitionerRole for use in FHIR STU3(0.1.0) | PractitionerRole | Cross-version Profile for R4.Device for use in FHIR STU3(0.1.0) | Device | Cross-version Profile for R4.Group for use in FHIR STU3(0.1.0) | Group | Cross-version Profile for R4.Organization for use in FHIR STU3(0.1.0) | Organization) R4: Who asked for action (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.term.action.requester #xD; extension:requesterLinkId 0..* string R4: Pointer to specific item (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.term.action.requesterLinkId #xD; extension:performerType 0..* CodeableConcept R4: Kind of service performer (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.term.action.performerType Binding: R4ProvenanceAgentTypeForR3 (0.1.0) (example): Codes for the types of action perfomer. #xD; extension:performerRole 0..1 CodeableConcept R4: Competency of the performer (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.term.action.performerRole Binding: R4ProvenanceAgentRoleForR3 (0.1.0) (example): Codes for the role of the action performer. #xD; extension:performer 0..1 Reference(Cross-version Profile for R4.RelatedPerson for use in FHIR STU3(0.1.0) | RelatedPerson | Cross-version Profile for R4.Patient for use in FHIR STU3(0.1.0) | Patient | Cross-version Profile for R4.Practitioner for use in FHIR STU3(0.1.0) | Practitioner | Cross-version Profile for R4.PractitionerRole for use in FHIR STU3(0.1.0) | PractitionerRole | Cross-version Profile for R4.CareTeam for use in FHIR STU3(0.1.0) | CareTeam | Cross-version Profile for R4.Device for use in FHIR STU3(0.1.0) | Device | Cross-version Profile for R4.Substance for use in FHIR STU3(0.1.0) | Substance | Cross-version Profile for R4.Organization for use in FHIR STU3(0.1.0) | Organization | Cross-version Profile for R4.Location for use in FHIR STU3(0.1.0) | Location) R4: Actor that wil execute (or not) the action (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.term.action.performer #xD; extension:performerLinkId 0..* string R4: Pointer to specific item (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.term.action.performerLinkId #xD; extension:reasonCode 0..* CodeableConcept R4: Why is action (not) needed? (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.term.action.reasonCode Binding: R4V3PurposeOfUseForR3 (0.1.0) (example): Detailed codes for the contract action reason. #xD; extension:reasonReference 0..* Reference(Cross-version Profile for R4.Condition for use in FHIR STU3(0.1.0) | Condition | Cross-version Profile for R4.Observation for use in FHIR STU3(0.1.0) | Observation | Cross-version Profile for R4.DiagnosticReport for use in FHIR STU3(0.1.0) | DiagnosticReport | Cross-version Profile for R4.DocumentReference for use in FHIR STU3(0.1.0) | DocumentReference | Cross-version Profile for R4.Questionnaire for use in FHIR STU3(0.1.0) | Questionnaire | Cross-version Profile for R4.QuestionnaireResponse for use in FHIR STU3(0.1.0) | QuestionnaireResponse) R4: Why is action (not) needed? (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.term.action.reasonReference #xD; extension:reason 0..* string R4: Why action is to be performed (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.term.action.reason #xD; extension:reasonLinkId 0..* string R4: Pointer to specific item (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.term.action.reasonLinkId #xD; extension:note 0..* Annotation R4: Comments about the action (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.term.action.note #xD; extension:securityLabelNumber 0..* unsignedInt R4: Action restriction numbers (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.term.action.securityLabelNumber #xD; securityLabel #xD; Slices for extension 1..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:number 0..* unsignedInt R4: Link to Security Labels (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.term.securityLabel.number #xD; extension:classification 1..1 Coding R4: Confidentiality Protection (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.term.securityLabel.classification Binding: R4ContractSecurityClassificationForR3 (0.1.0) (example): Codes for confidentiality protection. #xD; extension:category 0..* Coding R4: Applicable Policy (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.term.securityLabel.category Binding: R4ContractSecurityCategoryForR3 (0.1.0) (example): Codes for policy category. #xD; extension:control 0..* Coding R4: Handling Instructions (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-Contract.term.securityLabel.control Binding: R4ContractSecurityControlForR3 (0.1.0) (example): Codes for handling instructions. #xD; Documentation for this format
Cross-version Profile for R4.Contract for use in FHIR STU3
This cross-version profile allows R4 Contract content to be represented via FHIR STU3 Contract resources.
A formal agreement between parties regarding the conduct of business, exchange of information or other matters.
If the resource is contained in another resource, it SHALL NOT contain nested Resources
not(parent::f:contained and f:contained)
If the resource is contained in another resource, it SHALL NOT contain any narrative
If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
not(exists(f:contained/*/f:meta/f:versionId)) and not(exists(f:contained/*/f:meta/f:lastUpdated))
If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource
contained.where(('#'+id in %resource.descendants().reference).not()).empty()
not(exists(for $id in f:contained/*/@id return $id[not(ancestor::f:contained/parent::*/descendant::f:reference/@value=concat('#', $id))]))
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource.
A set of rules under which this content was created
A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.
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. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.
The base language in which the resource is written.
Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
Text summary of the resource, for human interpretation
A human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.
Contained resources do not have 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 in formation is added later.
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.
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.
Additional Content defined by implementations
May be used to represent additional information that is not part of the basic definition of the resource. In order 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.
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.
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. Usually modifier elements provide negation or qualification. In order 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.
amended | appended | cancelled | disputed | entered-in-error | executable | executed | negotiable | offered | policy | rejected | renewed | revoked | resolved | terminated
This element is labeled as a modifier because the status contains codes that mark the contract as not currently valid or active.
A code specifying the state of the resource instance.
Act.availabilityTime. Definition: A time expression specifying when an Observation, Procedure, or other Act occurs, or, depending on the mood, is supposed to occur, scheduled to occur, etc. The activityTime includes the times of component actions (such as preparation and clean-up). For Procedures and SubstanceAdministrations, the activityTime can provide a needed administrative function by providing a more inclusive time to be anticipated in scheduling. UsageNotes:The activityTime is primarily of administrative rather than clinical use. The clinically relevant time is the effectiveTime. When an observation of a prior symptom is made, the activityTime describes the time the observation is made, as opposed to effectiveTime which is the time the symptom is reported to have occurred. Thus the activityTime may be entirely different from the effectiveTime of the same Act. However, even apart from clinical use cases, designers should first consider effectiveTime as the primary relevant time for an Act. ActivityTime indicates when an Act occurs, not when it is recorded.
Relevant time or time-period when this Contract is applicable.
Act.effectiveTime Definition: The clinically or operationally relevant time of an act, exclusive of administrative activity.
The target entity impacted by or of interest to parties to the agreement.
The Contract.subject is an entity that has some role with respect to the Contract.topic and Contract.topic.term, which is of focal interest to the parties to the contract and likely impacted in a significant way by the Contract.action/Contract.action.reason and the Contract.term.action/Contract.action.reason. In many cases, the Contract.subject is a Contract.signer if the subject is an adult; has a legal interest in the contract; and incompetent to participate in the contract agreement.
The matter of concern in the context of this agreement.
The Contract.topic may be an application for or offer of a policy or service (e.g., uri to a consent directive form or a health insurance policy), which becomes the Contract once accepted by both the grantor and grantee. The Contract Resource may function simply as the computable representation of the executed contract, which may be the attached to the Contract Resource as the “binding” or as the “friendly” electronic form. For example, a Contract Resource may be automatically populated with the values expressed in a related QuestionnaireResponse. However, the Contract Resource may be considered the legally binding contract if it is the only “executed” form of this contract, and includes the signatures as *The Contract Resource may function as the computable representation of an application or offer in a pre-executed Contract if the grantor has not entered any values. In this case, it is populated with values in a “legal” form of the application or offer or by the values in an associated Questionnaire. If the grantor has filled in the legal form or the associated Questionnaire Response, then these values are used to populate a pre-executed Contract Resource. If the Contract.topic is considered an application or offer, then the policy is often required to be attached as the “legal” basis for the application to ensure “informed consent” to the contract, and that any discrepancy between the application and the policy are interpreted against the policy. Implementers should check organizational and jurisdictional policies to determine the relationship among multiple representations of a contract pre- and post-execution.
In the context of a contract, the topic is the matter under consideration in regards to which specific rights, privileges, obligations, restrictions, and prohibitions are binding on any grantor and grantee parties upon the execution of the contract. Given the wide range of contract topics, implementers need to be cognizant of the business use case for which they are designing a FHIR Contract, and narrowly specify the topic being represented with respect to the Contract.type and any specializing Contract.subtype. The same topic, e.g., an asset such as a good or service, such as a real property, medical supply, insurance, information, a procedure or employment, or a manner of conduct, such adherence to a privacy, trust, or security policy, may be the topic of multiple types of contracts. One way to determine the Contract.topic is to answer the question: “What is the object of negotiation?” Answer: The Contract.topic, which may be described with more detail in the [0..*]Contract.valuedItem @ [0..1] Contract.valuedItem.entity[x] Definition: Specific type of Contract Valued Item that may be priced. CodeableConcept|Reference(Any) Contract.topic is “the what” that a grantor is exchanging with a grantee in return for some benefit. Contract.topic is “the what” to which any Contract.action is being applied for any stipulated Contract.action.reason. AContract.topic is “the what” governed by the execution of the contract to which any party’s rights, privileges, obligations, restrictions, and prohibitions apply.
Includes many ActClass, ActCode, RoleClass, RoleCode, EntityClass, EntityCode, ParticipationType codes from HL7 concept domains and code systems. For example, RoleCode: HLD (held entity) Description: Entity that is currently in the possession of a holder (scoper), who holds, or uses it, usually based on some agreement with the owner. MANU (manufactured product) Description: Scoped by the manufacturer. OWN (owned entity) Description: An Entity (player) for which someone (scoper) is granted by law the right to call the material (player) his own. This entitles the scoper to make decisions about the disposition of that material. WRTE (warranted product) Description: A role a product plays when a guarantee is given to the purchaser by the seller (scoping entity) stating that the product is reliable and free from known defects and that the seller will repair or replace defective parts within a given time limit and under certain conditions.
unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
R4: Focus of contract interest additional types
R4: `Contract.topic[x]` additional types (CodeableConcept) additional types from child elements (coding, text)
Element `Contract.topic[x]` is mapped to FHIR STU3 element `Contract.topic` as `RelatedTo`. The mappings for `Contract.topic[x]` do not cover the following types: CodeableConcept. The mappings for `Contract.topic[x]` do not cover the following types based on type expansion: coding, text.
Literal reference, Relative, internal or absolute URL
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
Logical reference, when literal reference is not known
An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
Plain text narrative that identifies the resource in addition to the resource reference.
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
Authority under which this Contract has standing
A formally or informally recognized grouping of people, principals, organizations, or jurisdictions formed for the purpose of achieving some form of collective action such as the promulgation, administration and enforcement of contracts and policies.
Organization Role. CONCEPT DOMAIN: OrganizationEntityType Description: Further classifies entities of EntityClass ORG.
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.
TERR (territory of authority) Description: Relates a place entity (player) as the region over which the scoper (typically an Organization) has certain authority (jurisdiction). For example, the Calgary Regional Health Authority (scoper) has authority over the territory "Region 4 of Alberta" (player) in matters of health. Entity Class = Place? A physical place or site with its containing structure. May be natural or man-made. The geographic position of a place may or may not be constant. CONCEPT DOMAIN: TerritoryEntityType Description: A territorial entity that may be cited as the body over which an agency exercises jurisdiction, or which defines a sphere in which a party has a particular responsibility. CONCEPT DOMAIN: OrganizationEntityType Description: Further classifies entities of EntityClass ORG.
Type of Contract such as an insurance policy, real estate contract, a will, power of attorny, Privacy or Security policy , trust framework agreement, etc.
Maps to multiple ActClass and ActCode Concept Domains and Code Systems such as the following: In the ActClass Concept Domain: ActClassPolicy. In the ActCode Concept Domain: ActContractType, which generalizes ActFinancialContractType, ActCoverageType, ActBillingArrangementType. ActConsentType, which generalizes ActDataConsentType; ActFinancialParticipationConsentType; ActInformationAccessCode; AdvanceBeneficiaryNoticeType. ActPolicyType, which generalizes: ActPrivacyPolicyType, ActSensitivityPrivacyPolicyType, ActSecurityPolicyType. In the ActClass Code System: CNTRCT (contract) Description: An agreement of obligation between two or more parties that is subject to contractual law and enforcement, lwhich generalizes FCNTRCT (financial contract) and COV (coverage). POLICY (policy) - Description: A mandate, regulation, obligation, requirement, rule, or expectation unilaterally imposed by one party on: The activity of another party; the behavior of another party; or the manner in which an act is executed. LEAF CONCEPTS: JURISPOL (jurisdictional policy) Description:A mandate, regulation, obligation, requirement, rule, or expectation unilaterally imposed by a jurisdiction on: The activity of another party; the behavior of another party; or the manner in which an act is executed.Examples:A jurisdictional mandate regarding the prescribing and dispensing of a particular medication. A jurisdictional privacy or security regulation dictating the manner in which personal health information is disclosed. A jurisdictional requirement that certain services or health conditions are reported to a monitoring program, e.g., immunizations, methadone treatment, or cancer registries.ORGPOL (organizational policy)Examples:A clinical or research protocols imposed by a payer, a malpractice insurer, or an institution to which a provider must adhere. A mandate imposed by a denominational institution for a provider to provide or withhold certain information from the patient about treatment options.SCOPOL (scope of practice policy)Description:An ethical or clinical obligation, requirement, rule, or expectation imposed or strongly encouraged by organizations that oversee particular clinical domains or provider certification which define the boundaries within which a provider may practice and which may have legal basis or ramifications.Examples:An ethical obligation for a provider to fully inform a patient about all treatment options. An ethical obligation for a provider not to disclose personal health information that meets certain criteria, e.g., where disclosure might result in harm to the patient or another person. The set of health care services which a provider is credentialed or privileged to provide. STDPOL (standard of practice policy) Examples:A payer may require a prescribing provider to adhere to formulary guidelines. An institution may adopt clinical guidelines and protocols and implement these within its electronic health record and decision support systems. CONS (consent)Description: The Consent class represents informed consents and all similar medico-legal transactions between the patient (or his legal guardian) and the provider. Examples are informed consent for surgical procedures, informed consent for clinical trials, advanced beneficiary notice, against medical advice decline from service, release of information agreement, etc. The details of consents vary. Often an institution has a number of different consent forms for various purposes, including reminding the physician about the topics to mention. Such forms also include patient education material. In electronic medical record communication, consents thus are information-generating acts on their own and need to be managed similar to medical activities. Thus, Consent is modeled as a special class of Act. The "signatures" to the consent document are represented electronically through Participation instances to the consent object. Typically an informed consent has Participation.typeCode of "performer", the healthcare provider informing the patient, and "consenter", the patient or legal guardian. Some consent may associate a witness or a notary public (e.g., living wills, advanced directives). In consents where a healthcare provider is not required (e.g. living will), the performer may be the patient himself or a notary public.
More specific type or specialization of an overarching or more general contract such as auto insurance, home owner insurance, prenupial agreement, Advanced-Directive, or privacy consent.
Examples of Contract or Policy subtypes in ActCodes:_ActCoverageTypeCode Definition: Set of codes indicating the type of insurance policy or program that pays for the cost of benefits provided to covered parties. Generalizes: _ActInsurancePolicyCode; _ActInsuranceTypeCode; ActProgramTypeCode. _ActPolicyType Description:Types of policies that further specify the ActClassPolicy value set. Generalizes: _ActPrivacyPolicy; _ActPrivacyLaw; _InformationSensitivityPolicy; ActTrustPolicyType; SecurityPolicy. _ActInvoiceAdjudicationPaymentGroupCode Description: Codes representing adjustments to a Payment Advice such as retroactive, clawback, garnishee, etc., e.g. RECOV (recovery) Description: Retroactive adjustment such as fee rate adjustment due to contract negotiations.
Maps to multiple ActClass and ActCode Concept Domains and Code Systems.
Reason for action stipulated by this Contract.
Detailed codes for the contract action reason.
Examples from ActReason Concept Domains: ActCoverageReason Description:Codes used to specify reasons or criteria relating to coverage provided under a policy or program. May be used to convey reasons pertaining to coverage contractual provisions, including criteria for eligibility, coverage limitations, coverage maximums, or financial participation required of covered parties. ActInformationPrivacyReason Description: The rationale or purpose for an act relating to the management of personal information, such as disclosing personal tax information for the purpose of complying with a court order. ClinicalResearchObservationReason Definition: Specifies the reason that a test was performed or observation collected in a clinical research study. SafetyInvestigationReportReasonType Description: Possible reasons generating a report providing information developed during the investigation of an adverse event or a product problem. ControlActReason Description: Indicates the motivation, cause or rationale of an Act which results in a trigger event. NonPerformanceReasonCode Description: The reason the action was not performed, e.g. why the medication was not taken. If an action was not performed, it is often clinically important to know why the action was not taken. RefusalReasonCode Description: Identifies why a request to add (or activate) a record is being refused. Examples include the receiving system not able to match the identifier and find that record in the receiving system, having no permission, or a detected issue exists which precludes the requested action. Examples from HL7 ActReason Code System: QUALIMP (quality improvement) Description:Operational activities conducted for the purposes of improving the quality of an activity, product, or service. _PatientProfileQueryReasonCode Description: A collection of concepts identifying why the patient's profile is being queried. _ActInformationManagementReason Description:The rationale or purpose for an act relating to information management, such as archiving information for the purpose of complying with an enterprise data retention policy. _ActInvalidReason (ActInvalidReason) Description: Types of reasons why a substance is invalid for use. _NonPerformanceReasonCode Description: The reason the action wasn't performed, e.g. why the medication was not taken. If an action wasn"t performed, it is often clinically important to know why the action wasn"t taken.
The type of decision made by a grantor with respect to an offer made by a grantee.
ActCode: _ActConsentDirective [abstract term] Description: Specifies the type of agreement between one or more grantor and grantee in which rights and obligations related to one or more shared items of interest are allocated. Usage Note: Such agreements may be considered "consent directives" or "contracts" depending on the context, and are considered closely related or synonymous from a legal perspective.
Content derived from the basal information
The minimal content derived from the basal information source at a specific stage in its lifecycle.
This is an example set of Content Derivative type codes, which represent the minimal content derived from the basal information source.
Maps partially to several v3 codes: ActClass: REG (registration) Description: Represents the act of maintaining information about the registration of its associated registered subject. The subject can be either an Act or a Role, and includes subjects such as lab exam definitions, drug protocol definitions, prescriptions, persons, patients, practitioners, and equipment. The registration may have a unique identifier - separate from the unique identification of the subject - as well as a core set of related participations and act relationships that characterize the registration event and aid in the disposition of the subject information by a receiving system. Observation: VERIF (Verification) Description: An act which describes the process whereby a 'verifying party' validates either the existence of the Role attested to by some Credential or the actual Vetting act and its details. TRFR (transfer) Description: The act of transferring information without the intent of imparting understanding about a topic to the subject that is the recipient or holder of the transferred information where the participation association must be RCV or HLD. _ActDetectedIssueManagementCode [abstract term] Description: Codes dealing with the management of Detected Issue observations. _ActInformationAccessContextCode [abstract term] Description: Concepts conveying the context in which authorization given under jurisdictional law, by organizational policy, or by a patient consent directive permits the collection, access, use or disclosure of specified patient health information. _ActListCode [abstract term]vDescription: Provides codes associated with ActClass value of LIST (working list). RefusalReasonCode [abstract term] Description: Description: Identifies why a request to add (or activate) a record is being refused. Examples include the receiving system not able to match the identifier and find that record in the receiving system, having no permission, or a detected issue exists which precludes the requested action.
Security Labels that define affected resources
A set of security labels that define which resources are controlled by this consent. If more than one label is specified, all resources must have all the specified labels.
Security Labels from the Healthcare Privacy and Security Classification System.
ActCode ObservationType:SECOBS [abstract term] Description: An observation identifying security metadata about an IT resource (data, information object, service, or system capability), which may be used to make access control decisions. Security metadata are used to name security labels. Rationale: According to ISO/TS 22600-3:2009(E) A.9.1.7 SECURITY LABEL MATCHING, Security label matching compares the initiator's clearance to the target's security label. All of the following must be true for authorization to be granted: The security policy identifiers shall be identical. The classification level of the initiator shall be greater than or equal to that of the target (that is, there shall be at least one value in the classification list of the clearance greater than or equal to the classification of the target), and For each security category in the target label, there shall be a security category of the same type in the initiator's clearance and the initiator's classification level shall dominate that of the target. Examples: SecurityObservationType security label fields include: Confidentiality classification; Compartment category; Sensitivity category Security mechanisms used to ensure data integrity or to perform authorized data transformation Indicators of an IT resource completeness, veracity, reliability, trustworthiness, or provenance. Usage Note: SecurityObservationType codes designate security label field types, which are valued with an applicable SecurityObservationValue code as the "security label tag". _SecurityObservationValue [abstract term] Description: Observation values used to indicate security observation metadata.
An actor taking a role in an activity for which it can be assigned some degree of responsibility for the activity taking place.
Several agents may be associated (i.e. has some responsibility for an activity) with an activity and vice-versa. For example, in cases of actions initiated by one user for other users, or in events that involve more than one user, hardware device, software, or system process. However, only one user may be the initiator/requestor for the event.
An agent can be a person, an organization, software, device, or other entities that may be ascribed responsibility.
All FHIR elements must have a @value or children
hasValue() | (children().count() > id.count())
Element `Contract.url` has a context of Contract.agent based on following the parent source element upwards and mapping to `Contract`. Element `Contract.url` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Used in a domain that uses a supplied contract repository.
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])
Element `Contract.version` has a context of Contract.agent based on following the parent source element upwards and mapping to `Contract`. Element `Contract.version` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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].
R4: `Contract.legalState` (new:CodeableConcept)
Element `Contract.legalState` has a context of Contract.agent based on following the parent source element upwards and mapping to `Contract`. Element `Contract.legalState` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4: `Contract.instantiatesCanonical` (new:Reference(Contract))
Element `Contract.instantiatesCanonical` has a context of Contract.agent based on following the parent source element upwards and mapping to `Contract`. Element `Contract.instantiatesCanonical` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4: `Contract.instantiatesUri` (new:uri)
Element `Contract.instantiatesUri` has a context of Contract.agent based on following the parent source element upwards and mapping to `Contract`. Element `Contract.instantiatesUri` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4: `Contract.expirationType` (new:CodeableConcept)
Element `Contract.expirationType` has a context of Contract.agent based on following the parent source element upwards and mapping to `Contract`. Element `Contract.expirationType` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4: `Contract.site` (new:Reference(Location))
Element `Contract.site` has a context of Contract.agent based on following the parent source element upwards and mapping to `Contract`. Element `Contract.site` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `Contract.name` has a context of Contract.agent based on following the parent source element upwards and mapping to `Contract`. Element `Contract.name` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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.
Element `Contract.title` has a context of Contract.agent based on following the parent source element upwards and mapping to `Contract`. Element `Contract.title` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `Contract.subtitle` has a context of Contract.agent based on following the parent source element upwards and mapping to `Contract`. Element `Contract.subtitle` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `Contract.alias` has a context of Contract.agent based on following the parent source element upwards and mapping to `Contract`. Element `Contract.alias` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4: `Contract.scope` (new:CodeableConcept)
Element `Contract.scope` has a context of Contract.agent based on following the parent source element upwards and mapping to `Contract`. Element `Contract.scope` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4: `Contract.contentDefinition` (new:BackboneElement)
Element `Contract.contentDefinition` has a context of Contract.agent based on following the parent source element upwards and mapping to `Contract`. Element `Contract.contentDefinition` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4: `Contract.supportingInfo` (new:Reference(Resource))
Element `Contract.supportingInfo` has a context of Contract.agent based on following the parent source element upwards and mapping to `Contract`. Element `Contract.supportingInfo` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4: `Contract.relevantHistory` (new:Reference(Provenance))
Element `Contract.relevantHistory` has a context of Contract.agent based on following the parent source element upwards and mapping to `Contract`. Element `Contract.relevantHistory` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4: `Contract.legallyBinding[x]` (new:Attachment, Reference(Composition,DocumentReference,QuestionnaireResponse,Contract))
Element `Contract.legallyBinding[x]` has a context of Contract.agent based on following the parent source element upwards and mapping to `Contract`. Element `Contract.legallyBinding[x]` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order 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.
Who or what parties are assigned roles in this Contract.
Element `Contract.author` is mapped to FHIR STU3 element `Contract.agent.actor` as `RelatedTo`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R4 element `Contract.author` with unmapped reference targets: PractitionerRole.
Role type of agent assigned roles in this Contract.
Detailed codes for the contract actor role.
RoleClass, RoleCode, ParticipationType, ParticipationFunction codes
Parties with legal standing in the Contract, including the principal parties, the grantor(s) and grantee(s), which are any person or organization bound by the contract, and any ancillary parties, which facilitate the execution of the contract such as a notary or witness.
Signers who are principal parties to the contract are bound by the Contract.activity related to the Contract.topic, and the Contract.term(s), which either extend or restrict the overall action on the topic by, for example, stipulating specific policies or obligations constraining actions, action reason, or agents with respect to some or all of the topic. For example, specifying how policies or obligations shall constrain actions and action reasons permitted or denied on all or a subset of the Contract.topic (e.g., all or a portion of property being transferred by the contract), agents (e.g., who can resell, assign interests, or alter the property being transferred by the contract), actions, and action reasons; or with respect to Contract.terms, stipulating, extending, or limiting the Contract.period of applicability or valuation of items under consideration.
The Contract.signer applies a signature to the Contract.binding referenced resource, which is the documentation that is the legal "source of truth". The Contract.signer may delegate, such as a legally recognized personal representative, or have a delegate assigned e.g., by a court of law, to actually sign the Contract, such as a trustee in the case of incompetence.
May be used to represent additional information that is not part of the basic definition of the element. In order 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.
Role of this Contract signer, e.g. notary, grantee.
RoleClass, RoleCode, ParticipationType, ParticipationFunction class codes.
Party which is a signator to this Contract.
Element `Contract.signer.party` is mapped to FHIR STU3 element `Contract.signer.party` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R4 element `Contract.signer.party` with unmapped reference targets: PractitionerRole.
Legally binding Contract DSIG signature contents in Base64.
Participation.signatureCode :: CD (0..1) Definition: Whether the participant has attested participation through a signature, or whether such a signature is needed. Examples: A surgical Procedure act object (representing a procedure report) requires a signature of the performing and responsible surgeon, and possibly other participants; The participant intends to provide a signature. Participation.signatureText :: ED (0..1) Definition: A textual or multimedia depiction of the signature by which the participant endorses and accepts responsibility for his or her participation in the Act as specified in the Participation.typeCode. UsageNotes: The signature can be represented either inline or by reference according to the ED data type. Typical cases are 1) Paper-based signatures: the ED data type may refer to a document or other resource that can be retrieved through an electronic interface to a hardcopy archive. 2) Electronic signature: this attribute can represent virtually any electronic signature scheme. 3) Digital signature: this attribute can represent digital signatures by reference to a signature data block that is constructed in accordance to a digital signature standard, such as XML-DSIG, PKCS#7, PGP, etc. Examples: 1) An "author" participant assumes accountability for the truth of the Act statement to the best of his knowledge. 2) An information recipient only attests to the fact that he or she has received the information.
COCT_RM440000UV09 ValuedItem classCode INVE
Specific type of Contract Valued Item that may be priced.
Identifies a Contract Valued Item instance.
Indicates the time during which this Contract ValuedItem information is effective.
COCT_RM440000UV09 ValuedItem effectiveTime
Specifies the units by which the Contract Valued Item is measured or counted, and quantifies the countable or measurable Contract Valued Item instances.
COCT_RM440000UV09 ValuedItem unitQuantity
Contract Valued Item fee, charge, or cost
A Contract Valued Item unit valuation measure.
COCT_RM440000UV09 ValuedItem unitPriceAmt
Contract Valued Item Price Scaling Factor
A real number that represents a multiplier used in determining the overall value of the Contract Valued Item delivered. The concept of a Factor allows for a discount or surcharge multiplier to be applied to a monetary amount.
COCT_RM440000UV09 ValuedItem factorNumber
Contract Valued Item Difficulty Scaling Factor
An amount that expresses the weighting (based on difficulty, cost and/or resource intensiveness) associated with the Contract Valued Item delivered. The concept of Points allows for assignment of point values for a Contract Valued Item, such that a monetary amount can be assigned to each point.
COCT_RM440000UV09 ValuedItem pointNumber
Expresses the product of the Contract Valued Item unitQuantity and the unitPriceAmt. For example, the formula: unit Quantity * unit Price (Cost per Point) * factor Number * points = net Amount. Quantity, factor and points are assumed to be 1 if not supplied.
One or more Contract Provisions, which may be related and conveyed as a group, and may contain nested groups.
RIM mechanism for grouping or nesting rules, which are likely Acts and Observations.
R4: `Contract.term.offer` (new:BackboneElement)
Element `Contract.term.offer` has a context of Contract.term based on following the parent source element upwards and mapping to `Contract`. Element `Contract.term.offer` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4: `Contract.term.offer.answer` (new:BackboneElement)
Element `Contract.term.offer.answer` is part of an existing definition because parent element `Contract.term.offer` requires a cross-version extension. Element `Contract.term.offer.answer` has a context of Contract.term based on following the parent source element upwards and mapping to `Contract`. Element `Contract.term.offer.answer` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4: `Contract.term.asset` (new:BackboneElement)
Element `Contract.term.asset` has a context of Contract.term based on following the parent source element upwards and mapping to `Contract`. Element `Contract.term.asset` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4: `Contract.term.asset.answer` (new:Contract.term.offer.answer)
Element `Contract.term.asset.answer` is part of an existing definition because parent element `Contract.term.asset` requires a cross-version extension. Element `Contract.term.asset.answer` has a context of Contract.term based on following the parent source element upwards and mapping to `Contract`. Element `Contract.term.asset.answer` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Unique identifier for this particular Contract Provision.
When this Contract Provision was issued.
Relevant time or time-period when this Contract Provision is applicable.
Type of Contract Provision such as specific requirements, purposes for actions, obligations, prohibitions, e.g. life time maximum benefit.
Detailed codes for the types of contract provisions.
Contract Term Type specific classification
Subtype of this Contract Provision, e.g. life time maximum payment for a contract term for specific valued item, e.g. disability payment.
Detailed codes for the subtypes of contract provisions.
The matter of concern in the context of this provision of the agrement.
The Contract.term.topic, as a Contract Resource subpart, is handled in the same manner as the Contract Resource as discussed above.
A contract term topic is typically about a portion of the contract topic which has additional or specialized rights, privileges, obligations, restrictions, and prohibitions that are binding on any grantor and grantee parties upon the execution of the contract. Contract.term.topic may be described in more detail in the [0..*] Contract.term.valuedItem @[0..1] Contract.term.valuedItem [x] Definition: Specific type of Contract Provision Valued Item that may be priced. CodeableConcept|Reference(Any) [See Contract.topic Requirements for further elaboration on this requirement.].
R4: `Contract.term.topic[x]` additional types (CodeableConcept) additional types from child elements (coding, text)
Element `Contract.term.topic[x]` is mapped to FHIR STU3 element `Contract.term.topic` as `RelatedTo`. The mappings for `Contract.term.topic[x]` do not cover the following types: CodeableConcept. The mappings for `Contract.term.topic[x]` do not cover the following types based on type expansion: coding, text.
Action stipulated by this Contract Provision.
R4: `Contract.term.action.type` (new:CodeableConcept)
Element `Contract.term.action.type` has a context of Contract.term.action based on following the parent source element upwards and mapping to `Contract`. Element `Contract.term.action.type` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4: `Contract.term.action.subject` (new:BackboneElement)
Element `Contract.term.action.subject` has a context of Contract.term.action based on following the parent source element upwards and mapping to `Contract`. Element `Contract.term.action.subject` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4: Purpose for the Contract Term Action (new)
R4: `Contract.term.action.intent` (new:CodeableConcept)
Element `Contract.term.action.intent` has a context of Contract.term.action based on following the parent source element upwards and mapping to `Contract`. Element `Contract.term.action.intent` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4: `Contract.term.action.linkId` (new:string)
Element `Contract.term.action.linkId` has a context of Contract.term.action based on following the parent source element upwards and mapping to `Contract`. Element `Contract.term.action.linkId` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4: `Contract.term.action.status` (new:CodeableConcept)
Element `Contract.term.action.status` has a context of Contract.term.action based on following the parent source element upwards and mapping to `Contract`. Element `Contract.term.action.status` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4: Episode associated with action (new)
R4: `Contract.term.action.context` (new:Reference(Encounter,EpisodeOfCare))
Element `Contract.term.action.context` has a context of Contract.term.action based on following the parent source element upwards and mapping to `Contract`. Element `Contract.term.action.context` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4: `Contract.term.action.contextLinkId` (new:string)
Element `Contract.term.action.contextLinkId` has a context of Contract.term.action based on following the parent source element upwards and mapping to `Contract`. Element `Contract.term.action.contextLinkId` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4: `Contract.term.action.occurrence[x]` (new:dateTime, Period, Timing)
Element `Contract.term.action.occurrence[x]` has a context of Contract.term.action based on following the parent source element upwards and mapping to `Contract`. Element `Contract.term.action.occurrence[x]` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4: `Contract.term.action.requester` (new:Reference(Patient,RelatedPerson,Practitioner,PractitionerRole,Device,Group,Organization))
Element `Contract.term.action.requester` has a context of Contract.term.action based on following the parent source element upwards and mapping to `Contract`. Element `Contract.term.action.requester` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4: `Contract.term.action.requesterLinkId` (new:string)
Element `Contract.term.action.requesterLinkId` has a context of Contract.term.action based on following the parent source element upwards and mapping to `Contract`. Element `Contract.term.action.requesterLinkId` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4: `Contract.term.action.performerType` (new:CodeableConcept)
Element `Contract.term.action.performerType` has a context of Contract.term.action based on following the parent source element upwards and mapping to `Contract`. Element `Contract.term.action.performerType` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4: `Contract.term.action.performerRole` (new:CodeableConcept)
Element `Contract.term.action.performerRole` has a context of Contract.term.action based on following the parent source element upwards and mapping to `Contract`. Element `Contract.term.action.performerRole` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4: Actor that wil execute (or not) the action (new)
R4: `Contract.term.action.performer` (new:Reference(RelatedPerson,Patient,Practitioner,PractitionerRole,CareTeam,Device,Substance,Organization,Location))
Element `Contract.term.action.performer` has a context of Contract.term.action based on following the parent source element upwards and mapping to `Contract`. Element `Contract.term.action.performer` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4: `Contract.term.action.performerLinkId` (new:string)
Element `Contract.term.action.performerLinkId` has a context of Contract.term.action based on following the parent source element upwards and mapping to `Contract`. Element `Contract.term.action.performerLinkId` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4: `Contract.term.action.reasonCode` (new:CodeableConcept)
Element `Contract.term.action.reasonCode` has a context of Contract.term.action based on following the parent source element upwards and mapping to `Contract`. Element `Contract.term.action.reasonCode` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4: `Contract.term.action.reasonReference` (new:Reference(Condition,Observation,DiagnosticReport,DocumentReference,Questionnaire,QuestionnaireResponse))
Element `Contract.term.action.reasonReference` has a context of Contract.term.action based on following the parent source element upwards and mapping to `Contract`. Element `Contract.term.action.reasonReference` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4: `Contract.term.action.reason` (new:string)
Element `Contract.term.action.reason` has a context of Contract.term.action based on following the parent source element upwards and mapping to `Contract`. Element `Contract.term.action.reason` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4: `Contract.term.action.reasonLinkId` (new:string)
Element `Contract.term.action.reasonLinkId` has a context of Contract.term.action based on following the parent source element upwards and mapping to `Contract`. Element `Contract.term.action.reasonLinkId` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4: `Contract.term.action.note` (new:Annotation)
Element `Contract.term.action.note` has a context of Contract.term.action based on following the parent source element upwards and mapping to `Contract`. Element `Contract.term.action.note` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4: `Contract.term.action.securityLabelNumber` (new:unsignedInt)
Element `Contract.term.action.securityLabelNumber` has a context of Contract.term.action based on following the parent source element upwards and mapping to `Contract`. Element `Contract.term.action.securityLabelNumber` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
A reference to a code defined by a terminology system.
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.
Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings.
fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
Plain text representation of the concept
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.
Very often the text is the same as a displayName of one of the codings.
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.
C*E.9. But note many systems use C*E.2 for this
fhir:CodeableConcept.text rdfs:subPropertyOf dt:CD.originalText
Reason or purpose for the action stipulated by this Contract Provision.
Security Labels that define affected terms
A set of security labels that define which terms are controlled by this condition.
R4: `Contract.term.securityLabel.number` (new:unsignedInt)
Element `Contract.term.securityLabel.number` has a context of Contract.term.securityLabel based on following the parent source element upwards and mapping to `Contract`. Element `Contract.term.securityLabel.number` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4: `Contract.term.securityLabel.classification` (new:Coding)
Element `Contract.term.securityLabel.classification` has a context of Contract.term.securityLabel based on following the parent source element upwards and mapping to `Contract`. Element `Contract.term.securityLabel.classification` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4: `Contract.term.securityLabel.category` (new:Coding)
Element `Contract.term.securityLabel.category` has a context of Contract.term.securityLabel based on following the parent source element upwards and mapping to `Contract`. Element `Contract.term.securityLabel.category` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R4: `Contract.term.securityLabel.control` (new:Coding)
Element `Contract.term.securityLabel.control` has a context of Contract.term.securityLabel based on following the parent source element upwards and mapping to `Contract`. Element `Contract.term.securityLabel.control` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
The identification of the code system that defines the meaning of the symbol in the code.
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 de-reference to some definition that establish the system clearly and unambiguously.
Need to be unambiguous about the source of the definition of the symbol.
fhir:Coding.system rdfs:subPropertyOf dt:CDCoding.codeSystem
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.
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.
fhir:Coding.version rdfs:subPropertyOf dt:CDCoding.codeSystemVersion
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).
Need to refer to a particular code in the system.
fhir:Coding.code rdfs:subPropertyOf dt:CDCoding.code
A representation of the meaning of the code in the system, following the rules of the system.
Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
C*E.2 - but note this is not well followed
fhir:Coding.display rdfs:subPropertyOf dt:CDCoding.displayName
If this coding was chosen directly by the user
Indicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays).
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.
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.
fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map; fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [ fhir:source "true"; fhir:target dt:CDCoding.codingRationale\#O ]
The agent assigned a role in this Contract Provision.
Role played by the agent assigned this role in the execution of this Contract Provision.
Human readable form of this Contract Provision.
COCT_RM440000UV09 ValuedUnitItem classCode INVE
Specific type of Contract Provision Valued Item that may be priced.
Identifies a Contract Provision Valued Item instance.
Contract Term Valued Item Effective Tiem
Indicates the time during which this Contract Term ValuedItem information is effective.
COCT_RM440000UV09 ValuedUnitItem effectiveTime
Specifies the units by which the Contract Provision Valued Item is measured or counted, and quantifies the countable or measurable Contract Term Valued Item instances.
COCT_RM440000UV09 ValuedUnitItem unitQuantity
Contract Term Valued Item fee, charge, or cost
A Contract Provision Valued Item unit valuation measure.
COCT_RM440000UV09 ValuedUnitItem unitPriceAmt
Contract Term Valued Item Price Scaling Factor
A real number that represents a multiplier used in determining the overall value of the Contract Provision Valued Item delivered. The concept of a Factor allows for a discount or surcharge multiplier to be applied to a monetary amount.
COCT_RM440000UV09 ValuedUnitItem factorNumber
Contract Term Valued Item Difficulty Scaling Factor
An amount that expresses the weighting (based on difficulty, cost and/or resource intensiveness) associated with the Contract Provision Valued Item delivered. The concept of Points allows for assignment of point values for a Contract ProvisionValued Item, such that a monetary amount can be assigned to each point.
COCT_RM440000UV09 ValuedUnitItem pointNumber
Expresses the product of the Contract Provision 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.
Legally binding Contract: This is the signed and legally recognized representation of the Contract, which is considered the "source of truth" and which would be the basis for legal action related to enforcement of this Contract.
DocumentCompletion code system AU (authenticated) Description: A completion status in which a document has been signed manually or electronically by one or more individuals who attest to its accuracy. No explicit determination is made that the assigned individual has performed the authentication. While the standard allows multiple instances of authentication, it would be typical to have a single instance of authentication, usually by the assigned individual.
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.
Easily comprehended representation of this Contract
Human readable rendering of this Contract in a format and representation intended to enhance comprehension and ensure understandability.
Act.text Definition: A renderable textual or multimedia description (or reference to a description) of the complete information which would reasonably be expected to be displayed to a human reader conveyed by the Act.
List of Legal expressions or representations of this Contract.
Contract legal text in human renderable form.
Example: Act.text of an Act coded as with ActPrivacyLaw, ActPolicy code
List of Computable Policy Rule Language Representations of this Contract.
Computable Contract conveyed using a policy rule language (e.g. XACML, DKAL, SecPal).
Computable Policy Consent [Observation: templateId 2.16.840.1.113883.3.445.16] This template is used to represent an alternative representation of the Privacy Consent Directive (e.g.,ODRL, XrML, XACML) as a computer-readable set of rules. An implementation may use any appropriate representations of the privacy consent in addition to the "ConsentDirectiveStructuredDefinition" which uses the Clinical Template structure to express the elements of a consent directive in an interoperable way. 1. SHALL contain exactly one [1..1] templateId ( CONF-CD-16 ) such that it a. SHALL contain exactly one [1..1] @root="2.16.840.1.113883.3.445.16" 2. SHALL contain exactly one [1..1] @moodCode="DEF" (CodeSystem: 2.16.840.1.113883.5.1001 HL7ActMood) (CONF:14912) 3. SHALL contain exactly one [1..1] code (CONF:9139)/@code="57016-8" Privacy Policy Acknowledgement Document (CodeSystem: 2.16.840.1.113883.6.1 LOINC) (CONF:9138) It specifies the LOINC code corresponding to "Privacy Policy Acknowledgement Document", it is fixed at this value. 4. SHOULD contain zero or more [0..*] value with @xsi:type="ANY" (CONF:9140) The value contains the computable representation of the policy. This may be a standard-based access control or attribute control based policy (See "References"). Computable Policy Consent example <entryRelationship typeCode="COMP"> <templateId root="2.16.840.1.113883.3.445.16" /> <observationMedia classCode="OBS" moodCode="EVN"> <value mediaType="text/xml" representation="TXT"> ... </value> </observationMedia> </entryRelationship>
R4: True if the term prohibits the action (new)
R4: `Contract.term.action.doNotPerform` (new:boolean)
Element `Contract.term.action.doNotPerform` has a context of Contract.term.action based on following the parent source element upwards and mapping to `Contract`. Element `Contract.term.action.doNotPerform` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).