#99 Value set extension of AbstractOperationDescriptor/@AccessLevel

[Martin]

According to discussions in the PoCSpec project there can be interesting use cases to define operations in the SCO that cannot be triggered via SDC remotely, e.g., activate power emission of an HF device.

The current way to model this, would be setting AccessLevel="Oth". AccessLevel="Usr" (default value) would not be suitable. However, the user ("Any person interacting with (i.e., operating or handling) the POC MEDICAL DEVICE.") is actually doing the activation, but not via SDC. Therefore, I suggest adding a new value describing "Local User", maybe "LUsr".

Proposal:
LUsr = Local User. Any person interacting locally, this means not via SDC, with (i.e., operating or handling) the POC MEDICAL DEVICE.

See also [#187]

[Stefan Schlichting]

All the AccessLevel have to be interpreted as being used by a Service Consumer as defined in 5054.

Proposed Change:
Usr:
Usr = User. Any person interacting with (i.e., operating or handling) the POC MEDICAL DEVICE through a SERVICE CONSUMER.

CSUsr:
CSUsr = Clinical Super User.Individuals or entity accountable to the RESPONSIBLE ORGANIZATION that configure clinical relevant settings of a POC MEDICAL DEVICE through a SERVICE PROVIDER.

[Martin]

If this was intended by "CSUsr" this would work quite fine. I thought that CSUsr was also meant to describe SDC-based operation triggers.

[Björn Andersen]

I am not convinced this offers the same semantics as what Martin suggested above. Even if "through a SERVICE PROVIDER" means locally, the accountability and clinical relevance still restrict this AccessLevel in a way that is far narrower than the proposed local user.

[Björn Andersen]

Modelling local user interaction by means of SDC Operations is questionable. Consider alternative options before accepting this ticket.