FQL is a query language that allows you to retrieve, filter and project data from any data source containing FHIR Resources. It brings the power of three existing languages together: SQL, JSON and FhirPath. It allows you to create tables and is useful for gaining insight and perform quality control.
Query
-
Default
What is FQL?
-
FQL Query resources
FQL Playground
Try Firely Query Language in our playground by using this scope as data source.
- FQL Documentation
-
FQL Language
Syntax specification
To learn more about FQL syntax choose this menu item.
-
YamlGen Generate resources
YamlGen Playground
Try YamlGen in our playground by using this scope as data source.
-
YamlGen Language
YamlGen Syntax specification
To learn more about YamlGen syntax choose this.
-
FHIRPath Inspect resource
FHIRPath Playground
Try out the FHIRPath playground and navigate inside this resource.
-
FHIRPath Documentation
FHIRPath Documentation
Find out what FHIRPath is or learn how to write FHIRPath scripts.
API
-
Project FHIR API
This is the location where you can find your resource using a FHIR client.
-
Simplifier FHIR API
The global endpoint is where users can search for all resources in Simplifier. Resources have a globally unique guid Id here.
Tools
-
Custom Example generation
Custom Example generation beta
Experiment with resource instance generation using YamlGen and based on this profile.
This feature is in beta. You can help us improve it by giving feedback with the feedback button at the top of the screen.
Project FirstProfile
Device
This profile specifies additional constraints on the US Core Device Profile to support coverage requirements discovery.
- type Profile on Device
- FHIR R4
- status Draft
-
version1.1.0-ballot
Unregistered conflicting canonical
The canonical from this resource does not match any claim in this context and conflicts with a claim from another scope.
http://hl7.org/fhir
Canonical claims are used to verify ownership of your canonical URLs.
Canonical
| Device | I | Device | There are no (further) constraints on this element Element idDevice Item used in healthcare DefinitionA type of a manufactured item that is used in the provision of healthcare without being substantially changed through that activity. The device may be a medical or non-medical device.
| |
| id | Σ | 0..1 | id | There are no (further) constraints on this element Element idDevice.id Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. 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 | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idDevice.meta Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
|
| implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idDevice.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 its narrative along with other profiles, value sets, etc.
|
| language | 0..1 | codeBinding | There are no (further) constraints on this element Element idDevice.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). IETF language tag for a human language
| |
| text | I | 0..1 | Narrative | There are no (further) constraints on this element Element idDevice.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 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 | I | 0..* | Resource | There are no (further) constraints on this element Element idDevice.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, 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 | I | 0..* | Extension | There are no (further) constraints on this element Element idDevice.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 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.
|
| modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idDevice.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 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
| identifier | 0..* | Identifier | There are no (further) constraints on this element Element idDevice.identifier Instance identifier DefinitionUnique instance identifiers assigned to a device by manufacturers other organizations or owners. Certain attributes, like serial number and UDI Carrier (the HRF or AIDC barcode string) are not device instance identifiers as they are not consistently able to uniquely identify the instance of a device, thus are not appropriate to be used to value Device.identifier. The barcode string from a barcode present on a device label or package may identify the instance, include names given to the device in local usage, or may identify the type of device. If the identifier identifies the type of device, Device.type element should be used. The identifier is typically valued if the serialNumber or lotNumber 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.
| |
| displayName | 0..1 | string | There are no (further) constraints on this element Element idDevice.displayName The name used to display by default when the device is referenced DefinitionThe name used to display by default when the device is referenced. Based on intent of use by the resource creator, this may reflect one of the names in Device.name, or may be another simple name.
| |
| definition | 0..1 | CodeableReference | There are no (further) constraints on this element Element idDevice.definition The reference to the definition for the device DefinitionThe reference to the definition for the device.
| |
| udiCarrier | S Σ | 0..1 | BackboneElement | There are no (further) constraints on this element Element idDevice.udiCarrier Unique Device Identifier (UDI) Barcode string DefinitionUnique 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 may identify an unique instance of a device, or it may only identify the type of the device. See UDI mappings for a complete mapping of UDI parts to Device.
|
| id | 0..1 | string | There are no (further) constraints on this element Element idDevice.udiCarrier.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 idDevice.udiCarrier.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 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.
|
| modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idDevice.udiCarrier.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 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. 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.
|
| deviceIdentifier | S Σ | 1..1 | string | There are no (further) constraints on this element Element idDevice.udiCarrier.deviceIdentifier Mandatory fixed portion of UDI Alternate namesDI DefinitionThe device identifier (DI) is a mandatory, fixed portion of a UDI that identifies the labeler and the specific version or model of a device.
|
| issuer | Σ | 1..1 | uri | There are no (further) constraints on this element Element idDevice.udiCarrier.issuer UDI Issuing Organization Alternate namesBarcode System DefinitionOrganization that is charged with issuing UDIs for devices. For example, the US FDA issuers include:
|
| jurisdiction | 0..1 | uri | There are no (further) constraints on this element Element idDevice.udiCarrier.jurisdiction Regional UDI authority DefinitionThe identity of the authoritative source for UDI generation within a jurisdiction. All UDIs are globally unique within a single namespace with the appropriate repository uri as the system. For example, UDIs of devices managed in the U.S. by the FDA, the value is http://hl7.org/fhir/NamingSystem/us-fda-udi or in the European Union by the European Commission http://hl7.org/fhir/NamingSystem/eu-ec-udi. Allows a recipient of a UDI to know which database will contain the UDI-associated metadata.
| |
| carrierAIDC | Σ | 0..1 | base64Binary | There are no (further) constraints on this element Element idDevice.udiCarrier.carrierAIDC UDI Machine Readable Barcode String Alternate namesAutomatic Identification and Data Capture DefinitionThe full UDI carrier of the Automatic Identification and Data Capture (AIDC) technology representation of the barcode string as printed on the packaging of the device - e.g., a barcode or RFID. Because of limitations on character sets in XML and the need to round-trip JSON data through XML, AIDC Formats SHALL be base64 encoded. The AIDC form of UDIs should be scanned or otherwise used for the identification of the device whenever possible to minimize errors in records resulting from manual transcriptions. If separate barcodes for DI and PI are present, concatenate the string with DI first and in order of human readable expression on label.
|
| carrierHRF | Σ | 0..1 | string | There are no (further) constraints on this element Element idDevice.udiCarrier.carrierHRF UDI Human Readable Barcode String Alternate namesHuman Readable Form DefinitionThe full UDI carrier as the human readable form (HRF) representation of the barcode string as printed on the packaging of the device. If separate barcodes for DI and PI are present, concatenate the string with DI first and in order of human readable expression on label.
|
| entryType | 0..1 | codeBinding | There are no (further) constraints on this element Element idDevice.udiCarrier.entryType barcode | rfid | manual | card | self-reported | electronic-transmission | unknown DefinitionA coded entry to indicate how the data was entered. Supports a way to distinguish hand entered from machine read data. Codes to identify how UDI data was entered.
| |
| status | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idDevice.status active | inactive | entered-in-error DefinitionThe Device record status. This is not the status of the device like availability. The record status of the device.
|
| availabilityStatus | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idDevice.availabilityStatus lost | damaged | destroyed | available DefinitionThe availability of the device. The availability status reason of the device.
| |
| biologicalSourceEvent | 0..1 | Identifier | There are no (further) constraints on this element Element idDevice.biologicalSourceEvent An identifier that supports traceability to the event during which material in this product from one or more biological entities was obtained or pooled Alternate namesDistinct Identification Code (DIC) DefinitionAn identifier that supports traceability to the event during which material in this product from one or more biological entities was obtained or pooled. Necessary to support mandatory requirements for traceability from donor/source to recipient and vice versa, while also satisfying donor anonymity requirements. The element is defined consistently across BiologicallyDerivedProduct, NutritionProduct, and Device. The identifier references an event that links to a single biological entity such as a blood donor, or to multiple biological entities (e.g. when the product is an embryo or a pooled platelet product). A single biologicalSourceEvent identifier may appear on multiple products of many types derived from a single donation event or source extraction. As an example, a single donation event may provide 2 kidneys and a liver for organ transplantation, 2 corneas for eye surgery, heart valves and arterial tissue for cardiovascular surgery, multiple skin grafts, tendons, multiple shaped bone grafts and a large number of bone putty/paste products; and each of them may be assigned to the same biological source event identifier.
| |
| manufacturer | 0..1 | string | There are no (further) constraints on this element Element idDevice.manufacturer Name of device manufacturer DefinitionA name of the manufacturer or entity legally responsible for the device.
| |
| manufactureDate | 0..1 | dateTime | There are no (further) constraints on this element Element idDevice.manufactureDate Date when the device was made DefinitionThe date and time when the device was manufactured.
| |
| expirationDate | 0..1 | dateTime | There are no (further) constraints on this element Element idDevice.expirationDate Date and time of expiry of this device (if applicable) DefinitionThe date and time beyond which this device is no longer valid or should not be used (if applicable).
| |
| lotNumber | 0..1 | string | There are no (further) constraints on this element Element idDevice.lotNumber Lot number of manufacture DefinitionLot number assigned by the manufacturer.
| |
| serialNumber | 0..1 | string | There are no (further) constraints on this element Element idDevice.serialNumber Serial number assigned by the manufacturer DefinitionThe serial number assigned by the organization when the device was manufactured. Alphanumeric Maximum 20. While a serial number is a type of identifier, in the context of devices for which a UDI is required, thus a serial number may be part of the production identifier, it is more informative to have the serial number as a dedicated attribute together with the other UDI production identifier. When the device is not subject to including the UDI (e.g., its presence and exchange is not mandated by local regulatory requirements or specific use case at hand), thus the concept of production identifiers is not relevant as a set, it remains helpful for consistency to still use Device.serialNumber rather than using Device.identifier with an appropriate type. Systems that do not realize an identifier is a serial number may place it in Device.identifier or if the identifier.system is known for the serial number, it may also be populated in the Device.identifier as a globally unique id_.
| |
| name | I | 0..* | BackboneElement | There are no (further) constraints on this element Element idDevice.name The name or names of the device as known to the manufacturer and/or patient DefinitionThis represents the manufacturer's name of the device as provided by the device, from a UDI label, or by a person describing the Device. This typically would be used when a person provides the name(s) or when the device represents one of the names available from DeviceDefinition.
|
| id | 0..1 | string | There are no (further) constraints on this element Element idDevice.name.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 idDevice.name.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 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.
|
| modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idDevice.name.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 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. 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.
|
| value | Σ | 1..1 | string | There are no (further) constraints on this element Element idDevice.name.value The term that names the device Alternate namesΣ DefinitionThe actual name that identifies the device.
|
| type | Σ | 1..1 | codeBinding | There are no (further) constraints on this element Element idDevice.name.type registered-name | user-friendly-name | patient-reported-name DefinitionIndicates the kind of name. RegisteredName | UserFriendlyName | PatientReportedName. The type of name the device is referred by.
|
| display | Σ ?! I | 0..1 | boolean | There are no (further) constraints on this element Element idDevice.name.display The preferred device name DefinitionIndicates the default or preferred name to be displayed.
|
| modelNumber | 0..1 | string | There are no (further) constraints on this element Element idDevice.modelNumber The manufacturer's model number for the device DefinitionThe manufacturer's model number for the device.
| |
| partNumber | 0..1 | string | There are no (further) constraints on this element Element idDevice.partNumber The part number or catalog number of the device DefinitionThe part number or catalog number of the device. Alphanumeric Maximum 20.
| |
| category | 0..* | CodeableConcept | There are no (further) constraints on this element Element idDevice.category Indicates a high-level grouping of the device DefinitionDevices may be associated with one or more categories. Categories of medical devices.
| |
| type | 0..* | CodeableConcept | There are no (further) constraints on this element Element idDevice.type The kind or type of device DefinitionThe kind or type of device. A device instance may have more than one type - in which case those are the types that apply to the specific instance of the device. Multiple device types are use when a device is categorized in more than one context – for example, hybrid devices in which the device is both of type gateway and sensor. Codes to identify medical devices.
| |
| version | 0..* | BackboneElement | There are no (further) constraints on this element Element idDevice.version The actual design of the device or software version running on the device DefinitionThe actual design of the device or software version running on the device.
| |
| id | 0..1 | string | There are no (further) constraints on this element Element idDevice.version.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 idDevice.version.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 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.
|
| modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idDevice.version.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 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. 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.
|
| type | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idDevice.version.type The type of the device version, e.g. manufacturer, approved, internal Alternate namesΣ DefinitionThe type of the device version, e.g. manufacturer, approved, internal. The type of version indicated for the device.
| |
| component | 0..1 | Identifier | There are no (further) constraints on this element Element idDevice.version.component The hardware or software module of the device to which the version applies DefinitionThe hardware or software module of the device to which the version applies. Note that the module of the device would not need to be tracked as a separate device, e.g., using different UDI, thus would typically involve one or more software modules. For example, a device may involve two software modules each on a different version.
| |
| installDate | 0..1 | dateTime | There are no (further) constraints on this element Element idDevice.version.installDate The date the version was installed on the device DefinitionThe date the version was installed on the device.
| |
| value | 1..1 | string | There are no (further) constraints on this element Element idDevice.version.value The version text DefinitionThe version text.
| |
| conformsTo | 0..* | BackboneElement | There are no (further) constraints on this element Element idDevice.conformsTo Identifies the standards, specifications, or formal guidances for the capabilities supported by the device DefinitionIdentifies 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.
| |
| id | 0..1 | string | There are no (further) constraints on this element Element idDevice.conformsTo.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 idDevice.conformsTo.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 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.
|
| modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idDevice.conformsTo.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 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. 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.
|
| category | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idDevice.conformsTo.category Describes the common type of the standard, specification, or formal guidance. communication | performance | measurement DefinitionDescribes the type of the standard, specification, or formal guidance. The kind of standards used by the device.
| |
| specification | 1..1 | CodeableConcept | There are no (further) constraints on this element Element idDevice.conformsTo.specification Identifies the standard, specification, or formal guidance that the device adheres to DefinitionCode that identifies the specific standard, specification, protocol, formal guidance, regulation, legislation, or certification scheme to which the device adheres. The type of version indicated for the device.
| |
| version | 0..1 | string | There are no (further) constraints on this element Element idDevice.conformsTo.version Specific form or variant of the standard DefinitionIdentifies the specific form or variant of the standard, specification, or formal guidance. This may be a 'version number', release, document edition, publication year, or other label.
| |
| property | S | 0..* | BackboneElement | There are no (further) constraints on this element Element idDevice.property Inherent, essentially fixed, characteristics of the device. e.g., time properties, size, material, etc. DefinitionStatic or essentially fixed characteristics or features of the device (e.g., time or timing attributes, resolution, accuracy, intended use or instructions for use, and physical attributes) that are not otherwise captured in more specific 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 a device could also be documented in an associated [DeviceDefinition] instance. The Device instance's properties, and their values, could be, but need not be, the same as those described in an associated DeviceDefinition.
|
| id | 0..1 | string | There are no (further) constraints on this element Element idDevice.property.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 idDevice.property.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 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.
|
| modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idDevice.property.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 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. 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.
|
| type | S | 1..1 | CodeableConcept | There are no (further) constraints on this element Element idDevice.property.type Code that specifies the property being represented DefinitionCode that specifies the property, such as resolution, color, size, being represented. Device property type.
|
| value[x] | 1..1 | There are no (further) constraints on this element Element idDevice.property.value[x] Value of the property DefinitionThe value of the property specified by the associated property.type code. The text element in CodeableConcept.text is used for properties which would usually be coded (such as the size of an implant, or a security classification) but for which there is not currently an appropriate concept in the vocabulary (e.g. a custom implant size, or a security classification which depends on configuration). Otherwise the string choice type is used for descriptive properties, or instructions. Unordered, Open, by $this(Type) Constraints
| ||
| (All Slices) | There are no (further) constraints on this element | |||
| valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||
| valueString | string | There are no (further) constraints on this element Data type | ||
| valueBoolean | boolean | There are no (further) constraints on this element Data type | ||
| valueInteger | integer | There are no (further) constraints on this element Data type | ||
| valueRange | Range | There are no (further) constraints on this element Data type | ||
| valueAttachment | Attachment | There are no (further) constraints on this element Data type | ||
| valueCode | S | 0..1 | Quantity | There are no (further) constraints on this element Element idDevice.property.value[x]:valueCode Value of the property DefinitionThe value of the property specified by the associated property.type code. The text element in CodeableConcept.text is used for properties which would usually be coded (such as the size of an implant, or a security classification) but for which there is not currently an appropriate concept in the vocabulary (e.g. a custom implant size, or a security classification which depends on configuration). Otherwise the string choice type is used for descriptive properties, or instructions.
|
| mode | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idDevice.mode The designated condition for performing a task DefinitionThe designated condition for performing a task with the device. Operational mode of a device.
| |
| cycle | 0..1 | Count | There are no (further) constraints on this element Element idDevice.cycle The series of occurrences that repeats during the operation of the device DefinitionThe series of occurrences that repeats during the operation of the device.
| |
| duration | 0..1 | Duration | There are no (further) constraints on this element Element idDevice.duration A measurement of time during the device's operation (e.g., days, hours, mins, etc.) DefinitionA measurement of time during the device's operation (e.g., days, hours, mins, etc.).
| |
| owner | 0..1 | Reference(Organization) | There are no (further) constraints on this element Element idDevice.owner Organization responsible for device DefinitionAn organization that is responsible for the provision and ongoing maintenance of the device.
| |
| contact | 0..* | ContactPoint | There are no (further) constraints on this element Element idDevice.contact Details for human/organization for support DefinitionContact details for an organization or a particular human that is responsible for the device. used for troubleshooting etc.
| |
| location | 0..1 | Reference(Location) | There are no (further) constraints on this element Element idDevice.location Where the device is found DefinitionThe place where the device can be found. Device.location can be used to track device location.
| |
| url | 0..1 | uri | There are no (further) constraints on this element Element idDevice.url Network address to contact device DefinitionA network address on which the device may be contacted directly. If the device is running a FHIR server, the network address should be the Base URL from which a conformance statement may be retrieved.
| |
| endpoint | 0..* | Reference(Endpoint) | There are no (further) constraints on this element Element idDevice.endpoint Technical endpoints providing access to electronic services provided by the device DefinitionTechnical endpoints providing access to services provided by the device defined at this resource.
| |
| gateway | 0..* | CodeableReference | There are no (further) constraints on this element Element idDevice.gateway Linked device acting as a communication/data collector, translator or controller DefinitionThe linked device acting as a communication controller, data collector, translator, or concentrator for the current device (e.g., mobile phone application that relays a blood pressure device's data). The Device.gateway may be used when the Device being referenced has a gateway and/or to capture one or more gateways associated with the device. If the Gateway is included in the Observation resource, the Observation.gatewayDevice should be used instead.
| |
| note | 0..* | Annotation | There are no (further) constraints on this element Element idDevice.note Device notes and comments DefinitionDescriptive information, usage information or implantation information that is not captured in an existing element.
| |
| safety | Σ | 0..* | CodeableConcept | There are no (further) constraints on this element Element idDevice.safety Safety Characteristics of Device DefinitionProvides additional safety characteristics about a medical device. For example devices containing latex.
|
| parent | 0..1 | Reference(Device) | There are no (further) constraints on this element Element idDevice.parent The higher level or encompassing device that this device is a logical part of DefinitionThe higher level or encompassing device that this device is a logical part of. For example a vital signs monitor (parent) where three separate modules can be plugged into such as interchangeable blood pressure, oximeter, temperature modules. These modules are represented as devices with the .parent valued to the vital signs monitor when plugged in.
|
Documentation:
https://simplifier.net/firstprofile3/device
Last updated on