Location lists to be used by service / biomeds

[d-gregorczyk]

Motivation

When dealing with location contexts in SDC, in order to couple medical devices to each other, those medical devices need to be configured in a way that they share the same location context. This can be done by either manually setting location context parameters at each and every device, which is an error prone and laborous task, or by distributing location contexts (semi-)automatically.

Solution space

As manual interaction on each device is inacceptable in terms of effort und time, esp. when changes to a location occur, it may be of value to share location lists between service interfaces, so that locations can be configured centrally.

First step

Specify a data exchange garammar that provides information as to where devices can be located. A service app can consume this data and provide valid lists of locations to the biomed, who than does not need to configure by manually typing in information.

Example: Locations.ucon 1.json

Second step

The first step is just a data format specification. How that data is transferred between service apps of different vendors or central servers, is not in scope. In a second step, we may specify a means to exchange said data.

[ToddCooper]

SDPi Friday 2024.03.08: David reviewed the issue.
Is it a location list for equipment + patients too?
See what is currently supported in the DEV/PCD/MEMLS (Location Service) profile (focused on RTLS location, non-patient specific)
See if there is also a touch point with the DEV/PCD/PCIM profile
How does this get integrated into SDPi? Does it get integrated into SDPi?

[ToddCooper]

SDPi Friday 2024.07.05 Discussion:

Keep on list BUT determine priority for implementation. @ToddCooper engage stakeholders to reassess need.

[ToddCooper]

SDPi Workshop #4 -

See workshop notes (Wednesday morning). Need more detail to understand implementation requirements + this is closely related to the Context Management topic.