Stream: SDPi+FHIR
Topic: ICE Data Logger & Capturing Clinician Changes
Todd Cooper (Jun 04 2020 at 18:23):
When implementing an ICE forensics DataLogger component, it would be good to capture not only changes to settings but how they came about: Clinician input, automatically updated (e.g., per internal algorithm derivations, or even external control service invocations). One approach would be to monitor a Metric object's derivation value (AbstractMetricDescriptor/@DerivationMethod) method (AUTO / MAN), but is that the best approach? And does it allow differentiation between all three of the change sources mentioned above?
Todd Cooper (Jun 05 2020 at 12:38):
@Stefan Schlichting thoughts on how to best address this?
Stefan Schlichting (Jun 05 2020 at 19:19):
You can send an OperationInvokedReport if the device represents the operations that are locally invoked. Just set the accesslevel=Other and use the extension that we have defined for "LocaleOnly" and optionally disable the operations if they should not be invoked externally.
You can use InvocationSource to identify the object/person/SDC participant that invoked the operation.
Todd Cooper (Jun 08 2020 at 12:29):
@Stefan Schlichting good point re. InvocationSource; @Scott Gearhart @Jan Rizzuto this could be useful for this component of the MDIRA/ICE ref implementation;
Last updated: Apr 12 2022 at 19:14 UTC
