Stream: implementers
Topic: Multiple identifiers
Brian Reinhold (Sep 09 2018 at 21:45):
In my profile I want to be able to specify multiple identifiers for Personal Health Devices (which do not yet electronically communicate UIDs). The identifiers are the system id and bluetooth address or ZigBee address. The system id is an EUI-64. The BT address is an EUI-48. The ZigBee address is an EUI-64.
How can I discriminate between these three cases?
How can I best indicate the EUI-XX? The identifier.system="urn:oid:1.2.840.10004.1.1.1.0.0.1.0.0.1.2680" indicating an EUI-xx.
Is there a clever way to use the identifier.type fpr a discriminator? Probably but I just don't know how to best populate it.
Grahame Grieve (Sep 09 2018 at 21:47):
let's start by being clear about what an instance looks like
Grahame Grieve (Sep 09 2018 at 21:47):
have you got an example?
Brian Reinhold (Sep 09 2018 at 21:47):
let's start by being clear about what an instance looks like
yes ... coming ...
Here is a best-guess identifier with a system id and Bluetooth address
"identifier": [{
"system": "urn:oid:1.2.840.10004.1.1.1.0.0.1.0.0.1.2680",
"value": "01-04-03-02-f0-00-00-00",
"assigner": {
"display": "EUI-64"
}
},
{
"system": "urn:oid:1.2.840.10004.1.1.1.0.0.1.0.0.1.2680",
"value": "12-34-56-78-9A-BC",
"assigner": {
"display": "EUI-48"
}
}],
arrg; formatting stinks...
Grahame Grieve (Sep 09 2018 at 22:07):
you can use 3 backticks to get preformatted code - ```
Grahame Grieve (Sep 09 2018 at 22:11):
I thought we had assigned some human readable URIs for the bluetooth identifiers, and had used different ones for -48 and -64. So I had thought it would be something like this:
Grahame Grieve (Sep 09 2018 at 22:12):
"identifier": [{ "system": "http://hl7.org/fhir/sid/eui-64", "value": "01-04-03-02-f0-00-00-00", }, { "system": "http://hl7.org/fhir/sid/eui-48", "value": "12-34-56-78-9A-BC", }]
Grahame Grieve (Sep 09 2018 at 22:12):
but I see that this has not made it's way into the spec.
Brian Reinhold (Sep 09 2018 at 22:15):
but I see that this has not made it's way into the spec.
I like that option. Right now we are using an oid to identify the use of an EUI but that does not specify what type of EUI.
Still need something to separate ZigBee addresses. which are also 64 bit.
Grahame Grieve (Sep 09 2018 at 22:16):
how are they different from EUI-64?
Brian Reinhold (Sep 09 2018 at 22:22):
I am not too sure about ZigBee addresses. I am assuming that ZigBee, like BLuetooth, has an EUI for its addresses so it identifies the producer of the device. ZigBee is pretty rare in PHDs at the moment and I might just delay on that...
Last updated: Apr 12 2022 at 19:14 UTC
