R4 Ballot #1 (Mixed Normative/Trial use)

This page is part of the FHIR Specification (v3.3.0: R4 Ballot 2). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4B R4 R3

4.2.13.746 Code System http://hl7.org/fhir/contract-content-derivative

Financial Management Work Group Maturity Level: 1Draft Use Context: Not Intended for Production use

This is a code system defined by the FHIR project.

Summary

Defining URL:http://hl7.org/fhir/contract-content-derivative
Name:Contract Content Derivation Codes
Definition:

This is an example set of Content Derivative type codes, which represent the minimal content derived from the basal information source at a specific stage in its lifecycle, which is sufficient to manage that source information, for example, in a repository, registry, processes and workflows, for making access control decisions, and providing query responses.

Committee:Financial Management Work Group
OID:2.16.840.1.113883.4.642.1.746 (for OID based terminology systems)
Copyright:This is an example set.
Source ResourceXML / JSON

This Code system is used in the following value sets:

  • Contract Content Derivation Codes (This is an example set of Content Derivative type codes, which represent the minimal content derived from the basal information source at a specific stage in its lifecycle, which is sufficient to manage that source information, for example, in a repository, registry, processes and workflows, for making access control decisions, and providing query responses.)
This is an example set of Content Derivative type codes, which represent the minimal content derived from the basal information source at a specific stage in its lifecycle, which is sufficient to manage that source information, for example, in a repository, registry, processes and workflows, for making access control decisions, and providing query responses.

This is an example set of Content Derivative type codes, which represent the minimal content derived from the basal information source at a specific stage in its lifecycle, which is sufficient to manage that source information, for example, in a repository, registry, processes and workflows, for making access control decisions, and providing query responses.

Copyright Statement: This is an example set.

This code system http://hl7.org/fhir/contract-content-derivative defines the following codes:

CodeDisplayDefinition
registration Content RegistrationContent derivative that conveys sufficient information needed to register the source basal content from which it is derived. This derivative content may be used to register the basal content as it changes status in its lifecycle. For example, content registration may occur when the basal content is created, updated, inactive, or deleted.
retrieval Content RetrievalA content derivative that conveys sufficient information to locate and retrieve the content.
statement Content StatementContent derivative that has less than full fidelity to the basal information source from which it was 'transcribed'. It provides recipients with the full content representation they may require for compliance purposes, and typically include a reference to or an attached unstructured representation for recipients needing an exact copy of the legal agreement.
shareable Shareable ContentA Content Derivative that conveys sufficient information to determine the authorized entities with which the content may be shared.

 

See the full registry of value sets defined as part of FHIR.


Explanation of the columns that may appear on this page:

LvlA few code lists that FHIR defines are hierarchical - each code is assigned a level. See Code System for further information.
SourceThe source of the definition of the code (when the value set draws in codes defined elsewhere)
CodeThe code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')
DisplayThe display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
DefinitionAn explanation of the meaning of the concept
CommentsAdditional notes about how to use the code