Roche RIS Feedback Portal

Please submit any feature requests and vote on ideas that have already been submitted to indicate your interest in seeing them developed

Make userID for satellite sites independent from the centralized database

  • Guest
  • Oct 10 2024
Idea detail description

Situation: private lab company manages POCT instruments for more than 130 hospitals. The hospitals are the customers of the lab. The hospitals are independant from each other and thus data needs to be seperated because of data protection/GDPR. For that, the lab operates 3 centralized nPocOps servers (1 for mg/dL, 1 for mmol/L, 1 for its own purposes). Each hospital w/in that server is a separate satellite so that regulations regarding data protection can be followed.


Problem: userID in nPocOps needs to be unique on the whole server instance. But the hospitals of course do not share a common user base, because they ARE independant. So, a specific userID (say "4711") can be used in more than one hospital. In order to make the usage of nPocOps possible, the lab now requires the customer to issue new userIDs which makes the userIDs unique across the whole customer base. This is done by a lab-defined prefix per customer. Example: Marien Krankenhaus Ludwigshafen gets "MKH-LU" as prefix and Stadtklinik Frankenthal "SKL-FT" this maps userId 4711 to MKH-LU_4711 or MKH-FT_4711 respectively . As a further consequence, this requires the hospitals to issue new badges. This is not desirable, because it is cost-intensive and produces a liot of effort.

Required solution: nPocOps needs to be able to manage userIDs per Satellite independantly from other satellites on the same server.