1. Device related Resources
Stefan Schlichting

2. Options for Modelling
PHD – only measurements, no other state of device
(PHD – measurements, operational state of metric and MDS is relevant)*
PoCD - measurements, operational state of metric and MDS is relevant
* if needed

3. 1. PHD – only measurements, no other state of device
Info:
‘no other state’ means that no information about the state/status of the device exist. Only static information is available.
Device
Brian:
Not sure what you mean by ‘no other state’.
It is possible for no production spec, but PCHA
requires serial number and firmware revision.
This would be okay for no production spec
To date no such PHD exists that maps to this
configuration.
Device
Observation
Patient
subject
Static Device
Observation
Dynamic Device
Patient

4. 1. PHD – only measurements, no other state of device
Proposal
Device,v1
model
manufacturer l
SerialNumber in Id
Brian:
This would only work if the production spec
contained only the serial number. The Lot number
is not obtainable by protocol unless one overloads
the production-spec part number. To date no such
PHD exists that maps to this configuration.
Device
Observation,v1
Observation,v1
Patient,v12
effectiveDateTime:
:53
valueQuant:
99%
effectiveDateTime:
:55
valueQuant:
98%
Name
Roberta C. Schmidt
identifier:
887345
subject
Static Device
Observation
Dynamic Device
Patient

5. 2. PHD –measurements, operational state of metric and MDS is relevant*
DevComp <MDS>,v1
Device,v1
lastSysChange:
:52
operationalStatus:
off
model
manufacturer
SerialNumber in Id
source
Note:
The proposed change is to make the lastSystemChange optional.
There is no implied value.
Not in use
Brian:
This configuration does not exist in the PHD world.
The last system change is never available by protocol.
The only possible use of a DeviceMetric would be to
report multiple specializations.
DevMetric,v1
lastSysChange:
:52
operationalStatus:
off
parent
Static Device
Observation
* if needed
Dynamic Device
Patient

6. 2. PHD –measurements, operational state of metric and MDS is relevant
DevComp <MDS>,v2
Device,v1
lastSysChange:
:53
operationalStatus: on
model
manufacturer
SerialNumber in Id
source
Not in use
DevMetric,v2
lastSysChange:
:53
operationalStatus: on
parent
Device
Observation,v1
Observation,v1
Patient,v12
effectiveDateTime:
:53
valueQuant:
99%
effectiveDateTime:
:55
valueQuant:
98%
Name
Roberta C. Schmidt
identifier:
887345
subject
Static Device
Observation
Dynamic Device
Patient

7. 2.PHD –measurements, operational state of metric and MDS is relevant
Proposal
DevComp <MDS>,v2
Device,v1
(lastSysChange :
:53)
operationalStatus: on
model
manufacturer
lotNumber
SerialNumber in Id
source
Not in use
DevMetric,v2
(lastSysChange :
:53)
operationalStatus: on
parent
Device
Observation,v1
Observation,v1
Patient,v12
effectiveDateTime:
:53
valueQuant:
99%
effectiveDateTime:
:55
valueQuant:
98%
Name
Roberta C. Schmidt
identifier:
887345
subject
Static Device
Observation
Dynamic Device
Patient

8. 3. PoCD - measurements, operational state of metric and MDS is relevant
DevComp <MDS>
Device
source
DevComp <VMD>
parent
DevComp <Chan>
parent
DevMetric
parent
Device
Observation
Patient
subject
Static Device
Observation
Dynamic Device
Patient

9. lastSystemChange lastSystemChange is either:
manufacturing date, if no changes have been made afterwards
the time when the device resource is initially uploaded to the FHIR Repository and if no changes have been made
The time when the component has been changed the last time
If no lastSystemChange is given it is implied that the date is irrelevant and equals the option b.

10. 3. PoCD - measurements, operational state of metric and MDS is relevant
Proposal
DevComp <MDS>,v2
Device,v1
lastSysChange:
:53
operationalStatus: on
model
manufacturer
lotNumber
SerialNumber in Id
source
DevComp <VMD>,v2
(lastSysChange :
:53)
operationalStatus: on
parent
DevComp <Chan>,v1
DevComp <Chan>,v4
(lastSysChange :
:53)
operationalStatus:
off
(lastSysChange :
:54)
operationalStatus: on
parent
Brian:
How can one represent a sub-component device that has a different manufacturer name and model number, even if the sub-component comes from the same company?
Stefan
Currently I don’t see any use case for it. The manufacturer that brings the device into the field does all the tracking of it suppliers. If it is accessory that also generates data on its own which can also be another manufacturer then this would be another device (pot. with DeviceComponents) . I don’ t know any accessory of that kind.
DevMetric,v1
DevMetric,v4
(lastSysChange :
:53)
operationalStatus:
off
(lastSysChange :
:54)
operationalStatus: on
parent
parent
Device
Observation,v1
Observation,v1
effectiveDateTime:
:55:01
valueQuant:
99%
effectiveDateTime:
:55:02
valueQuant:
98%
Static Device
Observation
Dynamic Device
Patient

11. 3. PoCD - measurements, operational state of metric and MDS is relevant
DevComp <MDS>,v2
Device,v1
lastSysChange:
:53
operationalStatus: on
model
manufacturer
lotNumber
SerialNumber in Id
source
DevComp <VMD>,v2
(lastSysChange :
:53)
operationalStatus: on
parent
parent
DevComp <Chan>,v1
DevComp <Chan>,v4
(lastSysChange :
:53)
operationalStatus:
off
(lastSysChange :
:54)
operationalStatus: on
parent
parent
DevMetric,v1
DevMetric,v4
(lastSysChange :
:53)
operationalStatus:
off
(lastSysChange :
:54)
operationalStatus: on
parent
parent
Patient Demogr. available after first measurements
Device
Observation,v2
Observation,v2
Patient
effectiveDateTime:
:55:01
valueQuant:
99%
effectiveDateTime:
:55:02
valueQuant:
98%
Name
Roberta C. Schmidt
identifier:
887345
subject
Static Device
Observation
Dynamic Device
Patient

12. Backup

13. DevComp <MDS> Device DevComp <VMD> DevComp <Chan>
source
DevComp <VMD>
parent
DevComp <Chan>
parent
DevMetric
parent
Device
Observation
Patient
subject

14. DevComp <MDS>
Device
DevComp <VMD>
DevComp <Chan>
DevMetric
Observation
Patient