RLDeviceRequestProtesiAusili
Descrizione
Il profilo RLDeviceRequestProtesiAusili è stato strutturato a partire dalla risorsa generica FHIR DeviceRequest per contenere le informazioni necessarie per la fornitura al paziente della protesi o dell’ausilio previsto in fase di stesura del progetto individuale.
Di seguito è presentato il contenuto del profilo in diversi formati. La corrispondente definizione è consultabile al seguente link: RLDeviceRequestProtesiAusili.
Snapshot View
RLDeviceRequestProtesiAusili (DeviceRequest) | I | DeviceRequest | There are no (further) constraints on this element Element idDeviceRequest Medical device request DefinitionRepresents a request for a patient to employ a medical device. The device may be an implantable device, or an external assistive device, such as a walker.
| |
id | Σ | 1..1 | string | Element idDeviceRequest.id UUID prodotto dal server FHIR (applicativo) che detiene la risorsa. Per maggiori informazioni su chi detiene la risorsa consultare il paragrafo API-Restful nella pagina di Contesto. 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 | Σ | 1..1 | Meta | Element idDeviceRequest.meta Metadati della risorsa 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idDeviceRequest.meta.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 idDeviceRequest.meta.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
|
versionId | Σ | 1..1 | id | Element idDeviceRequest.meta.versionId Versione della risorsa DefinitionThe version specific identifier, as it appears in the version portion of the URL. This value changes when the resource is created, updated, or deleted. The server assigns this value, and ignores what the client specifies, except in the case that the server is imposing version integrity on updates/deletes.
|
lastUpdated | Σ | 1..1 | instant | Element idDeviceRequest.meta.lastUpdated Data e ora di ultimo aggiornamento della risorsa DefinitionFormato standard FHIR: YYY-MM-DDThh:mm:ss.sss+zz:zz This value is always populated except when the resource is first being created. The server / resource manager sets this value; what a client provides is irrelevant. This is equivalent to the HTTP Last-Modified and SHOULD have the same value on a read interaction.
|
source | Σ | 0..1 | uri | There are no (further) constraints on this element Element idDeviceRequest.meta.source Identifies where the resource comes from DefinitionA uri that identifies the source system of the resource. This provides a minimal amount of Provenance information that can be used to track or differentiate the source of information in the resource. The source may identify another FHIR server, document, message, database, etc. In the provenance resource, this corresponds to Provenance.entity.what[x]. The exact use of the source (and the implied Provenance.entity.role) is left to implementer discretion. Only one nominated source is allowed; for additional provenance details, a full Provenance resource should be used. This element can be used to indicate where the current master source of a resource that has a canonical URL if the resource is no longer hosted at the canonical URL.
|
profile | Σ | 1..1 | canonical(StructureDefinition)Fixed Value | Element idDeviceRequest.meta.profile Profilo al quale la risorsa si riferisce DefinitionA list of profiles (references to StructureDefinition resources) that this resource claims to conform to. The URL is a reference to StructureDefinition.url. It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set. canonical(StructureDefinition) Constraints
https://fhir.siss.regione.lombardia.it/StructureDefinition/RLDeviceRequestProtesiAusili
|
security | Σ | 0..* | CodingBinding | There are no (further) constraints on this element Element idDeviceRequest.meta.security Security Labels applied to this resource DefinitionSecurity labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure. The security labels can be updated without changing the stated version of the resource. The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored. Security Labels from the Healthcare Privacy and Security Classification System.
|
tag | Σ | 0..* | Coding | There are no (further) constraints on this element Element idDeviceRequest.meta.tag Tags applied to this resource DefinitionTags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource. The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored. Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
|
implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idDeviceRequest.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 idDeviceRequest.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 idDeviceRequest.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 idDeviceRequest.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 idDeviceRequest.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
|
prescrizioneElettronica | I | 0..1 | Extension(boolean) | Element idDeviceRequest.extension:prescrizioneElettronica Flag riguardo la necessità di una prescrizione elettronica per il paziente Alternate namesextensions, user content DefinitionOptional Extension Element - found in all resources. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. https://fhir.siss.regione.lombardia.it/StructureDefinition/RLDeviceRequestPrescrizioneElettronica Constraints
|
modifierExtension | ?! I | 0..* | Extension | There are no (further) constraints on this element Element idDeviceRequest.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 | There are no (further) constraints on this element Element idDeviceRequest.identifier External Request identifier DefinitionIdentifiers assigned to this order by the orderer or by the receiver.
|
instantiatesCanonical | Σ | 0..* | canonical(ActivityDefinition | PlanDefinition) | There are no (further) constraints on this element Element idDeviceRequest.instantiatesCanonical Instantiates FHIR protocol or definition DefinitionThe URL pointing to a FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this DeviceRequest. Note: This is a business identifier, not a resource identifier (see discussion). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number. canonical(ActivityDefinition | PlanDefinition) Constraints
|
instantiatesUri | Σ | 0..* | uri | There are no (further) constraints on this element Element idDeviceRequest.instantiatesUri Instantiates external protocol or definition DefinitionThe URL pointing to an externally maintained protocol, guideline, orderset or other definition that is adhered to in whole or in part by this DeviceRequest. This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier.
|
basedOn | Σ I | 1..1 | Reference(RLCarePlanProgettoIndividuale) | Element idDeviceRequest.basedOn Riferimento al progetto individuale nel quale è prevista la fornitura della protesi o dell'ausilio DefinitionReference al profilo RLCarePlanProgettoIndividuale contenente il progetto individuale del paziente. Deve essere inserito l'UUID generato dal server FHIR (applicativo) detentore della risorsa. Per tutte le informazioni sui server FHIR (applicativi) e le relative risorse detenute consultare la pagina API RESTful della sezione Contesto di questa Implementation Guide Il dato è detenuto dal SGDT Reference(RLCarePlanProgettoIndividuale) Constraints
|
priorRequest | Σ I | 0..* | Reference(Resource) | There are no (further) constraints on this element Element idDeviceRequest.priorRequest What request replaces DefinitionThe request takes the place of the referenced completed or terminated request(s). 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.
|
groupIdentifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element idDeviceRequest.groupIdentifier Identifier of composite request DefinitionComposite request this is part of.
|
status | Σ ?! | 1..1 | codeBindingFixed Value | Element idDeviceRequest.status Stato della fornitura della protesi o dell'ausilio DefinitionValore fisso su "active" This element is labeled as a modifier because the status contains the codes cancelled and entered-in-error that mark the request as not currently valid. Codes representing the status of the request.
active
|
intent | Σ ?! | 1..1 | codeBindingFixed Value | Element idDeviceRequest.intent Intento della richesta DefinitionValore fisso su "order" Note that FHIR strings SHALL NOT exceed 1MB in size The kind of diagnostic request.
order
|
priority | Σ | 0..1 | codeBinding | There are no (further) constraints on this element Element idDeviceRequest.priority routine | urgent | asap | stat DefinitionIndicates how quickly the {{title}} should be addressed with respect to other requests. Note that FHIR strings SHALL NOT exceed 1MB in size If missing, normal priority Identifies the level of importance to be assigned to actioning the request.
|
code[x] | Σ | 1..1 | Element idDeviceRequest.code[x] Codice e descrizione dell'ausilio di protesica DefinitionThe details of the device to be used. Codes for devices that can be requested.
| |
codeCodeableConcept | CodeableConcept | Data type | ||
id | 0..1 | string | There are no (further) constraints on this element Element idDeviceRequest.code[x].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 idDeviceRequest.code[x].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 | Σ | 1..1 | Coding | There are no (further) constraints on this element Element idDeviceRequest.code[x].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 idDeviceRequest.code[x].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 idDeviceRequest.code[x].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 | Σ | 1..1 | uriFixed Value | Element idDeviceRequest.code[x].coding.system Identity of the terminology system 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. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
https://fhir.siss.regione.lombardia.it/ValueSet/DDC-AusilioProtesi
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idDeviceRequest.code[x].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 | Σ | 1..1 | codeBinding | Element idDeviceRequest.code[x].coding.code Codice dell'ausilio di protesica DefinitionStringa alfanumerica di al più 26 caratteri Need to refer to a particular code in the system. La fonte del dato è il campo CD_AUSILIO della tabella ausili di Protesica i cui dettagli sono consultabili nel documento DC-DDC-SIAA#02 ed accessibili tramite i servizi descritti nel documento DC-DDC-SIAA#01 ValueSet che identifica gli ausili di protesica
|
display | Σ | 1..1 | string | Element idDeviceRequest.code[x].coding.display Descrizione dell'ausilio di protesica DefinitionStringra alfanumerica di al più 1024 caratteri. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. La fonte del dato è il campo DS_AUSILIO della tabella ausili di Protesica i cui dettagli sono consultabili nel documento DC-DDC-SIAA#02 ed accessibili tramite i servizi descritti nel documento DC-DDC-SIAA#01
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idDeviceRequest.code[x].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 idDeviceRequest.code[x].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.
|
parameter | 0..* | BackboneElement | There are no (further) constraints on this element Element idDeviceRequest.parameter Device details DefinitionSpecific parameters for the ordered item. For example, the prism value for lenses.
| |
id | 0..1 | string | There are no (further) constraints on this element Element idDeviceRequest.parameter.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 idDeviceRequest.parameter.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 idDeviceRequest.parameter.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.
|
code | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idDeviceRequest.parameter.code Device detail DefinitionA code or string that identifies the device detail being asserted. 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. A code that identifies the device detail.
| |
value[x] | 0..1 | There are no (further) constraints on this element Element idDeviceRequest.parameter.value[x] Value of detail DefinitionThe value of the device detail. Range means device should have a value that falls somewhere within the specified range.
| ||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||
valueQuantity | Quantity | There are no (further) constraints on this element Data type | ||
valueRange | Range | There are no (further) constraints on this element Data type | ||
valueBoolean | boolean | There are no (further) constraints on this element Data type | ||
subject | Σ I | 1..1 | Reference(RLPatientCittadino) | Element idDeviceRequest.subject Paziente al quale deve essere fornita la protesi o l'ausilio DefinitionReference alla risorsa RLPatientCittadino contenente i dettagli anagrafici del paziente Il dato è detenuto dal SGDT
|
encounter | Σ I | 0..1 | Reference(Encounter) | There are no (further) constraints on this element Element idDeviceRequest.encounter Encounter motivating request DefinitionAn encounter that provides additional context in which this request is made. 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.
|
occurrence[x] | Σ | 0..1 | Element idDeviceRequest.occurrence[x] Periodo di utilizzo della protesi o dell'ausilio DefinitionThe timing schedule for the use of the device. The Schedule data type allows many different expressions, for example. "Every 8 hours"; "Three times a day"; "1/2 an hour before breakfast for 10 days from 23-Dec 2011:"; "15 Oct 2013, 17 Oct 2013 and 1 Nov 2013".
| |
occurrencePeriod | Period | Data type | ||
id | 0..1 | string | There are no (further) constraints on this element Element idDeviceRequest.occurrence[x].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 idDeviceRequest.occurrence[x].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
|
start | Σ I | 1..1 | dateTime | Element idDeviceRequest.occurrence[x].start Data di inizio del period di utilizzo DefinitionFormato: YYYY-MM-DD secondo lo standard FHIR Il dato a detenuto dal SGDT
|
end | Σ I | 1..1 | dateTime | Element idDeviceRequest.occurrence[x].end Data di fine del periodo di utilizzo DefinitionFormato: YYYY-MM-DD secondo lo standard FHIR Il dato a detenuto dal SGDT If the end of the period is missing, it means that the period is ongoing
|
authoredOn | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element idDeviceRequest.authoredOn When recorded DefinitionWhen the request transitioned to being actionable.
|
requester | Σ I | 0..1 | Reference(Device | Practitioner | PractitionerRole | Organization) | There are no (further) constraints on this element Element idDeviceRequest.requester Who/what is requesting diagnostics DefinitionThe individual who initiated the request and has responsibility for its activation. 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(Device | Practitioner | PractitionerRole | Organization) Constraints
|
performerType | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idDeviceRequest.performerType Filler role DefinitionDesired type of performer for doing the diagnostic testing. 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. Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc.
|
performer | Σ I | 0..1 | Reference(Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService | Patient | Device | RelatedPerson) | There are no (further) constraints on this element Element idDeviceRequest.performer Requested Filler DefinitionThe desired performer for doing the diagnostic testing. 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 | Organization | CareTeam | HealthcareService | Patient | Device | RelatedPerson) Constraints
|
reasonCode | Σ | 0..* | CodeableConcept | There are no (further) constraints on this element Element idDeviceRequest.reasonCode Coded Reason for request DefinitionReason or justification for the use of this device. 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. Diagnosis or problem codes justifying the reason for requesting the device.
|
reasonReference | Σ I | 0..* | Reference(Condition | Observation | DiagnosticReport | DocumentReference) | There are no (further) constraints on this element Element idDeviceRequest.reasonReference Linked Reason for request DefinitionReason or justification for the use of this device. 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(Condition | Observation | DiagnosticReport | DocumentReference) Constraints
|
insurance | I | 0..* | Reference(Coverage | ClaimResponse) | There are no (further) constraints on this element Element idDeviceRequest.insurance Associated insurance coverage DefinitionInsurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be required for delivering the requested service. 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(Coverage | ClaimResponse) Constraints
|
supportingInfo | I | 0..* | Reference(Resource) | There are no (further) constraints on this element Element idDeviceRequest.supportingInfo Additional clinical information DefinitionAdditional clinical information about the patient that may influence the request fulfilment. For example, this may include where on the subject's body the device will be used (i.e. the target site). Knowing where the device is targeted is important for tracking if multiple sites are possible. 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.
|
note | 0..1 | Annotation | Element idDeviceRequest.note Note / commenti aggiuntivi DefinitionStringa alfanumerica al più di 1000 caratteri Il dato è detenuto dal SGDT
| |
relevantHistory | I | 0..* | Reference(Provenance) | There are no (further) constraints on this element Element idDeviceRequest.relevantHistory Request provenance DefinitionKey events in the history of the request. This might not include provenances for all versions of the request - only those deemed "relevant" or important. This SHALL NOT include the Provenance associated with this current version of the resource. (If that provenance is deemed to be a "relevant" change, it will need to be added as part of a later update. Until then, it can be queried directly as the Provenance that points to this version using _revinclude All Provenances should have some historical version of this Request as their subject.
|
Differential View
RLDeviceRequestProtesiAusili (DeviceRequest) | I | DeviceRequest | There are no (further) constraints on this element Element idDeviceRequest Medical device request DefinitionRepresents a request for a patient to employ a medical device. The device may be an implantable device, or an external assistive device, such as a walker.
| |
id | Σ | 1..1 | string | Element idDeviceRequest.id UUID prodotto dal server FHIR (applicativo) che detiene la risorsa. Per maggiori informazioni su chi detiene la risorsa consultare il paragrafo API-Restful nella pagina di Contesto. 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 | Σ | 1..1 | Meta | Element idDeviceRequest.meta Metadati della risorsa 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idDeviceRequest.meta.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 idDeviceRequest.meta.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
|
versionId | Σ | 1..1 | id | Element idDeviceRequest.meta.versionId Versione della risorsa DefinitionThe version specific identifier, as it appears in the version portion of the URL. This value changes when the resource is created, updated, or deleted. The server assigns this value, and ignores what the client specifies, except in the case that the server is imposing version integrity on updates/deletes.
|
lastUpdated | Σ | 1..1 | instant | Element idDeviceRequest.meta.lastUpdated Data e ora di ultimo aggiornamento della risorsa DefinitionFormato standard FHIR: YYY-MM-DDThh:mm:ss.sss+zz:zz This value is always populated except when the resource is first being created. The server / resource manager sets this value; what a client provides is irrelevant. This is equivalent to the HTTP Last-Modified and SHOULD have the same value on a read interaction.
|
source | Σ | 0..1 | uri | There are no (further) constraints on this element Element idDeviceRequest.meta.source Identifies where the resource comes from DefinitionA uri that identifies the source system of the resource. This provides a minimal amount of Provenance information that can be used to track or differentiate the source of information in the resource. The source may identify another FHIR server, document, message, database, etc. In the provenance resource, this corresponds to Provenance.entity.what[x]. The exact use of the source (and the implied Provenance.entity.role) is left to implementer discretion. Only one nominated source is allowed; for additional provenance details, a full Provenance resource should be used. This element can be used to indicate where the current master source of a resource that has a canonical URL if the resource is no longer hosted at the canonical URL.
|
profile | Σ | 1..1 | canonical(StructureDefinition)Fixed Value | Element idDeviceRequest.meta.profile Profilo al quale la risorsa si riferisce DefinitionA list of profiles (references to StructureDefinition resources) that this resource claims to conform to. The URL is a reference to StructureDefinition.url. It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set. canonical(StructureDefinition) Constraints
https://fhir.siss.regione.lombardia.it/StructureDefinition/RLDeviceRequestProtesiAusili
|
security | Σ | 0..* | CodingBinding | There are no (further) constraints on this element Element idDeviceRequest.meta.security Security Labels applied to this resource DefinitionSecurity labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure. The security labels can be updated without changing the stated version of the resource. The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored. Security Labels from the Healthcare Privacy and Security Classification System.
|
tag | Σ | 0..* | Coding | There are no (further) constraints on this element Element idDeviceRequest.meta.tag Tags applied to this resource DefinitionTags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource. The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored. Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
|
implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idDeviceRequest.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 idDeviceRequest.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 idDeviceRequest.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 idDeviceRequest.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 idDeviceRequest.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
|
prescrizioneElettronica | I | 0..1 | Extension(boolean) | Element idDeviceRequest.extension:prescrizioneElettronica Flag riguardo la necessità di una prescrizione elettronica per il paziente Alternate namesextensions, user content DefinitionOptional Extension Element - found in all resources. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. https://fhir.siss.regione.lombardia.it/StructureDefinition/RLDeviceRequestPrescrizioneElettronica Constraints
|
modifierExtension | ?! I | 0..* | Extension | There are no (further) constraints on this element Element idDeviceRequest.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 | There are no (further) constraints on this element Element idDeviceRequest.identifier External Request identifier DefinitionIdentifiers assigned to this order by the orderer or by the receiver.
|
instantiatesCanonical | Σ | 0..* | canonical(ActivityDefinition | PlanDefinition) | There are no (further) constraints on this element Element idDeviceRequest.instantiatesCanonical Instantiates FHIR protocol or definition DefinitionThe URL pointing to a FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this DeviceRequest. Note: This is a business identifier, not a resource identifier (see discussion). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number. canonical(ActivityDefinition | PlanDefinition) Constraints
|
instantiatesUri | Σ | 0..* | uri | There are no (further) constraints on this element Element idDeviceRequest.instantiatesUri Instantiates external protocol or definition DefinitionThe URL pointing to an externally maintained protocol, guideline, orderset or other definition that is adhered to in whole or in part by this DeviceRequest. This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier.
|
basedOn | Σ I | 1..1 | Reference(RLCarePlanProgettoIndividuale) | Element idDeviceRequest.basedOn Riferimento al progetto individuale nel quale è prevista la fornitura della protesi o dell'ausilio DefinitionReference al profilo RLCarePlanProgettoIndividuale contenente il progetto individuale del paziente. Deve essere inserito l'UUID generato dal server FHIR (applicativo) detentore della risorsa. Per tutte le informazioni sui server FHIR (applicativi) e le relative risorse detenute consultare la pagina API RESTful della sezione Contesto di questa Implementation Guide Il dato è detenuto dal SGDT Reference(RLCarePlanProgettoIndividuale) Constraints
|
priorRequest | Σ I | 0..* | Reference(Resource) | There are no (further) constraints on this element Element idDeviceRequest.priorRequest What request replaces DefinitionThe request takes the place of the referenced completed or terminated request(s). 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.
|
groupIdentifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element idDeviceRequest.groupIdentifier Identifier of composite request DefinitionComposite request this is part of.
|
status | Σ ?! | 1..1 | codeBindingFixed Value | Element idDeviceRequest.status Stato della fornitura della protesi o dell'ausilio DefinitionValore fisso su "active" This element is labeled as a modifier because the status contains the codes cancelled and entered-in-error that mark the request as not currently valid. Codes representing the status of the request.
active
|
intent | Σ ?! | 1..1 | codeBindingFixed Value | Element idDeviceRequest.intent Intento della richesta DefinitionValore fisso su "order" Note that FHIR strings SHALL NOT exceed 1MB in size The kind of diagnostic request.
order
|
priority | Σ | 0..1 | codeBinding | There are no (further) constraints on this element Element idDeviceRequest.priority routine | urgent | asap | stat DefinitionIndicates how quickly the {{title}} should be addressed with respect to other requests. Note that FHIR strings SHALL NOT exceed 1MB in size If missing, normal priority Identifies the level of importance to be assigned to actioning the request.
|
code[x] | Σ | 1..1 | Element idDeviceRequest.code[x] Codice e descrizione dell'ausilio di protesica DefinitionThe details of the device to be used. Codes for devices that can be requested.
| |
codeCodeableConcept | CodeableConcept | Data type | ||
id | 0..1 | string | There are no (further) constraints on this element Element idDeviceRequest.code[x].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 idDeviceRequest.code[x].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 | Σ | 1..1 | Coding | There are no (further) constraints on this element Element idDeviceRequest.code[x].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 idDeviceRequest.code[x].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 idDeviceRequest.code[x].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 | Σ | 1..1 | uriFixed Value | Element idDeviceRequest.code[x].coding.system Identity of the terminology system 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. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
https://fhir.siss.regione.lombardia.it/ValueSet/DDC-AusilioProtesi
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idDeviceRequest.code[x].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 | Σ | 1..1 | codeBinding | Element idDeviceRequest.code[x].coding.code Codice dell'ausilio di protesica DefinitionStringa alfanumerica di al più 26 caratteri Need to refer to a particular code in the system. La fonte del dato è il campo CD_AUSILIO della tabella ausili di Protesica i cui dettagli sono consultabili nel documento DC-DDC-SIAA#02 ed accessibili tramite i servizi descritti nel documento DC-DDC-SIAA#01 ValueSet che identifica gli ausili di protesica
|
display | Σ | 1..1 | string | Element idDeviceRequest.code[x].coding.display Descrizione dell'ausilio di protesica DefinitionStringra alfanumerica di al più 1024 caratteri. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. La fonte del dato è il campo DS_AUSILIO della tabella ausili di Protesica i cui dettagli sono consultabili nel documento DC-DDC-SIAA#02 ed accessibili tramite i servizi descritti nel documento DC-DDC-SIAA#01
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idDeviceRequest.code[x].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 idDeviceRequest.code[x].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.
|
parameter | 0..* | BackboneElement | There are no (further) constraints on this element Element idDeviceRequest.parameter Device details DefinitionSpecific parameters for the ordered item. For example, the prism value for lenses.
| |
id | 0..1 | string | There are no (further) constraints on this element Element idDeviceRequest.parameter.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 idDeviceRequest.parameter.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 idDeviceRequest.parameter.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.
|
code | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idDeviceRequest.parameter.code Device detail DefinitionA code or string that identifies the device detail being asserted. 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. A code that identifies the device detail.
| |
value[x] | 0..1 | There are no (further) constraints on this element Element idDeviceRequest.parameter.value[x] Value of detail DefinitionThe value of the device detail. Range means device should have a value that falls somewhere within the specified range.
| ||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||
valueQuantity | Quantity | There are no (further) constraints on this element Data type | ||
valueRange | Range | There are no (further) constraints on this element Data type | ||
valueBoolean | boolean | There are no (further) constraints on this element Data type | ||
subject | Σ I | 1..1 | Reference(RLPatientCittadino) | Element idDeviceRequest.subject Paziente al quale deve essere fornita la protesi o l'ausilio DefinitionReference alla risorsa RLPatientCittadino contenente i dettagli anagrafici del paziente Il dato è detenuto dal SGDT
|
encounter | Σ I | 0..1 | Reference(Encounter) | There are no (further) constraints on this element Element idDeviceRequest.encounter Encounter motivating request DefinitionAn encounter that provides additional context in which this request is made. 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.
|
occurrence[x] | Σ | 0..1 | Element idDeviceRequest.occurrence[x] Periodo di utilizzo della protesi o dell'ausilio DefinitionThe timing schedule for the use of the device. The Schedule data type allows many different expressions, for example. "Every 8 hours"; "Three times a day"; "1/2 an hour before breakfast for 10 days from 23-Dec 2011:"; "15 Oct 2013, 17 Oct 2013 and 1 Nov 2013".
| |
occurrencePeriod | Period | Data type | ||
id | 0..1 | string | There are no (further) constraints on this element Element idDeviceRequest.occurrence[x].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 idDeviceRequest.occurrence[x].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
|
start | Σ I | 1..1 | dateTime | Element idDeviceRequest.occurrence[x].start Data di inizio del period di utilizzo DefinitionFormato: YYYY-MM-DD secondo lo standard FHIR Il dato a detenuto dal SGDT
|
end | Σ I | 1..1 | dateTime | Element idDeviceRequest.occurrence[x].end Data di fine del periodo di utilizzo DefinitionFormato: YYYY-MM-DD secondo lo standard FHIR Il dato a detenuto dal SGDT If the end of the period is missing, it means that the period is ongoing
|
authoredOn | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element idDeviceRequest.authoredOn When recorded DefinitionWhen the request transitioned to being actionable.
|
requester | Σ I | 0..1 | Reference(Device | Practitioner | PractitionerRole | Organization) | There are no (further) constraints on this element Element idDeviceRequest.requester Who/what is requesting diagnostics DefinitionThe individual who initiated the request and has responsibility for its activation. 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(Device | Practitioner | PractitionerRole | Organization) Constraints
|
performerType | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idDeviceRequest.performerType Filler role DefinitionDesired type of performer for doing the diagnostic testing. 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. Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc.
|
performer | Σ I | 0..1 | Reference(Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService | Patient | Device | RelatedPerson) | There are no (further) constraints on this element Element idDeviceRequest.performer Requested Filler DefinitionThe desired performer for doing the diagnostic testing. 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 | Organization | CareTeam | HealthcareService | Patient | Device | RelatedPerson) Constraints
|
reasonCode | Σ | 0..* | CodeableConcept | There are no (further) constraints on this element Element idDeviceRequest.reasonCode Coded Reason for request DefinitionReason or justification for the use of this device. 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. Diagnosis or problem codes justifying the reason for requesting the device.
|
reasonReference | Σ I | 0..* | Reference(Condition | Observation | DiagnosticReport | DocumentReference) | There are no (further) constraints on this element Element idDeviceRequest.reasonReference Linked Reason for request DefinitionReason or justification for the use of this device. 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(Condition | Observation | DiagnosticReport | DocumentReference) Constraints
|
insurance | I | 0..* | Reference(Coverage | ClaimResponse) | There are no (further) constraints on this element Element idDeviceRequest.insurance Associated insurance coverage DefinitionInsurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be required for delivering the requested service. 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(Coverage | ClaimResponse) Constraints
|
supportingInfo | I | 0..* | Reference(Resource) | There are no (further) constraints on this element Element idDeviceRequest.supportingInfo Additional clinical information DefinitionAdditional clinical information about the patient that may influence the request fulfilment. For example, this may include where on the subject's body the device will be used (i.e. the target site). Knowing where the device is targeted is important for tracking if multiple sites are possible. 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.
|
note | 0..1 | Annotation | Element idDeviceRequest.note Note / commenti aggiuntivi DefinitionStringa alfanumerica al più di 1000 caratteri Il dato è detenuto dal SGDT
| |
relevantHistory | I | 0..* | Reference(Provenance) | There are no (further) constraints on this element Element idDeviceRequest.relevantHistory Request provenance DefinitionKey events in the history of the request. This might not include provenances for all versions of the request - only those deemed "relevant" or important. This SHALL NOT include the Provenance associated with this current version of the resource. (If that provenance is deemed to be a "relevant" change, it will need to be added as part of a later update. Until then, it can be queried directly as the Provenance that points to this version using _revinclude All Provenances should have some historical version of this Request as their subject.
|
Hybrid View
RLDeviceRequestProtesiAusili (DeviceRequest) | I | DeviceRequest | There are no (further) constraints on this element Element idDeviceRequest Medical device request DefinitionRepresents a request for a patient to employ a medical device. The device may be an implantable device, or an external assistive device, such as a walker.
| |
id | Σ | 1..1 | string | Element idDeviceRequest.id UUID prodotto dal server FHIR (applicativo) che detiene la risorsa. Per maggiori informazioni su chi detiene la risorsa consultare il paragrafo API-Restful nella pagina di Contesto. 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 | Σ | 1..1 | Meta | Element idDeviceRequest.meta Metadati della risorsa 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idDeviceRequest.meta.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 idDeviceRequest.meta.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
|
versionId | Σ | 1..1 | id | Element idDeviceRequest.meta.versionId Versione della risorsa DefinitionThe version specific identifier, as it appears in the version portion of the URL. This value changes when the resource is created, updated, or deleted. The server assigns this value, and ignores what the client specifies, except in the case that the server is imposing version integrity on updates/deletes.
|
lastUpdated | Σ | 1..1 | instant | Element idDeviceRequest.meta.lastUpdated Data e ora di ultimo aggiornamento della risorsa DefinitionFormato standard FHIR: YYY-MM-DDThh:mm:ss.sss+zz:zz This value is always populated except when the resource is first being created. The server / resource manager sets this value; what a client provides is irrelevant. This is equivalent to the HTTP Last-Modified and SHOULD have the same value on a read interaction.
|
source | Σ | 0..1 | uri | There are no (further) constraints on this element Element idDeviceRequest.meta.source Identifies where the resource comes from DefinitionA uri that identifies the source system of the resource. This provides a minimal amount of Provenance information that can be used to track or differentiate the source of information in the resource. The source may identify another FHIR server, document, message, database, etc. In the provenance resource, this corresponds to Provenance.entity.what[x]. The exact use of the source (and the implied Provenance.entity.role) is left to implementer discretion. Only one nominated source is allowed; for additional provenance details, a full Provenance resource should be used. This element can be used to indicate where the current master source of a resource that has a canonical URL if the resource is no longer hosted at the canonical URL.
|
profile | Σ | 1..1 | canonical(StructureDefinition)Fixed Value | Element idDeviceRequest.meta.profile Profilo al quale la risorsa si riferisce DefinitionA list of profiles (references to StructureDefinition resources) that this resource claims to conform to. The URL is a reference to StructureDefinition.url. It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set. canonical(StructureDefinition) Constraints
https://fhir.siss.regione.lombardia.it/StructureDefinition/RLDeviceRequestProtesiAusili
|
security | Σ | 0..* | CodingBinding | There are no (further) constraints on this element Element idDeviceRequest.meta.security Security Labels applied to this resource DefinitionSecurity labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure. The security labels can be updated without changing the stated version of the resource. The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored. Security Labels from the Healthcare Privacy and Security Classification System.
|
tag | Σ | 0..* | Coding | There are no (further) constraints on this element Element idDeviceRequest.meta.tag Tags applied to this resource DefinitionTags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource. The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored. Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
|
implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idDeviceRequest.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 idDeviceRequest.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 idDeviceRequest.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 idDeviceRequest.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 idDeviceRequest.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
|
prescrizioneElettronica | I | 0..1 | Extension(boolean) | Element idDeviceRequest.extension:prescrizioneElettronica Flag riguardo la necessità di una prescrizione elettronica per il paziente Alternate namesextensions, user content DefinitionOptional Extension Element - found in all resources. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. https://fhir.siss.regione.lombardia.it/StructureDefinition/RLDeviceRequestPrescrizioneElettronica Constraints
|
modifierExtension | ?! I | 0..* | Extension | There are no (further) constraints on this element Element idDeviceRequest.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 | There are no (further) constraints on this element Element idDeviceRequest.identifier External Request identifier DefinitionIdentifiers assigned to this order by the orderer or by the receiver.
|
instantiatesCanonical | Σ | 0..* | canonical(ActivityDefinition | PlanDefinition) | There are no (further) constraints on this element Element idDeviceRequest.instantiatesCanonical Instantiates FHIR protocol or definition DefinitionThe URL pointing to a FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this DeviceRequest. Note: This is a business identifier, not a resource identifier (see discussion). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number. canonical(ActivityDefinition | PlanDefinition) Constraints
|
instantiatesUri | Σ | 0..* | uri | There are no (further) constraints on this element Element idDeviceRequest.instantiatesUri Instantiates external protocol or definition DefinitionThe URL pointing to an externally maintained protocol, guideline, orderset or other definition that is adhered to in whole or in part by this DeviceRequest. This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier.
|
basedOn | Σ I | 1..1 | Reference(RLCarePlanProgettoIndividuale) | Element idDeviceRequest.basedOn Riferimento al progetto individuale nel quale è prevista la fornitura della protesi o dell'ausilio DefinitionReference al profilo RLCarePlanProgettoIndividuale contenente il progetto individuale del paziente. Deve essere inserito l'UUID generato dal server FHIR (applicativo) detentore della risorsa. Per tutte le informazioni sui server FHIR (applicativi) e le relative risorse detenute consultare la pagina API RESTful della sezione Contesto di questa Implementation Guide Il dato è detenuto dal SGDT Reference(RLCarePlanProgettoIndividuale) Constraints
|
priorRequest | Σ I | 0..* | Reference(Resource) | There are no (further) constraints on this element Element idDeviceRequest.priorRequest What request replaces DefinitionThe request takes the place of the referenced completed or terminated request(s). 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.
|
groupIdentifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element idDeviceRequest.groupIdentifier Identifier of composite request DefinitionComposite request this is part of.
|
status | Σ ?! | 1..1 | codeBindingFixed Value | Element idDeviceRequest.status Stato della fornitura della protesi o dell'ausilio DefinitionValore fisso su "active" This element is labeled as a modifier because the status contains the codes cancelled and entered-in-error that mark the request as not currently valid. Codes representing the status of the request.
active
|
intent | Σ ?! | 1..1 | codeBindingFixed Value | Element idDeviceRequest.intent Intento della richesta DefinitionValore fisso su "order" Note that FHIR strings SHALL NOT exceed 1MB in size The kind of diagnostic request.
order
|
priority | Σ | 0..1 | codeBinding | There are no (further) constraints on this element Element idDeviceRequest.priority routine | urgent | asap | stat DefinitionIndicates how quickly the {{title}} should be addressed with respect to other requests. Note that FHIR strings SHALL NOT exceed 1MB in size If missing, normal priority Identifies the level of importance to be assigned to actioning the request.
|
code[x] | Σ | 1..1 | Element idDeviceRequest.code[x] Codice e descrizione dell'ausilio di protesica DefinitionThe details of the device to be used. Codes for devices that can be requested.
| |
codeCodeableConcept | CodeableConcept | Data type | ||
id | 0..1 | string | There are no (further) constraints on this element Element idDeviceRequest.code[x].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 idDeviceRequest.code[x].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 | Σ | 1..1 | Coding | There are no (further) constraints on this element Element idDeviceRequest.code[x].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 idDeviceRequest.code[x].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 idDeviceRequest.code[x].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 | Σ | 1..1 | uriFixed Value | Element idDeviceRequest.code[x].coding.system Identity of the terminology system 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. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
https://fhir.siss.regione.lombardia.it/ValueSet/DDC-AusilioProtesi
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idDeviceRequest.code[x].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 | Σ | 1..1 | codeBinding | Element idDeviceRequest.code[x].coding.code Codice dell'ausilio di protesica DefinitionStringa alfanumerica di al più 26 caratteri Need to refer to a particular code in the system. La fonte del dato è il campo CD_AUSILIO della tabella ausili di Protesica i cui dettagli sono consultabili nel documento DC-DDC-SIAA#02 ed accessibili tramite i servizi descritti nel documento DC-DDC-SIAA#01 ValueSet che identifica gli ausili di protesica
|
display | Σ | 1..1 | string | Element idDeviceRequest.code[x].coding.display Descrizione dell'ausilio di protesica DefinitionStringra alfanumerica di al più 1024 caratteri. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. La fonte del dato è il campo DS_AUSILIO della tabella ausili di Protesica i cui dettagli sono consultabili nel documento DC-DDC-SIAA#02 ed accessibili tramite i servizi descritti nel documento DC-DDC-SIAA#01
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idDeviceRequest.code[x].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 idDeviceRequest.code[x].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.
|
parameter | 0..* | BackboneElement | There are no (further) constraints on this element Element idDeviceRequest.parameter Device details DefinitionSpecific parameters for the ordered item. For example, the prism value for lenses.
| |
id | 0..1 | string | There are no (further) constraints on this element Element idDeviceRequest.parameter.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 idDeviceRequest.parameter.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 idDeviceRequest.parameter.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.
|
code | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idDeviceRequest.parameter.code Device detail DefinitionA code or string that identifies the device detail being asserted. 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. A code that identifies the device detail.
| |
value[x] | 0..1 | There are no (further) constraints on this element Element idDeviceRequest.parameter.value[x] Value of detail DefinitionThe value of the device detail. Range means device should have a value that falls somewhere within the specified range.
| ||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||
valueQuantity | Quantity | There are no (further) constraints on this element Data type | ||
valueRange | Range | There are no (further) constraints on this element Data type | ||
valueBoolean | boolean | There are no (further) constraints on this element Data type | ||
subject | Σ I | 1..1 | Reference(RLPatientCittadino) | Element idDeviceRequest.subject Paziente al quale deve essere fornita la protesi o l'ausilio DefinitionReference alla risorsa RLPatientCittadino contenente i dettagli anagrafici del paziente Il dato è detenuto dal SGDT
|
encounter | Σ I | 0..1 | Reference(Encounter) | There are no (further) constraints on this element Element idDeviceRequest.encounter Encounter motivating request DefinitionAn encounter that provides additional context in which this request is made. 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.
|
occurrence[x] | Σ | 0..1 | Element idDeviceRequest.occurrence[x] Periodo di utilizzo della protesi o dell'ausilio DefinitionThe timing schedule for the use of the device. The Schedule data type allows many different expressions, for example. "Every 8 hours"; "Three times a day"; "1/2 an hour before breakfast for 10 days from 23-Dec 2011:"; "15 Oct 2013, 17 Oct 2013 and 1 Nov 2013".
| |
occurrencePeriod | Period | Data type | ||
id | 0..1 | string | There are no (further) constraints on this element Element idDeviceRequest.occurrence[x].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 idDeviceRequest.occurrence[x].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
|
start | Σ I | 1..1 | dateTime | Element idDeviceRequest.occurrence[x].start Data di inizio del period di utilizzo DefinitionFormato: YYYY-MM-DD secondo lo standard FHIR Il dato a detenuto dal SGDT
|
end | Σ I | 1..1 | dateTime | Element idDeviceRequest.occurrence[x].end Data di fine del periodo di utilizzo DefinitionFormato: YYYY-MM-DD secondo lo standard FHIR Il dato a detenuto dal SGDT If the end of the period is missing, it means that the period is ongoing
|
authoredOn | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element idDeviceRequest.authoredOn When recorded DefinitionWhen the request transitioned to being actionable.
|
requester | Σ I | 0..1 | Reference(Device | Practitioner | PractitionerRole | Organization) | There are no (further) constraints on this element Element idDeviceRequest.requester Who/what is requesting diagnostics DefinitionThe individual who initiated the request and has responsibility for its activation. 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(Device | Practitioner | PractitionerRole | Organization) Constraints
|
performerType | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idDeviceRequest.performerType Filler role DefinitionDesired type of performer for doing the diagnostic testing. 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. Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc.
|
performer | Σ I | 0..1 | Reference(Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService | Patient | Device | RelatedPerson) | There are no (further) constraints on this element Element idDeviceRequest.performer Requested Filler DefinitionThe desired performer for doing the diagnostic testing. 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 | Organization | CareTeam | HealthcareService | Patient | Device | RelatedPerson) Constraints
|
reasonCode | Σ | 0..* | CodeableConcept | There are no (further) constraints on this element Element idDeviceRequest.reasonCode Coded Reason for request DefinitionReason or justification for the use of this device. 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. Diagnosis or problem codes justifying the reason for requesting the device.
|
reasonReference | Σ I | 0..* | Reference(Condition | Observation | DiagnosticReport | DocumentReference) | There are no (further) constraints on this element Element idDeviceRequest.reasonReference Linked Reason for request DefinitionReason or justification for the use of this device. 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(Condition | Observation | DiagnosticReport | DocumentReference) Constraints
|
insurance | I | 0..* | Reference(Coverage | ClaimResponse) | There are no (further) constraints on this element Element idDeviceRequest.insurance Associated insurance coverage DefinitionInsurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be required for delivering the requested service. 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(Coverage | ClaimResponse) Constraints
|
supportingInfo | I | 0..* | Reference(Resource) | There are no (further) constraints on this element Element idDeviceRequest.supportingInfo Additional clinical information DefinitionAdditional clinical information about the patient that may influence the request fulfilment. For example, this may include where on the subject's body the device will be used (i.e. the target site). Knowing where the device is targeted is important for tracking if multiple sites are possible. 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.
|
note | 0..1 | Annotation | Element idDeviceRequest.note Note / commenti aggiuntivi DefinitionStringa alfanumerica al più di 1000 caratteri Il dato è detenuto dal SGDT
| |
relevantHistory | I | 0..* | Reference(Provenance) | There are no (further) constraints on this element Element idDeviceRequest.relevantHistory Request provenance DefinitionKey events in the history of the request. This might not include provenances for all versions of the request - only those deemed "relevant" or important. This SHALL NOT include the Provenance associated with this current version of the resource. (If that provenance is deemed to be a "relevant" change, it will need to be added as part of a later update. Until then, it can be queried directly as the Provenance that points to this version using _revinclude All Provenances should have some historical version of this Request as their subject.
|
Table View
DeviceRequest | .. | |
DeviceRequest.id | 1.. | |
DeviceRequest.meta | 1.. | |
DeviceRequest.meta.versionId | 1.. | |
DeviceRequest.meta.lastUpdated | 1.. | |
DeviceRequest.meta.profile | 1..1 | |
DeviceRequest.extension | Extension | ..1 |
DeviceRequest.basedOn | Reference(RLCarePlanProgettoIndividuale) | 1..1 |
DeviceRequest.status | 1.. | |
DeviceRequest.intent | .. | |
DeviceRequest.code[x] | CodeableConcept | .. |
DeviceRequest.code[x].coding | 1..1 | |
DeviceRequest.code[x].coding.system | 1.. | |
DeviceRequest.code[x].coding.code | 1.. | |
DeviceRequest.code[x].coding.display | 1.. | |
DeviceRequest.subject | Reference(RLPatientCittadino) | .. |
DeviceRequest.occurrence[x] | Period | .. |
DeviceRequest.occurrence[x].start | 1.. | |
DeviceRequest.occurrence[x].end | 1.. | |
DeviceRequest.note | ..1 |
XML View
<StructureDefinition xmlns="http://hl7.org/fhir"> <id value="RLDeviceRequestProtesiAusili" /> <meta> <lastUpdated value="2023-10-17T08:57:24.6840585+00:00" /> </meta> <url value="https://fhir.siss.regione.lombardia.it/StructureDefinition/RLDeviceRequestProtesiAusili" /> <name value="RLDeviceRequestProtesiAusili" /> <status value="active" /> <description value="Profilo volto a descrivere la prostesi o l’ausilio di cui il paziente necessita come definito dal suo progetto individuale." /> <keyword> <system value="https://fhir.siss.regione.lombardia.it/CodeSystem/Tag" /> <code value="PI" /> </keyword> <fhirVersion value="4.0.1" /> <kind value="resource" /> <abstract value="false" /> <type value="DeviceRequest" /> <baseDefinition value="http://hl7.org/fhir/StructureDefinition/DeviceRequest" /> <derivation value="constraint" /> <differential> <element id="DeviceRequest.id"> <path value="DeviceRequest.id" /> <short value="UUID prodotto dal server FHIR (applicativo) che detiene la risorsa. Per maggiori informazioni su chi detiene la risorsa consultare il paragrafo API-Restful nella pagina di Contesto." /> <min value="1" /> </element> <element id="DeviceRequest.meta"> <path value="DeviceRequest.meta" /> <short value="Metadati della risorsa" /> <min value="1" /> </element> <element id="DeviceRequest.meta.versionId"> <path value="DeviceRequest.meta.versionId" /> <short value="Versione della risorsa" /> <min value="1" /> </element> <element id="DeviceRequest.meta.lastUpdated"> <path value="DeviceRequest.meta.lastUpdated" /> <short value="Data e ora di ultimo aggiornamento della risorsa" /> <definition value="Formato standard FHIR: YYY-MM-DDThh:mm:ss.sss+zz:zz" /> <min value="1" /> </element> <element id="DeviceRequest.meta.profile"> <path value="DeviceRequest.meta.profile" /> <short value="Profilo al quale la risorsa si riferisce" /> <min value="1" /> <max value="1" /> <fixedCanonical value="https://fhir.siss.regione.lombardia.it/StructureDefinition/RLDeviceRequestProtesiAusili" /> </element> <element id="DeviceRequest.extension:prescrizioneElettronica"> <path value="DeviceRequest.extension" /> <sliceName value="prescrizioneElettronica" /> <short value="Flag riguardo la necessità di una prescrizione elettronica per il paziente" /> <max value="1" /> <type> <code value="Extension" /> <profile value="https://fhir.siss.regione.lombardia.it/StructureDefinition/RLDeviceRequestPrescrizioneElettronica" /> </type> <isModifier value="false" /> </element> <element id="DeviceRequest.basedOn"> <path value="DeviceRequest.basedOn" /> <short value="Riferimento al progetto individuale nel quale è prevista la fornitura della protesi o dell'ausilio" /> <definition value="Reference al profilo RLCarePlanProgettoIndividuale contenente il progetto individuale del paziente. Deve essere inserito l'UUID generato dal server FHIR (applicativo) detentore della risorsa. Per tutte le informazioni sui server FHIR (applicativi) e le relative risorse detenute consultare la pagina API RESTful della sezione Contesto di questa Implementation Guide" /> <comment value="Il dato è detenuto dal SGDT" /> <min value="1" /> <max value="1" /> <type> <code value="Reference" /> <targetProfile value="https://fhir.siss.regione.lombardia.it/StructureDefinition/RLCarePlanProgettoIndividuale" /> </type> </element> <element id="DeviceRequest.status"> <path value="DeviceRequest.status" /> <short value="Stato della fornitura della protesi o dell'ausilio" /> <definition value="Valore fisso su "active"" /> <min value="1" /> <fixedCode value="active" /> </element> <element id="DeviceRequest.intent"> <path value="DeviceRequest.intent" /> <short value="Intento della richesta" /> <definition value="Valore fisso su "order"" /> <fixedCode value="order" /> </element> <element id="DeviceRequest.code[x]"> <path value="DeviceRequest.code[x]" /> <short value="Codice e descrizione dell'ausilio di protesica" /> <type> <code value="CodeableConcept" /> </type> </element> <element id="DeviceRequest.code[x].coding"> <path value="DeviceRequest.code[x].coding" /> <min value="1" /> <max value="1" /> </element> <element id="DeviceRequest.code[x].coding.system"> <path value="DeviceRequest.code[x].coding.system" /> <min value="1" /> <fixedUri value="https://fhir.siss.regione.lombardia.it/ValueSet/DDC-AusilioProtesi" /> </element> <element id="DeviceRequest.code[x].coding.code"> <path value="DeviceRequest.code[x].coding.code" /> <short value="Codice dell'ausilio di protesica" /> <definition value="Stringa alfanumerica di al più 26 caratteri" /> <comment value="La fonte del dato è il campo CD_AUSILIO della tabella ausili di Protesica i cui dettagli sono consultabili nel documento DC-DDC-SIAA#02 ed accessibili tramite i servizi descritti nel documento DC-DDC-SIAA#01" /> <min value="1" /> <binding> <strength value="required" /> <description value="ValueSet che identifica gli ausili di protesica" /> <valueSet value="https://fhir.siss.regione.lombardia.it/ValueSet/DDC-AusilioProtesi" /> </binding> </element> <element id="DeviceRequest.code[x].coding.display"> <path value="DeviceRequest.code[x].coding.display" /> <short value="Descrizione dell'ausilio di protesica" /> <definition value="Stringra alfanumerica di al più 1024 caratteri." /> <comment value="La fonte del dato è il campo DS_AUSILIO della tabella ausili di Protesica i cui dettagli sono consultabili nel documento DC-DDC-SIAA#02 ed accessibili tramite i servizi descritti nel documento DC-DDC-SIAA#01" /> <min value="1" /> </element> <element id="DeviceRequest.subject"> <path value="DeviceRequest.subject" /> <short value="Paziente al quale deve essere fornita la protesi o l'ausilio" /> <definition value="Reference alla risorsa RLPatientCittadino contenente i dettagli anagrafici del paziente" /> <comment value="Il dato è detenuto dal SGDT" /> <type> <code value="Reference" /> <targetProfile value="https://fhir.siss.regione.lombardia.it/StructureDefinition/RLPatientCittadino" /> </type> </element> <element id="DeviceRequest.occurrence[x]"> <path value="DeviceRequest.occurrence[x]" /> <short value="Periodo di utilizzo della protesi o dell'ausilio" /> <type> <code value="Period" /> </type> </element> <element id="DeviceRequest.occurrence[x].start"> <path value="DeviceRequest.occurrence[x].start" /> <short value="Data di inizio del period di utilizzo" /> <definition value="Formato: YYYY-MM-DD secondo lo standard FHIR" /> <comment value="Il dato a detenuto dal SGDT" /> <min value="1" /> </element> <element id="DeviceRequest.occurrence[x].end"> <path value="DeviceRequest.occurrence[x].end" /> <short value="Data di fine del periodo di utilizzo" /> <definition value="Formato: YYYY-MM-DD secondo lo standard FHIR" /> <comment value="Il dato a detenuto dal SGDT" /> <min value="1" /> </element> <element id="DeviceRequest.note"> <path value="DeviceRequest.note" /> <short value="Note / commenti aggiuntivi" /> <definition value="Stringa alfanumerica al più di 1000 caratteri" /> <comment value="Il dato è detenuto dal SGDT" /> <max value="1" /> </element> </differential> </StructureDefinition>
JSON View
{ "resourceType": "StructureDefinition", "id": "RLDeviceRequestProtesiAusili", "meta": { "lastUpdated": "2023-10-17T08:57:24.6840585+00:00" }, "url": "https://fhir.siss.regione.lombardia.it/StructureDefinition/RLDeviceRequestProtesiAusili", "name": "RLDeviceRequestProtesiAusili", "status": "active", "description": "Profilo volto a descrivere la prostesi o l’ausilio di cui il paziente necessita come definito dal suo progetto individuale.", "keyword": [ { "system": "https://fhir.siss.regione.lombardia.it/CodeSystem/Tag", "code": "PI" } ], "fhirVersion": "4.0.1", "kind": "resource", "abstract": false, "type": "DeviceRequest", "baseDefinition": "http://hl7.org/fhir/StructureDefinition/DeviceRequest", "derivation": "constraint", "differential": { "element": [ { "id": "DeviceRequest.id", "path": "DeviceRequest.id", "short": "UUID prodotto dal server FHIR (applicativo) che detiene la risorsa. Per maggiori informazioni su chi detiene la risorsa consultare il paragrafo API-Restful nella pagina di Contesto.", "min": 1 }, { "id": "DeviceRequest.meta", "path": "DeviceRequest.meta", "short": "Metadati della risorsa", "min": 1 }, { "id": "DeviceRequest.meta.versionId", "path": "DeviceRequest.meta.versionId", "short": "Versione della risorsa", "min": 1 }, { "id": "DeviceRequest.meta.lastUpdated", "path": "DeviceRequest.meta.lastUpdated", "short": "Data e ora di ultimo aggiornamento della risorsa", "definition": "Formato standard FHIR: YYY-MM-DDThh:mm:ss.sss+zz:zz", "min": 1 }, { "id": "DeviceRequest.meta.profile", "path": "DeviceRequest.meta.profile", "short": "Profilo al quale la risorsa si riferisce", "min": 1, "max": "1", "fixedCanonical": "https://fhir.siss.regione.lombardia.it/StructureDefinition/RLDeviceRequestProtesiAusili" }, { "id": "DeviceRequest.extension:prescrizioneElettronica", "path": "DeviceRequest.extension", "sliceName": "prescrizioneElettronica", "short": "Flag riguardo la necessità di una prescrizione elettronica per il paziente", "max": "1", "type": [ { "code": "Extension", "profile": [ "https://fhir.siss.regione.lombardia.it/StructureDefinition/RLDeviceRequestPrescrizioneElettronica" ] } ], "isModifier": false }, { "id": "DeviceRequest.basedOn", "path": "DeviceRequest.basedOn", "short": "Riferimento al progetto individuale nel quale è prevista la fornitura della protesi o dell'ausilio", "definition": "Reference al profilo RLCarePlanProgettoIndividuale contenente il progetto individuale del paziente. Deve essere inserito l'UUID generato dal server FHIR (applicativo) detentore della risorsa. Per tutte le informazioni sui server FHIR (applicativi) e le relative risorse detenute consultare la pagina API RESTful della sezione Contesto di questa Implementation Guide", "comment": "Il dato è detenuto dal SGDT", "min": 1, "max": "1", "type": [ { "code": "Reference", "targetProfile": [ "https://fhir.siss.regione.lombardia.it/StructureDefinition/RLCarePlanProgettoIndividuale" ] } ] }, { "id": "DeviceRequest.status", "path": "DeviceRequest.status", "short": "Stato della fornitura della protesi o dell'ausilio", "definition": "Valore fisso su \"active\"", "min": 1, "fixedCode": "active" }, { "id": "DeviceRequest.intent", "path": "DeviceRequest.intent", "short": "Intento della richesta", "definition": "Valore fisso su \"order\"", "fixedCode": "order" }, { "id": "DeviceRequest.code[x]", "path": "DeviceRequest.code[x]", "short": "Codice e descrizione dell'ausilio di protesica", "type": [ { "code": "CodeableConcept" } ] }, { "id": "DeviceRequest.code[x].coding", "path": "DeviceRequest.code[x].coding", "min": 1, "max": "1" }, { "id": "DeviceRequest.code[x].coding.system", "path": "DeviceRequest.code[x].coding.system", "min": 1, "fixedUri": "https://fhir.siss.regione.lombardia.it/ValueSet/DDC-AusilioProtesi" }, { "id": "DeviceRequest.code[x].coding.code", "path": "DeviceRequest.code[x].coding.code", "short": "Codice dell'ausilio di protesica", "definition": "Stringa alfanumerica di al più 26 caratteri", "comment": "La fonte del dato è il campo CD_AUSILIO della tabella ausili di Protesica i cui dettagli sono consultabili nel documento DC-DDC-SIAA#02 ed accessibili tramite i servizi descritti nel documento DC-DDC-SIAA#01", "min": 1, "binding": { "strength": "required", "description": "ValueSet che identifica gli ausili di protesica", "valueSet": "https://fhir.siss.regione.lombardia.it/ValueSet/DDC-AusilioProtesi" } }, { "id": "DeviceRequest.code[x].coding.display", "path": "DeviceRequest.code[x].coding.display", "short": "Descrizione dell'ausilio di protesica", "definition": "Stringra alfanumerica di al più 1024 caratteri.", "comment": "La fonte del dato è il campo DS_AUSILIO della tabella ausili di Protesica i cui dettagli sono consultabili nel documento DC-DDC-SIAA#02 ed accessibili tramite i servizi descritti nel documento DC-DDC-SIAA#01", "min": 1 }, { "id": "DeviceRequest.subject", "path": "DeviceRequest.subject", "short": "Paziente al quale deve essere fornita la protesi o l'ausilio", "definition": "Reference alla risorsa RLPatientCittadino contenente i dettagli anagrafici del paziente", "comment": "Il dato è detenuto dal SGDT", "type": [ { "code": "Reference", "targetProfile": [ "https://fhir.siss.regione.lombardia.it/StructureDefinition/RLPatientCittadino" ] } ] }, { "id": "DeviceRequest.occurrence[x]", "path": "DeviceRequest.occurrence[x]", "short": "Periodo di utilizzo della protesi o dell'ausilio", "type": [ { "code": "Period" } ] }, { "id": "DeviceRequest.occurrence[x].start", "path": "DeviceRequest.occurrence[x].start", "short": "Data di inizio del period di utilizzo", "definition": "Formato: YYYY-MM-DD secondo lo standard FHIR", "comment": "Il dato a detenuto dal SGDT", "min": 1 }, { "id": "DeviceRequest.occurrence[x].end", "path": "DeviceRequest.occurrence[x].end", "short": "Data di fine del periodo di utilizzo", "definition": "Formato: YYYY-MM-DD secondo lo standard FHIR", "comment": "Il dato a detenuto dal SGDT", "min": 1 }, { "id": "DeviceRequest.note", "path": "DeviceRequest.note", "short": "Note / commenti aggiuntivi", "definition": "Stringa alfanumerica al più di 1000 caratteri", "comment": "Il dato è detenuto dal SGDT", "max": "1" } ] } }
Tipologie di ricerca
Attualmente non sono stati definiti criteri di ricerca.
Search parameter
Attualmente non sono definiti Search Parameters oltre quelli previsti dallo standard per la risorsa DeviceRequest.
ValueSet
Nella seguente tabella sono elencati i value set relativi al profilo RLDeviceRequestProtesiAusili:
Nome | Descrizione | Riferimento al dettaglio della codifica |
---|---|---|
codeCodeableConcept | Codice e descrizione dell'ausilio di protesica | *Codicia in fase di definizione |