Tollwutexpositionsverdacht-Erkrankungsinformationen (DiseaseInformationTTVD)
https://demis.rki.de/fhir/StructureDefinition/DiseaseInformationTTVD
Das DiseaseInformationTTVD-Profil ist eine Spezialisierung des DiseaseInformation-Profils.
Der Hauptunterschied zum Elternprofil liegt in der Bindung des questionnaire-Elementes an einen fest definierten Wert, der den zugrundeliegenden Fragebogen referenziert. In diesem Fall handelt es sich um die Questionnaire-Ressource DiseaseQuestionsTTVD. Diese Ressource wird neben der hier vorgestellten StructureDefinition für die Validierung der jeweiligen QuestionnaireResponse herangezogen. Dort werden auch die (fachlichen) Inhalte detailliert dargestellt, welche über die hier profilierte QuestionnaireResponse transportiert werden können/müssen.
Profilansicht
DiseaseInformationTTVD (QuestionnaireResponse) | I | DiseaseInformation | There are no (further) constraints on this element Element idQuestionnaireResponse A structured set of questions and their answers Alternate namesForm, QuestionnaireAnswers DefinitionA structured set of questions and their answers. The questions are ordered and grouped into coherent subsets, corresponding to the structure of the grouping of the questionnaire being responded to. The QuestionnaireResponse contains enough information about the questions asked and their organization that it can be interpreted somewhat independently from the Questionnaire it is based on. I.e. You don't need access to the Questionnaire in order to extract basic information from a QuestionnaireResponse.
| |
id | Σ | 0..1 | string | There are no (further) constraints on this element Element idQuestionnaireResponse.id Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idQuestionnaireResponse.meta Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
|
implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idQuestionnaireResponse.implicitRules A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.
|
language | 0..1 | codeBinding | There are no (further) constraints on this element Element idQuestionnaireResponse.language Language of the resource content DefinitionThe base language in which the resource is written. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). A human language.
| |
text | 0..1 | Narrative | There are no (further) constraints on this element Element idQuestionnaireResponse.text Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
| |
contained | 0..* | Resource | There are no (further) constraints on this element Element idQuestionnaireResponse.contained Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idQuestionnaireResponse.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | ?! I | 0..* | Extension | There are no (further) constraints on this element Element idQuestionnaireResponse.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element idQuestionnaireResponse.identifier Unique id for this set of answers DefinitionA business identifier assigned to a particular completed (or partially completed) questionnaire. Used for tracking, registration and other business purposes.
|
basedOn | Σ I | 0..0 | Reference(CarePlan | ServiceRequest) | There are no (further) constraints on this element Element idQuestionnaireResponse.basedOn Request fulfilled by this QuestionnaireResponse Alternate namesorder DefinitionThe order, proposal or plan that is fulfilled in whole or in part by this QuestionnaireResponse. For example, a ServiceRequest seeking an intake assessment or a decision support recommendation to assess for post-partum depression. Supports traceability of responsibility for the action and allows linkage of an action to the recommendations acted upon. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(CarePlan | ServiceRequest) Constraints
|
partOf | Σ I | 0..0 | Reference(Observation | Procedure) | There are no (further) constraints on this element Element idQuestionnaireResponse.partOf Part of this action DefinitionA procedure or observation that this questionnaire was performed as part of the execution of. For example, the surgery a checklist was executed as part of. Composition of questionnaire responses will be handled by the parent questionnaire having answers that reference the child questionnaire. For relationships to referrals, and other types of requests, use basedOn. Reference(Observation | Procedure) Constraints
|
questionnaire | S Σ | 1..1 | canonical(Questionnaire)Fixed Value | Element idQuestionnaireResponse.questionnaire Form being answered Alternate namesForm DefinitionThe Questionnaire that defines and organizes the questions for which answers are being provided. Needed to allow editing of the questionnaire response in a manner that enforces the constraints of the original form. If a QuestionnaireResponse references a Questionnaire, then the QuestionnaireResponse structure must be consistent with the Questionnaire (i.e. questions must be organized into the same groups, nested questions must still be nested, etc.).
https://demis.rki.de/fhir/Questionnaire/DiseaseQuestionsTTVD
|
status | Σ ?! | 1..1 | codeBinding | There are no (further) constraints on this element Element idQuestionnaireResponse.status Status der Fragebogeninhalte DefinitionStatus der Fragebogeninhalte The information on Questionnaire resources may possibly be gathered during multiple sessions and altered after considered being finished. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid. Lifecycle status of the questionnaire response.
|
subject | S Σ I | 1..1 | Reference(NotifiedPerson) | There are no (further) constraints on this element Element idQuestionnaireResponse.subject Verweis auf die in der Meldung benannte betroffene Person. Alternate namesPatient, Focus DefinitionVerweis auf die in der Meldung benannte betroffene Person. Hierbei handelt es sich grundsätzlich um den Verweis auf die in der Erregernachweismeldung als „subject“ referenzierte Patient Ressource. Allows linking the answers to the individual the answers describe. May also affect access control. If the Questionnaire declared a subjectType, the resource pointed to by this element must be an instance of one of the listed types.
|
id | 0..1 | string | There are no (further) constraints on this element Element idQuestionnaireResponse.subject.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idQuestionnaireResponse.subject.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
reference | S Σ I | 1..1 | string | There are no (further) constraints on this element Element idQuestionnaireResponse.subject.reference Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
|
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element idQuestionnaireResponse.subject.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model).
|
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element idQuestionnaireResponse.subject.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element idQuestionnaireResponse.subject.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
|
encounter | Σ I | 0..0 | Reference(Encounter) | There are no (further) constraints on this element Element idQuestionnaireResponse.encounter Encounter created as part of DefinitionThe Encounter during which this questionnaire response was created or to which the creation of this record is tightly associated. Provides context for the information that was captured. May also affect access control. This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter. A questionnaire that was initiated during an encounter but not fully completed during the encounter would still generally be associated with the encounter.
|
authored | Σ | 0..0 | dateTime | There are no (further) constraints on this element Element idQuestionnaireResponse.authored Date the answers were gathered Alternate namesDate Created, Date published, Date Issued, Date updated DefinitionThe date and/or time that this set of answers were last changed. Clinicians need to be able to check the date that the information in the questionnaire was collected, to derive the context of the answers. May be different from the lastUpdateTime of the resource itself, because that reflects when the data was known to the server, not when the data was captured. This element is optional to allow for systems that might not know the value, however it SHOULD be populated if possible.
|
author | Σ I | 0..0 | Reference(Device | Practitioner | PractitionerRole | Patient | RelatedPerson | Organization) | There are no (further) constraints on this element Element idQuestionnaireResponse.author Person who received and recorded the answers Alternate namesLaboratory, Service, Practitioner, Department, Company, Performer DefinitionPerson who received the answers to the questions in the QuestionnaireResponse and recorded them in the system. Need to know who interpreted the subject's answers to the questions in the questionnaire, and selected the appropriate options for answers. Mapping a subject's answers to multiple choice options and determining what to put in the textual answer is a matter of interpretation. Authoring by device would indicate that some portion of the questionnaire had been auto-populated. Reference(Device | Practitioner | PractitionerRole | Patient | RelatedPerson | Organization) Constraints
|
source | Σ I | 0..0 | Reference(Patient | Practitioner | PractitionerRole | RelatedPerson) | There are no (further) constraints on this element Element idQuestionnaireResponse.source The person who answered the questions DefinitionThe person who answered the questions about the subject. When answering questions about a subject that is minor, incapable of answering or an animal, another human source may answer the questions. If not specified, no inference can be made about who provided the data. Reference(Patient | Practitioner | PractitionerRole | RelatedPerson) Constraints
|
item | S I | 1..* | BackboneElement | There are no (further) constraints on this element Element idQuestionnaireResponse.item Groups and questions DefinitionA group or question item from the original questionnaire for which answers are provided. Groups cannot have answers and therefore must nest directly within item. When dealing with questions, nesting must occur within each answer because some questions may have multiple answers (and the nesting occurs for each answer).
|
id | 0..1 | string | There are no (further) constraints on this element Element idQuestionnaireResponse.item.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idQuestionnaireResponse.item.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idQuestionnaireResponse.item.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
linkId | 1..1 | string | There are no (further) constraints on this element Element idQuestionnaireResponse.item.linkId Pointer to specific item from Questionnaire DefinitionThe item from the Questionnaire that corresponds to this item in the QuestionnaireResponse resource. Items can repeat in the answers, so a direct 1..1 correspondence by position might not exist - requiring correspondence by identifier. Note that FHIR strings SHALL NOT exceed 1MB in size
| |
definition | 0..1 | uri | There are no (further) constraints on this element Element idQuestionnaireResponse.item.definition ElementDefinition - details for the item DefinitionA reference to an ElementDefinition that provides the details for the item. A common pattern is to define a set of data elements, and then build multiple different questionnaires for different circumstances to gather the data. This element provides traceability to the common definition. The ElementDefinition must be in a StructureDefinition, and must have a fragment identifier that identifies the specific data element by its id (Element.id). E.g. http://hl7.org/fhir/StructureDefinition/Observation#Observation.value[x]. There is no need for this element if the item pointed to by the linkId has a definition listed.
| |
text | 0..1 | string | There are no (further) constraints on this element Element idQuestionnaireResponse.item.text Name for group or question text DefinitionText that is displayed above the contents of the group or as the text of the question being answered. Allows the questionnaire response to be read without access to the questionnaire. Note that FHIR strings SHALL NOT exceed 1MB in size
| |
answer | 0..* | BackboneElement | There are no (further) constraints on this element Element idQuestionnaireResponse.item.answer The response(s) to the question DefinitionThe respondent's answer(s) to the question. The value is nested because we cannot have a repeating structure that has variable type.
| |
id | 0..1 | string | There are no (further) constraints on this element Element idQuestionnaireResponse.item.answer.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idQuestionnaireResponse.item.answer.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idQuestionnaireResponse.item.answer.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
value[x] | 0..1 | There are no (further) constraints on this element Element idQuestionnaireResponse.item.answer.value[x] Single-valued answer to the question DefinitionThe answer (or one of the answers) provided by the respondent to the question. Ability to retain a single-valued answer to a question. More complex structures (Attachment, Resource and Quantity) will typically be limited to electronic forms that can expose an appropriate user interface to capture the components and enforce the constraints of a complex data type. Additional complex types can be introduced through extensions. Must match the datatype specified by Questionnaire.item.type in the corresponding Questionnaire. Code indicating the response provided for a question.
| ||
valueBoolean | boolean | There are no (further) constraints on this element Data type | ||
valueDecimal | decimal | There are no (further) constraints on this element Data type | ||
valueInteger | integer | There are no (further) constraints on this element Data type | ||
valueDate | date | There are no (further) constraints on this element Data type | ||
valueDateTime | dateTime | There are no (further) constraints on this element Data type | ||
valueTime | time | There are no (further) constraints on this element Data type | ||
valueString | string | There are no (further) constraints on this element Data type | ||
valueUri | uri | There are no (further) constraints on this element Data type | ||
valueAttachment | Attachment | There are no (further) constraints on this element Data type | ||
valueCoding | Coding | There are no (further) constraints on this element Data type | ||
valueQuantity | Quantity | There are no (further) constraints on this element Data type | ||
valueReference | Reference(Resource) | There are no (further) constraints on this element Data type | ||
item | 0..* | see (item) | There are no (further) constraints on this element Element idQuestionnaireResponse.item.answer.item Nested groups and questions DefinitionNested groups and/or questions found within this particular answer. It is useful to have "sub-questions", questions which normally appear when certain answers are given and which collect additional details.
| |
item | 0..* | see (item) | There are no (further) constraints on this element Element idQuestionnaireResponse.item.item Nested questionnaire response items DefinitionQuestions or sub-groups nested beneath a question or group. Reports can consist of complex nested groups.
|
Beispiel
<QuestionnaireResponse xmlns="http://hl7.org/fhir"> <id value="ddd0c137-d7ea-3aa1-b155-7493753b0ec8" /> <meta> <profile value="https://demis.rki.de/fhir/StructureDefinition/DiseaseInformationTTVD" /> </meta> <questionnaire value="https://demis.rki.de/fhir/Questionnaire/DiseaseQuestionsTTVD" /> <status value="completed" /> <subject> <reference value="Patient/3355d427-ea9b-33aa-88da-f48acd78cd73" /> </subject> <item> <linkId value="immunization" /> <answer> <valueCoding> <system value="https://demis.rki.de/fhir/CodeSystem/yesOrNoAnswer" /> <code value="yes" /> <display value="Ja" /> </valueCoding> <item> <linkId value="immunizationRef" /> <answer> <valueReference> <reference value="Immunization/4305faac-c4f6-3210-bf15-4b4983a67c48" /> </valueReference> </answer> </item> <item> <linkId value="immunizationRef" /> <answer> <valueReference> <reference value="Immunization/4732caa4-333c-3f8c-bae4-ff05aa81e535" /> </valueReference> </answer> </item> <item> <linkId value="immunizationRef" /> <answer> <valueReference> <reference value="Immunization/8c193a1d-c79e-35db-97b0-53437cbec612" /> </valueReference> </answer> </item> <item> <linkId value="immunizationRef" /> <answer> <valueReference> <reference value="Immunization/40a850c0-dc42-3ce6-a47b-c8b113d870fe" /> </valueReference> </answer> </item> </answer> </item> <item> <linkId value="infectionRiskKindAnimal" /> <answer> <valueCoding> <system value="http://snomed.info/sct" /> <code value="18646008" /> <display value="Fuchs" /> </valueCoding> <item> <linkId value="animal" /> <answer> <valueCoding> <system value="http://terminology.hl7.org/CodeSystem/v3-NullFlavor" /> <code value="NASK" /> <display value="not asked" /> </valueCoding> </answer> </item> </answer> </item> </QuestionnaireResponse>