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: R5 R4B R4 R3

• Using Codes
• Code Systems
• Value Sets
• Concept Maps
• Identifier Systems

4.3.1.747 Value Set http://hl7.org/fhir/ValueSet/consent-content-class

Community Based Collaborative Care Work Group

Maturity Level: 1

Trial Use

Use Context: Not Intended for Production use

This is a value set defined by the FHIR project.

Summary

Defining URL:	http://hl7.org/fhir/ValueSet/consent-content-class
Name:	Consent Content Class
Definition:	This value set includes the FHIR resource types, along with some other important content class codes
Committee:	Community Based Collaborative Care Work Group
OID:	2.16.840.1.113883.4.642.3.747 (for OID based terminology systems)
Source Resource	XML / JSON

This value set is used in the following places:

• Consent.provision.class (Extensible)
• StructureDefinition ConsentDirective: Contract.term.asset.class ((Extensible))

4.3.1.747.1 Content Logical Definition

---

 

4.3.1.747.2 Expansion

This expansion generated 03 Apr 2018

---

This value set could not be expanded by the publication tooling: Unable to provide support for code system urn:ietf:bcp:13

 

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

---

Explanation of the columns that may appear on this page:

Lvl	A few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - see Code System for further information
Source	The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code	The code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')
Display	The 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
Definition	An explanation of the meaning of the concept
Comments	Additional notes about how to use the code