Release 4B

This page is part of the FHIR Specification (v4.3.0: R4B - STU). 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

4.4.1.553 Value Set http://hl7.org/fhir/ValueSet/guide-parameter-code

FHIR Infrastructure Work Group Maturity Level: 1Trial Use Use Context: Not yet ready for Production use

This is a value set defined by the FHIR project.

Summary

Defining URL:http://hl7.org/fhir/ValueSet/guide-parameter-code
Version:4.3.0
Name:GuideParameterCode
Title:GuideParameterCode
Definition:

Code of parameter that is input to the guide.

Committee:FHIR Infrastructure Work Group
OID:2.16.840.1.113883.4.642.3.996 (for OID based terminology systems)
Source ResourceXML / JSON

This value set is used in the following places:


 

This expansion generated 28 May 2022


This value set contains 10 concepts

Expansion based on GuideParameterCode v4.3.0 (CodeSystem)

All codes in this table are from the system http://hl7.org/fhir/guide-parameter-code

CodeDisplayDefinition
  applyApply Metadata ValueIf the value of this string 0..* parameter is one of the metadata fields then all conformance resources will have any specified [Resource].[field] overwritten with the ImplementationGuide.[field], where field is one of: version, date, status, publisher, contact, copyright, experimental, jurisdiction, useContext.
  path-resourceResource PathThe value of this string 0..* parameter is a subfolder of the build context's location that is to be scanned to load resources. Scope is (if present) a particular resource type.
  path-pagesPages PathThe value of this string 0..1 parameter is a subfolder of the build context's location that contains files that are part of the html content processed by the builder.
  path-tx-cacheTerminology Cache PathThe value of this string 0..1 parameter is a subfolder of the build context's location that is used as the terminology cache. If this is not present, the terminology cache is on the local system, not under version control.
  expansion-parameterExpansion ProfileThe value of this string 0..* parameter is a parameter (name=value) when expanding value sets for this implementation guide. This is particularly used to specify the versions of published terminologies such as SNOMED CT.
  rule-broken-linksBroken Links RuleThe value of this string 0..1 parameter is either "warning" or "error" (default = "error"). If the value is "warning" then IG build tools allow the IG to be considered successfully build even when there is no internal broken links.
  generate-xmlGenerate XMLThe value of this boolean 0..1 parameter specifies whether the IG publisher creates examples in XML format. If not present, the Publication Tool decides whether to generate XML.
  generate-jsonGenerate JSONThe value of this boolean 0..1 parameter specifies whether the IG publisher creates examples in JSON format. If not present, the Publication Tool decides whether to generate JSON.
  generate-turtleGenerate TurtleThe value of this boolean 0..1 parameter specifies whether the IG publisher creates examples in Turtle format. If not present, the Publication Tool decides whether to generate Turtle.
  html-templateHTML TemplateThe value of this string singleton parameter is the name of the file to use as the builder template for each generated page (see templating).

 

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. 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
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