ReteLabSpecimenCampioneDaAnalizzareCheckInCheckOut
Descrizione
Il profilo ReteLabSpecimenCampioneDaAnalizzareCheckInCheckOut è stato strutturato a partire dalla risorsa generica FHIR Specimen utilizzata per descrivere i campioni che:
- sono stati prelevati (check-in da LR a LS),
- pronti per essere mandati in service (check-out da LR a LS)
Di seguito è presentato il contenuto del profilo in diversi formati. La corrispondente definizione è consultabile al seguente link: ReteLabSpecimenCampioneDaAnalizzareCheckInCheckOut.
Snapshot View
ReteLabSpecimenCampioneDaAnalizzareCheckInCheckOut (Specimen) | I | Specimen | Element idSpecimen Descrive i campioni che verranno analizzati DefinitionRisorsa utilizzata per descrivere i campioni che:
Segmento HL7 secondo specifiche regionali: SPM
| |
id | Σ | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.id Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idSpecimen.meta Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
|
implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idSpecimen.implicitRules A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.
|
language | 0..1 | codeBinding | There are no (further) constraints on this element Element idSpecimen.language Language of the resource content DefinitionThe base language in which the resource is written. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). A human language.
| |
text | 0..1 | Narrative | There are no (further) constraints on this element Element idSpecimen.text Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
| |
contained | 0..* | Resource | There are no (further) constraints on this element Element idSpecimen.contained Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | ?! I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
identifier | Σ | 0..* | Identifier | Element idSpecimen.identifier Identificativo del campione DefinitionId for specimen. Corrispondente campo HL7 secondo specifiche regionali: SPM-2
|
id | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.identifier.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.identifier.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idSpecimen.identifier.use 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 idSpecimen.identifier.type 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.
|
system | Σ | 0..1 | uriFixed Value | Element idSpecimen.identifier.system 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/SpecimenIdentifier
|
value | Σ | 0..1 | string | Element idSpecimen.identifier.value 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. Identificativo del campione
General 123456 Mappings
|
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element idSpecimen.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
|
assigner | Σ I | 0..1 | Reference(Organization) | There are no (further) constraints on this element Element idSpecimen.identifier.assigner 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.
|
accessionIdentifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element idSpecimen.accessionIdentifier Identifier assigned by the lab DefinitionThe identifier assigned by the lab when accessioning specimen(s). This is not necessarily the same as the specimen identifier, depending on local lab procedures.
|
status | Σ ?! | 1..1 | codeBinding | Element idSpecimen.status Stato del campione DefinitionUtilizzato nei flussi di checkin e checkout per indicare lo stato del campione (disponibile, non disponibile, non utilizzabile..) Nel dettaglio è previsto l'utilizzo dello status "unavailable" per l'identificazione del flusso di check in richiedente e "available" per l'identificazione del flusso check out richiedente. Codes providing the status/availability of a specimen.
|
type | Σ | 1..1 | CodeableConcept | Element idSpecimen.type Tipologia del campione o identificativo del materiale biologico DefinitionThe kind of material that forms the specimen. Corrispondente campo HL7 secondo specifiche regionali: SPM-4 The type of the specimen.
|
id | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.type.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.type.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idSpecimen.type.coding 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.type.coding.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.type.coding.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uri | Element idSpecimen.type.coding.system Sistema di codifica DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. Corrispondente campo HL7 secondo specifiche regionali: SPM-4 CWE-3
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.type.coding.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
|
code | Σ | 0..1 | code | Element idSpecimen.type.coding.code Codice del campione DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Corrispondente campo HL7 secondo specifiche regionali: SPM-4 CWE-1
|
display | Σ | 0..1 | string | Element idSpecimen.type.coding.display Descrizione DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Corrispondente campo HL7 secondo specifiche regionali: SPM-4 CWE-2
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idSpecimen.type.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.type.text 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 | Σ I | 0..1 | Reference(ReteLabPatientCittadino) | Element idSpecimen.subject Paziente di riferimento DefinitionReference al profilo ReteLabPatientCittadino Must know the subject context. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(ReteLabPatientCittadino) Constraints
|
receivedTime | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element idSpecimen.receivedTime The time when specimen was received for processing DefinitionTime when specimen was received for processing or testing.
|
parent | I | 0..* | Reference(Specimen) | There are no (further) constraints on this element Element idSpecimen.parent Specimen from which this specimen originated DefinitionReference to the parent (source) specimen which is used when the specimen was either derived from or a component of another specimen. The parent specimen could be the source from which the current specimen is derived by some processing step (e.g. an aliquot or isolate or extracted nucleic acids from clinical samples) or one of many specimens that were combined to create a pooled sample.
|
request | I | 0..* | Reference(ServiceRequest) | There are no (further) constraints on this element Element idSpecimen.request Why the specimen was collected DefinitionDetails concerning a service request that required a specimen to be collected. The request may be explicit or implied such with a ServiceRequest that requires a blood draw.
|
collection | 0..1 | BackboneElement | Element idSpecimen.collection Descrizione campione DefinitionNote aggiuntive relative al singolo campione
| |
id | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.collection.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.collection.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.collection.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
collector | Σ I | 0..1 | Reference(Practitioner | PractitionerRole) | There are no (further) constraints on this element Element idSpecimen.collection.collector Who collected the specimen DefinitionPerson who collected the specimen. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Practitioner | PractitionerRole) Constraints
|
collected[x] | Σ | 0..1 | Element idSpecimen.collection.collected[x] Data e ora del prelievo del campione. DefinitionObbligatorio nel flusso di check in richiedente. La valorizzazione di questa informazione, se disponibile, si consiglia sempre. Formato: YYYY-MM-DDThh:mm:ss+zz:zz secondo lo standard FHIR Corrispondente campo HL7 secondo specifiche regionali: SPM-17
| |
collectedDateTime | dateTime | Data type | ||
duration | Σ I | 0..1 | Duration | There are no (further) constraints on this element Element idSpecimen.collection.duration How long it took to collect specimen DefinitionThe span of time over which the collection of a specimen occurred. The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator.
|
quantity | I | 0..1 | SimpleQuantity | Element idSpecimen.collection.quantity Quantità del campione prelevata DefinitionComposto dai due componenti: quantità (numerica) e unità di misura (CE) Corrispondente campo HL7 secondo specifiche regionali: SPM-12
|
id | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.collection.quantity.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.collection.quantity.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
value | Σ | 0..1 | decimal | Element idSpecimen.collection.quantity.value Quantità DefinitionThe value of the measured amount. The value includes an implicit precision in the presentation of the value. Precision is handled implicitly in almost all cases of measurement. Corrispondente campo HL7 secondo specifiche regionali: SPM-12.1
|
comparator | Σ ?! | 0..0 | codeBinding | There are no (further) constraints on this element Element idSpecimen.collection.quantity.comparator < | <= | >= | > - how to understand the value DefinitionNot allowed to be used in this context Need a framework for handling measures where the value is <5ug/L or >400mg/L due to the limitations of measuring methodology. Note that FHIR strings SHALL NOT exceed 1MB in size If there is no comparator, then there is no modification of the value How the Quantity should be understood and represented.
|
unit | Σ | 0..1 | string | Element idSpecimen.collection.quantity.unit Unità di misura DefinitionA human-readable form of the unit. There are many representations for units of measure and in many contexts, particular representations are fixed and required. I.e. mcg for micrograms. Note that FHIR strings SHALL NOT exceed 1MB in size
|
system | Σ I | 0..1 | uri | There are no (further) constraints on this element Element idSpecimen.collection.quantity.system System that defines coded unit form DefinitionThe identification of the system that provides the coded form of the unit. Need to know the system that defines the coded form of the unit. see http://en.wikipedia.org/wiki/Uniform_resource_identifier
|
code | Σ | 0..1 | code | There are no (further) constraints on this element Element idSpecimen.collection.quantity.code Coded form of the unit DefinitionA computer processable form of the unit in some unit representation system. Need a computable form of the unit that is fixed across all forms. UCUM provides this for quantities, but SNOMED CT provides many units of interest. The preferred system is UCUM, but SNOMED CT can also be used (for customary units) or ISO 4217 for currency. The context of use may additionally require a code from a particular system.
|
method | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idSpecimen.collection.method Technique used to perform collection DefinitionA coded value specifying the technique that is used to perform the procedure. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. The technique that is used to perform the procedure.
| |
bodySite | 0..1 | CodeableConcept | Element idSpecimen.collection.bodySite Sede anatomica di prelievo DefinitionAnatomical location from which the specimen was collected (if subject is a patient). This is the target site. This element is not used for environmental specimens. Corrispondente campo HL7 secondo specifiche regionali: SPM-8 Codes describing anatomical locations. May include laterality.
| |
id | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.collection.bodySite.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.collection.bodySite.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idSpecimen.collection.bodySite.coding 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.collection.bodySite.coding.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.collection.bodySite.coding.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uri | Element idSpecimen.collection.bodySite.coding.system Sistema di codifica DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. Corrispondente campo HL7 secondo specifiche regionali: SPM-8.3
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.collection.bodySite.coding.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
|
code | Σ | 0..1 | code | Element idSpecimen.collection.bodySite.coding.code Codice sede anatomica di prelievo DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Corrispondente campo HL7 secondo specifiche regionali: SPM-8.1
|
display | Σ | 0..1 | string | Element idSpecimen.collection.bodySite.coding.display Descrizione sede anatomica di prelievo DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings SHALL NOT exceed 1MB in size
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idSpecimen.collection.bodySite.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.collection.bodySite.text 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.
|
fastingStatus[x] | Σ | 0..1 | Binding | There are no (further) constraints on this element Element idSpecimen.collection.fastingStatus[x] Whether or how long patient abstained from food and/or drink DefinitionAbstinence or reduction from some or all food, drink, or both, for a period of time prior to sample collection. Many diagnostic tests require fasting to facilitate accurate interpretation. Representing fasting status using this element is preferred to representing it with an observation using a 'pre-coordinated code' such as LOINC 2005-7 (Calcium [Moles/time] in 2 hour Urine --12 hours fasting), or using a component observation Codes describing the fasting status of the patient.
|
fastingStatusCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||
fastingStatusDuration | Duration | There are no (further) constraints on this element Data type | ||
processing | 0..* | BackboneElement | Element idSpecimen.processing Indica come il campione o il contenitore deve essere trattato (maneggiato, conservato) DefinitionDetails concerning processing and processing steps for the specimen. Corrispondente campo HL7 secondo specifiche regionali: SPM-15
| |
id | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.processing.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.processing.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.processing.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
description | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.processing.description Textual description of procedure DefinitionTextual description of procedure. Note that FHIR strings SHALL NOT exceed 1MB in size
| |
procedure | 0..1 | CodeableConceptBinding | Element idSpecimen.processing.procedure Indica come il campione o il contenitore deve essere trattato (maneggiato, conservato). DefinitionA coded value specifying the procedure used to process the specimen. Corrispondente campo HL7 secondo specifiche regionali: SPM-15 Type indicating the technique used to process the specimen.
| |
id | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.processing.procedure.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.processing.procedure.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idSpecimen.processing.procedure.coding 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.processing.procedure.coding.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.processing.procedure.coding.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uri | Element idSpecimen.processing.procedure.coding.system Sistema di codifica DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. Corrispondente campo HL7 secondo specifiche regionali: SPM-15.3
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.processing.procedure.coding.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
|
code | Σ | 0..1 | code | Element idSpecimen.processing.procedure.coding.code Codice DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Corrispondente campo HL7 secondo specifiche regionali: SPM-15.1
|
display | Σ | 0..1 | string | Element idSpecimen.processing.procedure.coding.display Descrizione DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings SHALL NOT exceed 1MB in size
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idSpecimen.processing.procedure.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.processing.procedure.text 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.
|
additive | I | 0..* | Reference(Substance) | There are no (further) constraints on this element Element idSpecimen.processing.additive Material used in the processing step DefinitionMaterial used in the processing step. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
time[x] | 0..1 | There are no (further) constraints on this element Element idSpecimen.processing.time[x] Date and time of specimen processing DefinitionA record of the time or period when the specimen processing occurred. For example the time of sample fixation or the period of time the sample was in formalin.
| ||
timeDateTime | dateTime | There are no (further) constraints on this element Data type | ||
timePeriod | Period | There are no (further) constraints on this element Data type | ||
container | 0..* | BackboneElement | Element idSpecimen.container Direct container of specimen (tube/slide, etc.) DefinitionObbligatorio per messaggi con MessageHeader.eventCoding.code uguale a OML^O35
| |
id | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.container.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.container.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.container.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
identifier | Σ | 0..* | Identifier | Element idSpecimen.container.identifier Id for the container DefinitionObbligatorio per messaggi con MessageHeader.eventCoding.code uguale a OML^O35. Corrispondente al campo SAC-3.
|
description | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.container.description Textual description of the container DefinitionTextual description of the container. Note that FHIR strings SHALL NOT exceed 1MB in size
| |
type | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idSpecimen.container.type Kind of container directly associated with specimen DefinitionThe type of container associated with the specimen (e.g. slide, aliquot, etc.). Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Type of specimen container.
| |
capacity | I | 0..1 | SimpleQuantity | There are no (further) constraints on this element Element idSpecimen.container.capacity Container volume or size DefinitionThe capacity (volume or other measure) the container may contain. The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator.
|
specimenQuantity | I | 0..1 | SimpleQuantity | There are no (further) constraints on this element Element idSpecimen.container.specimenQuantity Quantity of specimen within container DefinitionThe quantity of specimen in the container; may be volume, dimensions, or other appropriate measurements, depending on the specimen type. The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator.
|
additive[x] | 0..1 | There are no (further) constraints on this element Element idSpecimen.container.additive[x] Additive associated with container DefinitionIntroduced substance to preserve, maintain or enhance the specimen. Examples: Formalin, Citrate, EDTA. Substance added to specimen container.
| ||
additiveCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||
additiveReference | Reference(Substance) | There are no (further) constraints on this element Data type | ||
condition | Σ | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idSpecimen.condition State of the specimen DefinitionA mode or state of being that describes the nature of the specimen. The specimen condition can be used to assess its quality or appropriateness for a specific test. Specimen condition is an observation made about the specimen. It's a point-in-time assessment. It can be used to assess its quality or appropriateness for a specific test. Codes describing the state of the specimen.
|
note | 0..* | Annotation | There are no (further) constraints on this element Element idSpecimen.note Comments DefinitionTo communicate any details or issues about the specimen or during the specimen collection. (for example: broken vial, sent with patient, frozen). For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. Annotations SHOULD NOT be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible).
|
Differential View
ReteLabSpecimenCampioneDaAnalizzareCheckInCheckOut (Specimen) | I | Specimen | Element idSpecimen Descrive i campioni che verranno analizzati DefinitionRisorsa utilizzata per descrivere i campioni che:
Segmento HL7 secondo specifiche regionali: SPM
| |
id | Σ | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.id Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idSpecimen.meta Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
|
implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idSpecimen.implicitRules A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.
|
language | 0..1 | codeBinding | There are no (further) constraints on this element Element idSpecimen.language Language of the resource content DefinitionThe base language in which the resource is written. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). A human language.
| |
text | 0..1 | Narrative | There are no (further) constraints on this element Element idSpecimen.text Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
| |
contained | 0..* | Resource | There are no (further) constraints on this element Element idSpecimen.contained Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | ?! I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
identifier | Σ | 0..* | Identifier | Element idSpecimen.identifier Identificativo del campione DefinitionId for specimen. Corrispondente campo HL7 secondo specifiche regionali: SPM-2
|
id | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.identifier.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.identifier.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idSpecimen.identifier.use 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 idSpecimen.identifier.type 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.
|
system | Σ | 0..1 | uriFixed Value | Element idSpecimen.identifier.system 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/SpecimenIdentifier
|
value | Σ | 0..1 | string | Element idSpecimen.identifier.value 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. Identificativo del campione
General 123456 Mappings
|
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element idSpecimen.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
|
assigner | Σ I | 0..1 | Reference(Organization) | There are no (further) constraints on this element Element idSpecimen.identifier.assigner 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.
|
accessionIdentifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element idSpecimen.accessionIdentifier Identifier assigned by the lab DefinitionThe identifier assigned by the lab when accessioning specimen(s). This is not necessarily the same as the specimen identifier, depending on local lab procedures.
|
status | Σ ?! | 1..1 | codeBinding | Element idSpecimen.status Stato del campione DefinitionUtilizzato nei flussi di checkin e checkout per indicare lo stato del campione (disponibile, non disponibile, non utilizzabile..) Nel dettaglio è previsto l'utilizzo dello status "unavailable" per l'identificazione del flusso di check in richiedente e "available" per l'identificazione del flusso check out richiedente. Codes providing the status/availability of a specimen.
|
type | Σ | 1..1 | CodeableConcept | Element idSpecimen.type Tipologia del campione o identificativo del materiale biologico DefinitionThe kind of material that forms the specimen. Corrispondente campo HL7 secondo specifiche regionali: SPM-4 The type of the specimen.
|
id | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.type.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.type.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idSpecimen.type.coding 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.type.coding.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.type.coding.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uri | Element idSpecimen.type.coding.system Sistema di codifica DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. Corrispondente campo HL7 secondo specifiche regionali: SPM-4 CWE-3
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.type.coding.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
|
code | Σ | 0..1 | code | Element idSpecimen.type.coding.code Codice del campione DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Corrispondente campo HL7 secondo specifiche regionali: SPM-4 CWE-1
|
display | Σ | 0..1 | string | Element idSpecimen.type.coding.display Descrizione DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Corrispondente campo HL7 secondo specifiche regionali: SPM-4 CWE-2
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idSpecimen.type.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.type.text 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 | Σ I | 0..1 | Reference(ReteLabPatientCittadino) | Element idSpecimen.subject Paziente di riferimento DefinitionReference al profilo ReteLabPatientCittadino Must know the subject context. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(ReteLabPatientCittadino) Constraints
|
receivedTime | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element idSpecimen.receivedTime The time when specimen was received for processing DefinitionTime when specimen was received for processing or testing.
|
parent | I | 0..* | Reference(Specimen) | There are no (further) constraints on this element Element idSpecimen.parent Specimen from which this specimen originated DefinitionReference to the parent (source) specimen which is used when the specimen was either derived from or a component of another specimen. The parent specimen could be the source from which the current specimen is derived by some processing step (e.g. an aliquot or isolate or extracted nucleic acids from clinical samples) or one of many specimens that were combined to create a pooled sample.
|
request | I | 0..* | Reference(ServiceRequest) | There are no (further) constraints on this element Element idSpecimen.request Why the specimen was collected DefinitionDetails concerning a service request that required a specimen to be collected. The request may be explicit or implied such with a ServiceRequest that requires a blood draw.
|
collection | 0..1 | BackboneElement | Element idSpecimen.collection Descrizione campione DefinitionNote aggiuntive relative al singolo campione
| |
id | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.collection.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.collection.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.collection.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
collector | Σ I | 0..1 | Reference(Practitioner | PractitionerRole) | There are no (further) constraints on this element Element idSpecimen.collection.collector Who collected the specimen DefinitionPerson who collected the specimen. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Practitioner | PractitionerRole) Constraints
|
collected[x] | Σ | 0..1 | Element idSpecimen.collection.collected[x] Data e ora del prelievo del campione. DefinitionObbligatorio nel flusso di check in richiedente. La valorizzazione di questa informazione, se disponibile, si consiglia sempre. Formato: YYYY-MM-DDThh:mm:ss+zz:zz secondo lo standard FHIR Corrispondente campo HL7 secondo specifiche regionali: SPM-17
| |
collectedDateTime | dateTime | Data type | ||
duration | Σ I | 0..1 | Duration | There are no (further) constraints on this element Element idSpecimen.collection.duration How long it took to collect specimen DefinitionThe span of time over which the collection of a specimen occurred. The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator.
|
quantity | I | 0..1 | SimpleQuantity | Element idSpecimen.collection.quantity Quantità del campione prelevata DefinitionComposto dai due componenti: quantità (numerica) e unità di misura (CE) Corrispondente campo HL7 secondo specifiche regionali: SPM-12
|
id | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.collection.quantity.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.collection.quantity.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
value | Σ | 0..1 | decimal | Element idSpecimen.collection.quantity.value Quantità DefinitionThe value of the measured amount. The value includes an implicit precision in the presentation of the value. Precision is handled implicitly in almost all cases of measurement. Corrispondente campo HL7 secondo specifiche regionali: SPM-12.1
|
comparator | Σ ?! | 0..0 | codeBinding | There are no (further) constraints on this element Element idSpecimen.collection.quantity.comparator < | <= | >= | > - how to understand the value DefinitionNot allowed to be used in this context Need a framework for handling measures where the value is <5ug/L or >400mg/L due to the limitations of measuring methodology. Note that FHIR strings SHALL NOT exceed 1MB in size If there is no comparator, then there is no modification of the value How the Quantity should be understood and represented.
|
unit | Σ | 0..1 | string | Element idSpecimen.collection.quantity.unit Unità di misura DefinitionA human-readable form of the unit. There are many representations for units of measure and in many contexts, particular representations are fixed and required. I.e. mcg for micrograms. Note that FHIR strings SHALL NOT exceed 1MB in size
|
system | Σ I | 0..1 | uri | There are no (further) constraints on this element Element idSpecimen.collection.quantity.system System that defines coded unit form DefinitionThe identification of the system that provides the coded form of the unit. Need to know the system that defines the coded form of the unit. see http://en.wikipedia.org/wiki/Uniform_resource_identifier
|
code | Σ | 0..1 | code | There are no (further) constraints on this element Element idSpecimen.collection.quantity.code Coded form of the unit DefinitionA computer processable form of the unit in some unit representation system. Need a computable form of the unit that is fixed across all forms. UCUM provides this for quantities, but SNOMED CT provides many units of interest. The preferred system is UCUM, but SNOMED CT can also be used (for customary units) or ISO 4217 for currency. The context of use may additionally require a code from a particular system.
|
method | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idSpecimen.collection.method Technique used to perform collection DefinitionA coded value specifying the technique that is used to perform the procedure. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. The technique that is used to perform the procedure.
| |
bodySite | 0..1 | CodeableConcept | Element idSpecimen.collection.bodySite Sede anatomica di prelievo DefinitionAnatomical location from which the specimen was collected (if subject is a patient). This is the target site. This element is not used for environmental specimens. Corrispondente campo HL7 secondo specifiche regionali: SPM-8 Codes describing anatomical locations. May include laterality.
| |
id | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.collection.bodySite.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.collection.bodySite.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idSpecimen.collection.bodySite.coding 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.collection.bodySite.coding.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.collection.bodySite.coding.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uri | Element idSpecimen.collection.bodySite.coding.system Sistema di codifica DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. Corrispondente campo HL7 secondo specifiche regionali: SPM-8.3
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.collection.bodySite.coding.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
|
code | Σ | 0..1 | code | Element idSpecimen.collection.bodySite.coding.code Codice sede anatomica di prelievo DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Corrispondente campo HL7 secondo specifiche regionali: SPM-8.1
|
display | Σ | 0..1 | string | Element idSpecimen.collection.bodySite.coding.display Descrizione sede anatomica di prelievo DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings SHALL NOT exceed 1MB in size
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idSpecimen.collection.bodySite.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.collection.bodySite.text 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.
|
fastingStatus[x] | Σ | 0..1 | Binding | There are no (further) constraints on this element Element idSpecimen.collection.fastingStatus[x] Whether or how long patient abstained from food and/or drink DefinitionAbstinence or reduction from some or all food, drink, or both, for a period of time prior to sample collection. Many diagnostic tests require fasting to facilitate accurate interpretation. Representing fasting status using this element is preferred to representing it with an observation using a 'pre-coordinated code' such as LOINC 2005-7 (Calcium [Moles/time] in 2 hour Urine --12 hours fasting), or using a component observation Codes describing the fasting status of the patient.
|
fastingStatusCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||
fastingStatusDuration | Duration | There are no (further) constraints on this element Data type | ||
processing | 0..* | BackboneElement | Element idSpecimen.processing Indica come il campione o il contenitore deve essere trattato (maneggiato, conservato) DefinitionDetails concerning processing and processing steps for the specimen. Corrispondente campo HL7 secondo specifiche regionali: SPM-15
| |
id | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.processing.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.processing.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.processing.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
description | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.processing.description Textual description of procedure DefinitionTextual description of procedure. Note that FHIR strings SHALL NOT exceed 1MB in size
| |
procedure | 0..1 | CodeableConceptBinding | Element idSpecimen.processing.procedure Indica come il campione o il contenitore deve essere trattato (maneggiato, conservato). DefinitionA coded value specifying the procedure used to process the specimen. Corrispondente campo HL7 secondo specifiche regionali: SPM-15 Type indicating the technique used to process the specimen.
| |
id | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.processing.procedure.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.processing.procedure.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idSpecimen.processing.procedure.coding 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.processing.procedure.coding.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.processing.procedure.coding.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uri | Element idSpecimen.processing.procedure.coding.system Sistema di codifica DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. Corrispondente campo HL7 secondo specifiche regionali: SPM-15.3
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.processing.procedure.coding.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
|
code | Σ | 0..1 | code | Element idSpecimen.processing.procedure.coding.code Codice DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Corrispondente campo HL7 secondo specifiche regionali: SPM-15.1
|
display | Σ | 0..1 | string | Element idSpecimen.processing.procedure.coding.display Descrizione DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings SHALL NOT exceed 1MB in size
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idSpecimen.processing.procedure.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.processing.procedure.text 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.
|
additive | I | 0..* | Reference(Substance) | There are no (further) constraints on this element Element idSpecimen.processing.additive Material used in the processing step DefinitionMaterial used in the processing step. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
time[x] | 0..1 | There are no (further) constraints on this element Element idSpecimen.processing.time[x] Date and time of specimen processing DefinitionA record of the time or period when the specimen processing occurred. For example the time of sample fixation or the period of time the sample was in formalin.
| ||
timeDateTime | dateTime | There are no (further) constraints on this element Data type | ||
timePeriod | Period | There are no (further) constraints on this element Data type | ||
container | 0..* | BackboneElement | Element idSpecimen.container Direct container of specimen (tube/slide, etc.) DefinitionObbligatorio per messaggi con MessageHeader.eventCoding.code uguale a OML^O35
| |
id | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.container.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.container.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.container.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
identifier | Σ | 0..* | Identifier | Element idSpecimen.container.identifier Id for the container DefinitionObbligatorio per messaggi con MessageHeader.eventCoding.code uguale a OML^O35. Corrispondente al campo SAC-3.
|
description | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.container.description Textual description of the container DefinitionTextual description of the container. Note that FHIR strings SHALL NOT exceed 1MB in size
| |
type | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idSpecimen.container.type Kind of container directly associated with specimen DefinitionThe type of container associated with the specimen (e.g. slide, aliquot, etc.). Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Type of specimen container.
| |
capacity | I | 0..1 | SimpleQuantity | There are no (further) constraints on this element Element idSpecimen.container.capacity Container volume or size DefinitionThe capacity (volume or other measure) the container may contain. The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator.
|
specimenQuantity | I | 0..1 | SimpleQuantity | There are no (further) constraints on this element Element idSpecimen.container.specimenQuantity Quantity of specimen within container DefinitionThe quantity of specimen in the container; may be volume, dimensions, or other appropriate measurements, depending on the specimen type. The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator.
|
additive[x] | 0..1 | There are no (further) constraints on this element Element idSpecimen.container.additive[x] Additive associated with container DefinitionIntroduced substance to preserve, maintain or enhance the specimen. Examples: Formalin, Citrate, EDTA. Substance added to specimen container.
| ||
additiveCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||
additiveReference | Reference(Substance) | There are no (further) constraints on this element Data type | ||
condition | Σ | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idSpecimen.condition State of the specimen DefinitionA mode or state of being that describes the nature of the specimen. The specimen condition can be used to assess its quality or appropriateness for a specific test. Specimen condition is an observation made about the specimen. It's a point-in-time assessment. It can be used to assess its quality or appropriateness for a specific test. Codes describing the state of the specimen.
|
note | 0..* | Annotation | There are no (further) constraints on this element Element idSpecimen.note Comments DefinitionTo communicate any details or issues about the specimen or during the specimen collection. (for example: broken vial, sent with patient, frozen). For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. Annotations SHOULD NOT be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible).
|
Hybrid View
ReteLabSpecimenCampioneDaAnalizzareCheckInCheckOut (Specimen) | I | Specimen | Element idSpecimen Descrive i campioni che verranno analizzati DefinitionRisorsa utilizzata per descrivere i campioni che:
Segmento HL7 secondo specifiche regionali: SPM
| |
id | Σ | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.id Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idSpecimen.meta Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
|
implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idSpecimen.implicitRules A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.
|
language | 0..1 | codeBinding | There are no (further) constraints on this element Element idSpecimen.language Language of the resource content DefinitionThe base language in which the resource is written. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). A human language.
| |
text | 0..1 | Narrative | There are no (further) constraints on this element Element idSpecimen.text Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
| |
contained | 0..* | Resource | There are no (further) constraints on this element Element idSpecimen.contained Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | ?! I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
identifier | Σ | 0..* | Identifier | Element idSpecimen.identifier Identificativo del campione DefinitionId for specimen. Corrispondente campo HL7 secondo specifiche regionali: SPM-2
|
id | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.identifier.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.identifier.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idSpecimen.identifier.use 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 idSpecimen.identifier.type 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.
|
system | Σ | 0..1 | uriFixed Value | Element idSpecimen.identifier.system 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/SpecimenIdentifier
|
value | Σ | 0..1 | string | Element idSpecimen.identifier.value 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. Identificativo del campione
General 123456 Mappings
|
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element idSpecimen.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
|
assigner | Σ I | 0..1 | Reference(Organization) | There are no (further) constraints on this element Element idSpecimen.identifier.assigner 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.
|
accessionIdentifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element idSpecimen.accessionIdentifier Identifier assigned by the lab DefinitionThe identifier assigned by the lab when accessioning specimen(s). This is not necessarily the same as the specimen identifier, depending on local lab procedures.
|
status | Σ ?! | 1..1 | codeBinding | Element idSpecimen.status Stato del campione DefinitionUtilizzato nei flussi di checkin e checkout per indicare lo stato del campione (disponibile, non disponibile, non utilizzabile..) Nel dettaglio è previsto l'utilizzo dello status "unavailable" per l'identificazione del flusso di check in richiedente e "available" per l'identificazione del flusso check out richiedente. Codes providing the status/availability of a specimen.
|
type | Σ | 1..1 | CodeableConcept | Element idSpecimen.type Tipologia del campione o identificativo del materiale biologico DefinitionThe kind of material that forms the specimen. Corrispondente campo HL7 secondo specifiche regionali: SPM-4 The type of the specimen.
|
id | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.type.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.type.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idSpecimen.type.coding 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.type.coding.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.type.coding.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uri | Element idSpecimen.type.coding.system Sistema di codifica DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. Corrispondente campo HL7 secondo specifiche regionali: SPM-4 CWE-3
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.type.coding.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
|
code | Σ | 0..1 | code | Element idSpecimen.type.coding.code Codice del campione DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Corrispondente campo HL7 secondo specifiche regionali: SPM-4 CWE-1
|
display | Σ | 0..1 | string | Element idSpecimen.type.coding.display Descrizione DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Corrispondente campo HL7 secondo specifiche regionali: SPM-4 CWE-2
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idSpecimen.type.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.type.text 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 | Σ I | 0..1 | Reference(ReteLabPatientCittadino) | Element idSpecimen.subject Paziente di riferimento DefinitionReference al profilo ReteLabPatientCittadino Must know the subject context. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(ReteLabPatientCittadino) Constraints
|
receivedTime | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element idSpecimen.receivedTime The time when specimen was received for processing DefinitionTime when specimen was received for processing or testing.
|
parent | I | 0..* | Reference(Specimen) | There are no (further) constraints on this element Element idSpecimen.parent Specimen from which this specimen originated DefinitionReference to the parent (source) specimen which is used when the specimen was either derived from or a component of another specimen. The parent specimen could be the source from which the current specimen is derived by some processing step (e.g. an aliquot or isolate or extracted nucleic acids from clinical samples) or one of many specimens that were combined to create a pooled sample.
|
request | I | 0..* | Reference(ServiceRequest) | There are no (further) constraints on this element Element idSpecimen.request Why the specimen was collected DefinitionDetails concerning a service request that required a specimen to be collected. The request may be explicit or implied such with a ServiceRequest that requires a blood draw.
|
collection | 0..1 | BackboneElement | Element idSpecimen.collection Descrizione campione DefinitionNote aggiuntive relative al singolo campione
| |
id | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.collection.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.collection.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.collection.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
collector | Σ I | 0..1 | Reference(Practitioner | PractitionerRole) | There are no (further) constraints on this element Element idSpecimen.collection.collector Who collected the specimen DefinitionPerson who collected the specimen. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Practitioner | PractitionerRole) Constraints
|
collected[x] | Σ | 0..1 | Element idSpecimen.collection.collected[x] Data e ora del prelievo del campione. DefinitionObbligatorio nel flusso di check in richiedente. La valorizzazione di questa informazione, se disponibile, si consiglia sempre. Formato: YYYY-MM-DDThh:mm:ss+zz:zz secondo lo standard FHIR Corrispondente campo HL7 secondo specifiche regionali: SPM-17
| |
collectedDateTime | dateTime | Data type | ||
duration | Σ I | 0..1 | Duration | There are no (further) constraints on this element Element idSpecimen.collection.duration How long it took to collect specimen DefinitionThe span of time over which the collection of a specimen occurred. The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator.
|
quantity | I | 0..1 | SimpleQuantity | Element idSpecimen.collection.quantity Quantità del campione prelevata DefinitionComposto dai due componenti: quantità (numerica) e unità di misura (CE) Corrispondente campo HL7 secondo specifiche regionali: SPM-12
|
id | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.collection.quantity.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.collection.quantity.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
value | Σ | 0..1 | decimal | Element idSpecimen.collection.quantity.value Quantità DefinitionThe value of the measured amount. The value includes an implicit precision in the presentation of the value. Precision is handled implicitly in almost all cases of measurement. Corrispondente campo HL7 secondo specifiche regionali: SPM-12.1
|
comparator | Σ ?! | 0..0 | codeBinding | There are no (further) constraints on this element Element idSpecimen.collection.quantity.comparator < | <= | >= | > - how to understand the value DefinitionNot allowed to be used in this context Need a framework for handling measures where the value is <5ug/L or >400mg/L due to the limitations of measuring methodology. Note that FHIR strings SHALL NOT exceed 1MB in size If there is no comparator, then there is no modification of the value How the Quantity should be understood and represented.
|
unit | Σ | 0..1 | string | Element idSpecimen.collection.quantity.unit Unità di misura DefinitionA human-readable form of the unit. There are many representations for units of measure and in many contexts, particular representations are fixed and required. I.e. mcg for micrograms. Note that FHIR strings SHALL NOT exceed 1MB in size
|
system | Σ I | 0..1 | uri | There are no (further) constraints on this element Element idSpecimen.collection.quantity.system System that defines coded unit form DefinitionThe identification of the system that provides the coded form of the unit. Need to know the system that defines the coded form of the unit. see http://en.wikipedia.org/wiki/Uniform_resource_identifier
|
code | Σ | 0..1 | code | There are no (further) constraints on this element Element idSpecimen.collection.quantity.code Coded form of the unit DefinitionA computer processable form of the unit in some unit representation system. Need a computable form of the unit that is fixed across all forms. UCUM provides this for quantities, but SNOMED CT provides many units of interest. The preferred system is UCUM, but SNOMED CT can also be used (for customary units) or ISO 4217 for currency. The context of use may additionally require a code from a particular system.
|
method | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idSpecimen.collection.method Technique used to perform collection DefinitionA coded value specifying the technique that is used to perform the procedure. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. The technique that is used to perform the procedure.
| |
bodySite | 0..1 | CodeableConcept | Element idSpecimen.collection.bodySite Sede anatomica di prelievo DefinitionAnatomical location from which the specimen was collected (if subject is a patient). This is the target site. This element is not used for environmental specimens. Corrispondente campo HL7 secondo specifiche regionali: SPM-8 Codes describing anatomical locations. May include laterality.
| |
id | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.collection.bodySite.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.collection.bodySite.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idSpecimen.collection.bodySite.coding 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.collection.bodySite.coding.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.collection.bodySite.coding.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uri | Element idSpecimen.collection.bodySite.coding.system Sistema di codifica DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. Corrispondente campo HL7 secondo specifiche regionali: SPM-8.3
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.collection.bodySite.coding.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
|
code | Σ | 0..1 | code | Element idSpecimen.collection.bodySite.coding.code Codice sede anatomica di prelievo DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Corrispondente campo HL7 secondo specifiche regionali: SPM-8.1
|
display | Σ | 0..1 | string | Element idSpecimen.collection.bodySite.coding.display Descrizione sede anatomica di prelievo DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings SHALL NOT exceed 1MB in size
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idSpecimen.collection.bodySite.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.collection.bodySite.text 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.
|
fastingStatus[x] | Σ | 0..1 | Binding | There are no (further) constraints on this element Element idSpecimen.collection.fastingStatus[x] Whether or how long patient abstained from food and/or drink DefinitionAbstinence or reduction from some or all food, drink, or both, for a period of time prior to sample collection. Many diagnostic tests require fasting to facilitate accurate interpretation. Representing fasting status using this element is preferred to representing it with an observation using a 'pre-coordinated code' such as LOINC 2005-7 (Calcium [Moles/time] in 2 hour Urine --12 hours fasting), or using a component observation Codes describing the fasting status of the patient.
|
fastingStatusCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||
fastingStatusDuration | Duration | There are no (further) constraints on this element Data type | ||
processing | 0..* | BackboneElement | Element idSpecimen.processing Indica come il campione o il contenitore deve essere trattato (maneggiato, conservato) DefinitionDetails concerning processing and processing steps for the specimen. Corrispondente campo HL7 secondo specifiche regionali: SPM-15
| |
id | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.processing.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.processing.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.processing.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
description | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.processing.description Textual description of procedure DefinitionTextual description of procedure. Note that FHIR strings SHALL NOT exceed 1MB in size
| |
procedure | 0..1 | CodeableConceptBinding | Element idSpecimen.processing.procedure Indica come il campione o il contenitore deve essere trattato (maneggiato, conservato). DefinitionA coded value specifying the procedure used to process the specimen. Corrispondente campo HL7 secondo specifiche regionali: SPM-15 Type indicating the technique used to process the specimen.
| |
id | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.processing.procedure.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.processing.procedure.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idSpecimen.processing.procedure.coding 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.processing.procedure.coding.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.processing.procedure.coding.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uri | Element idSpecimen.processing.procedure.coding.system Sistema di codifica DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. Corrispondente campo HL7 secondo specifiche regionali: SPM-15.3
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.processing.procedure.coding.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
|
code | Σ | 0..1 | code | Element idSpecimen.processing.procedure.coding.code Codice DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Corrispondente campo HL7 secondo specifiche regionali: SPM-15.1
|
display | Σ | 0..1 | string | Element idSpecimen.processing.procedure.coding.display Descrizione DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings SHALL NOT exceed 1MB in size
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idSpecimen.processing.procedure.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.processing.procedure.text 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.
|
additive | I | 0..* | Reference(Substance) | There are no (further) constraints on this element Element idSpecimen.processing.additive Material used in the processing step DefinitionMaterial used in the processing step. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
time[x] | 0..1 | There are no (further) constraints on this element Element idSpecimen.processing.time[x] Date and time of specimen processing DefinitionA record of the time or period when the specimen processing occurred. For example the time of sample fixation or the period of time the sample was in formalin.
| ||
timeDateTime | dateTime | There are no (further) constraints on this element Data type | ||
timePeriod | Period | There are no (further) constraints on this element Data type | ||
container | 0..* | BackboneElement | Element idSpecimen.container Direct container of specimen (tube/slide, etc.) DefinitionObbligatorio per messaggi con MessageHeader.eventCoding.code uguale a OML^O35
| |
id | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.container.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.container.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idSpecimen.container.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
identifier | Σ | 0..* | Identifier | Element idSpecimen.container.identifier Id for the container DefinitionObbligatorio per messaggi con MessageHeader.eventCoding.code uguale a OML^O35. Corrispondente al campo SAC-3.
|
description | 0..1 | string | There are no (further) constraints on this element Element idSpecimen.container.description Textual description of the container DefinitionTextual description of the container. Note that FHIR strings SHALL NOT exceed 1MB in size
| |
type | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idSpecimen.container.type Kind of container directly associated with specimen DefinitionThe type of container associated with the specimen (e.g. slide, aliquot, etc.). Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Type of specimen container.
| |
capacity | I | 0..1 | SimpleQuantity | There are no (further) constraints on this element Element idSpecimen.container.capacity Container volume or size DefinitionThe capacity (volume or other measure) the container may contain. The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator.
|
specimenQuantity | I | 0..1 | SimpleQuantity | There are no (further) constraints on this element Element idSpecimen.container.specimenQuantity Quantity of specimen within container DefinitionThe quantity of specimen in the container; may be volume, dimensions, or other appropriate measurements, depending on the specimen type. The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator.
|
additive[x] | 0..1 | There are no (further) constraints on this element Element idSpecimen.container.additive[x] Additive associated with container DefinitionIntroduced substance to preserve, maintain or enhance the specimen. Examples: Formalin, Citrate, EDTA. Substance added to specimen container.
| ||
additiveCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||
additiveReference | Reference(Substance) | There are no (further) constraints on this element Data type | ||
condition | Σ | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idSpecimen.condition State of the specimen DefinitionA mode or state of being that describes the nature of the specimen. The specimen condition can be used to assess its quality or appropriateness for a specific test. Specimen condition is an observation made about the specimen. It's a point-in-time assessment. It can be used to assess its quality or appropriateness for a specific test. Codes describing the state of the specimen.
|
note | 0..* | Annotation | There are no (further) constraints on this element Element idSpecimen.note Comments DefinitionTo communicate any details or issues about the specimen or during the specimen collection. (for example: broken vial, sent with patient, frozen). For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. Annotations SHOULD NOT be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible).
|
Table View
Specimen | .. | |
Specimen.identifier | .. | |
Specimen.identifier.system | .. | |
Specimen.identifier.value | .. | |
Specimen.status | 1.. | |
Specimen.type | 1.. | |
Specimen.type.coding | .. | |
Specimen.type.coding.system | .. | |
Specimen.type.coding.code | .. | |
Specimen.type.coding.display | .. | |
Specimen.subject | Reference(ReteLabPatientCittadino) | .. |
Specimen.collection | .. | |
Specimen.collection.collected[x] | dateTime | .. |
Specimen.collection.quantity | .. | |
Specimen.collection.quantity.value | .. | |
Specimen.collection.quantity.unit | .. | |
Specimen.collection.bodySite | .. | |
Specimen.collection.bodySite.coding | .. | |
Specimen.collection.bodySite.coding.system | .. | |
Specimen.collection.bodySite.coding.code | .. | |
Specimen.collection.bodySite.coding.display | .. | |
Specimen.processing | .. | |
Specimen.processing.procedure | .. | |
Specimen.processing.procedure.coding | .. | |
Specimen.processing.procedure.coding.system | .. | |
Specimen.processing.procedure.coding.code | .. | |
Specimen.processing.procedure.coding.display | .. | |
Specimen.container | .. | |
Specimen.container.identifier | .. |
XML View
<StructureDefinition xmlns="http://hl7.org/fhir"> <url value="https://fhir.siss.regione.lombardia.it/StructureDefinition/ReteLabSpecimenCampioneDaAnalizzareCheckInCheckOut" /> <name value="ReteLabSpecimenCampioneDaAnalizzareCheckInCheckOut" /> <status value="active" /> <date value="2024-03-18T09:41:56.555349+00:00" /> <description value="Profilo che descrive i campioni che:\n- sono stati prelevati (checkIn da LR a LS), \n- pronti per essere mandati in service (checkOut da LR a LS)" /> <fhirVersion value="4.0.1" /> <kind value="resource" /> <abstract value="false" /> <type value="Specimen" /> <baseDefinition value="http://hl7.org/fhir/StructureDefinition/Specimen" /> <derivation value="constraint" /> <differential> <element id="Specimen"> <path value="Specimen" /> <short value="Descrive i campioni che verranno analizzati" /> <definition value="Risorsa utilizzata per descrivere i campioni che:\n- sono stati prelevati (checkIn da LR a LS), \n- pronti per essere mandati in service (checkOut da LR a LS)" /> <comment value="Segmento HL7 secondo specifiche regionali: SPM" /> </element> <element id="Specimen.identifier"> <path value="Specimen.identifier" /> <short value="Identificativo del campione" /> <comment value="Corrispondente campo HL7 secondo specifiche regionali: SPM-2" /> </element> <element id="Specimen.identifier.system"> <path value="Specimen.identifier.system" /> <fixedUri value="https://fhir.siss.regione.lombardia.it/sid/SpecimenIdentifier" /> </element> <element id="Specimen.identifier.value"> <path value="Specimen.identifier.value" /> <comment value="Identificativo del campione" /> </element> <element id="Specimen.status"> <path value="Specimen.status" /> <short value="Stato del campione" /> <definition value="Utilizzato nei flussi di checkin e checkout per indicare lo stato del campione (disponibile, non disponibile, non utilizzabile..)" /> <comment value="Nel dettaglio è previsto l'utilizzo dello status "unavailable" per l'identificazione del flusso di check in richiedente e "available" per l'identificazione del flusso check out richiedente." /> <min value="1" /> </element> <element id="Specimen.type"> <path value="Specimen.type" /> <short value="Tipologia del campione o identificativo del materiale biologico" /> <comment value="Corrispondente campo HL7 secondo specifiche regionali: SPM-4" /> <min value="1" /> </element> <element id="Specimen.type.coding.system"> <path value="Specimen.type.coding.system" /> <short value="Sistema di codifica" /> <comment value="Corrispondente campo HL7 secondo specifiche regionali: SPM-4 CWE-3" /> </element> <element id="Specimen.type.coding.code"> <path value="Specimen.type.coding.code" /> <short value="Codice del campione" /> <comment value="Corrispondente campo HL7 secondo specifiche regionali: SPM-4 CWE-1" /> </element> <element id="Specimen.type.coding.display"> <path value="Specimen.type.coding.display" /> <short value="Descrizione" /> <comment value="Corrispondente campo HL7 secondo specifiche regionali: SPM-4 CWE-2" /> </element> <element id="Specimen.subject"> <path value="Specimen.subject" /> <short value="Paziente di riferimento" /> <definition value="Reference al profilo ReteLabPatientCittadino" /> <type> <code value="Reference" /> <targetProfile value="https://fhir.siss.regione.lombardia.it/StructureDefinition/ReteLabPatientCittadino" /> </type> </element> <element id="Specimen.collection"> <path value="Specimen.collection" /> <short value="Descrizione campione" /> <definition value="Note aggiuntive relative al singolo campione" /> </element> <element id="Specimen.collection.collected[x]"> <path value="Specimen.collection.collected[x]" /> <short value="Data e ora del prelievo del campione." /> <definition value="Obbligatorio nel flusso di check in richiedente. \nLa valorizzazione di questa informazione, se disponibile, si consiglia sempre.\nFormato: YYYY-MM-DDThh:mm:ss+zz:zz secondo lo standard FHIR" /> <comment value="Corrispondente campo HL7 secondo specifiche regionali: SPM-17" /> <type> <code value="dateTime" /> </type> </element> <element id="Specimen.collection.quantity"> <path value="Specimen.collection.quantity" /> <short value="Quantità del campione prelevata" /> <definition value="Composto dai due componenti: quantità (numerica) e unità di misura (CE)" /> <comment value="Corrispondente campo HL7 secondo specifiche regionali: SPM-12" /> </element> <element id="Specimen.collection.quantity.value"> <path value="Specimen.collection.quantity.value" /> <short value="Quantità" /> <comment value="Corrispondente campo HL7 secondo specifiche regionali: SPM-12.1" /> </element> <element id="Specimen.collection.quantity.unit"> <path value="Specimen.collection.quantity.unit" /> <short value="Unità di misura" /> </element> <element id="Specimen.collection.bodySite"> <path value="Specimen.collection.bodySite" /> <short value="Sede anatomica di prelievo" /> <comment value="Corrispondente campo HL7 secondo specifiche regionali: SPM-8" /> </element> <element id="Specimen.collection.bodySite.coding.system"> <path value="Specimen.collection.bodySite.coding.system" /> <short value="Sistema di codifica" /> <comment value="Corrispondente campo HL7 secondo specifiche regionali: SPM-8.3" /> </element> <element id="Specimen.collection.bodySite.coding.code"> <path value="Specimen.collection.bodySite.coding.code" /> <short value="Codice sede anatomica di prelievo" /> <comment value="Corrispondente campo HL7 secondo specifiche regionali: SPM-8.1" /> </element> <element id="Specimen.collection.bodySite.coding.display"> <path value="Specimen.collection.bodySite.coding.display" /> <short value="Descrizione sede anatomica di prelievo" /> </element> <element id="Specimen.processing"> <path value="Specimen.processing" /> <short value="Indica come il campione o il contenitore deve essere trattato (maneggiato, conservato)" /> <comment value="Corrispondente campo HL7 secondo specifiche regionali: SPM-15" /> </element> <element id="Specimen.processing.procedure"> <path value="Specimen.processing.procedure" /> <short value="Indica come il campione o il contenitore deve essere trattato (maneggiato, conservato)." /> <comment value="Corrispondente campo HL7 secondo specifiche regionali: SPM-15" /> <binding> <strength value="required" /> <valueSet value="https://fhir.siss.regione.lombardia.it/ValueSet/SpecimenHandlingCode" /> </binding> </element> <element id="Specimen.processing.procedure.coding.system"> <path value="Specimen.processing.procedure.coding.system" /> <short value="Sistema di codifica" /> <comment value="Corrispondente campo HL7 secondo specifiche regionali: SPM-15.3" /> </element> <element id="Specimen.processing.procedure.coding.code"> <path value="Specimen.processing.procedure.coding.code" /> <short value="Codice" /> <comment value="Corrispondente campo HL7 secondo specifiche regionali: SPM-15.1" /> </element> <element id="Specimen.processing.procedure.coding.display"> <path value="Specimen.processing.procedure.coding.display" /> <short value="Descrizione" /> </element> <element id="Specimen.container"> <path value="Specimen.container" /> <definition value="Obbligatorio per messaggi con MessageHeader.eventCoding.code uguale a OML^O35" /> </element> <element id="Specimen.container.identifier"> <path value="Specimen.container.identifier" /> <definition value="Obbligatorio per messaggi con MessageHeader.eventCoding.code uguale a OML^O35. Corrispondente al campo SAC-3." /> </element> </differential> </StructureDefinition>
JSON View
{ "resourceType": "StructureDefinition", "url": "https://fhir.siss.regione.lombardia.it/StructureDefinition/ReteLabSpecimenCampioneDaAnalizzareCheckInCheckOut", "name": "ReteLabSpecimenCampioneDaAnalizzareCheckInCheckOut", "status": "active", "date": "2024-03-18T09:41:56.555349+00:00", "description": "Profilo che descrive i campioni che:\n- sono stati prelevati (checkIn da LR a LS), \n- pronti per essere mandati in service (checkOut da LR a LS)", "fhirVersion": "4.0.1", "kind": "resource", "abstract": false, "type": "Specimen", "baseDefinition": "http://hl7.org/fhir/StructureDefinition/Specimen", "derivation": "constraint", "differential": { "element": [ { "id": "Specimen", "path": "Specimen", "short": "Descrive i campioni che verranno analizzati", "definition": "Risorsa utilizzata per descrivere i campioni che:\n- sono stati prelevati (checkIn da LR a LS), \n- pronti per essere mandati in service (checkOut da LR a LS)", "comment": "Segmento HL7 secondo specifiche regionali: SPM" }, { "id": "Specimen.identifier", "path": "Specimen.identifier", "short": "Identificativo del campione", "comment": "Corrispondente campo HL7 secondo specifiche regionali: SPM-2" }, { "id": "Specimen.identifier.system", "path": "Specimen.identifier.system", "fixedUri": "https://fhir.siss.regione.lombardia.it/sid/SpecimenIdentifier" }, { "id": "Specimen.identifier.value", "path": "Specimen.identifier.value", "comment": "Identificativo del campione" }, { "id": "Specimen.status", "path": "Specimen.status", "short": "Stato del campione", "definition": "Utilizzato nei flussi di checkin e checkout per indicare lo stato del campione (disponibile, non disponibile, non utilizzabile..)", "comment": "Nel dettaglio è previsto l'utilizzo dello status \"unavailable\" per l'identificazione del flusso di check in richiedente e \"available\" per l'identificazione del flusso check out richiedente.", "min": 1 }, { "id": "Specimen.type", "path": "Specimen.type", "short": "Tipologia del campione o identificativo del materiale biologico", "comment": "Corrispondente campo HL7 secondo specifiche regionali: SPM-4", "min": 1 }, { "id": "Specimen.type.coding.system", "path": "Specimen.type.coding.system", "short": "Sistema di codifica", "comment": "Corrispondente campo HL7 secondo specifiche regionali: SPM-4 CWE-3" }, { "id": "Specimen.type.coding.code", "path": "Specimen.type.coding.code", "short": "Codice del campione", "comment": "Corrispondente campo HL7 secondo specifiche regionali: SPM-4 CWE-1" }, { "id": "Specimen.type.coding.display", "path": "Specimen.type.coding.display", "short": "Descrizione", "comment": "Corrispondente campo HL7 secondo specifiche regionali: SPM-4 CWE-2" }, { "id": "Specimen.subject", "path": "Specimen.subject", "short": "Paziente di riferimento", "definition": "Reference al profilo ReteLabPatientCittadino", "type": [ { "code": "Reference", "targetProfile": [ "https://fhir.siss.regione.lombardia.it/StructureDefinition/ReteLabPatientCittadino" ] } ] }, { "id": "Specimen.collection", "path": "Specimen.collection", "short": "Descrizione campione", "definition": "Note aggiuntive relative al singolo campione" }, { "id": "Specimen.collection.collected[x]", "path": "Specimen.collection.collected[x]", "short": "Data e ora del prelievo del campione.", "definition": "Obbligatorio nel flusso di check in richiedente. \nLa valorizzazione di questa informazione, se disponibile, si consiglia sempre.\nFormato: YYYY-MM-DDThh:mm:ss+zz:zz secondo lo standard FHIR", "comment": "Corrispondente campo HL7 secondo specifiche regionali: SPM-17", "type": [ { "code": "dateTime" } ] }, { "id": "Specimen.collection.quantity", "path": "Specimen.collection.quantity", "short": "Quantità del campione prelevata", "definition": "Composto dai due componenti: quantità (numerica) e unità di misura (CE)", "comment": "Corrispondente campo HL7 secondo specifiche regionali: SPM-12" }, { "id": "Specimen.collection.quantity.value", "path": "Specimen.collection.quantity.value", "short": "Quantità", "comment": "Corrispondente campo HL7 secondo specifiche regionali: SPM-12.1" }, { "id": "Specimen.collection.quantity.unit", "path": "Specimen.collection.quantity.unit", "short": "Unità di misura" }, { "id": "Specimen.collection.bodySite", "path": "Specimen.collection.bodySite", "short": "Sede anatomica di prelievo", "comment": "Corrispondente campo HL7 secondo specifiche regionali: SPM-8" }, { "id": "Specimen.collection.bodySite.coding.system", "path": "Specimen.collection.bodySite.coding.system", "short": "Sistema di codifica", "comment": "Corrispondente campo HL7 secondo specifiche regionali: SPM-8.3" }, { "id": "Specimen.collection.bodySite.coding.code", "path": "Specimen.collection.bodySite.coding.code", "short": "Codice sede anatomica di prelievo", "comment": "Corrispondente campo HL7 secondo specifiche regionali: SPM-8.1" }, { "id": "Specimen.collection.bodySite.coding.display", "path": "Specimen.collection.bodySite.coding.display", "short": "Descrizione sede anatomica di prelievo" }, { "id": "Specimen.processing", "path": "Specimen.processing", "short": "Indica come il campione o il contenitore deve essere trattato (maneggiato, conservato)", "comment": "Corrispondente campo HL7 secondo specifiche regionali: SPM-15" }, { "id": "Specimen.processing.procedure", "path": "Specimen.processing.procedure", "short": "Indica come il campione o il contenitore deve essere trattato (maneggiato, conservato).", "comment": "Corrispondente campo HL7 secondo specifiche regionali: SPM-15", "binding": { "strength": "required", "valueSet": "https://fhir.siss.regione.lombardia.it/ValueSet/SpecimenHandlingCode" } }, { "id": "Specimen.processing.procedure.coding.system", "path": "Specimen.processing.procedure.coding.system", "short": "Sistema di codifica", "comment": "Corrispondente campo HL7 secondo specifiche regionali: SPM-15.3" }, { "id": "Specimen.processing.procedure.coding.code", "path": "Specimen.processing.procedure.coding.code", "short": "Codice", "comment": "Corrispondente campo HL7 secondo specifiche regionali: SPM-15.1" }, { "id": "Specimen.processing.procedure.coding.display", "path": "Specimen.processing.procedure.coding.display", "short": "Descrizione" }, { "id": "Specimen.container", "path": "Specimen.container", "definition": "Obbligatorio per messaggi con MessageHeader.eventCoding.code uguale a OML^O35" }, { "id": "Specimen.container.identifier", "path": "Specimen.container.identifier", "definition": "Obbligatorio per messaggi con MessageHeader.eventCoding.code uguale a OML^O35. Corrispondente al campo SAC-3." } ] } }
Esempi
- Specimen check-in richiedente (prelievo del campione): Campione di sangue
- Specimen check-out richiedente (campione pronto per essere mandato al laboratorio in service): Campione di sangue
ValueSet
Nella seguente tabella sono elencati i value set relativi al profilo ReteLabSpecimenCampioneDaAnalizzareCheckInCheckOut:
Nome | Descrizione | Riferimento al dettaglio della codifica |
---|---|---|
Procedura di trattamento campione di laboratorio | Codifica della procedura di conservazione, trattamento o altro del campione | La codifica è definita dal ValueSet Procedura di trattamento campione di laboratorio |