ReteLabDiagnosticReportRefertato
Descrizione
Il profilo ReteLabDiagnosticReportRefertato è stato strutturato a partire dalla risorsa generica FHIR DiagnosticReport utilizzata per descrivere le informazioni relative al referto degli esami di laboratorio.
Di seguito è presentato il contenuto del profilo in diversi formati. La corrispondente definizione è consultabile al seguente link: ReteLabDiagnosticReportRefertato.
Snapshot View
| ReteLabDiagnosticReportRefertato (DiagnosticReport) | C | DiagnosticReport | Element idDiagnosticReportShort description Profilo che contiene informazioni relative al referto degli esami di laboratorio. Alternate namesReport, Test, Result, Results, Labs, Laboratory DefinitionQuesto profilo può essere presente nei seguenti flussi: "Notifica refertato da LS a LR" This is intended to capture a single report and is not suitable for use in displaying summary information that covers multiple reports. For example, this resource has not been designed for laboratory cumulative reporting formats nor detailed structured reports for sequencing.
| |||
| id | Σ | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.idShort description 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 idDiagnosticReport.metaShort description 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 idDiagnosticReport.implicitRulesShort description 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 idDiagnosticReport.languageShort description 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 idDiagnosticReport.textShort description 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 idDiagnosticReport.containedShort description 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 | C | 1..* | Extension | Element idDiagnosticReport.extensionShort description 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) Constraints
| ||
| refertoPadre | C | 0..* | Extension(Identifier) | Element idDiagnosticReport.extension:refertoPadreShort description Referto Padre Alternate namesextensions, user content DefinitionSe la naturaDCE è:
è necessario indicare in quest'attributo o il link logico o l'identificativo del documento padre. Può essere di diversi tipi, e si riconosce dal system:
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. https://fhir.siss.regione.lombardia.it/StructureDefinition/ReteLabDiagnosticReportRefertoPadre ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.extension:refertoPadre.idShort description 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 | C | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.extension:refertoPadre.extensionShort description 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
| ||
| url | 1..1 | uriAuto Value | There are no (further) constraints on this element Element idDiagnosticReport.extension:refertoPadre.urlShort description identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. https://fhir.siss.regione.lombardia.it/StructureDefinition/ReteLabDiagnosticReportRefertoPadreMappings
| |||
| value[x] | 0..1 | Element idDiagnosticReport.extension:refertoPadre.value[x]Short description Value of extension DefinitionLink logico al repository o identificativo del documento padre. Unordered, Open, by system(Value) Constraints
| ||||
| valueIdentifier | Identifier | There are no (further) constraints on this element Data type | ||||
| id | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.extension:refertoPadre.value[x].idShort description 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 | C | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.extension:refertoPadre.value[x].extensionShort description 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
| ||
| use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idDiagnosticReport.extension:refertoPadre.value[x].useShort description usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known .
| ||
| type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idDiagnosticReport.extension:refertoPadre.value[x].typeShort description Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible) Constraints
| ||
| system | Σ | 0..1 | uri | There are no (further) constraints on this element Element idDiagnosticReport.extension:refertoPadre.value[x].systemShort description Namespace a cui appartiene il valore identificativo DefinitionDeve essere uno dei seguenti: https://fhir.siss.regione.lombardia.it/CodeSystem/IdentificativoDocTestuale https://fhir.siss.regione.lombardia.it/CodeSystem/IdentificativoDocStrutturato https://fhir.siss.regione.lombardia.it/CodeSystem/LinkDocTestuale https://fhir.siss.regione.lombardia.it/CodeSystem/LinkDocStrutturato There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patientMappings
| ||
| value | Σ | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.extension:refertoPadre.value[x].valueShort description The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456Mappings
| ||
| period | Σ | 0..1 | Period | There are no (further) constraints on this element Element idDiagnosticReport.extension:refertoPadre.value[x].periodShort description Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use.
| ||
| assigner | Σ | 0..1 | Reference(Organization) | There are no (further) constraints on this element Element idDiagnosticReport.extension:refertoPadre.value[x].assignerShort description Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
| ||
| naturaDCE | C | 1..1 | Extension(CodeableConcept) | Element idDiagnosticReport.extension:naturaDCEShort description Indica la natura del DCE da archiviare Alternate namesextensions, user content DefinitionCorrispondente campo HL7 secondo specifiche regionali: TXA-21. Può assumere i seguenti valori:
https://fhir.siss.regione.lombardia.it/StructureDefinition/ReteLabDiagnosticReportRefertatoNaturaDCE ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.extension:naturaDCE.idShort description 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 | C | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.extension:naturaDCE.extensionShort description 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
| ||
| url | 1..1 | uriAuto Value | There are no (further) constraints on this element Element idDiagnosticReport.extension:naturaDCE.urlShort description identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. https://fhir.siss.regione.lombardia.it/StructureDefinition/ReteLabDiagnosticReportRefertatoNaturaDCEMappings
| |||
| value[x] | 0..1 | Binding | Element idDiagnosticReport.extension:naturaDCE.value[x]Short description Natura DCE da archiviare DefinitionValue of extension - must be one of a constrained set of the data types (see Extensibility for a list). Valueset da utilizzare per indicare la natura del referto. Corrispondente al campo HL7 secondo le specifiche regionali: TXA-21. Natura DCE da archiviare (required) Constraints
| |||
| valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
| tipologiaDCE | C | 0..* | Extension(code) | Element idDiagnosticReport.extension:tipologiaDCEShort description Tipologia referto Alternate namesextensions, user content DefinitionCorrispondente campo HL7 secondo specifiche regionali: OBX-3.3 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. https://fhir.siss.regione.lombardia.it/StructureDefinition/ReteLabDiagnosticReportTipologiaDCE ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| noteDocumento | C | 0..* | Extension(Annotation) | Element idDiagnosticReport.extension:noteDocumentoShort description Optional Extensions Element Alternate namesextensions, user content DefinitionDescrive la nota collegata al documento corrispondente campo HL7 secondo specifiche regionali: NTE. Può descrivere le seguenti casistiche:
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. https://fhir.siss.regione.lombardia.it/StructureDefinition/ReteLabDiagnosticReportNote ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| modifierExtension | ?! C | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.modifierExtensionShort description 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.
| ||
| identifier | Σ | 1..2 | Identifier | Element idDiagnosticReport.identifierShort description Identificativo univoco del referto Alternate namesReportID, Filler ID, Placer ID DefinitionIdentificativo univoco del referto:
Need to know what identifier to use when making queries about this report from the source laboratory, and for linking to the report outside FHIR context. Corrispondente campo HL7 secondo specifiche regionali: TXA-12 Unordered, Open, by system(Value) Constraints
| ||
| IdentificativoDocumentoTestuale | Σ | 0..1 | Identifier | Element idDiagnosticReport.identifier:IdentificativoDocumentoTestualeShort description Codice identificativo del documento testuale Alternate namesReportID, Filler ID, Placer ID DefinitionIdentificativo del documento testuale (max 64) Need to know what identifier to use when making queries about this report from the source laboratory, and for linking to the report outside FHIR context. Corrispondente campo HL7 secondo specifiche regionali: TXA-12, EI-1
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.identifier:IdentificativoDocumentoTestuale.idShort description 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 | C | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.identifier:IdentificativoDocumentoTestuale.extensionShort description 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
| ||
| use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idDiagnosticReport.identifier:IdentificativoDocumentoTestuale.useShort description usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known .
| ||
| type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idDiagnosticReport.identifier:IdentificativoDocumentoTestuale.typeShort description Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible) Constraints
| ||
| system | Σ | 0..1 | uriAuto Value | Element idDiagnosticReport.identifier:IdentificativoDocumentoTestuale.systemShort description The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
https://fhir.siss.regione.lombardia.it/sid/codiceIdentificativoDocumentoTestualeExamples General http://www.acme.com/identifiers/patientMappings
| ||
| value | Σ | 0..1 | string | Element idDiagnosticReport.identifier:IdentificativoDocumentoTestuale.valueShort description Identificativo documento testuale DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456Mappings
| ||
| period | Σ | 0..1 | Period | There are no (further) constraints on this element Element idDiagnosticReport.identifier:IdentificativoDocumentoTestuale.periodShort description Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use.
| ||
| assigner | Σ | 0..1 | Reference(Organization) | There are no (further) constraints on this element Element idDiagnosticReport.identifier:IdentificativoDocumentoTestuale.assignerShort description Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
| ||
| IdentificativoDocumentoStrutturato | Σ | 0..1 | Identifier | Element idDiagnosticReport.identifier:IdentificativoDocumentoStrutturatoShort description Business identifier for report Alternate namesReportID, Filler ID, Placer ID DefinitionIdentifiers assigned to this report by the performer or other systems. Need to know what identifier to use when making queries about this report from the source laboratory, and for linking to the report outside FHIR context. Corrispondente campo HL7 secondo specifiche regionali: TXA-12, EI-3
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.identifier:IdentificativoDocumentoStrutturato.idShort description 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 | C | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.identifier:IdentificativoDocumentoStrutturato.extensionShort description 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
| ||
| use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idDiagnosticReport.identifier:IdentificativoDocumentoStrutturato.useShort description usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known .
| ||
| type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idDiagnosticReport.identifier:IdentificativoDocumentoStrutturato.typeShort description Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible) Constraints
| ||
| system | Σ | 0..1 | uriAuto Value | Element idDiagnosticReport.identifier:IdentificativoDocumentoStrutturato.systemShort description The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
https://fhir.siss.regione.lombardia.it/sid/codiceIdentificativoDocumentoStrutturatoExamples General http://www.acme.com/identifiers/patientMappings
| ||
| value | Σ | 0..1 | string | Element idDiagnosticReport.identifier:IdentificativoDocumentoStrutturato.valueShort description Identificativo documento strutturato DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456Mappings
| ||
| period | Σ | 0..1 | Period | There are no (further) constraints on this element Element idDiagnosticReport.identifier:IdentificativoDocumentoStrutturato.periodShort description Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use.
| ||
| assigner | Σ | 0..1 | Reference(Organization) | There are no (further) constraints on this element Element idDiagnosticReport.identifier:IdentificativoDocumentoStrutturato.assignerShort description Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
| ||
| basedOn | 1..* | Reference(ReteLabServiceRequestRichiestaEsamiLab) | Element idDiagnosticReport.basedOnShort description Richiesta di esame di laboratorio di cui si riportano i risultati Alternate namesRequest DefinitionReference al profilo ReteLabServiceRequestRichiestaEsamiLab This allows tracing of authorization for the report and tracking whether proposals/recommendations were acted upon. Note: Usually there is one test request for each result, however in some circumstances multiple test requests may be represented using a single test result resource. Note that there are also cases where one request leads to multiple reports. Reference(ReteLabServiceRequestRichiestaEsamiLab) Constraints
| |||
| status | Σ ?! | 1..1 | codeBindingAuto Value | Element idDiagnosticReport.statusShort description Stato del DiagnosticReport DefinitionThe status of the diagnostic report. Diagnostic services routinely issue provisional/incomplete reports, and sometimes withdraw previously released reports. Corrispondente campo HL7 secondo specifiche regionali: TXA-17 The status of the diagnostic report. DiagnosticReportStatus (required) Constraints
finalMappings
| ||
| category | Σ | 0..* | CodeableConceptAuto Value | Element idDiagnosticReport.categoryShort description Referti di Laboratorio Alternate namesDepartment, Sub-department, Service, Discipline DefinitionValore fisso su LAB --> Laboratorio Multiple categories are allowed using various categorization schemes. The level of granularity is defined by the category concepts in the value set. More fine-grained filtering can be performed using the metadata and/or terminology hierarchy in DiagnosticReport.code. Codes for diagnostic service sections. DiagnosticServiceSectionCodes (example) Constraints
{
"coding": [
{
"code": "LAB",
"display": "Laboratorio"
}
]
}Mappings
| ||
| code | Σ | 1..1 | CodeableConceptBinding | Element idDiagnosticReport.codeShort description Codice diagnosticReport Alternate namesType DefinitionA code or name that describes this diagnostic report. Codes that describe Diagnostic Reports. LOINCDiagnosticReportCodes (preferred) Constraints
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.code.idShort description 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 | C | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.code.extensionShort description 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
| ||
| coding | Σ | 0..* | Coding | Element idDiagnosticReport.code.codingShort description Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. Unordered, Open, by system(Value) Constraints
| ||
| LOINC | Σ | 0..* | CodingBinding | Element idDiagnosticReport.code.coding:LOINCShort description Codifica LOINC che indica il referto di laboratorio. DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
| ||
| TipoDocumento | Σ | 0..* | CodingBinding | Element idDiagnosticReport.code.coding:TipoDocumentoShort description Tipologia documento. DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Corrispondente campo HL7 secondo specifiche regionali: OBX-3.2. Tipologia Documento SISS (required) Constraints
| ||
| TipoDocumentoInterno | Σ | 0..* | CodingBinding | Element idDiagnosticReport.code.coding:TipoDocumentoInternoShort description Tipologia interna di documento. DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Corrispondente campo HL7 secondo specifiche regionali: OBX-3.5. Tipologia documento interno (required) Constraints
| ||
| text | Σ | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.code.textShort description Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
| ||
| subject | Σ | 0..1 | Reference(ReteLabPatientCittadino) | Element idDiagnosticReport.subjectShort description Paziente al quale i risultati degli esami fanno riferimento Alternate namesPatient DefinitionReference al profilo ReteLabPatientCittadino SHALL know the subject context. Reference(ReteLabPatientCittadino) Constraints
| ||
| encounter | Σ | 0..1 | Reference(Encounter) | There are no (further) constraints on this element Element idDiagnosticReport.encounterShort description Health care event when test ordered Alternate namesContext DefinitionThe healthcare event (e.g. a patient and healthcare provider interaction) which this DiagnosticReport is about. Links the request to the Encounter context. This will typically be the encounter the event occurred within, but some events may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter (e.g. pre-admission laboratory tests).
| ||
| effective[x] | Σ | 0..1 | There are no (further) constraints on this element Element idDiagnosticReport.effective[x]Short description Clinically relevant time/time-period for report Alternate namesObservation time, Effective Time, Occurrence DefinitionThe time or time-period the observed values are related to. When the subject of the report is a patient, this is usually either the time of the procedure or of specimen collection(s), but very often the source of the date/time is not known, only the date/time itself. Need to know where in the patient history to file/present this report. If the diagnostic procedure was performed on the patient, this is the time it was performed. If there are specimens, the diagnostically relevant time can be derived from the specimen collection times, but the specimen information is not always available, and the exact relationship between the specimens and the diagnostically relevant time is not always automatic.
| |||
| effectiveDateTime | dateTime | There are no (further) constraints on this element Data type | ||||
| effectivePeriod | Period | There are no (further) constraints on this element Data type | ||||
| issued | Σ | 0..1 | instant | Element idDiagnosticReport.issuedShort description Data e ora di firma del documento Alternate namesDate published, Date Issued, Date Verified DefinitionObbligatorio per documenti firmati e/o marcati. Formato: YYYY-MM-DDThh:mm:ss+zz:zz secondo lo standard FHIR Clinicians need to be able to check the date that the report was released. Corrispondente campo HL7 secondo specifiche regionali: TXA-22
| ||
| performer | Σ | 0..* | Reference(Practitioner | PractitionerRole | Organization | CareTeam) | There are no (further) constraints on this element Element idDiagnosticReport.performerShort description Responsible Diagnostic Service Alternate namesLaboratory, Service, Practitioner, Department, Company, Authorized by, Director DefinitionThe diagnostic service that is responsible for issuing the report. Need to know whom to contact if there are queries about the results. Also may need to track the source of reports for secondary data analysis. This is not necessarily the source of the atomic data items or the entity that interpreted the results. It is the entity that takes responsibility for the clinical report. Reference(Practitioner | PractitionerRole | Organization | CareTeam) Constraints
| ||
| resultsInterpreter | Σ | 0..* | Reference(ReteLabPractitionerRoleMedico) | Element idDiagnosticReport.resultsInterpreterShort description Dati dell'operatore che compila e referta Alternate namesAnalyzed by, Reported by DefinitionReference al profilo ReteLabPractitionerRoleMedico Need to know whom to contact if there are queries about the results. Also may need to track the source of reports for secondary data analysis. Corrispondente campo HL7 secondo specifiche regionali: TXA-11 e PV1-8 Reference(ReteLabPractitionerRoleMedico) Constraints
| ||
| specimen | 0..* | Reference(Specimen) | There are no (further) constraints on this element Element idDiagnosticReport.specimenShort description Specimens this report is based on DefinitionDetails about the specimens on which this diagnostic report is based. Need to be able to report information about the collected specimens on which the report is based. If the specimen is sufficiently specified with a code in the test result name, then this additional data may be redundant. If there are multiple specimens, these may be represented per observation or group.
| |||
| result | 0..* | Reference(Observation) | There are no (further) constraints on this element Element idDiagnosticReport.resultShort description Observations Alternate namesData, Atomic Value, Result, Atomic result, Data, Test, Analyte, Battery, Organizer DefinitionObservations that are part of this diagnostic report. Need to support individual results, or groups of results, where the result grouping is arbitrary, but meaningful. Observations can contain observations.
| |||
| imagingStudy | 0..* | Reference(ImagingStudy) | There are no (further) constraints on this element Element idDiagnosticReport.imagingStudyShort description Reference to full details of imaging associated with the diagnostic report DefinitionOne or more links to full details of any imaging performed during the diagnostic investigation. Typically, this is imaging performed by DICOM enabled modalities, but this is not required. A fully enabled PACS viewer can use this information to provide views of the source images. ImagingStudy and the image element are somewhat overlapping - typically, the list of image references in the image element will also be found in one of the imaging study resources. However, each caters to different types of displays for different types of purposes. Neither, either, or both may be provided.
| |||
| media | Σ | 0..* | BackboneElement | There are no (further) constraints on this element Element idDiagnosticReport.mediaShort description Key images associated with this report Alternate namesDICOM, Slides, Scans DefinitionA list of key images associated with this report. The images are generally created during the diagnostic process, and may be directly of the patient, or of treated specimens (i.e. slides of interest). Many diagnostic services include images in the report as part of their service.
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.media.idShort description 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 | C | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.media.extensionShort description 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.
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.media.modifierExtensionShort description 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.
| ||
| comment | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.media.commentShort description Comment about the image (e.g. explanation) DefinitionA comment about the image. Typically, this is used to provide an explanation for why the image is included, or to draw the viewer's attention to important features. The provider of the report should make a comment about each image included in the report. The comment should be displayed with the image. It would be common for the report to include additional discussion of the image contents in other sections such as the conclusion.
| |||
| link | Σ | 1..1 | Reference(Media) | There are no (further) constraints on this element Element idDiagnosticReport.media.linkShort description Reference to the image source DefinitionReference to the image source.
| ||
| conclusion | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.conclusionShort description Clinical conclusion (interpretation) of test results Alternate namesReport DefinitionConcise and clinically contextualized summary conclusion (interpretation/impression) of the diagnostic report. Need to be able to provide a conclusion that is not lost among the basic result data.
| |||
| conclusionCode | 0..* | CodeableConcept | There are no (further) constraints on this element Element idDiagnosticReport.conclusionCodeShort description Codes for the clinical conclusion of test results DefinitionOne or more codes that represent the summary conclusion (interpretation/impression) of the diagnostic report. Diagnosis codes provided as adjuncts to the report. SNOMEDCTClinicalFindings (example) Constraints
| |||
| presentedForm | 1..2 | Attachment | Element idDiagnosticReport.presentedFormShort description Documento Allegato DefinitionContenuto da archiviare (documento o link). In questo campo verranno allegati il documento in formato PDF e quello in formato CDA-2. Gives laboratory the ability to provide its own fully formatted report for clinical fidelity. Corrispondente campo HL7 secondo specifiche regionali: OBX-5
| |||
| id | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.presentedForm.idShort description 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 | C | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.presentedForm.extensionShort description 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
| ||
| contentType | Σ | 0..1 | codeBinding | Element idDiagnosticReport.presentedForm.contentTypeShort description Formato documento Definitiontipo fisico del documento (obbligatorio). Valori ammessi:
Processors of the data need to be able to know how to interpret the data. Corrispondente campo HL7 secondo specifiche regionali: OBX-3 CE-6 OBX-5 : Contenuto da archiviare (documento o link). La compilazione del campo varia in funzione del contenuto: Documento OBX-5.2 = multipart OBX-5.3 = Octed-stream OBX-5.4 = Base64 OBX-5.5 = documento codificato in Base64 The mime type of an attachment. Any valid mime type is allowed.
General text/plain; charset=UTF-8, image/pngMappings
| ||
| language | Σ | 0..1 | codeBinding | There are no (further) constraints on this element Element idDiagnosticReport.presentedForm.languageShort description Human language of the content (BCP-47) DefinitionThe human language of the content. The value can be any valid value according to BCP 47. Users need to be able to choose between the languages in a set of attachments. A human language.
General en-AUMappings
| ||
| data | 0..1 | base64Binary | Element idDiagnosticReport.presentedForm.dataShort description Documento codificato in base64 DefinitionTale campo sarà sempre valorizzato come "Documento codificato in base64" The data needs to able to be transmitted inline. Corrispondente campo HL7 secondo specifiche regionali: OBX-5.5
| |||
| url | Σ | 0..1 | url | There are no (further) constraints on this element Element idDiagnosticReport.presentedForm.urlShort description Uri where the data can be found DefinitionA location where the data can be accessed. The data needs to be transmitted by reference. If both data and url are provided, the url SHALL point to the same content as the data contains. Urls may be relative references or may reference transient locations such as a wrapping envelope using cid: though this has ramifications for using signatures. Relative URLs are interpreted relative to the service url, like a resource reference, rather than relative to the resource itself. If a URL is provided, it SHALL resolve to actual data.
General http://www.acme.com/logo-small.pngMappings
| ||
| size | Σ | 0..1 | unsignedInt | There are no (further) constraints on this element Element idDiagnosticReport.presentedForm.sizeShort description Number of bytes of content (if url provided) DefinitionThe number of bytes of data that make up this attachment (before base64 encoding, if that is done). Representing the size allows applications to determine whether they should fetch the content automatically in advance, or refuse to fetch it at all. The number of bytes is redundant if the data is provided as a base64binary, but is useful if the data is provided as a url reference.
| ||
| hash | Σ | 0..1 | base64Binary | There are no (further) constraints on this element Element idDiagnosticReport.presentedForm.hashShort description Hash of the data (sha-1, base64ed) DefinitionThe calculated hash of the data using SHA-1. Represented using base64. Included so that applications can verify that the contents of a location have not changed due to technical failures (e.g., storage rot, transport glitch, incorrect version). The hash is calculated on the data prior to base64 encoding, if the data is based64 encoded. The hash is not intended to support digital signatures. Where protection against malicious threats a digital signature should be considered, see Provenance.signature for mechanism to protect a resource with a digital signature.
| ||
| title | Σ | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.presentedForm.titleShort description Label to display in place of the data DefinitionA label or set of text to display in place of the data. Applications need a label to display to a human user in place of the actual data if the data cannot be rendered or perceived by the viewer.
General Official Corporate LogoMappings
| ||
| creation | Σ | 0..1 | dateTime | Element idDiagnosticReport.presentedForm.creationShort description Data e ora compilazione del documento DefinitionFormato: YYYY-MM-DDThh:mm:ss+zz:zz secondo lo standard FHIR This is often tracked as an integrity issue for use of the attachment. Corrispondente campo HL7 secondo specifiche regionali: TXA-6
|
Differential View
| ReteLabDiagnosticReportRefertato (DiagnosticReport) | C | DiagnosticReport | Element idDiagnosticReportShort description Profilo che contiene informazioni relative al referto degli esami di laboratorio. Alternate namesReport, Test, Result, Results, Labs, Laboratory DefinitionQuesto profilo può essere presente nei seguenti flussi: "Notifica refertato da LS a LR" This is intended to capture a single report and is not suitable for use in displaying summary information that covers multiple reports. For example, this resource has not been designed for laboratory cumulative reporting formats nor detailed structured reports for sequencing.
| |||
| id | Σ | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.idShort description 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 idDiagnosticReport.metaShort description 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 idDiagnosticReport.implicitRulesShort description 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 idDiagnosticReport.languageShort description 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 idDiagnosticReport.textShort description 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 idDiagnosticReport.containedShort description 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 | C | 1..* | Extension | Element idDiagnosticReport.extensionShort description 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) Constraints
| ||
| refertoPadre | C | 0..* | Extension(Identifier) | Element idDiagnosticReport.extension:refertoPadreShort description Referto Padre Alternate namesextensions, user content DefinitionSe la naturaDCE è:
è necessario indicare in quest'attributo o il link logico o l'identificativo del documento padre. Può essere di diversi tipi, e si riconosce dal system:
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. https://fhir.siss.regione.lombardia.it/StructureDefinition/ReteLabDiagnosticReportRefertoPadre ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.extension:refertoPadre.idShort description 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 | C | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.extension:refertoPadre.extensionShort description 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
| ||
| url | 1..1 | uriAuto Value | There are no (further) constraints on this element Element idDiagnosticReport.extension:refertoPadre.urlShort description identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. https://fhir.siss.regione.lombardia.it/StructureDefinition/ReteLabDiagnosticReportRefertoPadreMappings
| |||
| value[x] | 0..1 | Element idDiagnosticReport.extension:refertoPadre.value[x]Short description Value of extension DefinitionLink logico al repository o identificativo del documento padre. Unordered, Open, by system(Value) Constraints
| ||||
| valueIdentifier | Identifier | There are no (further) constraints on this element Data type | ||||
| id | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.extension:refertoPadre.value[x].idShort description 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 | C | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.extension:refertoPadre.value[x].extensionShort description 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
| ||
| use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idDiagnosticReport.extension:refertoPadre.value[x].useShort description usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known .
| ||
| type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idDiagnosticReport.extension:refertoPadre.value[x].typeShort description Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible) Constraints
| ||
| system | Σ | 0..1 | uri | There are no (further) constraints on this element Element idDiagnosticReport.extension:refertoPadre.value[x].systemShort description Namespace a cui appartiene il valore identificativo DefinitionDeve essere uno dei seguenti: https://fhir.siss.regione.lombardia.it/CodeSystem/IdentificativoDocTestuale https://fhir.siss.regione.lombardia.it/CodeSystem/IdentificativoDocStrutturato https://fhir.siss.regione.lombardia.it/CodeSystem/LinkDocTestuale https://fhir.siss.regione.lombardia.it/CodeSystem/LinkDocStrutturato There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patientMappings
| ||
| value | Σ | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.extension:refertoPadre.value[x].valueShort description The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456Mappings
| ||
| period | Σ | 0..1 | Period | There are no (further) constraints on this element Element idDiagnosticReport.extension:refertoPadre.value[x].periodShort description Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use.
| ||
| assigner | Σ | 0..1 | Reference(Organization) | There are no (further) constraints on this element Element idDiagnosticReport.extension:refertoPadre.value[x].assignerShort description Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
| ||
| naturaDCE | C | 1..1 | Extension(CodeableConcept) | Element idDiagnosticReport.extension:naturaDCEShort description Indica la natura del DCE da archiviare Alternate namesextensions, user content DefinitionCorrispondente campo HL7 secondo specifiche regionali: TXA-21. Può assumere i seguenti valori:
https://fhir.siss.regione.lombardia.it/StructureDefinition/ReteLabDiagnosticReportRefertatoNaturaDCE ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.extension:naturaDCE.idShort description 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 | C | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.extension:naturaDCE.extensionShort description 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
| ||
| url | 1..1 | uriAuto Value | There are no (further) constraints on this element Element idDiagnosticReport.extension:naturaDCE.urlShort description identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. https://fhir.siss.regione.lombardia.it/StructureDefinition/ReteLabDiagnosticReportRefertatoNaturaDCEMappings
| |||
| value[x] | 0..1 | Binding | Element idDiagnosticReport.extension:naturaDCE.value[x]Short description Natura DCE da archiviare DefinitionValue of extension - must be one of a constrained set of the data types (see Extensibility for a list). Valueset da utilizzare per indicare la natura del referto. Corrispondente al campo HL7 secondo le specifiche regionali: TXA-21. Natura DCE da archiviare (required) Constraints
| |||
| valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
| tipologiaDCE | C | 0..* | Extension(code) | Element idDiagnosticReport.extension:tipologiaDCEShort description Tipologia referto Alternate namesextensions, user content DefinitionCorrispondente campo HL7 secondo specifiche regionali: OBX-3.3 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. https://fhir.siss.regione.lombardia.it/StructureDefinition/ReteLabDiagnosticReportTipologiaDCE ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| noteDocumento | C | 0..* | Extension(Annotation) | Element idDiagnosticReport.extension:noteDocumentoShort description Optional Extensions Element Alternate namesextensions, user content DefinitionDescrive la nota collegata al documento corrispondente campo HL7 secondo specifiche regionali: NTE. Può descrivere le seguenti casistiche:
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. https://fhir.siss.regione.lombardia.it/StructureDefinition/ReteLabDiagnosticReportNote ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| modifierExtension | ?! C | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.modifierExtensionShort description 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.
| ||
| identifier | Σ | 1..2 | Identifier | Element idDiagnosticReport.identifierShort description Identificativo univoco del referto Alternate namesReportID, Filler ID, Placer ID DefinitionIdentificativo univoco del referto:
Need to know what identifier to use when making queries about this report from the source laboratory, and for linking to the report outside FHIR context. Corrispondente campo HL7 secondo specifiche regionali: TXA-12 Unordered, Open, by system(Value) Constraints
| ||
| IdentificativoDocumentoTestuale | Σ | 0..1 | Identifier | Element idDiagnosticReport.identifier:IdentificativoDocumentoTestualeShort description Codice identificativo del documento testuale Alternate namesReportID, Filler ID, Placer ID DefinitionIdentificativo del documento testuale (max 64) Need to know what identifier to use when making queries about this report from the source laboratory, and for linking to the report outside FHIR context. Corrispondente campo HL7 secondo specifiche regionali: TXA-12, EI-1
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.identifier:IdentificativoDocumentoTestuale.idShort description 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 | C | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.identifier:IdentificativoDocumentoTestuale.extensionShort description 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
| ||
| use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idDiagnosticReport.identifier:IdentificativoDocumentoTestuale.useShort description usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known .
| ||
| type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idDiagnosticReport.identifier:IdentificativoDocumentoTestuale.typeShort description Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible) Constraints
| ||
| system | Σ | 0..1 | uriAuto Value | Element idDiagnosticReport.identifier:IdentificativoDocumentoTestuale.systemShort description The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
https://fhir.siss.regione.lombardia.it/sid/codiceIdentificativoDocumentoTestualeExamples General http://www.acme.com/identifiers/patientMappings
| ||
| value | Σ | 0..1 | string | Element idDiagnosticReport.identifier:IdentificativoDocumentoTestuale.valueShort description Identificativo documento testuale DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456Mappings
| ||
| period | Σ | 0..1 | Period | There are no (further) constraints on this element Element idDiagnosticReport.identifier:IdentificativoDocumentoTestuale.periodShort description Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use.
| ||
| assigner | Σ | 0..1 | Reference(Organization) | There are no (further) constraints on this element Element idDiagnosticReport.identifier:IdentificativoDocumentoTestuale.assignerShort description Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
| ||
| IdentificativoDocumentoStrutturato | Σ | 0..1 | Identifier | Element idDiagnosticReport.identifier:IdentificativoDocumentoStrutturatoShort description Business identifier for report Alternate namesReportID, Filler ID, Placer ID DefinitionIdentifiers assigned to this report by the performer or other systems. Need to know what identifier to use when making queries about this report from the source laboratory, and for linking to the report outside FHIR context. Corrispondente campo HL7 secondo specifiche regionali: TXA-12, EI-3
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.identifier:IdentificativoDocumentoStrutturato.idShort description 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 | C | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.identifier:IdentificativoDocumentoStrutturato.extensionShort description 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
| ||
| use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idDiagnosticReport.identifier:IdentificativoDocumentoStrutturato.useShort description usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known .
| ||
| type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idDiagnosticReport.identifier:IdentificativoDocumentoStrutturato.typeShort description Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible) Constraints
| ||
| system | Σ | 0..1 | uriAuto Value | Element idDiagnosticReport.identifier:IdentificativoDocumentoStrutturato.systemShort description The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
https://fhir.siss.regione.lombardia.it/sid/codiceIdentificativoDocumentoStrutturatoExamples General http://www.acme.com/identifiers/patientMappings
| ||
| value | Σ | 0..1 | string | Element idDiagnosticReport.identifier:IdentificativoDocumentoStrutturato.valueShort description Identificativo documento strutturato DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456Mappings
| ||
| period | Σ | 0..1 | Period | There are no (further) constraints on this element Element idDiagnosticReport.identifier:IdentificativoDocumentoStrutturato.periodShort description Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use.
| ||
| assigner | Σ | 0..1 | Reference(Organization) | There are no (further) constraints on this element Element idDiagnosticReport.identifier:IdentificativoDocumentoStrutturato.assignerShort description Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
| ||
| basedOn | 1..* | Reference(ReteLabServiceRequestRichiestaEsamiLab) | Element idDiagnosticReport.basedOnShort description Richiesta di esame di laboratorio di cui si riportano i risultati Alternate namesRequest DefinitionReference al profilo ReteLabServiceRequestRichiestaEsamiLab This allows tracing of authorization for the report and tracking whether proposals/recommendations were acted upon. Note: Usually there is one test request for each result, however in some circumstances multiple test requests may be represented using a single test result resource. Note that there are also cases where one request leads to multiple reports. Reference(ReteLabServiceRequestRichiestaEsamiLab) Constraints
| |||
| status | Σ ?! | 1..1 | codeBindingAuto Value | Element idDiagnosticReport.statusShort description Stato del DiagnosticReport DefinitionThe status of the diagnostic report. Diagnostic services routinely issue provisional/incomplete reports, and sometimes withdraw previously released reports. Corrispondente campo HL7 secondo specifiche regionali: TXA-17 The status of the diagnostic report. DiagnosticReportStatus (required) Constraints
finalMappings
| ||
| category | Σ | 0..* | CodeableConceptAuto Value | Element idDiagnosticReport.categoryShort description Referti di Laboratorio Alternate namesDepartment, Sub-department, Service, Discipline DefinitionValore fisso su LAB --> Laboratorio Multiple categories are allowed using various categorization schemes. The level of granularity is defined by the category concepts in the value set. More fine-grained filtering can be performed using the metadata and/or terminology hierarchy in DiagnosticReport.code. Codes for diagnostic service sections. DiagnosticServiceSectionCodes (example) Constraints
{
"coding": [
{
"code": "LAB",
"display": "Laboratorio"
}
]
}Mappings
| ||
| code | Σ | 1..1 | CodeableConceptBinding | Element idDiagnosticReport.codeShort description Codice diagnosticReport Alternate namesType DefinitionA code or name that describes this diagnostic report. Codes that describe Diagnostic Reports. LOINCDiagnosticReportCodes (preferred) Constraints
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.code.idShort description 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 | C | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.code.extensionShort description 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
| ||
| coding | Σ | 0..* | Coding | Element idDiagnosticReport.code.codingShort description Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. Unordered, Open, by system(Value) Constraints
| ||
| LOINC | Σ | 0..* | CodingBinding | Element idDiagnosticReport.code.coding:LOINCShort description Codifica LOINC che indica il referto di laboratorio. DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
| ||
| TipoDocumento | Σ | 0..* | CodingBinding | Element idDiagnosticReport.code.coding:TipoDocumentoShort description Tipologia documento. DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Corrispondente campo HL7 secondo specifiche regionali: OBX-3.2. Tipologia Documento SISS (required) Constraints
| ||
| TipoDocumentoInterno | Σ | 0..* | CodingBinding | Element idDiagnosticReport.code.coding:TipoDocumentoInternoShort description Tipologia interna di documento. DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Corrispondente campo HL7 secondo specifiche regionali: OBX-3.5. Tipologia documento interno (required) Constraints
| ||
| text | Σ | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.code.textShort description Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
| ||
| subject | Σ | 0..1 | Reference(ReteLabPatientCittadino) | Element idDiagnosticReport.subjectShort description Paziente al quale i risultati degli esami fanno riferimento Alternate namesPatient DefinitionReference al profilo ReteLabPatientCittadino SHALL know the subject context. Reference(ReteLabPatientCittadino) Constraints
| ||
| encounter | Σ | 0..1 | Reference(Encounter) | There are no (further) constraints on this element Element idDiagnosticReport.encounterShort description Health care event when test ordered Alternate namesContext DefinitionThe healthcare event (e.g. a patient and healthcare provider interaction) which this DiagnosticReport is about. Links the request to the Encounter context. This will typically be the encounter the event occurred within, but some events may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter (e.g. pre-admission laboratory tests).
| ||
| effective[x] | Σ | 0..1 | There are no (further) constraints on this element Element idDiagnosticReport.effective[x]Short description Clinically relevant time/time-period for report Alternate namesObservation time, Effective Time, Occurrence DefinitionThe time or time-period the observed values are related to. When the subject of the report is a patient, this is usually either the time of the procedure or of specimen collection(s), but very often the source of the date/time is not known, only the date/time itself. Need to know where in the patient history to file/present this report. If the diagnostic procedure was performed on the patient, this is the time it was performed. If there are specimens, the diagnostically relevant time can be derived from the specimen collection times, but the specimen information is not always available, and the exact relationship between the specimens and the diagnostically relevant time is not always automatic.
| |||
| effectiveDateTime | dateTime | There are no (further) constraints on this element Data type | ||||
| effectivePeriod | Period | There are no (further) constraints on this element Data type | ||||
| issued | Σ | 0..1 | instant | Element idDiagnosticReport.issuedShort description Data e ora di firma del documento Alternate namesDate published, Date Issued, Date Verified DefinitionObbligatorio per documenti firmati e/o marcati. Formato: YYYY-MM-DDThh:mm:ss+zz:zz secondo lo standard FHIR Clinicians need to be able to check the date that the report was released. Corrispondente campo HL7 secondo specifiche regionali: TXA-22
| ||
| performer | Σ | 0..* | Reference(Practitioner | PractitionerRole | Organization | CareTeam) | There are no (further) constraints on this element Element idDiagnosticReport.performerShort description Responsible Diagnostic Service Alternate namesLaboratory, Service, Practitioner, Department, Company, Authorized by, Director DefinitionThe diagnostic service that is responsible for issuing the report. Need to know whom to contact if there are queries about the results. Also may need to track the source of reports for secondary data analysis. This is not necessarily the source of the atomic data items or the entity that interpreted the results. It is the entity that takes responsibility for the clinical report. Reference(Practitioner | PractitionerRole | Organization | CareTeam) Constraints
| ||
| resultsInterpreter | Σ | 0..* | Reference(ReteLabPractitionerRoleMedico) | Element idDiagnosticReport.resultsInterpreterShort description Dati dell'operatore che compila e referta Alternate namesAnalyzed by, Reported by DefinitionReference al profilo ReteLabPractitionerRoleMedico Need to know whom to contact if there are queries about the results. Also may need to track the source of reports for secondary data analysis. Corrispondente campo HL7 secondo specifiche regionali: TXA-11 e PV1-8 Reference(ReteLabPractitionerRoleMedico) Constraints
| ||
| specimen | 0..* | Reference(Specimen) | There are no (further) constraints on this element Element idDiagnosticReport.specimenShort description Specimens this report is based on DefinitionDetails about the specimens on which this diagnostic report is based. Need to be able to report information about the collected specimens on which the report is based. If the specimen is sufficiently specified with a code in the test result name, then this additional data may be redundant. If there are multiple specimens, these may be represented per observation or group.
| |||
| result | 0..* | Reference(Observation) | There are no (further) constraints on this element Element idDiagnosticReport.resultShort description Observations Alternate namesData, Atomic Value, Result, Atomic result, Data, Test, Analyte, Battery, Organizer DefinitionObservations that are part of this diagnostic report. Need to support individual results, or groups of results, where the result grouping is arbitrary, but meaningful. Observations can contain observations.
| |||
| imagingStudy | 0..* | Reference(ImagingStudy) | There are no (further) constraints on this element Element idDiagnosticReport.imagingStudyShort description Reference to full details of imaging associated with the diagnostic report DefinitionOne or more links to full details of any imaging performed during the diagnostic investigation. Typically, this is imaging performed by DICOM enabled modalities, but this is not required. A fully enabled PACS viewer can use this information to provide views of the source images. ImagingStudy and the image element are somewhat overlapping - typically, the list of image references in the image element will also be found in one of the imaging study resources. However, each caters to different types of displays for different types of purposes. Neither, either, or both may be provided.
| |||
| media | Σ | 0..* | BackboneElement | There are no (further) constraints on this element Element idDiagnosticReport.mediaShort description Key images associated with this report Alternate namesDICOM, Slides, Scans DefinitionA list of key images associated with this report. The images are generally created during the diagnostic process, and may be directly of the patient, or of treated specimens (i.e. slides of interest). Many diagnostic services include images in the report as part of their service.
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.media.idShort description 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 | C | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.media.extensionShort description 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.
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.media.modifierExtensionShort description 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.
| ||
| comment | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.media.commentShort description Comment about the image (e.g. explanation) DefinitionA comment about the image. Typically, this is used to provide an explanation for why the image is included, or to draw the viewer's attention to important features. The provider of the report should make a comment about each image included in the report. The comment should be displayed with the image. It would be common for the report to include additional discussion of the image contents in other sections such as the conclusion.
| |||
| link | Σ | 1..1 | Reference(Media) | There are no (further) constraints on this element Element idDiagnosticReport.media.linkShort description Reference to the image source DefinitionReference to the image source.
| ||
| conclusion | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.conclusionShort description Clinical conclusion (interpretation) of test results Alternate namesReport DefinitionConcise and clinically contextualized summary conclusion (interpretation/impression) of the diagnostic report. Need to be able to provide a conclusion that is not lost among the basic result data.
| |||
| conclusionCode | 0..* | CodeableConcept | There are no (further) constraints on this element Element idDiagnosticReport.conclusionCodeShort description Codes for the clinical conclusion of test results DefinitionOne or more codes that represent the summary conclusion (interpretation/impression) of the diagnostic report. Diagnosis codes provided as adjuncts to the report. SNOMEDCTClinicalFindings (example) Constraints
| |||
| presentedForm | 1..2 | Attachment | Element idDiagnosticReport.presentedFormShort description Documento Allegato DefinitionContenuto da archiviare (documento o link). In questo campo verranno allegati il documento in formato PDF e quello in formato CDA-2. Gives laboratory the ability to provide its own fully formatted report for clinical fidelity. Corrispondente campo HL7 secondo specifiche regionali: OBX-5
| |||
| id | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.presentedForm.idShort description 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 | C | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.presentedForm.extensionShort description 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
| ||
| contentType | Σ | 0..1 | codeBinding | Element idDiagnosticReport.presentedForm.contentTypeShort description Formato documento Definitiontipo fisico del documento (obbligatorio). Valori ammessi:
Processors of the data need to be able to know how to interpret the data. Corrispondente campo HL7 secondo specifiche regionali: OBX-3 CE-6 OBX-5 : Contenuto da archiviare (documento o link). La compilazione del campo varia in funzione del contenuto: Documento OBX-5.2 = multipart OBX-5.3 = Octed-stream OBX-5.4 = Base64 OBX-5.5 = documento codificato in Base64 The mime type of an attachment. Any valid mime type is allowed.
General text/plain; charset=UTF-8, image/pngMappings
| ||
| language | Σ | 0..1 | codeBinding | There are no (further) constraints on this element Element idDiagnosticReport.presentedForm.languageShort description Human language of the content (BCP-47) DefinitionThe human language of the content. The value can be any valid value according to BCP 47. Users need to be able to choose between the languages in a set of attachments. A human language.
General en-AUMappings
| ||
| data | 0..1 | base64Binary | Element idDiagnosticReport.presentedForm.dataShort description Documento codificato in base64 DefinitionTale campo sarà sempre valorizzato come "Documento codificato in base64" The data needs to able to be transmitted inline. Corrispondente campo HL7 secondo specifiche regionali: OBX-5.5
| |||
| url | Σ | 0..1 | url | There are no (further) constraints on this element Element idDiagnosticReport.presentedForm.urlShort description Uri where the data can be found DefinitionA location where the data can be accessed. The data needs to be transmitted by reference. If both data and url are provided, the url SHALL point to the same content as the data contains. Urls may be relative references or may reference transient locations such as a wrapping envelope using cid: though this has ramifications for using signatures. Relative URLs are interpreted relative to the service url, like a resource reference, rather than relative to the resource itself. If a URL is provided, it SHALL resolve to actual data.
General http://www.acme.com/logo-small.pngMappings
| ||
| size | Σ | 0..1 | unsignedInt | There are no (further) constraints on this element Element idDiagnosticReport.presentedForm.sizeShort description Number of bytes of content (if url provided) DefinitionThe number of bytes of data that make up this attachment (before base64 encoding, if that is done). Representing the size allows applications to determine whether they should fetch the content automatically in advance, or refuse to fetch it at all. The number of bytes is redundant if the data is provided as a base64binary, but is useful if the data is provided as a url reference.
| ||
| hash | Σ | 0..1 | base64Binary | There are no (further) constraints on this element Element idDiagnosticReport.presentedForm.hashShort description Hash of the data (sha-1, base64ed) DefinitionThe calculated hash of the data using SHA-1. Represented using base64. Included so that applications can verify that the contents of a location have not changed due to technical failures (e.g., storage rot, transport glitch, incorrect version). The hash is calculated on the data prior to base64 encoding, if the data is based64 encoded. The hash is not intended to support digital signatures. Where protection against malicious threats a digital signature should be considered, see Provenance.signature for mechanism to protect a resource with a digital signature.
| ||
| title | Σ | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.presentedForm.titleShort description Label to display in place of the data DefinitionA label or set of text to display in place of the data. Applications need a label to display to a human user in place of the actual data if the data cannot be rendered or perceived by the viewer.
General Official Corporate LogoMappings
| ||
| creation | Σ | 0..1 | dateTime | Element idDiagnosticReport.presentedForm.creationShort description Data e ora compilazione del documento DefinitionFormato: YYYY-MM-DDThh:mm:ss+zz:zz secondo lo standard FHIR This is often tracked as an integrity issue for use of the attachment. Corrispondente campo HL7 secondo specifiche regionali: TXA-6
|
Hybrid View
| ReteLabDiagnosticReportRefertato (DiagnosticReport) | C | DiagnosticReport | Element idDiagnosticReportShort description Profilo che contiene informazioni relative al referto degli esami di laboratorio. Alternate namesReport, Test, Result, Results, Labs, Laboratory DefinitionQuesto profilo può essere presente nei seguenti flussi: "Notifica refertato da LS a LR" This is intended to capture a single report and is not suitable for use in displaying summary information that covers multiple reports. For example, this resource has not been designed for laboratory cumulative reporting formats nor detailed structured reports for sequencing.
| |||
| id | Σ | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.idShort description 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 idDiagnosticReport.metaShort description 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 idDiagnosticReport.implicitRulesShort description 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 idDiagnosticReport.languageShort description 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 idDiagnosticReport.textShort description 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 idDiagnosticReport.containedShort description 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 | C | 1..* | Extension | Element idDiagnosticReport.extensionShort description 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) Constraints
| ||
| refertoPadre | C | 0..* | Extension(Identifier) | Element idDiagnosticReport.extension:refertoPadreShort description Referto Padre Alternate namesextensions, user content DefinitionSe la naturaDCE è:
è necessario indicare in quest'attributo o il link logico o l'identificativo del documento padre. Può essere di diversi tipi, e si riconosce dal system:
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. https://fhir.siss.regione.lombardia.it/StructureDefinition/ReteLabDiagnosticReportRefertoPadre ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.extension:refertoPadre.idShort description 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 | C | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.extension:refertoPadre.extensionShort description 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
| ||
| url | 1..1 | uriAuto Value | There are no (further) constraints on this element Element idDiagnosticReport.extension:refertoPadre.urlShort description identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. https://fhir.siss.regione.lombardia.it/StructureDefinition/ReteLabDiagnosticReportRefertoPadreMappings
| |||
| value[x] | 0..1 | Element idDiagnosticReport.extension:refertoPadre.value[x]Short description Value of extension DefinitionLink logico al repository o identificativo del documento padre. Unordered, Open, by system(Value) Constraints
| ||||
| valueIdentifier | Identifier | There are no (further) constraints on this element Data type | ||||
| id | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.extension:refertoPadre.value[x].idShort description 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 | C | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.extension:refertoPadre.value[x].extensionShort description 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
| ||
| use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idDiagnosticReport.extension:refertoPadre.value[x].useShort description usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known .
| ||
| type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idDiagnosticReport.extension:refertoPadre.value[x].typeShort description Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible) Constraints
| ||
| system | Σ | 0..1 | uri | There are no (further) constraints on this element Element idDiagnosticReport.extension:refertoPadre.value[x].systemShort description Namespace a cui appartiene il valore identificativo DefinitionDeve essere uno dei seguenti: https://fhir.siss.regione.lombardia.it/CodeSystem/IdentificativoDocTestuale https://fhir.siss.regione.lombardia.it/CodeSystem/IdentificativoDocStrutturato https://fhir.siss.regione.lombardia.it/CodeSystem/LinkDocTestuale https://fhir.siss.regione.lombardia.it/CodeSystem/LinkDocStrutturato There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patientMappings
| ||
| value | Σ | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.extension:refertoPadre.value[x].valueShort description The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456Mappings
| ||
| period | Σ | 0..1 | Period | There are no (further) constraints on this element Element idDiagnosticReport.extension:refertoPadre.value[x].periodShort description Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use.
| ||
| assigner | Σ | 0..1 | Reference(Organization) | There are no (further) constraints on this element Element idDiagnosticReport.extension:refertoPadre.value[x].assignerShort description Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
| ||
| naturaDCE | C | 1..1 | Extension(CodeableConcept) | Element idDiagnosticReport.extension:naturaDCEShort description Indica la natura del DCE da archiviare Alternate namesextensions, user content DefinitionCorrispondente campo HL7 secondo specifiche regionali: TXA-21. Può assumere i seguenti valori:
https://fhir.siss.regione.lombardia.it/StructureDefinition/ReteLabDiagnosticReportRefertatoNaturaDCE ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.extension:naturaDCE.idShort description 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 | C | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.extension:naturaDCE.extensionShort description 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
| ||
| url | 1..1 | uriAuto Value | There are no (further) constraints on this element Element idDiagnosticReport.extension:naturaDCE.urlShort description identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. https://fhir.siss.regione.lombardia.it/StructureDefinition/ReteLabDiagnosticReportRefertatoNaturaDCEMappings
| |||
| value[x] | 0..1 | Binding | Element idDiagnosticReport.extension:naturaDCE.value[x]Short description Natura DCE da archiviare DefinitionValue of extension - must be one of a constrained set of the data types (see Extensibility for a list). Valueset da utilizzare per indicare la natura del referto. Corrispondente al campo HL7 secondo le specifiche regionali: TXA-21. Natura DCE da archiviare (required) Constraints
| |||
| valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
| tipologiaDCE | C | 0..* | Extension(code) | Element idDiagnosticReport.extension:tipologiaDCEShort description Tipologia referto Alternate namesextensions, user content DefinitionCorrispondente campo HL7 secondo specifiche regionali: OBX-3.3 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. https://fhir.siss.regione.lombardia.it/StructureDefinition/ReteLabDiagnosticReportTipologiaDCE ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| noteDocumento | C | 0..* | Extension(Annotation) | Element idDiagnosticReport.extension:noteDocumentoShort description Optional Extensions Element Alternate namesextensions, user content DefinitionDescrive la nota collegata al documento corrispondente campo HL7 secondo specifiche regionali: NTE. Può descrivere le seguenti casistiche:
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. https://fhir.siss.regione.lombardia.it/StructureDefinition/ReteLabDiagnosticReportNote ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| modifierExtension | ?! C | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.modifierExtensionShort description 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.
| ||
| identifier | Σ | 1..2 | Identifier | Element idDiagnosticReport.identifierShort description Identificativo univoco del referto Alternate namesReportID, Filler ID, Placer ID DefinitionIdentificativo univoco del referto:
Need to know what identifier to use when making queries about this report from the source laboratory, and for linking to the report outside FHIR context. Corrispondente campo HL7 secondo specifiche regionali: TXA-12 Unordered, Open, by system(Value) Constraints
| ||
| IdentificativoDocumentoTestuale | Σ | 0..1 | Identifier | Element idDiagnosticReport.identifier:IdentificativoDocumentoTestualeShort description Codice identificativo del documento testuale Alternate namesReportID, Filler ID, Placer ID DefinitionIdentificativo del documento testuale (max 64) Need to know what identifier to use when making queries about this report from the source laboratory, and for linking to the report outside FHIR context. Corrispondente campo HL7 secondo specifiche regionali: TXA-12, EI-1
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.identifier:IdentificativoDocumentoTestuale.idShort description 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 | C | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.identifier:IdentificativoDocumentoTestuale.extensionShort description 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
| ||
| use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idDiagnosticReport.identifier:IdentificativoDocumentoTestuale.useShort description usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known .
| ||
| type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idDiagnosticReport.identifier:IdentificativoDocumentoTestuale.typeShort description Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible) Constraints
| ||
| system | Σ | 0..1 | uriAuto Value | Element idDiagnosticReport.identifier:IdentificativoDocumentoTestuale.systemShort description The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
https://fhir.siss.regione.lombardia.it/sid/codiceIdentificativoDocumentoTestualeExamples General http://www.acme.com/identifiers/patientMappings
| ||
| value | Σ | 0..1 | string | Element idDiagnosticReport.identifier:IdentificativoDocumentoTestuale.valueShort description Identificativo documento testuale DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456Mappings
| ||
| period | Σ | 0..1 | Period | There are no (further) constraints on this element Element idDiagnosticReport.identifier:IdentificativoDocumentoTestuale.periodShort description Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use.
| ||
| assigner | Σ | 0..1 | Reference(Organization) | There are no (further) constraints on this element Element idDiagnosticReport.identifier:IdentificativoDocumentoTestuale.assignerShort description Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
| ||
| IdentificativoDocumentoStrutturato | Σ | 0..1 | Identifier | Element idDiagnosticReport.identifier:IdentificativoDocumentoStrutturatoShort description Business identifier for report Alternate namesReportID, Filler ID, Placer ID DefinitionIdentifiers assigned to this report by the performer or other systems. Need to know what identifier to use when making queries about this report from the source laboratory, and for linking to the report outside FHIR context. Corrispondente campo HL7 secondo specifiche regionali: TXA-12, EI-3
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.identifier:IdentificativoDocumentoStrutturato.idShort description 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 | C | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.identifier:IdentificativoDocumentoStrutturato.extensionShort description 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
| ||
| use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idDiagnosticReport.identifier:IdentificativoDocumentoStrutturato.useShort description usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known .
| ||
| type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idDiagnosticReport.identifier:IdentificativoDocumentoStrutturato.typeShort description Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible) Constraints
| ||
| system | Σ | 0..1 | uriAuto Value | Element idDiagnosticReport.identifier:IdentificativoDocumentoStrutturato.systemShort description The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
https://fhir.siss.regione.lombardia.it/sid/codiceIdentificativoDocumentoStrutturatoExamples General http://www.acme.com/identifiers/patientMappings
| ||
| value | Σ | 0..1 | string | Element idDiagnosticReport.identifier:IdentificativoDocumentoStrutturato.valueShort description Identificativo documento strutturato DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456Mappings
| ||
| period | Σ | 0..1 | Period | There are no (further) constraints on this element Element idDiagnosticReport.identifier:IdentificativoDocumentoStrutturato.periodShort description Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use.
| ||
| assigner | Σ | 0..1 | Reference(Organization) | There are no (further) constraints on this element Element idDiagnosticReport.identifier:IdentificativoDocumentoStrutturato.assignerShort description Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
| ||
| basedOn | 1..* | Reference(ReteLabServiceRequestRichiestaEsamiLab) | Element idDiagnosticReport.basedOnShort description Richiesta di esame di laboratorio di cui si riportano i risultati Alternate namesRequest DefinitionReference al profilo ReteLabServiceRequestRichiestaEsamiLab This allows tracing of authorization for the report and tracking whether proposals/recommendations were acted upon. Note: Usually there is one test request for each result, however in some circumstances multiple test requests may be represented using a single test result resource. Note that there are also cases where one request leads to multiple reports. Reference(ReteLabServiceRequestRichiestaEsamiLab) Constraints
| |||
| status | Σ ?! | 1..1 | codeBindingAuto Value | Element idDiagnosticReport.statusShort description Stato del DiagnosticReport DefinitionThe status of the diagnostic report. Diagnostic services routinely issue provisional/incomplete reports, and sometimes withdraw previously released reports. Corrispondente campo HL7 secondo specifiche regionali: TXA-17 The status of the diagnostic report. DiagnosticReportStatus (required) Constraints
finalMappings
| ||
| category | Σ | 0..* | CodeableConceptAuto Value | Element idDiagnosticReport.categoryShort description Referti di Laboratorio Alternate namesDepartment, Sub-department, Service, Discipline DefinitionValore fisso su LAB --> Laboratorio Multiple categories are allowed using various categorization schemes. The level of granularity is defined by the category concepts in the value set. More fine-grained filtering can be performed using the metadata and/or terminology hierarchy in DiagnosticReport.code. Codes for diagnostic service sections. DiagnosticServiceSectionCodes (example) Constraints
{
"coding": [
{
"code": "LAB",
"display": "Laboratorio"
}
]
}Mappings
| ||
| code | Σ | 1..1 | CodeableConceptBinding | Element idDiagnosticReport.codeShort description Codice diagnosticReport Alternate namesType DefinitionA code or name that describes this diagnostic report. Codes that describe Diagnostic Reports. LOINCDiagnosticReportCodes (preferred) Constraints
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.code.idShort description 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 | C | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.code.extensionShort description 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
| ||
| coding | Σ | 0..* | Coding | Element idDiagnosticReport.code.codingShort description Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. Unordered, Open, by system(Value) Constraints
| ||
| LOINC | Σ | 0..* | CodingBinding | Element idDiagnosticReport.code.coding:LOINCShort description Codifica LOINC che indica il referto di laboratorio. DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
| ||
| TipoDocumento | Σ | 0..* | CodingBinding | Element idDiagnosticReport.code.coding:TipoDocumentoShort description Tipologia documento. DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Corrispondente campo HL7 secondo specifiche regionali: OBX-3.2. Tipologia Documento SISS (required) Constraints
| ||
| TipoDocumentoInterno | Σ | 0..* | CodingBinding | Element idDiagnosticReport.code.coding:TipoDocumentoInternoShort description Tipologia interna di documento. DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Corrispondente campo HL7 secondo specifiche regionali: OBX-3.5. Tipologia documento interno (required) Constraints
| ||
| text | Σ | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.code.textShort description Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
| ||
| subject | Σ | 0..1 | Reference(ReteLabPatientCittadino) | Element idDiagnosticReport.subjectShort description Paziente al quale i risultati degli esami fanno riferimento Alternate namesPatient DefinitionReference al profilo ReteLabPatientCittadino SHALL know the subject context. Reference(ReteLabPatientCittadino) Constraints
| ||
| encounter | Σ | 0..1 | Reference(Encounter) | There are no (further) constraints on this element Element idDiagnosticReport.encounterShort description Health care event when test ordered Alternate namesContext DefinitionThe healthcare event (e.g. a patient and healthcare provider interaction) which this DiagnosticReport is about. Links the request to the Encounter context. This will typically be the encounter the event occurred within, but some events may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter (e.g. pre-admission laboratory tests).
| ||
| effective[x] | Σ | 0..1 | There are no (further) constraints on this element Element idDiagnosticReport.effective[x]Short description Clinically relevant time/time-period for report Alternate namesObservation time, Effective Time, Occurrence DefinitionThe time or time-period the observed values are related to. When the subject of the report is a patient, this is usually either the time of the procedure or of specimen collection(s), but very often the source of the date/time is not known, only the date/time itself. Need to know where in the patient history to file/present this report. If the diagnostic procedure was performed on the patient, this is the time it was performed. If there are specimens, the diagnostically relevant time can be derived from the specimen collection times, but the specimen information is not always available, and the exact relationship between the specimens and the diagnostically relevant time is not always automatic.
| |||
| effectiveDateTime | dateTime | There are no (further) constraints on this element Data type | ||||
| effectivePeriod | Period | There are no (further) constraints on this element Data type | ||||
| issued | Σ | 0..1 | instant | Element idDiagnosticReport.issuedShort description Data e ora di firma del documento Alternate namesDate published, Date Issued, Date Verified DefinitionObbligatorio per documenti firmati e/o marcati. Formato: YYYY-MM-DDThh:mm:ss+zz:zz secondo lo standard FHIR Clinicians need to be able to check the date that the report was released. Corrispondente campo HL7 secondo specifiche regionali: TXA-22
| ||
| performer | Σ | 0..* | Reference(Practitioner | PractitionerRole | Organization | CareTeam) | There are no (further) constraints on this element Element idDiagnosticReport.performerShort description Responsible Diagnostic Service Alternate namesLaboratory, Service, Practitioner, Department, Company, Authorized by, Director DefinitionThe diagnostic service that is responsible for issuing the report. Need to know whom to contact if there are queries about the results. Also may need to track the source of reports for secondary data analysis. This is not necessarily the source of the atomic data items or the entity that interpreted the results. It is the entity that takes responsibility for the clinical report. Reference(Practitioner | PractitionerRole | Organization | CareTeam) Constraints
| ||
| resultsInterpreter | Σ | 0..* | Reference(ReteLabPractitionerRoleMedico) | Element idDiagnosticReport.resultsInterpreterShort description Dati dell'operatore che compila e referta Alternate namesAnalyzed by, Reported by DefinitionReference al profilo ReteLabPractitionerRoleMedico Need to know whom to contact if there are queries about the results. Also may need to track the source of reports for secondary data analysis. Corrispondente campo HL7 secondo specifiche regionali: TXA-11 e PV1-8 Reference(ReteLabPractitionerRoleMedico) Constraints
| ||
| specimen | 0..* | Reference(Specimen) | There are no (further) constraints on this element Element idDiagnosticReport.specimenShort description Specimens this report is based on DefinitionDetails about the specimens on which this diagnostic report is based. Need to be able to report information about the collected specimens on which the report is based. If the specimen is sufficiently specified with a code in the test result name, then this additional data may be redundant. If there are multiple specimens, these may be represented per observation or group.
| |||
| result | 0..* | Reference(Observation) | There are no (further) constraints on this element Element idDiagnosticReport.resultShort description Observations Alternate namesData, Atomic Value, Result, Atomic result, Data, Test, Analyte, Battery, Organizer DefinitionObservations that are part of this diagnostic report. Need to support individual results, or groups of results, where the result grouping is arbitrary, but meaningful. Observations can contain observations.
| |||
| imagingStudy | 0..* | Reference(ImagingStudy) | There are no (further) constraints on this element Element idDiagnosticReport.imagingStudyShort description Reference to full details of imaging associated with the diagnostic report DefinitionOne or more links to full details of any imaging performed during the diagnostic investigation. Typically, this is imaging performed by DICOM enabled modalities, but this is not required. A fully enabled PACS viewer can use this information to provide views of the source images. ImagingStudy and the image element are somewhat overlapping - typically, the list of image references in the image element will also be found in one of the imaging study resources. However, each caters to different types of displays for different types of purposes. Neither, either, or both may be provided.
| |||
| media | Σ | 0..* | BackboneElement | There are no (further) constraints on this element Element idDiagnosticReport.mediaShort description Key images associated with this report Alternate namesDICOM, Slides, Scans DefinitionA list of key images associated with this report. The images are generally created during the diagnostic process, and may be directly of the patient, or of treated specimens (i.e. slides of interest). Many diagnostic services include images in the report as part of their service.
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.media.idShort description 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 | C | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.media.extensionShort description 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.
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.media.modifierExtensionShort description 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.
| ||
| comment | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.media.commentShort description Comment about the image (e.g. explanation) DefinitionA comment about the image. Typically, this is used to provide an explanation for why the image is included, or to draw the viewer's attention to important features. The provider of the report should make a comment about each image included in the report. The comment should be displayed with the image. It would be common for the report to include additional discussion of the image contents in other sections such as the conclusion.
| |||
| link | Σ | 1..1 | Reference(Media) | There are no (further) constraints on this element Element idDiagnosticReport.media.linkShort description Reference to the image source DefinitionReference to the image source.
| ||
| conclusion | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.conclusionShort description Clinical conclusion (interpretation) of test results Alternate namesReport DefinitionConcise and clinically contextualized summary conclusion (interpretation/impression) of the diagnostic report. Need to be able to provide a conclusion that is not lost among the basic result data.
| |||
| conclusionCode | 0..* | CodeableConcept | There are no (further) constraints on this element Element idDiagnosticReport.conclusionCodeShort description Codes for the clinical conclusion of test results DefinitionOne or more codes that represent the summary conclusion (interpretation/impression) of the diagnostic report. Diagnosis codes provided as adjuncts to the report. SNOMEDCTClinicalFindings (example) Constraints
| |||
| presentedForm | 1..2 | Attachment | Element idDiagnosticReport.presentedFormShort description Documento Allegato DefinitionContenuto da archiviare (documento o link). In questo campo verranno allegati il documento in formato PDF e quello in formato CDA-2. Gives laboratory the ability to provide its own fully formatted report for clinical fidelity. Corrispondente campo HL7 secondo specifiche regionali: OBX-5
| |||
| id | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.presentedForm.idShort description 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 | C | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.presentedForm.extensionShort description 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
| ||
| contentType | Σ | 0..1 | codeBinding | Element idDiagnosticReport.presentedForm.contentTypeShort description Formato documento Definitiontipo fisico del documento (obbligatorio). Valori ammessi:
Processors of the data need to be able to know how to interpret the data. Corrispondente campo HL7 secondo specifiche regionali: OBX-3 CE-6 OBX-5 : Contenuto da archiviare (documento o link). La compilazione del campo varia in funzione del contenuto: Documento OBX-5.2 = multipart OBX-5.3 = Octed-stream OBX-5.4 = Base64 OBX-5.5 = documento codificato in Base64 The mime type of an attachment. Any valid mime type is allowed.
General text/plain; charset=UTF-8, image/pngMappings
| ||
| language | Σ | 0..1 | codeBinding | There are no (further) constraints on this element Element idDiagnosticReport.presentedForm.languageShort description Human language of the content (BCP-47) DefinitionThe human language of the content. The value can be any valid value according to BCP 47. Users need to be able to choose between the languages in a set of attachments. A human language.
General en-AUMappings
| ||
| data | 0..1 | base64Binary | Element idDiagnosticReport.presentedForm.dataShort description Documento codificato in base64 DefinitionTale campo sarà sempre valorizzato come "Documento codificato in base64" The data needs to able to be transmitted inline. Corrispondente campo HL7 secondo specifiche regionali: OBX-5.5
| |||
| url | Σ | 0..1 | url | There are no (further) constraints on this element Element idDiagnosticReport.presentedForm.urlShort description Uri where the data can be found DefinitionA location where the data can be accessed. The data needs to be transmitted by reference. If both data and url are provided, the url SHALL point to the same content as the data contains. Urls may be relative references or may reference transient locations such as a wrapping envelope using cid: though this has ramifications for using signatures. Relative URLs are interpreted relative to the service url, like a resource reference, rather than relative to the resource itself. If a URL is provided, it SHALL resolve to actual data.
General http://www.acme.com/logo-small.pngMappings
| ||
| size | Σ | 0..1 | unsignedInt | There are no (further) constraints on this element Element idDiagnosticReport.presentedForm.sizeShort description Number of bytes of content (if url provided) DefinitionThe number of bytes of data that make up this attachment (before base64 encoding, if that is done). Representing the size allows applications to determine whether they should fetch the content automatically in advance, or refuse to fetch it at all. The number of bytes is redundant if the data is provided as a base64binary, but is useful if the data is provided as a url reference.
| ||
| hash | Σ | 0..1 | base64Binary | There are no (further) constraints on this element Element idDiagnosticReport.presentedForm.hashShort description Hash of the data (sha-1, base64ed) DefinitionThe calculated hash of the data using SHA-1. Represented using base64. Included so that applications can verify that the contents of a location have not changed due to technical failures (e.g., storage rot, transport glitch, incorrect version). The hash is calculated on the data prior to base64 encoding, if the data is based64 encoded. The hash is not intended to support digital signatures. Where protection against malicious threats a digital signature should be considered, see Provenance.signature for mechanism to protect a resource with a digital signature.
| ||
| title | Σ | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.presentedForm.titleShort description Label to display in place of the data DefinitionA label or set of text to display in place of the data. Applications need a label to display to a human user in place of the actual data if the data cannot be rendered or perceived by the viewer.
General Official Corporate LogoMappings
| ||
| creation | Σ | 0..1 | dateTime | Element idDiagnosticReport.presentedForm.creationShort description Data e ora compilazione del documento DefinitionFormato: YYYY-MM-DDThh:mm:ss+zz:zz secondo lo standard FHIR This is often tracked as an integrity issue for use of the attachment. Corrispondente campo HL7 secondo specifiche regionali: TXA-6
|
Table View
| DiagnosticReport | .. | |
| DiagnosticReport.extension | 1.. | |
| DiagnosticReport.extension:refertoPadre | Extension | .. |
| DiagnosticReport.extension:refertoPadre.value[x] | .. | |
| DiagnosticReport.extension:naturaDCE | Extension | 1..1 |
| DiagnosticReport.extension:naturaDCE.value[x] | .. | |
| DiagnosticReport.extension:tipologiaDCE | Extension | .. |
| DiagnosticReport.extension:noteDocumento | Extension | .. |
| DiagnosticReport.identifier | 1..2 | |
| DiagnosticReport.identifier:IdentificativoDocumentoTestuale | 0..1 | |
| DiagnosticReport.identifier:IdentificativoDocumentoTestuale.system | .. | |
| DiagnosticReport.identifier:IdentificativoDocumentoTestuale.value | .. | |
| DiagnosticReport.identifier:IdentificativoDocumentoStrutturato | 0..1 | |
| DiagnosticReport.identifier:IdentificativoDocumentoStrutturato.system | .. | |
| DiagnosticReport.identifier:IdentificativoDocumentoStrutturato.value | .. | |
| DiagnosticReport.basedOn | Reference(ReteLabServiceRequestRichiestaEsamiLab) | 1.. |
| DiagnosticReport.status | .. | |
| DiagnosticReport.category | .. | |
| DiagnosticReport.code | .. | |
| DiagnosticReport.code.coding | .. | |
| DiagnosticReport.code.coding:LOINC | .. | |
| DiagnosticReport.code.coding:TipoDocumento | .. | |
| DiagnosticReport.code.coding:TipoDocumentoInterno | .. | |
| DiagnosticReport.subject | Reference(ReteLabPatientCittadino) | .. |
| DiagnosticReport.issued | .. | |
| DiagnosticReport.resultsInterpreter | Reference(ReteLabPractitionerRoleMedico) | .. |
| DiagnosticReport.presentedForm | 1..2 | |
| DiagnosticReport.presentedForm.contentType | .. | |
| DiagnosticReport.presentedForm.data | .. | |
| DiagnosticReport.presentedForm.creation | .. |
XML View
JSON View
ValueSet
Nella seguente tabella sono elencati i value set relativi al profilo ReteLabDiagnosticReportRefertato:
| Nome | Descrizione | Riferimento al dettaglio della codifica |
|---|---|---|
| Tipologia Documento | Codifica della tipologia di documento secondo le specifiche SISS | La codifica è definita dal ValueSet Tipologia Documento SISS |
| Tipologia Documento Interno | Codifica della tipologia di documento interno secondo le specifiche SISS | La codifica è definita dal ValueSet Tipologia documento interno |
| Tipologia Documento LOINC | Codifica della tipologia di documento secondo la codifica loinc | La codifica è definita dal ValueSet Codifica LOINC |
| Tipologia DCE | Codifica della tipologia di referto | La codifica è definita dal ValueSet Tipologia DCE |
| Natura DCE | Codifica della natura del referto | La codifica è definita dal ValueSet Natura DCE da archiviare |