eHealth Infrastructure
3.4.1 - release
eHealth Infrastructure
3.4.1 - release
eHealth Infrastructure, published by Den telemedicinske infrastruktur (eHealth Infrastructure). This guide is not an authorized publication; it is the continuous build for version 3.4.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/fut-infrastructure/implementation-guide/ and changes regularly. See the Directory of published versions
| Official URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-definedquestion | Version: 3.4.1 | |||
| Active as of 2025-03-14 | Computable Name: ehealth-definedquestion | |||
The ehealth-definedquestion profile of StructureDefinition represents the concept of a DefinedQuestion. A DefinedQuestion is a standalone representation of a question and possibly its answer options that can be used in one or more Questionnaire resources. Although a Questionnaire can be constructed without being based on any DefinedQuestion, it is expected that a catalogue of DefinedQuestion will emerge over time and the particular DefinedQuestion will be reused in multiple Questionnaire.
The DefinedQuestion concept is based on ideas described in https://www.hl7.org/fhir/stu3/questionnaire.html#2.38.5.4. Whether a DefinedQuestion is referenced in a Questionnaire or not, it is the Questionnaire's own definition which takes precedence.
In the eHealth Infrastructure, a reference to a DefinedQuestion by url in a Questionnaire question is used to enable robust extraction in automated processing rule(s) of answer(s) to that question from corresponding QuestionnaireResponse. An answer in a QuestionnaireResponse is already unambiguously related to a question in a Questionnaire through the question's linkId. If the same question is used in another Questionnaire it will likely end up with a different linkId in that Questionnaire. By referencing a DefinedQuestion by its url in Questionnaire.item.definition, the same question can be referenced unambiguously in multiple Questionnaire.
Multiple DefinedQuestion with identical url can coexist as long as they have differing business versions in version. This way, different versions of the same question can have different answer options.
When using a DefinedQuestion in a Questionnaire, the Questionnaire.item.definition element must contain the url followed by a pipe and the business version thereby referencing a versioned DefinedQuestion.
An automated processing rule captured in a Library resource can, when extracting answer(s) to the question in a QuestionnaireResponse, choose to search for either the versioned reference or the version-less reference to a DefinedQuestion. The latter can be obtained by disregarding the pipe and business version in the rule logic.
The actual details of the DefinedQuestion's question and possible answers are described in the ElementDefinition found in either snapshot.element or differential.element.
Usage:
Description of Profiles, Differentials, Snapshots and how the different presentations work.
| Name | Flags | Card. | Type | Description & Constraints |
|---|---|---|---|---|
  StructureDefinition |
C | 0..* | StructureDefinition | Structural Definition dom-2: If the resource is contained in another resource, it SHALL NOT contain nested Resources dom-3: If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource dom-4: If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated dom-5: If a resource is contained in another resource, it SHALL NOT have a security label dom-6: A resource should have narrative for robust management sdf-0: Name should be usable as an identifier for the module by machine processing applications such as code generation sdf-1: Element paths must be unique unless the structure is a constraint sdf-15a: If the first element in a differential has no "." in the path and it's not a logical model, it has no type sdf-4: If the structure is not abstract, then there SHALL be a baseDefinition sdf-5: If the structure defines an extension then the structure must have context information sdf-6: A structure must have either a differential, or a snapshot (or both) sdf-9: In any snapshot or differential, no label, code or requirements on an element without a "." in the path (e.g. the first element) sdf-11: If there's a type, its content must match the path name in the first element of a snapshot sdf-14: All element definitions must have an id sdf-15: The first element in a snapshot has no type unless model is a logical model. sdf-16: All element definitions must have unique ids (snapshot) sdf-17: All element definitions must have unique ids (diff) sdf-18: Context Invariants can only be used for extensions sdf-19: FHIR Specification models only use FHIR defined types sdf-21: Default values can only be specified on specializations sdf-22: FHIR Specification models never have default values sdf-23: No slice name on root |
  implicitRules |
?!Σ | 0..1 | uri | A set of rules under which this content was created ele-1: All FHIR elements must have a @value or children |
 modifierExtension |
?! | 0..* | Extension | Extensions that cannot be ignored ele-1: All FHIR elements must have a @value or children ext-1: Must have either extensions or value[x], not both |
| url |
Σ | 1..1 | uri | Canonical identifier for this structure definition, represented as a URI (globally unique) ele-1: All FHIR elements must have a @value or children |
| name |
ΣC | 1..1 | string | Name for this structure definition (computer friendly) ele-1: All FHIR elements must have a @value or children |
| status |
?!Σ | 1..1 | code | draft | active | retired | unknown Binding: PublicationStatus (required): The lifecycle status of an artifact. ele-1: All FHIR elements must have a @value or children |
| kind |
Σ | 1..1 | code | primitive-type | complex-type | resource | logical Binding: StructureDefinitionKind (required): Defines the type of structure that a definition is describing. ele-1: All FHIR elements must have a @value or children |
| abstract |
Σ | 1..1 | boolean | Whether the structure is abstract ele-1: All FHIR elements must have a @value or children |
 type |
ΣC | 1..1 | uri | Type defined or constrained by this structure Binding: FHIRDefinedType (extensible): Either a resource or a data type, including logical model types. ele-1: All FHIR elements must have a @value or children |
| Documentation for this format | ||||
| Path | Conformance | ValueSet | URI |
| StructureDefinition.status | required | PublicationStatushttp://hl7.org/fhir/ValueSet/publication-status|4.0.1from the FHIR Standard | |
| StructureDefinition.kind | required | StructureDefinitionKindhttp://hl7.org/fhir/ValueSet/structure-definition-kind|4.0.1from the FHIR Standard | |
| StructureDefinition.type | extensible | FHIRDefinedTypehttp://hl7.org/fhir/ValueSet/defined-typesfrom the FHIR Standard |
Other representations of profile: CSV, Excel, Schematron
IG © 2021+ Den telemedicinske infrastruktur (eHealth Infrastructure). Package dk.ehealth.sundhed.fhir.ig.core#3.4.1 based on FHIR 4.0.1. Generated 2025-03-14
