@prefix fhir: . @prefix owl: . @prefix rdfs: . @prefix xsd: . # - resource ------------------------------------------------------------------- a fhir:NamingSystem; fhir:nodeRole fhir:treeRoot; fhir:Resource.id [ fhir:value "usb-address-identifier"]; fhir:DomainResource.text [ fhir:Narrative.status [ fhir:value "generated" ]; fhir:Narrative.div "

Summary

Defining URLhttp://terminology.hl7.org/NamingSystem/usb-address-identifier
NameUSB_Address_Identifier
Statusactive
Definition

A USB device that is plugged in identifies itself by its VID/PID combination. A VID is a 16-bit vendor number (Vendor ID). A PID is a 16-bit product number (Product ID). A host uses the VID/PID combination to find the drivers (if any) that are to be used for the USB device. For this to work, the VID/PID combination must be unique, in the sense that each USB device with the same VID/PID will use the same driver. So, whenever you need a specific driver for your USB product, you will need a unique VID/PID for that product. In that sense, the VID/PID combination does not really serve as a truly unique identifier of a single device instance. It is, however, useful to know for medical devices that communicate using USB.

\n
PublisherIHE Patient Care Devices (PCD)

Identifiers

TypeValuePreferredComment
URIhttp://hl7.org/fhir/sid/usbtrueUSB VID (Vendor identifier) and PID (Product identifier) values
" ]; fhir:DomainResource.extension [ fhir:index 0; fhir:Extension.url [ fhir:value "http://hl7.org/fhir/tools/StructureDefinition/extension-title" ]; fhir:Extension.valueString [ fhir:value "USB VID and PID as a device identifier" ] ], [ fhir:index 1; fhir:Extension.url [ fhir:value "http://hl7.org/fhir/5.0/StructureDefinition/extension-NamingSystem.url" ]; fhir:Extension.valueUri [ fhir:value "http://terminology.hl7.org/NamingSystem/usb-address-identifier" ] ], [ fhir:index 2; fhir:Extension.url [ fhir:value "http://terminology.hl7.org/StructureDefinition/ext-namingsystem-version" ]; fhir:Extension.valueString [ fhir:value "1.0.0" ] ]; fhir:NamingSystem.name [ fhir:value "USB_Address_Identifier"]; fhir:NamingSystem.status [ fhir:value "active"]; fhir:NamingSystem.kind [ fhir:value "identifier"]; fhir:NamingSystem.date [ fhir:value "2021-06-14T00:00:00-00:00"^^xsd:dateTime]; fhir:NamingSystem.publisher [ fhir:value "IHE Patient Care Devices (PCD)"]; fhir:NamingSystem.contact [ fhir:index 0; fhir:ContactDetail.name [ fhir:value "Devices on FHIR working group; IHE Patient Care Devices" ] ]; fhir:NamingSystem.responsible [ fhir:value "IHE Patient Care Devices"]; fhir:NamingSystem.description [ fhir:value "A USB device that is plugged in identifies itself by its VID/PID combination. A VID is a 16-bit vendor number (Vendor ID). A PID is a 16-bit product number (Product ID). A host uses the VID/PID combination to find the drivers (if any) that are to be used for the USB device. For this to work, the VID/PID combination must be unique, in the sense that each USB device with the same VID/PID will use the same driver. So, whenever you need a specific driver for your USB product, you will need a unique VID/PID for that product. In that sense, the VID/PID combination does not really serve as a truly unique identifier of a single device instance. It is, however, useful to know for medical devices that communicate using USB."]; fhir:NamingSystem.uniqueId [ fhir:index 0; fhir:NamingSystem.uniqueId.type [ fhir:value "uri" ]; fhir:NamingSystem.uniqueId.value [ fhir:value "http://hl7.org/fhir/sid/usb" ]; fhir:NamingSystem.uniqueId.preferred [ fhir:value "true"^^xsd:boolean ]; fhir:NamingSystem.uniqueId.comment [ fhir:value "USB VID (Vendor identifier) and PID (Product identifier) values" ] ] . # - ontology header ------------------------------------------------------------ a owl:Ontology; owl:imports fhir:fhir.ttl . # -------------------------------------------------------------------------------------