This page is part of the Structured Data Capture FHIR IG (v3.0.0: STU 3) based on FHIR R4. This is the current published version. For a full list of available versions, see the Directory of published versions
Official URL: http://hl7.org/fhir/uv/sdc/ValueSet/questionnaire-answer-constraint | Version: 3.0.0 | |||
Standards status: Draft | Maturity Level: 0 | Computable Name: QuestionnaireAnswerConstraint | ||
Other Identifiers: : urn:oid:2.16.840.1.113883.4.642.3.0 |
Codes that describe the types of constraints possible on a question item that has a list of permitted answers [Note: This is a clone of QuestionnaireAnswerConstraint valueset from R5 (adopting R5 capability)]
References
http://hl7.org/fhir/uv/sdc/CodeSystem/questionnaire-answer-constraint
This value set contains 3 concepts
Expansion based on Questionnaire answer constraint codes v3.0.0 (CodeSystem)
All codes in this table are from the system http://hl7.org/fhir/uv/sdc/CodeSystem/questionnaire-answer-constraint
Code | Display | Definition |
optionsOnly | Options only | Only values listed as answerOption or in the expansion of the answerValueSet are permitted |
optionsOrType | Options or 'type' | In addition to the values listed as answerOption or in the expansion of the answerValueSet, any other values that correspond to the specified item.type are permitted |
optionsOrString | Options or string | In addition to the values listed as answerOption or in the expansion of the answerValueSet, free-text strings are permitted. Answers will have a type of 'string'. |
Explanation of the columns that may appear on this page:
Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
System | 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) |
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 |