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

NFC Tag: Secondary user ID for Pulse

Hi Jakub,


Jörg suggested to get you involved, I need to ask you to prioritize a certain feature in order to secure sales success of the cobas pulse System.


This is about the Agaplesion clinic group, which is one of the ten largest hospital operators in Germany (allegedly number 3 with 22 clinic locations alone with almost 6,500 beds and 36 MVZ). Currently about their Ulm location, which probably will be a role model for the rest of the group.

The customer uses NFC-tags for their user authentication. There are 2 properties you need to know about in this case: 1) Unique-ID which is kind of a SerialNumber, but unique across all vendors and pre-defined at manufacturing 2) User ID which is stored in a so called NDEF-record and defined by the customer.
Agaplesion uses Unique-IDs for user authentication: they assign Unique-IDs to users instead of writing an existing User-ID to the NDEF-record of the NFC-tag.
Problem: infinity POC is only able to handle NDEF-records. I
n consequence, Agaplesion cannot use cobas pulse.


So in order to keep the customer, we have to offer a solution as soon as possible. For a demo/FCM, I can still imagine reading out the unique ID and writing it back to the NDEF record as a user ID in the HOPE it would be justifiable for an FCM. For sales, we need (time) planning security for the customer.
So I would line to ask you to make the required changes a priority and I would line to ask how soon we can offer the customer a proper solution so that Agaplesion can use the Unique ID as a user authentication.
Bye & kind regardsTill

  • Guest
  • Jul 20 2022
  • Shipped