Troubleshooting 193 Starting up an instrument with low battery level A turned-off instrument with low battery level (<15%) will not start up automatically when placed in the charging station. However, an instrument with sufficient battery level (>15%) starts up automatically. In order for an instrument to start up and to operate, its battery must have sufficient charge (>15%). When it does not, the battery must be allowed to charge to a sufficient level so that the instrument can start up.
194 Starting up an instrument with low battery level 8 Troubleshooting Page intentionally left blank. Roche Diagnostics cobas® pulse · Software version 01.03 · User Assistance · Publication version 1.
Table of contents 195 In this chapter 9 About level 1 messages and level 2 errors................... 209 Level 1 messages................................................................... 213 B-AA: Invalid barcode............................................... 214 B-AB: Scan timeout.................................................... 214 B-AC: Wrong sequence............................................ 215 B-AD: Configuration error .......................................
9 Error messages 196 Table of contents I-AC: Software update error.................................... 221 I-AE: Encryption error................................................ 222 I-AF: Software update error .................................... 222 I-AG: Synchronization failed ................................... 222 I-AH: Connection error ............................................. 222 I-AJ: Encryption warning.......................................... 223 S-AB: Sample application error...
CA-0010: Communication with measuring unit interrupted .......................... 235 CA-0011: Software error ............................... 236 CA-0012: Synchronization with DMS failed ..................................................................... 236 CA-0013: Test strip inserted too early...... 236 CA-0014: Test strip ID not recognized..... 237 CA-0015: Error during Glucose app startup ..................................................................
9 Error messages 198 Table of contents CA-0048: Test strip lot not yet passed QC.......................................................................... 247 CA-0050: Date / time settings lost ............ 248 CA-0051: Invalid concentration value...... 248 CA-0052: Invalid sample ID ......................... 248 CA-0053: Strip lot data request timed out.......................................................................... 249 CA-0054: Wrong kit type scanned ............
CA-0086: Invalid user ID ............................... 259 CA-0087: Invalid patient ID.......................... 259 CA-0088: Invalid patient ID.......................... 260 CA-0089: Invalid patient ID.......................... 260 CA-0090: Invalid patient ID.......................... 260 CA-0091: Invalid QC material barcode .... 261 CA-0092: Invalid linearity material barcode................................................................ 261 CA-0093: Invalid configuration barcode .
200 Table of contents CA-0120: Invalid test strip container barcode................................................................ 270 CA-0121: Linearity lot expired .................... 270 CA-0122: Test strip lot expired ................... 270 CA-0123: DMS host cannot be reached. 271 CA-0124: DMS server certificate check failed ..................................................................... 271 CA-0125: Instrument client certificate check failed.........................................
MS-0013: SW update error .......................... 281 MS-0015: Forced measuring unit shutdown ............................................................ 281 MS-0016: Measuring unit error.................. 282 MS-0017: Measuring unit error.................. 282 MS-0018: Measuring unit error.................. 282 MS-0019: SW update error .......................... 282 MS-0020: Test strip ejection error............. 283 MS-0021: Measuring unit error..................
9 Error messages 202 Table of contents MU-0136: Measuring unit error ................. 296 MU-0137: Measuring unit error ................. 297 MU-0138: Measuring unit error ................. 297 MU-0139: Measuring unit error ................. 297 MU-0140: Measuring unit error ................. 298 MU-0141: Measuring unit error ................. 298 MU-0142: Measuring unit error ................. 298 MU-0143: Measuring unit error ................. 299 MU-0145: Measuring unit error ........
MU-0179: Voltage measurement failsafe activated .................................................... 308 MU-0180: Measuring unit error ................. 308 MU-0182: Measuring unit error ................. 309 MU-0183: Measuring unit error ................. 309 MU-0231: Test strip ejection error ............ 309 MU-0232: Test strip ejection error ............ 310 MU-0241: Test strip ejection error ............ 310 MU-0242: Measuring unit error .................
9 Error messages 204 Table of contents MU-0342: Test strip ID decoding error ... 320 MU-0343: Test strip insertion error........... 320 MU-0345: Test strip inserted upside down ..................................................................... 321 MU-0346: Measuring unit error ................. 321 MU-0347: Measuring unit error ................. 321 MU-0348: Measuring unit error ................. 322 MU-0350: Measuring unit error ................. 322 MU-0351: Measuring unit error ......
MU-0514: Measuring unit error ................. 333 MU-0515: Measuring unit error ................. 333 MU-0521: Measuring unit error ................. 333 MU-0523: Measuring unit error ................. 334 MU-0524: Measuring unit error ................. 334 MU-0525: Measuring unit error ................. 334 MU-0526: Measuring unit error ................. 335 MU-0527: Measuring unit error ................. 335 MU-0528: Measuring unit error .................
9 Error messages 206 Table of contents MU-0975: Signal range violation ............... 345 MU-0976: Signal range violation ............... 345 MU-0978: Signal range violation ............... 345 MU-0979: Removal of test strip during test......................................................................... 346 MU-0980: Signal range violation ............... 346 MU-0981: Signal range violation ............... 346 MU-0982: Signal range violation ...............
Table of contents 356 US-0024: Software update error ................ 356 US-0025: Software update error ................ 356 US-0026: Software update error ................ 357 US-0027: Software update error ................ 357 US-0028: Incompatible software update container ............................................................. 358 9 Error messages US-0023: Software update package download failed ................................................
208 Table of contents 9 Error messages Page intentionally left blank. Roche Diagnostics cobas® pulse · Software version 01.03 · User Assistance · Publication version 1.
Error messages 209 About level 1 messages and level 2 errors The cobas pulse user interface guides you through workflows based on the instrument configuration. Information, warning, and error screens indicate when cobas pulse detects specific conditions or events. Level 1 messages Level 1 messages are displayed on the user interface. They can also be retrieved by the DMS.
210 About level 1 messages and level 2 errors Warning (dialog) Warning with action (dialog) Error (dialog) 9 Error messages Camera related message Roche Diagnostics cobas® pulse · Software version 01.03 · User Assistance · Publication version 1.
Error messages 211 Inline error below a text entry field As well as being displayed on the user interface, level 1 Audit trail messages are listed in the audit trail ( > Audit trail). Settings changed 22-Mar-2020, 16:31 Level 1 messages are grouped by the nature of the underlying issue/error, and represented by a letter. The letter is incorporated in the message code (e.g.
212 About level 1 messages and level 2 errors • User assistance • Instrument audit trail • DMS You use the level 2 error code to locate the error message details in the User Assistance. When viewed in the User Assistance a level 2 error provides the following information: • Error code (e.g., CA-0010) • Title • Problem • Solution • Trace to the level 1 error message (e.g., G-AA) Using the instrument audit trail or the DMS, only the error code of the level 2 error is provided.
Error messages 213 Level 1 messages In this section B-AA: Invalid barcode (214) B-AB: Scan timeout (214) B-AC: Wrong sequence (215) B-AD: Configuration error (215) C-AA: Database full (215) C-AB: Database error (215) C-AD: Connection error (216) D-AA: Test strip error (216) D-AB: Lot expired (216) D-AE: Material expired (216) D-AF: Test strip error (217) D-AG: Insertion error (217) D-AH: Unknown lot (217) D-AJ: QC test required (217) D-AK: Insertion error (218) D-AL: Test strip error (218) D-AN: Unknown k
214 Level 1 messages S-AD: Sample type error (223) S-AF: Sample error (223) T-AA: Invalid RFID tag (224) T-AB: RFID timeout (224) U-AA: Invalid user ID (224) U-AB: Invalid password (224) U-AC: Patient not found (225) U-AD: Invalid observer (225) U-AE: Invalid patient ID (225) U-AF: User not found (225) U-AG: Unexpected bottle (226) U-AJ: User not found (226) U-AK: Patient not found (226) U-AL: Password too short (226) U-AM: Passwords do not match (227) U-AN: Inconsistent insulin value (227) U-AO: Invalid
Error messages 215 B-AC: Wrong sequence Wrong barcode scanned.* Scan barcode %s of %s.* * of Severity GUI Error DMS Note u About level 1 messages and level 2 errors (209) B-AD: Configuration error Check barcode configuration content. Severity GUI Error DMS Note u About level 1 messages and level 2 errors (209) C-AA: Database full Ensure that the instrument is connected to the network.
216 Level 1 messages C-AD: Connection error Test strip lot data retrieval not possible. Ensure that the instrument is connected to the network. Severity GUI Warning DMS Note u About level 1 messages and level 2 errors (209) D-AA: Test strip error Repeat the test with a new test strip. Severity GUI Warning DMS Critical u About level 1 messages and level 2 errors (209) D-AB: Lot expired Repeat the test with a test strip from a valid lot.
Error messages 217 D-AF: Test strip error Repeat the test with a new test strip. Follow proper usage in the handling recommendations. Severity GUI Warning DMS Critical u About level 1 messages and level 2 errors (209) D-AG: Insertion error Eject the test strip and insert it correctly. Severity GUI Warning DMS Note u About level 1 messages and level 2 errors (209) D-AH: Unknown lot Ensure that a correct test strip lot is used.
218 Level 1 messages D-AK: Insertion error Eject the test strip and insert it again when requested. Severity GUI Warning DMS Note u About level 1 messages and level 2 errors (209) D-AL: Test strip error Test strip was removed during the test. Repeat the test with a new test strip. Do not remove the test strip during processing. Severity GUI Warning DMS Note u About level 1 messages and level 2 errors (209) D-AN: Unknown kit lot Unknown kit lot.
Error messages 219 D-AP: Wrong lot Use the same test strip lot for all linearity test levels. Severity GUI Warning DMS Note u About level 1 messages and level 2 errors (209) E-AA: Temperature too low Testing not possible. Use the instrument at a higher temperature. Severity GUI Error DMS Critical u About level 1 messages and level 2 errors (209) E-AB: Temperature too high Testing not possible. Use the instrument at a lower temperature.
220 Level 1 messages G-AC: Process error Repeat the test with a new test strip. Severity GUI Warning DMS Warning u About level 1 messages and level 2 errors (209) G-AE: Instrument error Action is not possible. Severity GUI Warning DMS Warning u About level 1 messages and level 2 errors (209) H-AC: Low battery Charge the instrument.
Error messages 221 H-AG: Ejection error Eject the test strip using the eject button. If the problem persists, remove the test strip manually. Severity GUI Error DMS Critical u About level 1 messages and level 2 errors (209) H-AJ: Battery version error Due to the nature of this issue, only the ID (H-AJ) of the message is displayed on the screen. Incompatible battery detected. The instrument cannot be used. Contact your Roche representative.
222 Level 1 messages I-AE: Encryption error An encryption error occurred. Results cannot be synchronized. Severity GUI Error DMS Critical u About level 1 messages and level 2 errors (209) I-AF: Software update error A software update error occurred. Severity GUI Information DMS Warning u About level 1 messages and level 2 errors (209) I-AG: Synchronization failed Synchronization with the DMS failed.
Error messages 223 I-AJ: Encryption warning An encryption warning ocurred. Results are still being synchronized. Severity GUI Warning DMS Warning u About level 1 messages and level 2 errors (209) S-AB: Sample application error Repeat the test with a new test strip. Apply sufficient sample when requested without moving the test strip. Severity GUI Warning DMS Warning u About level 1 messages and level 2 errors (209) S-AD: Sample type error Repeat the test with a new test strip.
224 Level 1 messages T-AA: Invalid RFID tag Read a correct RFID tag. Severity GUI Error DMS Warning u About level 1 messages and level 2 errors (209) T-AB: RFID timeout Reading period has timed out. Ensure sufficient proximity. Severity GUI Warning DMS Note u About level 1 messages and level 2 errors (209) U-AA: Invalid user ID User ID is invalid.
Error messages 225 U-AC: Patient not found Patient ID was not found. Severity GUI Error DMS Warning u About level 1 messages and level 2 errors (209) U-AD: Invalid observer Invalid observer Severity GUI Error DMS Note u About level 1 messages and level 2 errors (209) U-AE: Invalid patient ID Patient ID is invalid. Severity GUI Error DMS Critical u About level 1 messages and level 2 errors (209) User ID was not found.
226 Level 1 messages U-AG: Unexpected bottle Scan bottle: %s, %s.* * , Dependant on the workflow: = ’QC’ or ’Linearity’ = Individual level number (e.g., 1 or 2 for ’QC’) Severity GUI Warning DMS Note u About level 1 messages and level 2 errors (209) U-AJ: User not found User was not found. Severity GUI Error DMS Critical u About level 1 messages and level 2 errors (209) U-AK: Patient not found Patient was not found.
Error messages 227 U-AM: Passwords do not match Passwords do not match. Severity GUI Error DMS Note u About level 1 messages and level 2 errors (209) U-AN: Inconsistent insulin value Value must be greater than 0 and less than 50 (maximum one decimal place). Severity GUI Error DMS Note u About level 1 messages and level 2 errors (209) U-AO: Invalid sample ID Sample ID is invalid. Severity GUI Error DMS Note U-AP: Invalid sample ID Sample ID is invalid.
228 Level 1 messages U-AQ: Insufficient user rights Action is not allowed. Severity GUI Error DMS Note 9 Error messages u About level 1 messages and level 2 errors (209) Roche Diagnostics cobas® pulse · Software version 01.03 · User Assistance · Publication version 1.
Error messages 229 Level 2 errors In this section CA (229) MS (277) MU (287) US (348) CA In this section CA-0001: Unknown error (232) CA-0002: Database access error (233) CA-0003: Database access error (233) CA-0004: Measuring unit communication error (233) CA-0005: Measuring unit communication error (234) CA-0006: Access to internal storage failed (234) CA-0007: Software error (234) CA-0008: Test strip lot information not found (235) CA-0009: Test strip lot expired (235) CA-0010: Communication with meas
230 Level 2 errors CA-0029: User ID not found (241) CA-0030: Scan timeout (242) CA-0031: RFID timeout (242) CA-0032: Incorrect sample applied in a QC test or linearity test (242) CA-0033: Incorrect sample applied in a glucose test (243) CA-0034: Wrong barcode sequence (243) CA-0035: Wrong analyte scanned (243) CA-0036: Wrong kit type scanned (244) CA-0037: Wrong QC level scanned (244) CA-0038: QC lot expired (244) CA-0039: Unknown QC lot scanned (244) CA-0040: TLS communication error (245) CA-0041: Databa
Error messages 231 CA-0072: Database error (254) CA-0073: Instrument was charged during measurement (254) CA-0074: Result database full (255) CA0075: Software error (255) CA-0077: Internal storage error (255) CA-0078: TLS communication warning (256) CA-0079: Certificate backup failed (256) CA-0080: Entry does not exist anymore (257) CA-0081: Configuration by barcode error (257) CA-0082: Low battery (257) CA-0083: Invalid user ID (258) CA-0084: Invalid user ID (258) CA-0085: Invalid user ID (258) CA-0086:
232 Level 2 errors CA-0113: Database limit reached for test strip lots (267) CA-0114: Password too long (268) CA-0115: Invalid certificate configuration update (268) CA-0116: Different users log on as observer before and after OTS (268) CA-0117: Invalid barcode content (269) CA-0118: Invalid platform interface detected (269) CA-0119: Patient ID not found (269) CA-0120: Invalid test strip container barcode (270) CA-0121: Linearity lot expired (270) CA-0122: Test strip lot expired (270) CA-0123: DMS host ca
Error messages Related L1 message 233 G-AA u About level 1 messages and level 2 errors (209) CA-0002: Database access error Problem A database access error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) CA-0003: Database access error Problem A database access error occurred. Solution Restart the instrument and try again.
234 Level 2 errors u About level 1 messages and level 2 errors (209) CA-0005: Measuring unit communication error Problem The instrument was not able to communicate with the measuring unit. Solution Restart the instrument and try again. Related L1 message G-AA u About level 1 messages and level 2 errors (209) CA-0006: Access to internal storage failed Problem The instrument was not able to access its internal storage. Solution Restart the instrument and try again.
Error messages 235 CA-0008: Test strip lot information not found Problem The lot information of the inserted test strip is missing. The inserted test strip cannot be used Solution Add the unknown test strip lot to the instrument database by using one of the following methods: • Scan the strip vial container and let the instrument request the lot from cobas® infinity edge. • Scan the complete lot information via a configuration barcode (generated in the cobas® infinity edge management portal).
236 Level 2 errors u About level 1 messages and level 2 errors (209) CA-0011: Software error Problem The instrument is defective and cannot be used for testing. Solution Contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) CA-0012: Synchronization with DMS failed Problem The synchronization with the DMS failed. The instrument cannot transmit results or receive updated data from the DMS.
Error messages 237 CA-0014: Test strip ID not recognized Problem The instrument was not able to read the test strip ID (e.g. due to dirt or scratches). Solution Eject the current test strip and insert a new test strip. If the problem persists, contact your Roche representative. Related L1 message D-AH u About level 1 messages and level 2 errors (209) CA-0015: Error during Glucose app startup Problem An error occured during the startup of the Glucose app.
238 Level 2 errors CA-0017: QC lot expired Problem The QC lot used has expired. Solution Repeat the test using a valid QC lot. Related L1 message D-AE u About level 1 messages and level 2 errors (209) CA-0019: User ID not found Problem The scanned user ID is unknown to the instrument. Solution Ensure that the instrument is connected to the network and the DMS. Check the connectivity and availability of the DMS using the network status test.
Error messages 239 CA-0021: RFID tag invalid Problem An unsupported RFID tag was read. Solution Only use supported RFID tags. Related L1 message T-AA u About level 1 messages and level 2 errors (209) CA-0022: Invalid password Problem The user entered an invalid password. Solution Enter a valid password. If the password has been changed recently, it might take a moment until it is propagated to all other instruments.
240 Level 2 errors CA-0024: Password too short Problem The password entered is shorter than the configured minimal password length. Solution Enter a password that has the same or more characters than the configured minimal password length value. Related L1 message U-AL u About level 1 messages and level 2 errors (209) CA-0025: Passwords do not match Problem While changing the user password on the instrument user interface, the user has entered two passwords that do not match.
Error messages 241 CA-0027: Invalid insulin units Problem The user entered an value for the insulin units that contains more than one decimal place. Solution Enter a valid insulin value what contains maximum 1 decimal place. Related L1 message U-AN u About level 1 messages and level 2 errors (209) CA-0028: Invalid user ID Problem The user entered a user ID that does not comply to the configured pattern for the user ID.
242 Level 2 errors u About level 1 messages and level 2 errors (209) CA-0030: Scan timeout Problem The barcode scanning period has timed out. Either the user did not scan the barcode correctly or the user tried to scan a barcode type which is deactivated in the instrument configuration. Solution Restart the barcode scanning and ensure that the barcode is visible in the scan area on the instrument screen.
Error messages 243 u About level 1 messages and level 2 errors (209) CA-0033: Incorrect sample applied in a glucose test Problem The user applied QC material or linearity material to the test strip instead of blood. Solution Eject the current test strip and repeat the test with blood. Related L1 message S-AD u About level 1 messages and level 2 errors (209) CA-0034: Wrong barcode sequence Problem The user scanned the barcodes for configuration in the wrong order.
244 Level 2 errors CA-0036: Wrong kit type scanned Problem The user scanned a linearity material bottle instead of a QC material bottle. Solution Scan the correct QC material bottle. Related L1 message U-AG u About level 1 messages and level 2 errors (209) CA-0037: Wrong QC level scanned Problem The user scanned a QC material bottle that did not match the selected QC level. Solution Scan the correct QC material level to continue the workflow.
Error messages Solution 245 Add the lot to the instrument database on the instrument in Settings > Lot management. Ensure that the instrument is connected to the network in order to enable the DMS to synchronize the kit lot database on the instrument. Related L1 message D-AN u About level 1 messages and level 2 errors (209) CA-0040: TLS communication error Problem The TLS (Transport Layer Security) handshake between the DMS and the instrument failed.
246 Level 2 errors CA-0041: Database error Problem A database error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) CA-0042: User ID not found Problem The entered user ID is unknown to the instrument. Solution Ensure that the instrument is connected to the network. Check the connectivity and availability of the DMS using the network status test.
Error messages 247 CA-0044: Measuring unit communication issue Problem The instrument was not able to start up the measuring unit. Solution Go to the app library and open the Glucose app again. If the problem persists, restart the instrument. Related L1 message G-AA u About level 1 messages and level 2 errors (209) CA-0045: Configuration update failed Problem The configuration barcode could not be processed.
248 Level 2 errors CA-0050: Date / time settings lost Problem The current date/time settings are lost (e.g., due to loss of power/battery change). Solution Enter the date and time manually and ensure that the instrument is connected to the network. Related L1 message H-AF u About level 1 messages and level 2 errors (209) CA-0051: Invalid concentration value Problem The measuring unit was not able to quantify the concentration of the measured sample.
Error messages 249 CA-0053: Strip lot data request timed out Problem The instrument was not able to retrieve the strip lot data from cobas infinity edge. Solution Ensure that the instrument is connected to the network. Check that the instrument is connected to cobas infinity edge using the network status test. Related L1 message C-AD u About level 1 messages and level 2 errors (209) CA-0054: Wrong kit type scanned Problem The user scanned a QC material bottle instead of a linearity material bottle.
250 Level 2 errors CA-0057: Linearity lot expired Problem The lot of the scanned linearity material has expired. Solution Use a valid linearity lot. Related L1 message D-AE u About level 1 messages and level 2 errors (209) CA-0058: Unknown linearity lot scanned Problem The scanned linearity lot is not available on this instrument. Solution Add the lot to the instrument database on the instrument using Settings > Lot management.
Error messages 251 CA-0060: Manual test strip removal Problem The user removed the test strip manually without using the eject button on the user interface. This can damage the instrument and must be avoided. Solution Never pull out the test strip manually. Always us the eject button to remove the test strip. Related L1 message D-AO u About level 1 messages and level 2 errors (209) CA-0061: Insufficient user rights Problem The user doesn't have the privileges to perform the requested action (e.g.
252 Level 2 errors Another user with the user role "Observer" (OTS_OBSERVER) needs to log on during the observed test sequence. Related L1 message U-AD u About level 1 messages and level 2 errors (209) CA-0063: QC / linearity lot rejected Problem The user tried to add a QC or linearity lot of which the target ranges are not known to the instrument. Solution Ensure that the instrument receives the updated target ranges either via barcode scanning or via DMS before you add this QC or linearity lot.
Error messages Related L1 message 253 G-AA u About level 1 messages and level 2 errors (209) CA-0067: Wi-Fi networks not deleted completely Problem The instrument could not delete all stored Wi-Fi networks after the user tapped the Delete instrument data button. Solution Restart the instrument and trigger the deletion of all instrument data in the GUI again.
254 Level 2 errors u About level 1 messages and level 2 errors (209) CA-0071: Invalid database encryption key Problem The instrument detected corrupted data in its database and has reset the database to the default settings. Solution Ensure that the instrument is connected to the network and the DMS and that the instrument synchronizes the configuration, patient, user, and lot data.
Error messages 255 CA-0074: Result database full Problem One of the result database tables is full and the instrument is not able to store additional results. No further tests can be performed. Solution Ensure that the instrument is connected to the network and the DMS and that the instrument synchronizes the configuration, patient, user, and lot data.
256 Level 2 errors u About level 1 messages and level 2 errors (209) CA-0078: TLS communication warning Problem The TLS (Transport Layer Security) handshake between the DMS and the instrument failed. The instrument still transmits results and receives updated data from the DMS. Possible reasons: Solution • Configuration issue (e.g., the configured certificate of the DMS (stored in the DMS TLS certificate) has expired. • Cybersecurity issue (e.g., man-in-the-middle attack).
Error messages Related L1 message 257 G-AA u About level 1 messages and level 2 errors (209) CA-0080: Entry does not exist anymore Problem The user tried to access a database entry or result which has been deleted either by the instrument deletion algorithm or by the DMS. Solution No action needed.
258 Level 2 errors u About level 1 messages and level 2 errors (209) CA-0083: Invalid user ID Problem The user read a user ID via barcode that does not comply to the configured patterns for the user ID. The scanned ID is invalid. Solution Check if the ID complies with the intended ID patterns (length, structure, allowed values). Adapt the configured ID patterns (via the DMS or by using the Configuration by barcode option) so that the scanned barcode will be accepted by the instrument.
Error messages Solution 259 Check if the ID complies with the intended ID patterns (length, structure, allowed values). Adapt the configured ID patterns (via the DMS or by using the Configuration by barcode option) so that the scanned barcode will be accepted by the instrument. Related L1 message T-AA u About level 1 messages and level 2 errors (209) CA-0086: Invalid user ID Problem The user read an ID via RFID tag that does not comply with the maximum length allowed for the user ID.
260 Level 2 errors u About level 1 messages and level 2 errors (209) CA-0088: Invalid patient ID Problem The user read a user ID via barcode that does not comply with the maximum length allowed for the user ID. The scanned ID is invalid. Solution Check if the user ID violates the maximum length allowed of 20 characters. Reduce the ID length to maximum 20 characters.
Error messages Solution 261 Check if the user ID violates the maximum length allowed of 20 characters. Reduce the ID length to maximum 20 characters. Related L1 message T-AA u About level 1 messages and level 2 errors (209) CA-0091: Invalid QC material barcode Problem The scanned QC material barcode is invalid (e.g., incorrect format). Solution Ensure that you scan a QC material barcode intended for use with the cobas pulse instrument.
262 Level 2 errors Solution Related L1 message Check the configuration settings in cobas® infinity edge. B-AA u About level 1 messages and level 2 errors (209) CA-0094: Invalid configuration barcode Problem Changing of the result unit in your country is not allowed. No configuration change was applied. Solution Ensure that the configuration barcode does change the result unit.
Error messages Related L1 message 263 B-AD u About level 1 messages and level 2 errors (209) CA-0097: Invalid configuration barcode Problem The configuration barcode scanned is invalid. Solution Check the configuration settings in cobas® infinity edge and try again with a newly generated barcode. Related L1 message B-AD u About level 1 messages and level 2 errors (209) CA-0098: Invalid configuration barcode Problem The configuration barcode scanned is invalid.
264 Level 2 errors CA-0101: Invalid configuration barcode Problem The configuration barcode scanned is invalid. Solution Check the configuration settings in cobas® infinity edge and try again with a newly generated barcode. Related L1 message B-AD u About level 1 messages and level 2 errors (209) CA-0102: Invalid configuration barcode Problem The configuration barcode scanned is invalid.
Error messages Solution Related L1 message 265 Check the configuration settings in cobas® infinity edge and try again with a newly generated barcode. B-AD u About level 1 messages and level 2 errors (209) CA-0105: Data integrity test failed Problem The instrument detected corrupted data in its database and has reset the database to the default settings.
266 Level 2 errors Solution Ensure that the instrument is connected to the network and the DMS and that the instrument synchronizes the configuration, patient, user, and lot data.
Error messages Solution 267 Delete all lots that are no longer needed from the instrument database (either directly on the instrument or via the DMS). Once an old lot is deleted, a new lot can be added to the instrument database. Related L1 message G-AE u About level 1 messages and level 2 errors (209) CA-0111: Database limit reached for linearity lots Problem The database table capacity limit has been reached and no additional lots can be saved.
268 Level 2 errors CA-0114: Password too long Problem The password entered is longer than the allowed 20 characters. Solution Enter a password which has the same or more characters than the configured minimal password length value, but not more than 20 characters.
Error messages Related L1 message 269 U-AD u About level 1 messages and level 2 errors (209) CA-0117: Invalid barcode content Problem During a shared workflow step, the user scanned a barcode with invalid content. Solution Ensure that the barcode scanned is valid, and that its content does not violate any validation rules.
270 Level 2 errors Related L1 message U-AK u About level 1 messages and level 2 errors (209) CA-0120: Invalid test strip container barcode Problem The test strip container barcode scanned is invalid (e.g., incorrect format). Solution Ensure that you scan a strip container barcode intended for use with the cobas pulse instrument. Related L1 message B-AA u About level 1 messages and level 2 errors (209) CA-0121: Linearity lot expired Problem Linearity lot has expired.
Error messages 271 CA-0123: DMS host cannot be reached Problem The instrument was not able to connect to the DMS server socket. Solution Ensure that the instrument is connected to the network and the DMS server can be reached (and not blocked by a firewall). Check the connectivity and availability of the DMS using the Network status test option.
272 Level 2 errors CA-0125: Instrument client certificate check failed Problem The DMS server was not able to validate the TLS client certificate of the instrument. Solution Ensure that the DMS server has the correct TLS certificate chain installed to be able to validate the instrument TLS (client) certificate. Ensure that the instrument and the DMS server have a valid current date and time. Check the connection between the instrument and the DMS using the Network status test option.
Error messages Solution 273 Ensure that the instrument is connected to the network and that the cobas® infinity edge server can be reached (and not blocked by a firewall). Check the connectivity and availability of the cobas® infinity edge server using the Network status test option.
274 Level 2 errors If the problem persists, contact your Roche representative. Related L1 message I-AH u About level 1 messages and level 2 errors (209) CA-0130: Instrument client certificate check failed Problem The cobas® infinity edge server was not able to validate the TLS client certificate of the instrument. Solution Ensure that the instrument and the cobas® infinity edge server have a valid current date and time.
Error messages Related L1 message 275 I-AH u About level 1 messages and level 2 errors (209) CA-0132: cobas® infinity edge execution timeout Problem An acknowledgement was received which exceeds the execution acknowledgment timeout. Solution Check the connection between the instrument and the cobas® infinity edge server using the Network status test option. If the problem persists, contact your Roche representative.
276 Level 2 errors Solution Check the connection between the instrument and the cobas® infinity edge server using the Network status test option. If the problem persists, contact your Roche representative. Related L1 message I-AH u About level 1 messages and level 2 errors (209) CA-0135: Service log data upload failed Problem An error occurred while uploading service log data to cobas® infinity edge.
Error messages 277 CA-0137: Generic cobas® infinity edge connection error Problem A generic cobas® infinity edge connection error occurred. Solution Ensure that the instrument is connected to the network and to cobas® infinity edge. Check the connectivity and availability of the cobas® infinity edge using the Network status test option.
278 Level 2 errors MS-0008: SW update error (280) MS-0010: Measuring unit error (280) MS-0011: Measuring unit error (280) MS-0012: Measuring unit error (281) MS-0013: SW update error (281) MS-0015: Forced measuring unit shutdown (281) MS-0016: Measuring unit error (282) MS-0017: Measuring unit error (282) MS-0018: Measuring unit error (282) MS-0019: SW update error (282) MS-0020: Test strip ejection error (283) MS-0021: Measuring unit error (283) MS-0022: SW update error (283) MS-0023: Measuring unit erro
Error messages Solution Related L1 message 279 Restart the instrument and try again. G-AA u About level 1 messages and level 2 errors (209) MS-0004: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MS-0005: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again.
280 Level 2 errors MS-0007: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MS-0008: SW update error Problem Software update was not completed successfully. Solution Trigger the software update process again via cobas® infinity edge.
Error messages Related L1 message 281 G-AA u About level 1 messages and level 2 errors (209) MS-0012: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MS-0013: SW update error Problem Software update was not completed successfully. Solution Trigger the software update process again via cobas® infinity edge.
282 Level 2 errors MS-0016: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MS-0017: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MS-0018: Measuring unit error Problem A measuring unit error occurred.
Error messages Related L1 message 283 I-AC u About level 1 messages and level 2 errors (209) MS-0020: Test strip ejection error Problem The measuring unit failed to eject the test strip. Solution Eject the test strip using the eject button. If the problems persists, remove the test strip manually. Related L1 message H-AG u About level 1 messages and level 2 errors (209) MS-0021: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again.
284 Level 2 errors MS-0023: Measuring unit error Problem The measuring unit detected an error during measurement. Solution Repeat the test with a new test strip. Related L1 message G-AC u About level 1 messages and level 2 errors (209) MS-0024: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again.
Error messages Related L1 message 285 G-AA u About level 1 messages and level 2 errors (209) MS-0027: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MS-0028: Strip insertion period timed out Problem The user did not insert the test strip within the permitted time period. Solution Repeat the test with a new test strip and apply sufficient sample when requested.
286 Level 2 errors MS-0030: Unexpected system shutdown Problem A measuring unit error occurred. Solution The instrument can be used without any restrictions. If the problem occurs on a regular basis, contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MS-0032: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again.
Error messages Solution 287 Trigger a software update process again via cobas® infinity edge. If the problem persists, contact your Roche representative.
288 Level 2 errors MU-0149: Measuring unit error (300) MU-0150: Measuring unit error (300) MU-0151: Measuring unit error (301) MU-0152: Measuring unit error (301) MU-0153: Measuring unit error (301) MS-0156: Temperature too low (301) MU-0157: Temperature too high (302) MU-0158: Measuring unit error (302) MU-0159: Measuring unit error (302) MU-0160: Measuring unit error (303) MU-0161: Measuring unit error (303) MU-0162: Measuring unit error (303) MU-0163: Measuring unit error (304) MU-0165: Measuring unit
Error messages 289 MU-0251: Measuring unit error (312) MU-0252: Measuring unit error (313) MU-0253: Measuring unit error (313) MU-0254: Measuring unit error (313) MU-0256: Measuring unit error (314) MU-0257: Measuring unit error (314) MU-0258: Measuring unit error (314) MU-0259: Measuring unit error (314) MU-0260: Measuring unit error (315) MU-0261: Measuring unit error (315) MU-0262: Measuring unit error (315) MU-0263: Measuring unit error (316) MU-0267: Measuring unit error (316) MU-0273: Measuring unit
290 Level 2 errors MU-0409: Measuring unit error (324) MU-0410: Measuring unit error (325) MU-0412: Measuring unit error (325) MU-0413: Measuring unit error (325) MU-0416: Measuring unit error (326) MU-0419: Measuring unit error (326) MU-0420: Measuring unit error (326) MU-0421: Measuring unit error (327) MU-0423: Measuring unit error (327) MU-0424: Measuring unit error (327) MU-0425: Measuring unit error (328) MU-0426: Measuring unit error (328) MU-0427: Measuring unit error (328) MU-0428: Measuring unit
Error messages 291 MU-0563: Measuring unit fail-safe activated (337) MU-0564: Test strip fail-safe activated (338) MU-0567: Measuring unit fail-safe activated (338) MU-0901: Measuring unit error (338) MU-0905: Test strip contact error (339) MU-0906: Test strip contact error (339) MU-0910: Measuring unit error (339) MU-0930: Sample application error (340) MU-0940: Sample application error (340) MU-0941: Sample application error (340) MU-0945: Sample application error (341) MU-0947: Sample application error
292 Level 2 errors If the problem persists, contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0091: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0092: Measuring unit error Problem A measuring unit error occurred.
Error messages 293 If the problem persists, contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0095: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0096: Measuring unit error Problem A measuring unit error occurred.
294 Level 2 errors If the problem persists, contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0098: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0120: Measuring unit error Problem A measuring unit error occurred.
Error messages Related L1 message 295 G-AA u About level 1 messages and level 2 errors (209) MU-0131: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0132: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again.
296 Level 2 errors Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0134: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0135: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again.
Error messages Related L1 message 297 G-AA u About level 1 messages and level 2 errors (209) MU-0137: Measuring unit error Problem A measuring unit error occurred. Solution Contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0138: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative.
298 Level 2 errors MU-0140: Measuring unit error Problem A measuring unit error occurred. Solution Trigger a software update via cobas® infinity edge. If the problem persists, contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0141: Measuring unit error Problem A measuring unit error occurred. Solution Trigger a software update via cobas® infinity edge. If the problem persists, contact your Roche representative.
Error messages 299 MU-0143: Measuring unit error Problem A measuring unit error occurred. Solution Trigger a software update via cobas® infinity edge. If the problem persists, contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0145: Measuring unit error Problem A measuring unit error occurred. Solution Trigger a software update via cobas® infinity edge. If the problem persists, contact your Roche representative.
300 Level 2 errors Solution Related L1 message Contact your Roche representative. G-AA u About level 1 messages and level 2 errors (209) MU-0148: Measuring unit error Problem A measuring unit error occurred. Solution Contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0149: Measuring unit error Problem A measuring unit error occurred. Solution Contact your Roche representative.
Error messages 301 MU-0151: Measuring unit error Problem A measuring unit error occurred. Solution Contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0152: Measuring unit error Problem A measuring unit error occurred. Solution Contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0153: Measuring unit error Problem A measuring unit error occurred.
302 Level 2 errors Solution Related L1 message Use the instrument at a higher temperature. The temperature lockout will be deactivated as soon as the instrument detects a supported instrument temperature. E-AA u About level 1 messages and level 2 errors (209) MU-0157: Temperature too high Problem The instrument has detected that the instrument temperature is too high for testing and has activated the temperature lockout. Solution Use the instrument at a lower temperature.
Error messages Solution Related L1 message 303 The instrument can be used without any restrictions.If the problem occurs on a regular basis, contact your Roche representative. G-AC u About level 1 messages and level 2 errors (209) MU-0160: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative.
304 Level 2 errors If the problem persists, contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0163: Measuring unit error Problem A measuring unit error occurred. Solution Contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0165: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again.
Error messages Related L1 message 305 G-AA u About level 1 messages and level 2 errors (209) MU-0168: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0169: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again.
306 Level 2 errors Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0171: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0172: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again.
Error messages Related L1 message 307 E-AB u About level 1 messages and level 2 errors (209) MU-0174: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative.
308 Level 2 errors Related L1 message D-AF u About level 1 messages and level 2 errors (209) MU-0178: Ascorbic-acid fail-safe activated Problem The measuring unit detected high ascorbic-acid concentration in the sample. The test failed. Solution Repeat the test with a new test strip. Follow proper usage in the handling recommendations. If this problem persists while testing other patients, contact your Roche representative.
Error messages Related L1 message 309 G-AA u About level 1 messages and level 2 errors (209) MU-0182: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative. Related L1 message G_AA u About level 1 messages and level 2 errors (209) MU-0183: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again.
310 Level 2 errors Related L1 message H-AG u About level 1 messages and level 2 errors (209) MU-0232: Test strip ejection error Problem An error with the strip ejection mechanism occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0241: Test strip ejection error Problem An error with the strip ejection mechanism occurred.
Error messages 311 MU-0243: Measuring unit error Problem A measuring unit error occurred. Solution Contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0245: Measuring unit error Problem A measuring unit error occurred. Solution Contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0246: Measuring unit error Problem A measuring unit error occurred.
312 Level 2 errors Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0249: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0250: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again.
Error messages Related L1 message 313 G-AA u About level 1 messages and level 2 errors (209) MU-0252: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0253: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again.
314 Level 2 errors Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0256: Measuring unit error Problem A measuring unit error occurred. Solution Contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0257: Measuring unit error Problem A measuring unit error occurred. Solution Contact your Roche representative.
Error messages Solution Related L1 message 315 Contact your Roche representative. G-AA u About level 1 messages and level 2 errors (209) MU-0260: Measuring unit error Problem A measuring unit error occurred. Solution Contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0261: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again.
316 Level 2 errors Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0263: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0267: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again.
Error messages Related L1 message 317 G-AA u About level 1 messages and level 2 errors (209) MU-0320: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0321: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again.
318 Level 2 errors Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0324: Measuring unit error Problem A measuring unit error occurred. Solution Contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0325: Measuring unit error Problem A measuring unit error occurred. Solution Contact your Roche representative.
Error messages Solution 319 Restart the instrument and try again. If the problem persists, contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0328: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative.
320 Level 2 errors Solution Restart the instrument and try again. If the problem persists, contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0341: Test strip ID decoding error Problem The instrument could not read the test strip ID (e.g. due to dirt or scratches). Solution Eject the test strip and insert a new test strip. If the problem persists, contact your Roche representative.
Error messages Related L1 message 321 D-AG u About level 1 messages and level 2 errors (209) MU-0345: Test strip inserted upside down Problem The measuring unit detected that the test strip was inserted upside down. Solution Eject the test strip and insert it correctly. Related L1 message D-AG u About level 1 messages and level 2 errors (209) MU-0346: Measuring unit error Problem A measuring unit error occurred. Solution Contact your Roche representative.
322 Level 2 errors MU-0348: Measuring unit error Problem A measuring unit error occurred. Solution Contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0350: Measuring unit error Problem A measuring unit error occurred. Solution Contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0351: Measuring unit error Problem A measuring unit error occurred.
Error messages 323 u About level 1 messages and level 2 errors (209) MU-0402: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0403: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative.
324 Level 2 errors MU-0406: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0407: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative.
Error messages 325 MU-0410: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0412: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative.
326 Level 2 errors MU-0416: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0419: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative.
Error messages 327 MU-0421: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0423: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative.
328 Level 2 errors MU-0425: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0426: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative.
Error messages 329 MU-0428: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0429: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative.
330 Level 2 errors MU-0431: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0432: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative.
Error messages 331 MU-0502: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0503: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative.
332 Level 2 errors MU-0506: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0512: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative.
Error messages 333 MU-0514: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0515: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative.
334 Level 2 errors MU-0523: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0524: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative.
Error messages 335 MU-0526: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0527: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative.
336 Level 2 errors MU-0529: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative. Related L1 message G-AA u About level 1 messages and level 2 errors (209) MU-0541: Measuring unit error Problem A measuring unit error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative.
Error messages 337 MU-0561: Measuring unit fail-safe activated Problem The measuring unit triggered a fail-safe logic for the applied sample. The test failed. Solution Repeat the test with a new test strip. Follow proper usage in the handling recommendations. Related L1 message S-AF u About level 1 messages and level 2 errors (209) MU-0562: Measuring unit fail-safe activated Problem The measuring unit triggered a fail-safe logic for the applied sample. The test failed.
338 Level 2 errors MU-0564: Test strip fail-safe activated Problem The measuring unit triggered a fail-safe related to external environmental conditions for the inserted test strip. The test failed. Solution Repeat the test with a new test strip. Follow proper usage in the handling recommendations. Related L1 message D-AF u About level 1 messages and level 2 errors (209) MU-0567: Measuring unit fail-safe activated Problem The measuring unit triggered a fail-safe logic for the applied sample.
Error messages 339 MU-0905: Test strip contact error Problem A test strip contact error occurred. Solution Repeat the test with a new test strip. If this problem persists, contact your Roche representative. Related L1 message D-AA u About level 1 messages and level 2 errors (209) MU-0906: Test strip contact error Problem A test strip contact error occurred. Solution Repeat the test with a new test strip. If this problem persists, contact your Roche representative.
340 Level 2 errors MU-0930: Sample application error Problem The sample was applied to early. Solution Repeat the test with a new test strip.Apply sufficient sample when requested without moving the test strip. If this problem persists, contact your Roche representative. Related L1 message S-AB u About level 1 messages and level 2 errors (209) MU-0940: Sample application error Problem The instrument could not detect a sample application within the given timeout.
Error messages 341 MU-0945: Sample application error Problem The instrument detected an unsteady sample application, or the test strip was moved during sample application or sample detection. Solution Repeat the test with a new test strip. Apply sufficient sample when requested without moving the test strip. If this problem persists, contact your Roche representative.
342 Level 2 errors Apply sufficient sample when requested without moving the test strip. If this problem persists, contact your Roche representative. Related L1 message S-AB u About level 1 messages and level 2 errors (209) MU-0952: Sample application error Problem The instrument detected an unsteady sample application, or the test strip was moved during sample application or sample detection. Solution Repeat the test with a new test strip.
Error messages Solution 343 Repeat the test with a strip from another container. If this does not solve the issue, repeat the test with another strip and another instrument. Related L1 message D-AF u About level 1 messages and level 2 errors (209) MU-0962: Test strip error Problem A test strip error occurred. Solution Repeat the test with a new test strip. If this problem persists while testing other patients, contact your Roche representative.
344 Level 2 errors If this problem persists while testing other patients, contact your Roche representative. Related L1 message G-AC u About level 1 messages and level 2 errors (209) MU-0972: Signal range violation Problem The measuring unit detected a signal range violation. Solution Repeat the test with a new test strip. If this problem persists while testing other patients, contact your Roche representative.
Error messages 345 If this problem persists while testing other patients, contact your Roche representative. Related L1 message G-AC u About level 1 messages and level 2 errors (209) MU-0975: Signal range violation Problem The measuring unit detected a signal range violation. Solution Repeat the test with a new test strip. If this problem persists while testing other patients, contact your Roche representative.
346 Level 2 errors If this problem persists while testing other patients, contact your Roche representative. Related L1 message G-AC u About level 1 messages and level 2 errors (209) MU-0979: Removal of test strip during test Problem The measuring unit detected a signal range violation. Solution The test strip was removed during the test. Repeat the test with a new test strip. Do not remove test strip during processing.
Error messages 347 If this problem persists while testing other patients, contact your Roche representative. Related L1 message G-AC u About level 1 messages and level 2 errors (209) MU-0982: Signal range violation Problem The measuring unit detected a signal range violation. Solution Repeat the test with a new test strip. If this problem persists while testing other patients, contact your Roche representative.
348 Level 2 errors If this problem persists while testing other patients, contact your Roche representative. Related L1 message G-AC u About level 1 messages and level 2 errors (209) MU-0987: Test strip insertion error Problem The test strip was inserted too early. Solution Eject the test strip and insert it again when requested.
Error messages 349 US-0022: Software update already in process (355) US-0023: Software update package download failed (356) US-0024: Software update error (356) US-0025: Software update error (356) US-0026: Software update error (357) US-0027: Software update error (357) US-0028: Incompatible software update container (358) US-0001: Unknown error Problem An unknown error occurred. Solution Restart the instrument and try again. If the problem persists, contact your Roche representative.
350 Level 2 errors US-0003: Invalid software update package Problem The meta-data of the software update package is invalid (e.g., malformed or incomplete). Solution Contact your Roche representative. Related L1 message I-AF u About level 1 messages and level 2 errors (209) US-0004: Measuring unit firmware update error Problem The measuring unit firmware update could not be started. Solution Restart the instrument.
Error messages Related L1 message 351 I-AC u About level 1 messages and level 2 errors (209) US-0007: SW update error Problem A software update error occurred. Solution Contact your Roche representative. Related L1 message I-AC u About level 1 messages and level 2 errors (209) US-0008: Error during shutdown Problem The instrument could not shut down the operating system as part of the software update process.
352 Level 2 errors US-0010: Measuring unit error Problem A measuring unit software update error occurred. Solution Restart the instrument. Ensure that the instrument is connected to the network using the Network status test option, and that the connection is stable. Restart the software update via cobas® infinity edge. Related L1 message G-AA u About level 1 messages and level 2 errors (209) US-0011: Measuring unit error Problem A measuring unit software update error occurred.
Error messages 353 u About level 1 messages and level 2 errors (209) US-0013: Software update failed Problem An error occurred during a planned restart of the instrument during a software update. The software update failed. Solution Restart the instrument. Ensure that the instrument is connected to the network using the Network status test option, and that the connection is stable. Restart the software update via cobas® infinity edge.
354 Level 2 errors Solution Related L1 message Ensure that the instrument is connected to the network using the Network status test option, and that the connection is stable. Restart the software update via cobas® infinity edge. I-AC u About level 1 messages and level 2 errors (209) US-0017: Measuring unit software update error Problem The low-level measuring unit firmware update failed. Solution Contact your Roche representative.
Error messages Related L1 message 355 I-AC u About level 1 messages and level 2 errors (209) US-0020: Component compatibility check failed Problem The software update package was rejected by the instrument because the compatibility check failed. Solution Check the available software update packages and ensure that a compatible software update package is available.
356 Level 2 errors US-0023: Software update package download failed Problem One or multiple parts of the software update package could not be retrieved. The connection to cobas® infinity edge was interrupted. Solution Ensure that the instrument is connected to the network. Check the connection between the instrument and cobas® infinity edge using the Network status test option.
Error messages 357 US-0026: Software update error Problem The uninstall of an essential instrument app was prevented. Solution Check the available software update packages and ensure that a compatible instrument software update package is available.Turn off and restart the instrument. Ensure that the instrument is connected to the network using the Network status test option and that the connection is stable. Restart the software update via cobas® infinity edge.
358 Level 2 errors US-0028: Incompatible software update container Problem The instrument detected an incompatible software update container and consequently did not start the software update process. Solution Check the available software update packages and ensure that a compatible software update package is available. Related L1 message I-AF 9 Error messages u About level 1 messages and level 2 errors (209) Roche Diagnostics cobas® pulse · Software version 01.
Configuration 10 Initial configuration..................................................................................... 361 11 General configuration................................................................................ 421 Roche Diagnostics cobas® pulse · Software version 01.03 · User Assistance · Publication version 1.
Page intentionally left blank. Roche Diagnostics cobas® pulse · Software version 01.03 · User Assistance · Publication version 1.
Table of contents 361 Initial configuration 10 About instrument configuration ....................................... 365 About the Settings menu access restrictions.............. 367 Setting the instrument date and time ............................ 368 Configuring by barcode....................................................... 370 Formats and language configuration ............................. 371 Date format ...................................................................
10 Initial configuration 362 Table of contents Minimum barcode scanning time......................... 388 Checksum validation of barcode type "Interleaved 2 of 5" ..................................................... 388 Connectivity.............................................................................. 390 Synchronization warning / lockout ...................... 390 Show synchronization lockout warning prior to actual lockout (in hours)...............
Table of contents 411 Wi-Fi cryptographic algorithm type .......... 412 List of Wi-Fi security configurations......... 412 TLS security................................................................... 414 DMS TLS certificate check........................... 414 cobas infinity edge TLS certificate check .................................................................... 415 DMS TLS level................................................... 416 DMS TLS certificate ..............................
364 Table of contents 10 Initial configuration Page intentionally left blank. Roche Diagnostics cobas® pulse · Software version 01.03 · User Assistance · Publication version 1.
Initial configuration 365 About instrument configuration You can perform a basic initial installation on the instrument manually, or by using a barcode. i Glucose Language Manual installation Installation by barcode For more detailed information, refer to the cobas pulse Connectivity guide. Depending on the systems to which the instrument is connected (DMS, cobas® infinity edge), further configuration will be made by the corresponding systems.
366 About instrument configuration Manual installation • Choose the date format using the Date format option (for example, dd-MMM-yyyy), and enter the current date. • Choose the time format using the Time format option (for example, 12 hour (am/pm)), and enter the current time. • Choose the Test strip lot option, scan a barcode containing the test strip lot data. The barcode is generated in cobas® infinity edge. It is not the barcode on the test strip container.
Initial configuration 367 About the Settings menu access restrictions The instrument can be configured to restrict access to certain options in the Settings menu. The following options enable restricted access configuration: • Date and time • Configuration by barcode • Lot management • Administrator The instrument can be configured to access the options by one of the following methods.
368 Setting the instrument date and time Setting the instrument date and time You use the date and time screens to set the instrument date and time. The date and time formats used by an instrument are determined by its configuration. j m You are logged onto the instrument u Logging on to the Glucose app (99) r To set the instrument date and time 1 Choose > Date and time. I Depending on your instrument configuration, this option may be password protected.
Initial configuration 369 5 To set the instrument time, on the Date and time screen tap the Set time option. Date and time 6 To set the time use one of the following methods: • Time picker • Type in time Set date 19-Nov-2021 Set time 11:06 AM 3:30 AM PM 7 To use the time picker, do the following: • Drag the clock hand to the desired hour. • Drag the clock hand to the desired minutes. • If the instrument uses the 12 hour clock format, tap AM or PM. • Tap the Confirm button. f The new time is set.
370 Configuring by barcode Configuring by barcode You can configure an instrument by scanning a barcode. The Configuration by barcode option can be used to do the following: • Initial instrument configuration • Subsequent instrument configuration After a subsequent configuration, the change takes effect the next time that you log onto the Glucose app c As required r To configure by barcode 1 Tap > Configuration by barcode.
Initial configuration 371 Formats and language configuration In this section Date format (371) Time format (372) Language and region (372) Regulatory region (374) Date format This configuration item specifies the date format that is used on the instrument. When an instrument is started for the first time and a manual installation is performed, you are prompted to select the date format using the user interface. Thereafter you cannot change the date format using the user interface.
372 Formats and language configuration Time format This configuration item specifies the time format that is used on the instrument. When an instrument is started for the first time and a manual installation is performed, you are prompted to select the time format using the user interface. Thereafter you cannot change of the time format using the user interface.
Initial configuration Item ID Available values/format • zh-CN corresponds to simplified Chinese. • zh-TW corresponds to traditional Chinese 373 INSTRUMENT_LOCALE The table contains valid combinations(3) of a language tag and region/country tag for the Language and region configuration item. Only one of the listed region/country tags can be combined with a given language tag (e.g.
374 Formats and language configuration Language tag Region/country tag th TH ru BY, KG, KZ, MD, RU, UA he IL el CY, GR tr CY, TR zh CN (for simplified Chinese), TW (for traditional Chinese) y Valid and combinations Default value: en-US Configuration You configure the Language and region configuration item using the following: • Data management system (e.g.
Initial configuration Configuration • The QC algorithm configuration item value is set to Time interval and changing it to Disabled is prevented. It is possible to change the QC algorithm configuration item to any other value than Disabled. • The Allow QC / synchronization lockout overrides configuration item value is set to Disabled and cannot be changed.
376 QC configuration QC configuration In this section QC algorithm (376) Show numeric QC result value (382) QC range handling (382) QC algorithm In this section QC algorithm (376) QC interval (in hours) (378) Shift length (in hours) (378) Shift start (379) Test strip count (380) Time of day (380) QC tests required for new test strip lots (381) QC algorithm This configuration item specifies how QC lockout is enabled on the instrument.
Initial configuration 377 QC lockout is enabled when the last QC test performed is out of range. Consequently if no successful QC test has been performed, the instrument will be in QC lockout. • Shift [SHIFT] A QC lockout is activated with each change of shift. It works in conjunction with the Shift length (in hours) and Shift start configuration items.
378 QC configuration • Time of day (380) QC interval (in hours) This configuration item specifies the time period (hours) for which a positive QC result is valid. A QC lockout is enabled after this period is exceeded. QC interval (in hours) works in conjunction with the QC algorithm configuration item. Item ID Available values/format Dependencies Configuration QC_HOURS 1-9999 hours (default: 1000 hours). Values must be integers.
Initial configuration Dependencies Configuring Shift length (in hours) is only necessary when the QC algorithm configuration item value is Shift or Shift (alternating QC level). Configuration You configure the Shift length (in hours) configuration item using the following: • Data management system (e.g.
380 QC configuration Test strip count This configuration item specifies the number of successful tests that are performed after which a QC lockout is enabled. QC tests and unsuccessful tests are not included in the calculation. Test strip count works in conjunction with the QC algorithm configuration item. Item ID Available values/format QC_STRIP_COUNT 1 - 999 (default: 50) Values must be integers.
Initial configuration • "06:00,12:00,18:00" • "02:00,06:00,10:00,14:00,18:00,22:00" 381 "06:00" (default) Dependencies Configuration Configuring Time of day is only relevant when the QC algorithm configuration item value is Time of day or Time of day (alternating QC level). You configure the Time of day configuration item using the following: • Data management system (e.g.
382 QC configuration Show numeric QC result value This configuration item specifies how a QC test result is displayed. Item ID Available values/format QC_RESULT_DISPLAY • Enabled (default) [true] The result is displayed as a "Pass" or "Fail" together with a numeric value. • Disabled [false] The result is displayed as a "Pass" or a "Fail" only. Configuration You configure the Show numeric QC result value configuration item using the following: • Data management system (e.g.
Initial configuration • The accepted maximum deviation values (for result unit mg/dL or mmol/L) are defined by Roche (see package insert of cobas® GLU QC kit). Custom deviation values which exceed the permitted deviation defined by Roche will be rejected by the instrument. • If the configuration item is empty (default) or the QC version is set to "0:0", no custom deviation is used.
384 QC configuration The custom deviation configuration depends upon the QC version. The QC version defines the target values (level 1 and level 2) of a QC kit provided by Roche. The QC version ranges from 0 to 9. The QC version of a QC kit is located in Settings > Lot management > Lot management > QC lots. The initial QC version at product launch is 0.
Initial configuration 385 Data deletion In this section Result deletion (385) Audit trail retention period (in days) (387) Result deletion In this section Result deletion algorithm (385) Result retention period (in days) (386) Result upload required before result deletion (386) Result deletion algorithm This configuration item specifies how test results are deleted from the instrument.
386 Data deletion Result retention period (in days) This configuration item specifies the length of time that test results are retained on the instrument. It determines the number of days since a result was measured before it can be automatically deleted. Deletion is triggered after the first DMS synchronization of each day. The value "0 days" means that the result is deleted when the next deletion is triggered.
Initial configuration Dependencies Configuration 387 If there is no DMS a value of Disabled must be set. You configure the Result upload required before result deletion configuration item using the following: • Data management system (e.g., cobas® infinity POC) • Barcode (generated via cobas® infinity edge) u Related topics • Result deletion algorithm (385) Audit trail retention period (in days) This configuration item specifies when audit trail entries are deleted.
388 Barcode camera configuration Barcode camera configuration In this section Minimum barcode scanning time (388) Checksum validation of barcode type "Interleaved 2 of 5" (388) Minimum barcode scanning time This configuration item specifies the minimum amount of time in milliseconds (ms), that the barcode camera preview window must focus on a barcode to ensure that it is read.
Initial configuration Available values/format • 389 Enabled (default) [true] • Disabled [false] Dependencies You configure the Checksum validation of barcode type "Interleaved 2 of 5" configuration item using the following: • Data management system (e.g., cobas® infinity POC) • Barcode (generated via cobas® infinity edge) 10 Initial configuration Configuration The configuration items Allowed barcode types for patient ID or Allowed barcode types for user ID have a value of Interleaved 2 of 5.
390 Connectivity Connectivity In this section Synchronization warning / lockout (390) DMS/cobas infinity edge connection retry timeout (in seconds) (392) DMS session timeout (in seconds) (392) DNS IPv4 address (393) DNS IPv6 address (393) Gateway IPv4 address (394) Gateway IPv6 address (395) Instrument IPv4 address (395) Instrument IPv6 address (396) IPv4 subnet mask (397) Network Time Protocol (NTP) (397) NTP server address (398) Instrument time zone (399) Data management system IP address / host name (4
Initial configuration 391 If a value of "0" is selected no warning is given. Item ID Available values/format DMS_SYNCHRONIZATION_LOCKOUT_HOURS 0-999 hours Default = "0" Configuration You configure the Show synchronization lockout warning prior to actual lockout (in hours) configuration item using the following: • Data management system (e.g.
392 Connectivity DMS/cobas infinity edge connection retry timeout (in seconds) This configuration item specifies the time, in seconds, that the instrument will try to establish a connection to the intended systems (DMS or cobas® infinity edge). Item ID Available values/format CONNECTION_TIMEOUT_IN_SECONDS 10-180 seconds (default=60) Configuration You configure the DMS/cobas infinity edge connection retry timeout (in seconds) configuration item using the following: • Data management system (e.g.
Initial configuration 393 DNS IPv4 address This configuration item specifies the DNS IPv4 address. Item ID Available values/format Dependencies Configuration DNS_IP4_ADDRESS 0.0.0.0 – 255.255.255.255 • If the Use DHCP configuration item has a value of Yes, the instrument will normally receive this value automatically (depending on the DHCP server configuration) and this configuration item can remain empty.
394 Connectivity Adherence to the supported form can be checked using the following regular expression: ((?:[A-Fa-f0-9]{1,4}:){7}[A-Fa-f0-9]{1,4})? Dependencies Configuration • If the Use DHCP configuration item has a value of Yes, the instrument will normally receive this value automatically (depending on the DHCP server configuration) and this configuration item can remain empty.
Initial configuration 395 Gateway IPv6 address This configuration item specifies the gateway IPv6 address. Item ID Available values/format GATE_IP6_ADDRESS Only the “preferred form"(5) is supported. Compressing zeros, mixed IPv6/IPv4 representations or scoped addresses are not supported. Examples: fd00:0:0:0:4533:4431:55b5:b46 is supported. fd00:0000:0000:0000:4533:4431:55b5:b46 is supported.fd00::4533:4431:55b5:b46 is not supported due to compressed zeros. fd00:0000:0000:0000:4533:4431:85.181.11.
396 Connectivity Item ID Available values/format Dependencies Configuration INSTRUMENT_IP4_ADDRESS 0.0.0.0 – 255.255.255.255 • If the Use DHCP configuration item has a value of Yes, the instrument will normally receive this value automatically (depending on the DHCP server configuration) and this configuration item can remain empty. • If the Use DHCP configuration item has a value of No, this configuration item must be set.
Initial configuration 397 Adherence to the supported form can be checked using the following regular expression: ((?:[A-Fa-f0-9]{1,4}:){7}[A-Fa-f0-9]{1,4})? Dependencies If this configuration item is set, the Instrument IPv4 address configuration item must not be used. If the Instrument IPv4 address configuration item is set, the instrument will ignore the value set in this configuration item as the operating system only allows one static IP address to be set.
398 Connectivity NTP servers can either be provided as part of the DHCP protocol, or specified via the NTP server address configuration item. Item ID Available values/format NTP_ENABLED • Enabled (default) [true] The instrument enables the NTP and prevents the time from being set by POCT1-A. • Disabled [false] The instrument deactivates the NTP. Dependencies Configuration • If the Network Time Protocol (NTP) configuration is enabled, the NTP server address is required.
Initial configuration Dependencies Configuration 399 Depending on the DHCP server capabilities, the instrument automatically receives an NTP server address. If the DHCP server does not provide an NTP server address, the NTP server address configuration item must be set to a valid value. You configure the NTP server address configuration item using the following: • Data management system (e.g.
400 Connectivity Data management system IP address / host name This configuration item specifies the DMS IP address / host name. It can either be a machine name, such as "dms.hospital.com", or a textual representation of its IP address. If a literal IP address is supplied, only the validity of the address format is checked. Item ID Available values/format DMS_Host 0-60 characters For a host specified as a literal IPv6 address, only the “preferred form” according to RFC 2373 (paragraph 2.2 1.
Initial configuration Configuration 401 You configure the Data management system IP address / host name configuration item using the following: • Data management system (e.g., cobas® infinity POC) • Barcode (generated via cobas® infinity edge) Data management system port number This configuration item specifies the DMS port number.
402 Connectivity Available values/format 0-60 characters For a host specified in literal IPv6 address, only the “preferred form” according to RFC 2373 (paragraph 2.2 1.) is supported. Compressing zeros, mixed IPv6/IPv4 representations or scoped addresses are not allowed. Examples: Dependencies • fd00:0:0:0:4533:4431:55b5:b46 is supported. • fd00:0000:0000:0000:4533:4431:55b5:b46 is supported. • fd00::4533:4431:55b5:b46 is not supported due to compressed zeros. • fd00:0000:0000:0000:4533:4431:85.
Initial configuration Dependencies 403 cobas® infinity edge only: The cobas infinity edge port number configuration item is shown. If the instrument will only be connected to cobas® infinity edge, the cobas infinity edge port number and cobas infinity edge IP address / host name configuration items must be set. cobas® infinity edge and DMS: The cobas infinity edge port number configuration item must be set by the DMS.
404 Connectivity Wi-Fi SSID This configuration item specifies the Service Set Identifier (SSID) of the Wi-Fi network. Item ID Available values/format Dependencies SSID_WLAN_1 0-32 characters Refer to the tables in "List of Wi-Fi security configurations". u List of Wi-Fi security configurations (412) Configuration You configure the Wi-Fi SSID configuration item using the following: • Data management system (e.g.
Initial configuration 405 If the DHCP is disabled, the instrument either needs to have a valid static IP configuration either as IP4 (DNS IPv4 address, Gateway IPv4 address, Instrument IPv4 address, IPv4 subnet mask), or as IP6 (DNS IPv6 address, Gateway IPv6 address, Instrument IPv6 address). Configuration You configure the Use DHCP configuration item using the following: • Data management system (e.g.
406 Connectivity Anonymous User This configuration item specifies the EAP anonymous user. Item ID Available values/format Dependencies EAP_ANONYMOUS_IDENTITY_WLAN_1 0-64 characters Refer to the tables in "List of Wi-Fi security configurations". u List of Wi-Fi security configurations (412) Configuration You configure the Anonymous User configuration item using the following: • Data management system (e.g.
Initial configuration 407 Client Certificate This configuration item specifies the EAP client certificate. Supported formats are "PEM" and "DER". The file must be stored as a Base64 encoded string. "PEM" can contain both the certificate and private key. However, the private key will be ignored if stored in this configuration item.
408 Connectivity Password This configuration item specifies the EAP password. Item ID Available values/format Dependencies EAP_PASSWORD_WLAN_1 0-64 characters Refer to the tables in "List of Wi-Fi security configurations". u List of Wi-Fi security configurations (412) Configuration You configure the Password configuration item using the following: • Data management system (e.g.
Initial configuration 409 Supported formats are "PEM" and "PKCS#12". The file must be stored as a Base64 encoded string. "PEM" and "PKCS#12" can contain both the certificate and private key. If the private key is protected by a password (mandatory for "PKCS#12", optional for "PEM") this password must be stored in the Client private key password configuration item. Bundled certificates in the "PKCS#12* or "PEM" are ignored.
410 Connectivity Wi-Fi security type This configuration item specifies the Wi-Fi security type. "EAP " is not supported for barcode configuration. The necessary certificates cannot be set by barcode due to size constraints. CAUTION! Wi-Fi security To avoid an unsecure Wi-Fi r Do not use open Wi-Fi.
Initial configuration 411 u List of Wi-Fi security configurations (412) Configuration You configure the Wi-Fi key type configuration item using the following: • Data management system (e.g., cobas® infinity POC) • Barcode (generated via cobas® infinity edge) Wi-Fi encryption key This configuration item specifies the Wi-Fi encryption key.
412 Connectivity • Barcode (generated via cobas® infinity edge) Wi-Fi cryptographic algorithm type This configuration item specifies the Wi-Fi cryptographic algorithm type. Item ID Available values/format Dependencies CIPHER_TYPE_WLAN_1 • None (default) [NONE] • AES [AES] • TKIP [TKIP] • AES+TKIP [AES_TKIP] Refer to the tables in "List of Wi-Fi security configurations".
Initial configuration Wi-Fi SSID Wi-Fi security type Wi-Fi cryptographic algorithm type Wi-Fi key type Wi-Fi encryption key WPA-PSK AES+TKIP Passphrase 1-32 characters WPA/WPA2 Personal (key) WPA-PSK AES+TKIP Encryption key 64 Hex characters - 1-32 characters EAP AES - - - WPA Enterprise 1-32 characters (EAP) EAP TKIP - - - WPA2 Enterprise (EAP) - Wi-Fi password 1-32 characters WPA/WPA2 Personal (passphrase) 413 8-63 characters y Valid Wi-Fi security configurations Valid Wi
414 Connectivity EAP Type User Name Password Anonymous User CA Certificate Client Certificate Client private key Client private key password TLS - Optional Optional Required TTLS Required Optional Optional - PEAP Required Optional Optional - y Valid Wi-Fi EAP security configurations TLS security In this section DMS TLS certificate check (414) cobas infinity edge TLS certificate check (415) DMS TLS level (416) DMS TLS certificate (417) DMS TLS certificate password (418) cobas infinity
Initial configuration Dependencies Configuration 415 This configuration item is only relevant when the DMS TLS level is set to TLS enabled or TLS enabled (FIPS approved mode). You configure the DMS TLS certificate check configuration item using the following: • Data management system (e.g.
416 Connectivity DMS TLS level This configuration item determines the TLS security level which is used for the connection to the DMS. Depending on the capabilities of a third party DMS, this configuration item needs to be set to TLS disabled. 10 Initial configuration The instrument only accepts TLSv1.
Initial configuration • TLS enabled (FIPS approved mode) [FIPS_APPROVED_MODE] TLS used in FIPS approved mode. i Dependencies Configuration 417 The cobas pulse instrument uses a cryptographic library which offers a "FIPS approved" mode. For more information about the FIPS140-2 status of cobas pulse, contact you Roche representative.
418 Connectivity Dependencies If the DMS TLS level configuration item is set to TLS enabled or to TLS enabled (FIPS approved mode), there must be a valid certificate stored in the DMS TLS certificate configuration item. Configuration You configure the DMS TLS certificate configuration item using the following: • Data management system (e.g., cobas® infinity POC) DMS TLS certificate password This configuration item specifies the password which is necessary if the DMS TLS certificate is stored as PFX.
Initial configuration Available values/format TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SH A256 • TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 • TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 • TLS_DHE_RSA_WITH_AES_256_CCM • TLS_DHE_RSA_WITH_AES_256_CCM_8 • TLS_ECDHE_ECDSA_WITH_AES_256_CCM_8 • TLS_ECDHE_ECDSA_WITH_AES_256_CCM • TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 • TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 • TLS_ECDHE_ECDSA_WITH_AES_128_CCM • TLS_ECDHE_ECDSA_WITH_AES_128_CCM_8 • TLS_ECDHE_RSA_WITH_AES_128_
420 Connectivity 10 Initial configuration Page intentionally left blank. Roche Diagnostics cobas® pulse · Software version 01.03 · User Assistance · Publication version 1.
Table of contents 421 General configuration 11 List of power management options ................................ 425 Standby timeout .......................................................... 425 Lift to wake.................................................................... 425 Patient ID handling................................................................ 427 Patient ID entry interfaces ....................................... 427 Patient entry type.......................................
11 General configuration 422 Table of contents User ID autocomplete .................................... 446 Allowed barcode types for user ID....................... 447 Result range handling.......................................................... 448 Normal range lower limit ......................................... 448 Normal range upper limit......................................... 449 Critical range lower limit .......................................... 449 Critical range upper limit .
Allow configuration by barcode on the instrument........................................................... 468 Access restrictions to date and time........ 469 Allow access to administrator features ... 470 Allow access to lot management on the instrument........................................................... 471 Lot management ......................................................... 471 Allow linearity lot selection from list......... 471 Allow QC lot selection from list .................
424 Table of contents 11 General configuration Page intentionally left blank. Roche Diagnostics cobas® pulse · Software version 01.03 · User Assistance · Publication version 1.
General configuration 425 List of power management options In this section Standby timeout (425) Lift to wake (425) Standby timeout This configuration item specifies the time in seconds that an instrument is idle before switching to standby mode. Item ID Available values/format ACTIVITY_TURN_OFF_IN_SECONDS 30-3600 seconds (default=300) Configuration You configure the Standby timeout configuration item using the following methods: • Data management system (e.g.
List of power management options • Data management system (e.g., cobas® infinity POC) • Barcode (generated via cobas® infinity edge) 11 General configuration 426 Roche Diagnostics cobas® pulse · Software version 01.03 · User Assistance · Publication version 1.
General configuration 427 Patient ID handling In this section Patient ID entry interfaces (427) Patient ID validation (428) Patient ID confirmation dialog (434) Patient ID autocomplete (435) Allowed barcode types for patient ID (436) Patient ID entry interfaces In this section Patient entry type (427) Patient entry keyboard type (428) Patient entry type This configuration item specifies the available interfaces with which a patient ID is entered. Combinations of interfaces can be configured (e.g.
428 Patient ID handling • Minimum barcode scanning time Keyboard: • Patient entry keyboard type • Patient ID pattern validation (keyboard) RFID Configuration • Patient ID pattern validation (RFID) • Patient RFID tag record configuration You configure the Patient entry type configuration item using the following: • Data management system (e.g.
General configuration 429 In this section Patient ID validation (429) Patient ID pattern validation (keyboard) (430) Patient ID pattern validation (barcode) (431) Patient ID pattern validation (RFID) (433) Patient ID validation This configuration item specifies how a patient ID is validated when entered.
430 Patient ID handling The Patient ID validation configuration works in conjunction with the following configuration items: • Patient ID pattern validation (keyboard) • Patient ID pattern validation (barcode) • Patient ID pattern validation (RFID) These configuration items specify the pattern used to validate a patient ID entered by the corresponding methods (keyboard, barcode scan, RFID tag).
General configuration Dependencies Configuration 431 The Patient entry type configuration item must have a value of Keyboard. You configure the Patient ID pattern validation (keyboard) configuration item using the following: • Data management system (e.g.
432 Patient ID handling • Regular expressions are checked by the Glucose app for correct regex syntax only. If the stated (project specific) format "id" is not correctly used, the regex will be saved in the database, but will not result in the intended behavior. Example of regex with two groups: (?[A-Z]{3}).(?[A-Z]{3})\$ This configuration item can contain wide characters. Item ID Available values/format PATIENT_ID_PATTERN_BCS ST:0-500 (regular expression) No default value set.
General configuration 433 Input: ;Mary Miller;;X1234321;5715486266Z;01-09-1982 Regex with one group: [^\;]*\;[^\;]*\;[^\;]*\;([^\;]*)\; [^\;]*\;[^\;]* Extracted ID: "X1234321" Dependencies The Patient entry type configuration item must have a value of Barcode. Configuration You configure the Patient ID pattern validation (barcode) configuration item item using the following: • Data management system (e.g.
434 Patient ID handling Based on the group name with the index, the extracted substrings are concatenated in the business logic of the Glucose app. • Regular expressions are checked by the Glucose app for correct regex syntax only. If the stated (project specific) format "id" is not correctly used, the regex will be saved in the database, but will not result in the intended behavior. Example of regex with two groups: (?[A-Z]{3}).(?[A-Z]{3})\$ This configuration item can contain Unicode
General configuration • Age • Date of birth 435 Depending on the capabilities of the DMS and the available data, only a subset of the listed patient details might be available and displayed. Item ID Available values/format PATIENT_ID_CONFIRMATION • Enabled (default) [true] The Confirm patient dialog box is displayed. • Disabled [false] The Confirm patient dialog box is not displayed.
436 Patient ID handling Configuration You configure the Patient ID autocomplete configuration item using the following: • Data management system (e.g., cobas® infinity POC) • Barcode (generated via cobas® infinity edge) Allowed barcode types for patient ID This configuration item specifies the barcode symbologies that are valid for reading patient IDs. All barcodes with a different symbology to the ones listed below are invalid and not processed.
General configuration 437 User ID handling In this section User ID entry interfaces (437) User ID validation (439) User ID handling (444) Allowed barcode types for user ID (447) User ID entry interfaces In this section User authentication required (437) User authentication type (438) User authentication keyboard type (439) User authentication required This configuration item specifies when a user must enter their user ID and, depending on the configuration, their password to use the Glucose app.
438 User ID handling User authentication type This configuration item specifies the available interfaces with which a user ID is entered. Combinations of interfaces can be configured (e.g., "barcode and keyboard" or "keyboard and RFID"). i Item ID Available values/format When the User authentication required configuration item has no value the configuration is rejected. OPERATOR_ID_ENTRY_TYPE • Barcode (default) [BARCODE] The user ID is entered using the barcode scan.
General configuration 439 User authentication keyboard type This configuration item specifies if an alphanumeric or a numeric keyboard is used to enter the user ID. Item ID Available values/format OPERATOR_ID_ENTRY_KB • Alphanumeric keyboard (default) [ALPHANUMERIC] • User authentication keyboard type [NUMERIC] Dependencies Configuration The User authentication required configuration item has a value of Keyboard.
440 User ID handling • • User ID pattern validation (barcode) • User ID pattern validation (RFID) List-based [LIST_BASED] The user ID entered is validated in the same way as with the Pattern-based value. It is also validated against a user list that is stored on the instrument. • List-based with password [LIST_BASED_WITH_PASSWORD] The user ID entered is validated in the same way as with the Pattern-based value. It is also validated against a user and password list that is stored on the instrument.
General configuration 441 A regular expression is used to validate character/ number patterns, minimum length, and maximum length with the following: • Validate the input and use it completely as an ID. This configuration item can contain Unicode characters. Item ID OPERATOR_ID_PATTERN_KB Available values/format ST:0-500 (regular expression) No default value set. Example: Input checked for pattern and completely used as ID Regular expression: OP\d{1,5} Input: "OP123" Extracted ID: "OP123" The input
442 User ID handling • Validate the input, extract and use multiple substrings of the input as the ID in a concatenated manner. The following logic is applied during the processing of patterns: • If the pattern does not contain a group, the complete content of the barcode needs to match and is used as the corresponding ID.
General configuration 443 u Related topics • User ID validation (439) • User authentication type (438) User ID pattern validation (RFID) This configuration item specifies the expression used to validate an user ID entered using an RFID tag. A regular expression is used to validate character/ number patterns, minimum length, and maximum length with the following options: • Validate the input and use it completely as an ID. • Validate the input, extract and use one substring of the input as the ID.
444 User ID handling Item ID Available values/format OPERATOR_ID_PATTERN_RFID ST:0-500 (regular expression) No default value set. Configuration You configure the User ID pattern validation (RFID) configuration item using the following: • Data management system (e.g.
General configuration • Configuration 445 The User ID validation configuration item has a value of List-based with password. You configure the Minimum password length configuration item using the following: • Data management system (e.g., cobas® infinity POC) • Barcode (generated via cobas® infinity edge) Logon session timeout This configuration item specifies the length of time (seconds) that a user ID remains logged on after the instrument has gone into standby mode.
446 User ID handling Default = 0 days Dependencies The Show user lockout warning prior to user certificate expiration configuration item is only relevant when user lists are used (User authentication required has a value of Enabled for QC test only or Enabled). Configuration You configure the Show user lockout warning prior to user certificate expiration configuration item using the following: • Data management system (e.g.
General configuration 447 Allowed barcode types for user ID This configuration item specifies the barcode symbologies that are valid for entering user IDs. If a symbology used is not listed below, the code scanned is invalid and will not be processed.
448 Result range handling Result range handling In this section Normal range lower limit (448) Normal range upper limit (449) Critical range lower limit (449) Critical range upper limit (450) Reportable range lower limit (451) Reportable range upper limit (451) Message displayed if the result is below the reportable range (452) Custom message (below reportable range) (453) Message displayed if the result is above the reportable range (454) Custom message (above reportable range) (454) Custom message (abov
General configuration • Configuration 449 The Normal range lower limit value must be greater than or equal to the Critical range lower limit value. You configure the Normal range lower limit configuration item using the following: • Data management system (e.g., cobas® infinity POC) • Barcode (generated via cobas® infinity edge) Normal range upper limit This configuration item specifies the value of the upper limit of the normal range for glucose test results. It is expressed in mg/dL or mmol/L.
450 Result range handling Item ID Available values/format Dependencies Configuration CRITICAL_RANGE_LO_LIMIT Default values: • 10 mg/dL • 0.6 mmol/L The following dependencies must be true: • The Critical range lower limit value must be greater than or equal to the Reportable range lower limit value. • The Critical range lower limit value must be less than or equal to the Normal range lower limit value.
General configuration Configuration 451 You configure the Critical range upper limit configuration item using the following: • Data management system (e.g., cobas® infinity POC) • Barcode (generated via cobas® infinity edge) u Related topics • Message displayed if the result is above the critical range (456) Reportable range lower limit This configuration item specifies the value of the lower limit of the reportable range for glucose test results. It is expressed in mg/dL or mmol/L.
452 Result range handling The default value is set by the Glucose app based on the Result unit (glucose tests) configuration item. Item ID Available values/format Dependencies Configuration REPORTABLE_RANGE_HI_LIMIT Default values: • 600 mg/dL • 33.3 mmol/L The Reportable range upper limit value must be greater than or equal to the Critical range upper limit value. You configure the Reportable range upper limit configuration item using the following: • Data management system (e.g.
General configuration 453 The message is displayed. Configuration You configure the Message displayed if the result is below the reportable range configuration item using the following: • Data management system (e.g.
454 Result range handling Message displayed if the result is above the reportable range This configuration item determines if the "above reportable range message" is displayed when a glucose test result value is above the reportable range. The content of the custom message is entered using the Custom message (above reportable range) configuration item. If a custom message has not been configured, a built-in message is displayed when the value for this configuration item is Enabled.
General configuration • Item ID Available values/format Configuration 455 The Message displayed if the result is above the reportable range configuration item has a value of Enabled. ABOVE_REPORTABLE_RANGE_HI_MESSAGE • The message can contain a maximum of 100 alphanumeric characters. • If this configuration item is left empty a built-in message is displayed. You configure the Custom message (above reportable range) configuration item using the following: • Data management system (e.g.
456 Result range handling Custom message (below critical range) You use this configuration item to create the content of the below critical range message. The message is displayed when the following conditions are true: Item ID Available values/format Configuration • The glucose test result is less than the value set in the Critical range lower limit configuration item. • The Message displayed if the result is below the critical range configuration item has a value of Enabled.
General configuration Configuration 457 You configure the Message displayed if the result is above the critical range configuration item using the following: • Data management system (e.g.
458 Measurement workflow Measurement workflow In this section Emergency workflow (458) Test strip ejection (459) Sample type (460) Result unit (glucose tests) (460) Configure override QC (461) Comment management (462) Emergency workflow In this section Allow emergency tests (458) Default patient ID for emergency tests (459) Allow emergency tests This configuration item enables or disables the emergency workflow. When enabled, the Emergency button is accessible on the Tests screen.
General configuration • 459 Barcode (generated via cobas® infinity edge) u Related topics • Default patient ID for emergency tests (459) Default patient ID for emergency tests This configuration item specifies the ID that is used as the patient ID for emergency glucose tests. Item ID Available values/format Dependencies Configuration EMERGENCY_ID • 1-20 alphanumeric characters • "99999999" (default) The Allow emergency tests configuration item has the value Enabled.
460 Measurement workflow • Barcode (generated via cobas® infinity edge) Sample type This configuration item specifies the available sample types that can be displayed to the user when performing a glucose test. The Sample type configuration item is used to indicate the source of the blood sample. If it has no value (default), the sample type selection screen is not displayed.
General configuration Item ID Available values/format 461 RESULT_UNIT_GLUCOSE • mmol/L (default) [MMOL_PER_LITER] • mg/dL [MG_PER_DECILITER] Dependencies Configuration If the result unit has been automatically set as a result of a change of the Regulatory region configuration item, this configuration item cannot be changed. You configure the Result unit (glucose tests) configuration item using the following: • Data management system (e.g.
462 Measurement workflow Configuration You configure the Allow QC / synchronization lockout overrides configuration item using the following: • Data management system (e.g., cobas® infinity POC) • Barcode (generated via cobas® infinity edge) u Related topics • Number of lockout overrides allowed (462) Number of lockout overrides allowed This configuration item specifies the number of lockout overrides that are permitted before a QC test or synchronization must be performed.
General configuration 463 Allow user-defined comments This configuration item specifies whether or not custom comments can be made. Custom comments enable free-text comments to be added on the Comments screen. Item ID Available values/format CUSTOM_COMMENTS • Enabled (default) [true] Custom comments is enabled. • Disabled [false] Custom comments is disabled.
464 Measurement workflow Condition for required comments on patient results This configuration item specifies when comments must be added to a patient result, based on the result range into which a patient test result falls. Item ID Available values/format COMMENTS_REQUIRED_LEVEL_PATIENT_TESTING • Below/above normal range (default) [REQUIRED_IF_OUT_OF_NORMAL_RANGE] A comment is required when the patient result is above or below the normal range.
General configuration Item ID Available values/format 465 COMMENTS_REQUIRED_PATIENT_TESTING • Optional (default) [OPTIONAL] Comment entry is optional for patient tests. • Required when below or above selected range [OUT_OF_RANGE] Comment entry is mandatory when a patient test result falls outside a specified range. • Always required [REQUIRED] Comment entry is mandatory for all patient tests. • Disabled [DISABLED] Comment entry is disabled for patient tests.
466 Measurement workflow Comment entry is mandatory when a QC test fails. • Always required [REQUIRED] Comment entry is mandatory for all QC tests. • Disabled [DISABLED] Comment entry is disabled for QC tests. Dependencies Configuration The Allow comments on patient results configuration item works in conjunction with the Allow user-defined comments configuration item. You configure the Allow comments on QC results configuration item using the following: • Data management system (e.g.
General configuration 467 Generic instrument functionality In this section Access restrictions (467) Lot management (471) Instrument site, location, and name (473) RFID tag (474) Tests menu (476) Cleaning (479) Access restrictions In this section Instrument settings password (467) Allow configuration by barcode on the instrument (468) Access restrictions to date and time (469) Allow access to administrator features (470) Allow access to lot management on the instrument (471) Instrument settings password
468 Generic instrument functionality CAUTION! Password protection Protecting instrument settings using the setup password.
General configuration 469 The instrument settings password must be entered in order to access the Settings > Configuration by barcode option. • Enabled (corresponding user rights required) [VIA_OPERATOR_PRIVILEGE] Access to the Settings > Configuration by barcode option is only available to users with the required ("POCC") privilege. Configuration You configure the Allow configuration by barcode on the instrument configuration item using the following: • Data management system (e.g.
470 Generic instrument functionality If the Network Time Protocol (NTP) configuration item has a value of Enabled, the Access restrictions to date and time configuration item is automatically disabled on the instrument user interface. Configuration You configure the Access restrictions to date and time configuration item using the following: • Data management system (e.g.
General configuration 471 Allow access to lot management on the instrument This configuration item determines access to the Settings > Lot management option. Item ID Available options/values LOT_MANAGEMENT_ACCESS • Disabled [DISABLED] Access to Settings > Lot management option is disabled. Lot management is only possible using cobas® infinity edge and/or the DMS. • Enabled (no restrictions) [UNLIMITED_ACCESS] Anyone can access the Settings > Lot management option.
472 Generic instrument functionality Available options/values • Enabled (default) [true] List selection activated. A linearity lot number can be selected from a list or by barcode scan. • Disabled [false] List selection deactivated. A linearity lot number can be selected by barcode scan only. Dependencies Configuration The Allow linearity lot selection from list configuration item is only relevant when the Allow linearity tests configuration item has a value of Enabled.
General configuration 473 Instrument site, location, and name In this section Site (473) Location (473) Device name (474) Site This configuration item assigns the name of the site at which the instrument is used. It is assigned by DMS or barcode. The site name is visible at the bottom of the Glucose screen and the charging screen, above the instrument location if set. It can contain wide characters.
474 Generic instrument functionality u About the charging screen (45) Item ID Available options/values Configuration LOCATION • ST: 0-20 • No default value set. You configure the Location configuration item using the following: • Data management system (e.g., cobas® infinity POC) • Barcode (generated via cobas® infinity edge) u Related topics • Site (473) Device name This configuration item assigns the name of the instrument. It is assigned by DMS or barcode.
General configuration 475 Patient RFID tag record configuration This configuration item specifies the NDEF record number stored on the patient RFID tag. Item ID Available options/values Dependencies Configuration PATIENT_RFID_TAG_RECORD • INT: 0-99 • A value of "0" indicates that the content of the first NDEF record is used for identification. The Patient RFID tag record configuration configuration item is only relevant when the Patient entry type configuration item has a value of RFID.
476 Generic instrument functionality RFID tag configuration This configuration item specifies what is used for identification when using a RFID tag. Item ID Available options/values RFID_TAG_CONFIGURATION • Unique RFID tag ID (default) [UNIQUE_ID] The unique ID of the tag is used (between 4 bytes to up to 11 bytes). • Stored NDEF record [NDEF_RECORD] An NDEF record stored on the tag is used (the record number is configured using the User RFID tag record configuration configuration item).
General configuration Available values/format • 477 Disabled (default) [false] Patient test series disabled. • Enabled [true] Patient test series enabled. Configuration You configure the Patient test series configuration item using the following: • Data management system (e.g., cobas® infinity POC) • Barcode (generated via cobas® infinity edge) Allow linearity tests This configuration item specifies if linearity tests can be performed on the instrument.
478 Generic instrument functionality Available values/format • Enabled (default) [true] Proficiency tests can be performed. • Disabled [false] Proficiency tests cannot be performed. Configuration You configure Allow proficiency tests configuration item using the following: • Data management system (e.g., cobas® infinity POC) • Barcode (generated via cobas® infinity edge) Insulin dose entry This configuration item specifies whether or not insulin dose entries can be made on the instrument.
General configuration 479 Depending on the configuration of the configuration item, either the Glucose app or the app library is displayed at startup. Item ID Available values/format LAUNCH_APP_LIBRARY_ON_TURN_ON • Automatically start the Glucose app (default) [false] The Glucose app starts up when the instrument starts up. • Remain in app library [true] The app library is displayed when the instrument starts up.
480 Generic instrument functionality Cleaning notification after each patient test (480) Time interval for cleaning notification (in hours) This configuration item specifies the time in hours since instrument cleaning was last performed and when a cleaning notification is displayed. The notification is displayed on the Settings > Notifications screen. You confirm that the instrument has been cleaned by choosing the Confirm button on the Instrument cleaning dialog box.
General configuration 481 A cleaning notification is displayed after a patient test has been made. Configuration You configure the Cleaning notification after each patient test configuration item using the following: • Data management system (e.g., cobas® infinity POC) • Barcode (generated via cobas® infinity edge) u Related topics 11 General configuration • List of notifications (72) Roche Diagnostics cobas® pulse · Software version 01.03 · User Assistance · Publication version 1.
482 Generic instrument functionality 11 General configuration Page intentionally left blank. Roche Diagnostics cobas® pulse · Software version 01.03 · User Assistance · Publication version 1.
483 Glossary age barcode type Length of time a person has lived or a thing has existed. Class of barcodes sharing the same characteristics. battery ambient temperature Temperature of the immediate surroundings where the equipment is kept. Electrochemical device consisting of a series of cells that produce electrical energy. battery compartment app library Compartment that holds the battery. Screen where a collection of available apps is displayed.
484 charge indicator direct sunlight Status indicator that shows the status of the charging process. Light that comes from the sun and shines directly onto something, without being reflected off something else first. charging station Device that connects portable devices to a power source and to other peripherals. cleaning solution Solution that is used for cleaning of surfaces and parts of a system.
485 glucose linearity material Parameter that provides information about the presence of glucose in a sample. QC material used for linearity tests. linearity test glucose test In vitro diagnostic test for the quantitative determination of glucose in a patient's sample. Measuring procedure that tests the linearity of the system over the full range of analyzed values. lint-free cloth hand-held instrument Instrument that is small enough to be hand-held.
486 override QC lockout To neutralize an action. Lockout that occurs in case of a QC error or a due QC test. package insert Information regarding the usage of a product that is inserted into the package alongside the product itself. QC lot Lot of a QC material. patient ID QC material Unique and permanent identification of a patient throughout the system.
487 RFID reader standby mode Component that interprets the data stored in the RFID tag and read by the RFID antenna. Operating mode that is activated when the system is not performing any processing or measurement. The system is ready to exit this operating mode and return to the normal mode with a short delay. RFID tag Component that stores the data that can be read by the RFID antenna and interpreted by an RFID reader. status indicator Device indicating the status of a component.
488 test strip port venous whole blood Port that is used to insert a test strip into an instrument or meter. Whole blood that has passed through the capillaries of various tissues, except the lungs, and is found in the veins, the right chambers of the heart, and the pulmonary arteries. test strip port light Light that illuminates the test strip port and gives information about the quality of the test strip and the status of the measurement workflow.
489 Index A G Accessories and consumables, 89 Glucose app, 47, 99 Addresses, 5 Glucose test, 52, 54, 116 App bar, 44 App library, 46 Audit trail, 148, 192 I Instrument – brightness, 147 B – clean and disinfect, 169, 172 Barcodes, 90 – components, 37 Battery, 177, 193 – delete data, 191 Blood sample collection, 51 – reset, 185 C – restart, 153 – synchronization status, 73 Carry case, 40 – turn off, 152 – clean and disinfect, 176 – turn on, 151 Charging, 45, 104 – volume, 147 Charging
490 O Tests screen, 46 Observed test sequence (OTS), 62, 145 U P User assistance, 75 Password, 22, 150 Patient, 49, 113, 120 Proficiency test, 60, 142 User interface, 41 – app bar, 44 – navigation bar, 44 – status bar, 43 Q QC lockout, 66, 68 QC lot, 160, 161, 162 W Warranty, 3 QC test, 58, 122, 126 R Revision history, 2 S Safety classifications, 17 Safety information – precautions, 18 Screenshot disclaimer, 2 Software, 41 Standby mode, 107, 108 Status bar, 43 System, 35 T Technical specificat
Page intentionally left blank.
Published by: Roche Diagnostics International Ltd CH-6343 Rotkreuz Switzerland www.roche.