pub struct DeviceDefinitionInner {Show 60 fields
pub id: Option<String>,
pub meta: Option<Meta>,
pub implicit_rules: Option<String>,
pub language: Option<String>,
pub text: Option<Narrative>,
pub contained: Vec<Resource>,
pub extension: Vec<Extension>,
pub modifier_extension: Vec<Extension>,
pub description: Option<String>,
pub description_ext: Option<FieldExtension>,
pub identifier: Vec<Option<Identifier>>,
pub identifier_ext: Vec<Option<FieldExtension>>,
pub udi_device_identifier: Vec<Option<DeviceDefinitionUdiDeviceIdentifier>>,
pub udi_device_identifier_ext: Vec<Option<FieldExtension>>,
pub regulatory_identifier: Vec<Option<DeviceDefinitionRegulatoryIdentifier>>,
pub regulatory_identifier_ext: Vec<Option<FieldExtension>>,
pub part_number: Option<String>,
pub part_number_ext: Option<FieldExtension>,
pub manufacturer: Option<Reference>,
pub manufacturer_ext: Option<FieldExtension>,
pub device_name: Vec<Option<DeviceDefinitionDeviceName>>,
pub device_name_ext: Vec<Option<FieldExtension>>,
pub model_number: Option<String>,
pub model_number_ext: Option<FieldExtension>,
pub classification: Vec<Option<DeviceDefinitionClassification>>,
pub classification_ext: Vec<Option<FieldExtension>>,
pub conforms_to: Vec<Option<DeviceDefinitionConformsTo>>,
pub conforms_to_ext: Vec<Option<FieldExtension>>,
pub has_part: Vec<Option<DeviceDefinitionHasPart>>,
pub has_part_ext: Vec<Option<FieldExtension>>,
pub packaging: Vec<Option<DeviceDefinitionPackaging>>,
pub packaging_ext: Vec<Option<FieldExtension>>,
pub version: Vec<Option<DeviceDefinitionVersion>>,
pub version_ext: Vec<Option<FieldExtension>>,
pub safety: Vec<Option<CodeableConcept>>,
pub safety_ext: Vec<Option<FieldExtension>>,
pub shelf_life_storage: Vec<Option<ProductShelfLife>>,
pub shelf_life_storage_ext: Vec<Option<FieldExtension>>,
pub language_code: Vec<Option<CodeableConcept>>,
pub language_code_ext: Vec<Option<FieldExtension>>,
pub property: Vec<Option<DeviceDefinitionProperty>>,
pub property_ext: Vec<Option<FieldExtension>>,
pub owner: Option<Reference>,
pub owner_ext: Option<FieldExtension>,
pub contact: Vec<Option<ContactPoint>>,
pub contact_ext: Vec<Option<FieldExtension>>,
pub link: Vec<Option<DeviceDefinitionLink>>,
pub link_ext: Vec<Option<FieldExtension>>,
pub note: Vec<Option<Annotation>>,
pub note_ext: Vec<Option<FieldExtension>>,
pub material: Vec<Option<DeviceDefinitionMaterial>>,
pub material_ext: Vec<Option<FieldExtension>>,
pub production_identifier_in_udi: Vec<Option<DeviceProductionIdentifierInUDI>>,
pub production_identifier_in_udi_ext: Vec<Option<FieldExtension>>,
pub guideline: Option<DeviceDefinitionGuideline>,
pub guideline_ext: Option<FieldExtension>,
pub corrective_action: Option<DeviceDefinitionCorrectiveAction>,
pub corrective_action_ext: Option<FieldExtension>,
pub charge_item: Vec<Option<DeviceDefinitionChargeItem>>,
pub charge_item_ext: Vec<Option<FieldExtension>>,
/* private fields */
}Expand description
This is a specialized resource that defines the characteristics and capabilities of a device.
DeviceDefinition v5.0.0
An instance of a medical-related component of a medical device
The characteristics, operational status and capabilities of a medical-related component of a medical device.
For the initial scope, this DeviceDefinition resource is only applicable to describe a single node in the containment tree that is produced by the context scanner in any medical device that implements or derives from the ISO/IEEE 11073 standard and that does not represent a metric. Examples for such a node are MDS, VMD, or Channel.
Fields§
§id: Option<String>Logical id of this artifact
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.
meta: Option<Meta>Metadata about the resource
The 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.
implicit_rules: Option<String>A set of rules under which this content was created
A 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 its narrative along with other profiles, value sets, etc.
language: Option<String>Language; Language of the resource content
The 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).
text: Option<Narrative>Text summary of the resource, for human interpretation
A 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 a 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: Vec<Resource>Contained, inline Resources
These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.
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: Vec<Extension>Additional content defined by implementations
May 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 managable, 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.
modifier_extension: Vec<Extension>Extensions that cannot be ignored
May 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 managable, 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).
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
description: Option<String>Additional information to describe the device
Additional information to describe the device.
description_ext: Option<FieldExtension>Extension field.
identifier: Vec<Option<Identifier>>Instance identifier
Unique instance identifiers assigned to a device by the software, manufacturers, other organizations or owners. For example: handle ID. The identifier is typically valued if the udiDeviceIdentifier, partNumber or modelNumber is not valued and represents a different type of identifier. However, it is permissible to still include those identifiers in DeviceDefinition.identifier with the appropriate identifier.type.
identifier_ext: Vec<Option<FieldExtension>>Extension field.
udi_device_identifier: Vec<Option<DeviceDefinitionUdiDeviceIdentifier>>Unique Device Identifier (UDI) Barcode string
Unique device identifier (UDI) assigned to device label or package. Note that the Device may include multiple udiCarriers as it either may include just the udiCarrier for the jurisdiction it is sold, or for multiple jurisdictions it could have been sold.
udi_device_identifier_ext: Vec<Option<FieldExtension>>Extension field.
regulatory_identifier: Vec<Option<DeviceDefinitionRegulatoryIdentifier>>Regulatory identifier(s) associated with this device
Identifier associated with the regulatory documentation (certificates, technical documentation, post-market surveillance documentation and reports) of a set of device models sharing the same intended purpose, risk class and essential design and manufacturing characteristics. One example is the Basic UDI-DI in Europe.
This should not be used for regulatory authorization numbers which are to be captured elsewhere.
regulatory_identifier_ext: Vec<Option<FieldExtension>>Extension field.
part_number: Option<String>The part number or catalog number of the device
The part number or catalog number of the device.
Alphanumeric Maximum 20.
part_number_ext: Option<FieldExtension>Extension field.
manufacturer: Option<Reference>Name of device manufacturer
A name of the manufacturer or legal representative e.g. labeler. Whether this is the actual manufacturer or the labeler or responsible depends on implementation and jurisdiction.
manufacturer_ext: Option<FieldExtension>Extension field.
device_name: Vec<Option<DeviceDefinitionDeviceName>>The name or names of the device as given by the manufacturer
The name or names of the device as given by the manufacturer.
device_name_ext: Vec<Option<FieldExtension>>Extension field.
model_number: Option<String>The catalog or model number for the device for example as defined by the manufacturer
The model number for the device for example as defined by the manufacturer or labeler, or other agency.
model_number_ext: Option<FieldExtension>Extension field.
classification: Vec<Option<DeviceDefinitionClassification>>What kind of device or device system this is
What kind of device or device system this is.
In this element various classifications can be used, such as GMDN, EMDN, SNOMED CT, risk classes, national product codes.
classification_ext: Vec<Option<FieldExtension>>Extension field.
conforms_to: Vec<Option<DeviceDefinitionConformsTo>>Identifies the standards, specifications, or formal guidances for the capabilities supported by the device
Identifies the standards, specifications, or formal guidances for the capabilities supported by the device. The device may be certified as conformant to these specifications e.g., communication, performance, process, measurement, or specialization standards.
conforms_to_ext: Vec<Option<FieldExtension>>Extension field.
has_part: Vec<Option<DeviceDefinitionHasPart>>A device, part of the current one
A device that is part (for example a component) of the present device.
has_part_ext: Vec<Option<FieldExtension>>Extension field.
packaging: Vec<Option<DeviceDefinitionPackaging>>Information about the packaging of the device, i.e. how the device is packaged
Information about the packaging of the device, i.e. how the device is packaged.
packaging_ext: Vec<Option<FieldExtension>>Extension field.
version: Vec<Option<DeviceDefinitionVersion>>The version of the device or software
The version of the device or software.
version_ext: Vec<Option<FieldExtension>>Extension field.
safety: Vec<Option<CodeableConcept>>Safety; Safety characteristics of the device
Safety characteristics of the device.
safety_ext: Vec<Option<FieldExtension>>Extension field.
shelf_life_storage: Vec<Option<ProductShelfLife>>Shelf Life and storage information
Shelf Life and storage information.
shelf_life_storage_ext: Vec<Option<FieldExtension>>Extension field.
language_code: Vec<Option<CodeableConcept>>Language code for the human-readable text strings produced by the device (all supported)
Language code for the human-readable text strings produced by the device (all supported).
language_code_ext: Vec<Option<FieldExtension>>Extension field.
property: Vec<Option<DeviceDefinitionProperty>>Inherent, essentially fixed, characteristics of this kind of device, e.g., time properties, size, etc
Static or essentially fixed characteristics or features of this kind of device that are otherwise not captured in more specific attributes, e.g., time or timing attributes, resolution, accuracy, and physical attributes.
Dynamic or current properties, such as settings, of an individual device are described using a Device instance-specific DeviceMetric and recorded using Observation. Static characteristics of an individual device could also be documented in a Device instance. The Device instance’s properties, and their values, could be, but need not be, the same as in the associated DeviceDefinition.
property_ext: Vec<Option<FieldExtension>>Extension field.
owner: Option<Reference>Organization responsible for device
An organization that is responsible for the provision and ongoing maintenance of the device.
owner_ext: Option<FieldExtension>Extension field.
contact: Vec<Option<ContactPoint>>Details for human/organization for support
Contact details for an organization or a particular human that is responsible for the device.
used for troubleshooting etc.
contact_ext: Vec<Option<FieldExtension>>Extension field.
link: Vec<Option<DeviceDefinitionLink>>An associated device, attached to, used with, communicating with or linking a previous or new device model to the focal device
An associated device, attached to, used with, communicating with or linking a previous or new device model to the focal device.
link_ext: Vec<Option<FieldExtension>>Extension field.
note: Vec<Option<Annotation>>Device notes and comments
Descriptive information, usage information or implantation information that is not captured in an existing element.
note_ext: Vec<Option<FieldExtension>>Extension field.
material: Vec<Option<DeviceDefinitionMaterial>>A substance used to create the material(s) of which the device is made
A substance used to create the material(s) of which the device is made.
material_ext: Vec<Option<FieldExtension>>Extension field.
production_identifier_in_udi: Vec<Option<DeviceProductionIdentifierInUDI>>DeviceProductionIdentifierInUDI; lot-number | manufactured-date | serial-number | expiration-date | biological-source | software-version
Indicates the production identifier(s) that are expected to appear in the UDI carrier on the device label.
production_identifier_in_udi_ext: Vec<Option<FieldExtension>>Extension field.
guideline: Option<DeviceDefinitionGuideline>Information aimed at providing directions for the usage of this model of device
Information aimed at providing directions for the usage of this model of device.
For more structured data, a ClinicalUseDefinition that points to the DeviceDefinition can be used.
guideline_ext: Option<FieldExtension>Extension field.
corrective_action: Option<DeviceDefinitionCorrectiveAction>Tracking of latest field safety corrective action
Tracking of latest field safety corrective action.
corrective_action_ext: Option<FieldExtension>Extension field.
charge_item: Vec<Option<DeviceDefinitionChargeItem>>Billing code or reference associated with the device
Billing code or reference associated with the device.
charge_item_ext: Vec<Option<FieldExtension>>Extension field.
Trait Implementations§
Source§impl Clone for DeviceDefinitionInner
impl Clone for DeviceDefinitionInner
Source§fn clone(&self) -> DeviceDefinitionInner
fn clone(&self) -> DeviceDefinitionInner
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more