Generated Narrative: StructureDefinition BeModelDevice Name Flags Card. Type Description & Constraints BeModelDevice 0..* Base Device Logical Model #xD; owner 0..1 Reference(Organization) Owner #xD; patient 0..1 Reference(Patient) Patient #xD; udiCarrier 0..1 BackboneElement UDI Carrier #xD; deviceIdentifier 0..1 string Device Identifier #xD; carrierHRF 0..1 string Carrier HRF #xD; identifier 0..1 Identifier Identifier #xD; status 0..1 code Status Binding: Device Status Value Set (required) #xD; statusReason 0..* CodeableConcept Status Reason Binding: Device Status Reason Value Set (example) #xD; type 0..1 CodeableConcept Type Binding: Device Type Value Set (example) #xD; deviceDefinition 0..1 Reference() Device Definition #xD; manufacturer 0..1 string Manufacturer #xD; manufactureDate 0..1 dateTime Manufacture Date #xD; expirationDate 0..1 dateTime Expiration Date #xD; lotNumber 0..1 string Lot Number #xD; version 0..1 string Version #xD; serialNumber 0..1 string Serial Number #xD; deviceName 0..1 string Device Name #xD; modelNumber 0..1 string Model Number #xD; property 0..* BackboneElement Property #xD; type 1..1 CodeableConcept Property Type #xD; value[x] 0..1 Property Value #xD; valueQuantity Quantity #xD; valueCodeableConcept CodeableConcept #xD; valueString string #xD; valueBoolean boolean #xD; valueInteger integer #xD; valueRange Range #xD; valueAttachment Attachment #xD; note 0..* Annotation Note #xD; Documentation for this format
Patient in whom the device is implanted or for whom it is used
The Unique Device Identifier (UDI), usually captured by scanning a barcode or RFID label, enabling unique identification of the exact device (manufacturer, type, lot number, serial number, expiration date, etc.)
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
Additional content defined by implementations
May 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.
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
Extensions that cannot be ignored even if unrecognized
May 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](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
The device identifier (DI) portion of the UDI
Alternative identifier when no UDI is available, e.g. a NIHDI notification number or other alternative identifier
Status of the device (active, inactive, entered-in-error, unknown)
Reason why the device has a particular status, e.g. why it is inactive or out of service
The kind of medical device, e.g. SNOMED CT code 304120007 - Cardiac pacemaker, device (physical object)
Reference to the generic definition of the device, describing general characteristics of the device type rather than the unique instance
The manufacturer that produced the device, e.g. Medtronic
The date after which the device may no longer be used
The lot or batch number in which the device was produced
The actual version of the device or the software version running on it
A unique identification code assigned by the manufacturer to one specific device
The name of the medical device as determined by the manufacturer
The model number of the device as assigned by the manufacturer
The actual configuration settings of a device as it operates, e.g. regulation status or time properties