Struct DeviceDefinitionBuilder

pub struct DeviceDefinitionBuilder { /* private fields */ }

Builder for DeviceDefinitionInner.

Implementations

impl DeviceDefinitionBuilder

pub fn id(self, value: String) -> DeviceDefinitionBuilder

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.

pub fn meta(self, value: Meta) -> DeviceDefinitionBuilder

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.

pub fn implicit_rules(self, value: String) -> DeviceDefinitionBuilder

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.

pub fn language(self, value: String) -> DeviceDefinitionBuilder

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).

pub fn text(self, value: Narrative) -> DeviceDefinitionBuilder

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.

pub fn contained(self, value: Vec<Resource>) -> DeviceDefinitionBuilder

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.

pub fn extension(self, value: Vec<Extension>) -> DeviceDefinitionBuilder

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.

pub fn modifier_extension( self, value: Vec<Extension>, ) -> DeviceDefinitionBuilder

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.

pub fn description(self, value: String) -> DeviceDefinitionBuilder

Additional information to describe the device

Additional information to describe the device.

pub fn description_ext(self, value: FieldExtension) -> DeviceDefinitionBuilder

Extension field.

pub fn identifier( self, value: Vec<Option<Identifier>>, ) -> DeviceDefinitionBuilder

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.

pub fn identifier_ext( self, value: Vec<Option<FieldExtension>>, ) -> DeviceDefinitionBuilder

Extension field.

pub fn udi_device_identifier( self, value: Vec<Option<DeviceDefinitionUdiDeviceIdentifier>>, ) -> DeviceDefinitionBuilder

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.

pub fn udi_device_identifier_ext( self, value: Vec<Option<FieldExtension>>, ) -> DeviceDefinitionBuilder

Extension field.

pub fn regulatory_identifier( self, value: Vec<Option<DeviceDefinitionRegulatoryIdentifier>>, ) -> DeviceDefinitionBuilder

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.

pub fn regulatory_identifier_ext( self, value: Vec<Option<FieldExtension>>, ) -> DeviceDefinitionBuilder

Extension field.

pub fn part_number(self, value: String) -> DeviceDefinitionBuilder

The part number or catalog number of the device

The part number or catalog number of the device.

Alphanumeric Maximum 20.

pub fn part_number_ext(self, value: FieldExtension) -> DeviceDefinitionBuilder

Extension field.

pub fn manufacturer(self, value: Reference) -> DeviceDefinitionBuilder

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.

pub fn manufacturer_ext(self, value: FieldExtension) -> DeviceDefinitionBuilder

Extension field.

pub fn device_name( self, value: Vec<Option<DeviceDefinitionDeviceName>>, ) -> DeviceDefinitionBuilder

The name or names of the device as given by the manufacturer

The name or names of the device as given by the manufacturer.

pub fn device_name_ext( self, value: Vec<Option<FieldExtension>>, ) -> DeviceDefinitionBuilder

Extension field.

pub fn model_number(self, value: String) -> DeviceDefinitionBuilder

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.

pub fn model_number_ext(self, value: FieldExtension) -> DeviceDefinitionBuilder

Extension field.

pub fn classification( self, value: Vec<Option<DeviceDefinitionClassification>>, ) -> DeviceDefinitionBuilder

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.

pub fn classification_ext( self, value: Vec<Option<FieldExtension>>, ) -> DeviceDefinitionBuilder

Extension field.

pub fn conforms_to( self, value: Vec<Option<DeviceDefinitionConformsTo>>, ) -> DeviceDefinitionBuilder

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.

pub fn conforms_to_ext( self, value: Vec<Option<FieldExtension>>, ) -> DeviceDefinitionBuilder

Extension field.

pub fn has_part( self, value: Vec<Option<DeviceDefinitionHasPart>>, ) -> DeviceDefinitionBuilder

A device, part of the current one

A device that is part (for example a component) of the present device.

pub fn has_part_ext( self, value: Vec<Option<FieldExtension>>, ) -> DeviceDefinitionBuilder

Extension field.

pub fn packaging( self, value: Vec<Option<DeviceDefinitionPackaging>>, ) -> DeviceDefinitionBuilder

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.

pub fn packaging_ext( self, value: Vec<Option<FieldExtension>>, ) -> DeviceDefinitionBuilder

Extension field.

pub fn version( self, value: Vec<Option<DeviceDefinitionVersion>>, ) -> DeviceDefinitionBuilder

The version of the device or software

The version of the device or software.

pub fn version_ext( self, value: Vec<Option<FieldExtension>>, ) -> DeviceDefinitionBuilder

Extension field.

pub fn safety( self, value: Vec<Option<CodeableConcept>>, ) -> DeviceDefinitionBuilder

Safety; Safety characteristics of the device

Safety characteristics of the device.

pub fn safety_ext( self, value: Vec<Option<FieldExtension>>, ) -> DeviceDefinitionBuilder

Extension field.

pub fn shelf_life_storage( self, value: Vec<Option<ProductShelfLife>>, ) -> DeviceDefinitionBuilder

Shelf Life and storage information

Shelf Life and storage information.

pub fn shelf_life_storage_ext( self, value: Vec<Option<FieldExtension>>, ) -> DeviceDefinitionBuilder

Extension field.

pub fn language_code( self, value: Vec<Option<CodeableConcept>>, ) -> DeviceDefinitionBuilder

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).

pub fn language_code_ext( self, value: Vec<Option<FieldExtension>>, ) -> DeviceDefinitionBuilder

Extension field.

pub fn property( self, value: Vec<Option<DeviceDefinitionProperty>>, ) -> DeviceDefinitionBuilder

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.

pub fn property_ext( self, value: Vec<Option<FieldExtension>>, ) -> DeviceDefinitionBuilder

Extension field.

pub fn owner(self, value: Reference) -> DeviceDefinitionBuilder

Organization responsible for device

An organization that is responsible for the provision and ongoing maintenance of the device.

pub fn owner_ext(self, value: FieldExtension) -> DeviceDefinitionBuilder

Extension field.

pub fn contact( self, value: Vec<Option<ContactPoint>>, ) -> DeviceDefinitionBuilder

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.

pub fn contact_ext( self, value: Vec<Option<FieldExtension>>, ) -> DeviceDefinitionBuilder

Extension field.

pub fn link( self, value: Vec<Option<DeviceDefinitionLink>>, ) -> DeviceDefinitionBuilder

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.

pub fn link_ext( self, value: Vec<Option<FieldExtension>>, ) -> DeviceDefinitionBuilder

Extension field.

pub fn note(self, value: Vec<Option<Annotation>>) -> DeviceDefinitionBuilder

Device notes and comments

Descriptive information, usage information or implantation information that is not captured in an existing element.

pub fn note_ext( self, value: Vec<Option<FieldExtension>>, ) -> DeviceDefinitionBuilder

Extension field.

pub fn material( self, value: Vec<Option<DeviceDefinitionMaterial>>, ) -> DeviceDefinitionBuilder

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.

pub fn material_ext( self, value: Vec<Option<FieldExtension>>, ) -> DeviceDefinitionBuilder

Extension field.

pub fn production_identifier_in_udi( self, value: Vec<Option<DeviceProductionIdentifierInUDI>>, ) -> DeviceDefinitionBuilder

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.

pub fn production_identifier_in_udi_ext( self, value: Vec<Option<FieldExtension>>, ) -> DeviceDefinitionBuilder

Extension field.

pub fn guideline( self, value: DeviceDefinitionGuideline, ) -> DeviceDefinitionBuilder

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.

pub fn guideline_ext(self, value: FieldExtension) -> DeviceDefinitionBuilder

Extension field.

pub fn corrective_action( self, value: DeviceDefinitionCorrectiveAction, ) -> DeviceDefinitionBuilder

Tracking of latest field safety corrective action

Tracking of latest field safety corrective action.

pub fn corrective_action_ext( self, value: FieldExtension, ) -> DeviceDefinitionBuilder

Extension field.

pub fn charge_item( self, value: Vec<Option<DeviceDefinitionChargeItem>>, ) -> DeviceDefinitionBuilder

Billing code or reference associated with the device

Billing code or reference associated with the device.

pub fn charge_item_ext( self, value: Vec<Option<FieldExtension>>, ) -> DeviceDefinitionBuilder

Extension field.

pub fn build_inner(self) -> Result<DeviceDefinitionInner, BuilderError>

Builds a new DeviceDefinitionInner.

Errors

If a required field has not been initialized.

impl DeviceDefinitionBuilder

pub fn build(self) -> Result<DeviceDefinition, BuilderError>

Finalize building DeviceDefinition.

Trait Implementations

impl Default for DeviceDefinitionBuilder

fn default() -> DeviceDefinitionBuilder

Returns the “default value” for a type.