HL7 FHIR Implementation Guide Laboratory Report
0.2.0 - trial-use

HL7 FHIR Implementation Guide Laboratory Report, published by HL7 Italia. This guide is not an authorized publication; it is the continuous build for version 0.2.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7-it/lab-report/ and changes regularly. See the Directory of published versions

## Logical Model: Richiesta - Detailed Descriptions

Active as of 2025-11-18

Definitions for the Richiesta logical model.

- Key Elements Table
- Differential Elements Table
- Snapshot Elements Table

Guidance on how to interpret the contents of this table can be foundhere

0. Richiesta
Definition | Informazioni sulla richiesta (A.2) e motivazioni (A3).
Short | A.2,A.3 - Richiesta
Control | 0..*
Is Modifier | false
Logical Model | Instances of this logical model are not marked to be the target of a Reference
2. Richiesta.dettagliRichiesta
Definition | A.2 Informazioni sulla richiesta (Laboratory Result Report could respond to multiple test orders)
Short | A.2 Informazioni sulla richiesta
Control | 0..1
Type | BackboneElement
Invariants | ele-1: All FHIR elements must have a @value or children (`hasValue() or (children().count() > id.count())`)
4. Richiesta.dettagliRichiesta.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Short | Unique id for inter-element referencing
Control | 0..1
Type | string
Is Modifier | false
XML Format | In the XML format, this property is represented as an attribute.
Summary | false
6. Richiesta.dettagliRichiesta.extension
Definition | May 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.
Short | Additional content defined by implementations
Comments | 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.
Control | 0..*
Type | Extension
Is Modifier | false
Summary | false
Alternate Names | extensions, user content
Invariants | ele-1: All FHIR elements must have a @value or children (hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (extension.exists() != value.exists())
Slicing | This element introduces a set of slices on `Richiesta.dettagliRichiesta.extension`. The slices areUnordered and Open, and can be differentiated using the following discriminators: value @ url
8. Richiesta.dettagliRichiesta.modifierExtension
Definition | May 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).
Short | Extensions that cannot be ignored even if unrecognized
Comments | 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.
Control | 0..*
Type | Extension
Is Modifier | true because Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
Summary | true
Requirements | 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.
Alternate Names | extensions, user content, modifiers
Invariants | ele-1: All FHIR elements must have a @value or children (hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (extension.exists() != value.exists())
10. Richiesta.dettagliRichiesta.identificativo
Definition | Identificativo della richiesta dell'esame di laboratorio. Ad un unico identificativo possono corrispondere più richieste.
Short | A.2.1 Identificativo della richiesta
Control | 0..*
Type | Identifier
12. Richiesta.dettagliRichiesta.dateTime
Definition | Data ed orario in cui è stata effettuata la richiesta - Preferred system(s): ISO 8601
Short | A.2.2 Data ed ora della richiesta
Control | 0..*
Type | dateTime
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
14. Richiesta.dettagliRichiesta.mittenteRichiesta
Definition | Operatore sanitario che invia la richiesta.
Short | A.2.3 Mittente della richiesta
Control | 0..*
Type | Identifier
16. Richiesta.dettagliRichiesta.codicePriorita
Definition | Priorità della richiesta
Short | A.2.7 Codice priorità
Control | 0..1
Type | code
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
18. Richiesta.quesitoDiagnostico
Definition | A.3 Motivazione della richiesta (Laboratory Result Report could respond to multiple reasons)
Short | A.3 Motivazione della richiesta
Control | 0..*
Type | BackboneElement
Invariants | ele-1: All FHIR elements must have a @value or children (`hasValue() or (children().count() > id.count())`)
20. Richiesta.quesitoDiagnostico.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Short | Unique id for inter-element referencing
Control | 0..1
Type | string
Is Modifier | false
XML Format | In the XML format, this property is represented as an attribute.
Summary | false
22. Richiesta.quesitoDiagnostico.extension
Definition | May 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.
Short | Additional content defined by implementations
Comments | 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.
Control | 0..*
Type | Extension
Is Modifier | false
Summary | false
Alternate Names | extensions, user content
Invariants | ele-1: All FHIR elements must have a @value or children (hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (extension.exists() != value.exists())
Slicing | This element introduces a set of slices on `Richiesta.quesitoDiagnostico.extension`. The slices areUnordered and Open, and can be differentiated using the following discriminators: value @ url
24. Richiesta.quesitoDiagnostico.modifierExtension
Definition | May 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).
Short | Extensions that cannot be ignored even if unrecognized
Comments | 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.
Control | 0..*
Type | Extension
Is Modifier | true because Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
Summary | true
Requirements | 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.
Alternate Names | extensions, user content, modifiers
Invariants | ele-1: All FHIR elements must have a @value or children (hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (extension.exists() != value.exists())
26. Richiesta.quesitoDiagnostico.code
Definition | Condizioni di salute che incidono sulla salute del paziente e sono importanti da conoscere per un professionista sanitario durante un incontro sanitario. Condizioni cliniche del soggetto rilevanti per l'interpretazione dei risultati. Sistema/i preferito/i: ICD-10 (ICD-11 when available) Sistema/i preferito/i: SNOMED CT Sistema/i preferito/i: Orphacode
Short | A.3.1 Quesito diagnostico associato alla richiesta
Control | 0..*
Type | CodeableConcept

Guidance on how to interpret the contents of this table can be foundhere

0. Richiesta
Definition | Informazioni sulla richiesta (A.2) e motivazioni (A3).
Short | A.2,A.3 - Richiesta
Logical Model | Instances of this logical model are not marked to be the target of a Reference
2. Richiesta.dettagliRichiesta
Definition | A.2 Informazioni sulla richiesta (Laboratory Result Report could respond to multiple test orders)
Short | A.2 Informazioni sulla richiesta
Control | 0..1
Type | BackboneElement
4. Richiesta.dettagliRichiesta.identificativo
Definition | Identificativo della richiesta dell'esame di laboratorio. Ad un unico identificativo possono corrispondere più richieste.
Short | A.2.1 Identificativo della richiesta
Control | 0..*
Type | Identifier
6. Richiesta.dettagliRichiesta.dateTime
Definition | Data ed orario in cui è stata effettuata la richiesta - Preferred system(s): ISO 8601
Short | A.2.2 Data ed ora della richiesta
Control | 0..*
Type | dateTime
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
8. Richiesta.dettagliRichiesta.mittenteRichiesta
Definition | Operatore sanitario che invia la richiesta.
Short | A.2.3 Mittente della richiesta
Control | 0..*
Type | Identifier
10. Richiesta.dettagliRichiesta.codicePriorita
Definition | Priorità della richiesta
Short | A.2.7 Codice priorità
Control | 0..1
Type | code
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
12. Richiesta.quesitoDiagnostico
Definition | A.3 Motivazione della richiesta (Laboratory Result Report could respond to multiple reasons)
Short | A.3 Motivazione della richiesta
Control | 0..*
Type | BackboneElement
14. Richiesta.quesitoDiagnostico.code
Definition | Condizioni di salute che incidono sulla salute del paziente e sono importanti da conoscere per un professionista sanitario durante un incontro sanitario. Condizioni cliniche del soggetto rilevanti per l'interpretazione dei risultati. Sistema/i preferito/i: ICD-10 (ICD-11 when available) Sistema/i preferito/i: SNOMED CT Sistema/i preferito/i: Orphacode
Short | A.3.1 Quesito diagnostico associato alla richiesta
Control | 0..*
Type | CodeableConcept

Guidance on how to interpret the contents of this table can be foundhere

0. Richiesta
Definition | Informazioni sulla richiesta (A.2) e motivazioni (A3).
Short | A.2,A.3 - Richiesta
Control | 0..*
Is Modifier | false
Logical Model | Instances of this logical model are not marked to be the target of a Reference
2. Richiesta.dettagliRichiesta
Definition | A.2 Informazioni sulla richiesta (Laboratory Result Report could respond to multiple test orders)
Short | A.2 Informazioni sulla richiesta
Control | 0..1
Type | BackboneElement
Invariants | ele-1: All FHIR elements must have a @value or children (`hasValue() or (children().count() > id.count())`)
4. Richiesta.dettagliRichiesta.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Short | Unique id for inter-element referencing
Control | 0..1
Type | string
Is Modifier | false
XML Format | In the XML format, this property is represented as an attribute.
Summary | false
6. Richiesta.dettagliRichiesta.extension
Definition | May 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.
Short | Additional content defined by implementations
Comments | 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.
Control | 0..*
Type | Extension
Is Modifier | false
Summary | false
Alternate Names | extensions, user content
Invariants | ele-1: All FHIR elements must have a @value or children (`hasValue() or (children().count() > id.count())`) ext-1: Must have either extensions or value[x], not both (`extension.exists() != value.exists()`)
Slicing | This element introduces a set of slices on `Richiesta.dettagliRichiesta.extension`. The slices areUnordered and Open, and can be differentiated using the following discriminators: value @ url
8. Richiesta.dettagliRichiesta.modifierExtension
Definition | May 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).
Short | Extensions that cannot be ignored even if unrecognized
Comments | 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.
Control | 0..*
Type | Extension
Is Modifier | true because Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
Summary | true
Requirements | 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.
Alternate Names | extensions, user content, modifiers
Invariants | ele-1: All FHIR elements must have a @value or children (`hasValue() or (children().count() > id.count())`) ext-1: Must have either extensions or value[x], not both (`extension.exists() != value.exists()`)
10. Richiesta.dettagliRichiesta.identificativo
Definition | Identificativo della richiesta dell'esame di laboratorio. Ad un unico identificativo possono corrispondere più richieste.
Short | A.2.1 Identificativo della richiesta
Control | 0..*
Type | Identifier
12. Richiesta.dettagliRichiesta.dateTime
Definition | Data ed orario in cui è stata effettuata la richiesta - Preferred system(s): ISO 8601
Short | A.2.2 Data ed ora della richiesta
Control | 0..*
Type | dateTime
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
14. Richiesta.dettagliRichiesta.mittenteRichiesta
Definition | Operatore sanitario che invia la richiesta.
Short | A.2.3 Mittente della richiesta
Control | 0..*
Type | Identifier
16. Richiesta.dettagliRichiesta.codicePriorita
Definition | Priorità della richiesta
Short | A.2.7 Codice priorità
Control | 0..1
Type | code
Primitive Value | This primitive element may be present, or absent, or replaced by an extension
18. Richiesta.quesitoDiagnostico
Definition | A.3 Motivazione della richiesta (Laboratory Result Report could respond to multiple reasons)
Short | A.3 Motivazione della richiesta
Control | 0..*
Type | BackboneElement
Invariants | ele-1: All FHIR elements must have a @value or children (`hasValue() or (children().count() > id.count())`)
20. Richiesta.quesitoDiagnostico.id
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Short | Unique id for inter-element referencing
Control | 0..1
Type | string
Is Modifier | false
XML Format | In the XML format, this property is represented as an attribute.
Summary | false
22. Richiesta.quesitoDiagnostico.extension
Definition | May 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.
Short | Additional content defined by implementations
Comments | 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.
Control | 0..*
Type | Extension
Is Modifier | false
Summary | false
Alternate Names | extensions, user content
Invariants | ele-1: All FHIR elements must have a @value or children (`hasValue() or (children().count() > id.count())`) ext-1: Must have either extensions or value[x], not both (`extension.exists() != value.exists()`)
Slicing | This element introduces a set of slices on `Richiesta.quesitoDiagnostico.extension`. The slices areUnordered and Open, and can be differentiated using the following discriminators: value @ url
24. Richiesta.quesitoDiagnostico.modifierExtension
Definition | May 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).
Short | Extensions that cannot be ignored even if unrecognized
Comments | 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.
Control | 0..*
Type | Extension
Is Modifier | true because Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
Summary | true
Requirements | 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.
Alternate Names | extensions, user content, modifiers
Invariants | ele-1: All FHIR elements must have a @value or children (`hasValue() or (children().count() > id.count())`) ext-1: Must have either extensions or value[x], not both (`extension.exists() != value.exists()`)
26. Richiesta.quesitoDiagnostico.code
Definition | Condizioni di salute che incidono sulla salute del paziente e sono importanti da conoscere per un professionista sanitario durante un incontro sanitario. Condizioni cliniche del soggetto rilevanti per l'interpretazione dei risultati. Sistema/i preferito/i: ICD-10 (ICD-11 when available) Sistema/i preferito/i: SNOMED CT Sistema/i preferito/i: Orphacode
Short | A.3.1 Quesito diagnostico associato alla richiesta
Control | 0..*
Type | CodeableConcept