هەموو ڕێبەرەکان

User Manual

ڕێبەری بەکارهێنەر بە زمانی تۆ ئامادە دەکرێت. تا تەواو دەبێت، ئەمە وەشانەکەیەتی بە English.

Chapter 34The manager's phone app

Menu: Users and permissions, tab Phones and screens; and the window My account. The app itself runs on an Android phone.

34.1 What this app is for

Clarus LIS Manager is a small app for the person who runs the laboratory. On the phone the manager follows the laboratory's figures branch by branch, receives its alerts, and can decide a few things without going to the computer: approve results, approve a discount or a refund, suspend an account, switch outside access off, send a message to the program's screens, and send a result to a patient. The same phone can also stand in for a verification code when someone signs in to the program from outside the laboratory.

The app speaks only to the laboratory's own program. It does not use Google services, does not track the person and does not read the phone's contacts or location. A notification never names a patient. The app is for Android only; there is no iPhone version.

The laboratory decides everything about it. The administrator switches the app on, chooses how phones reach the laboratory, and decides in the roles matrix who may carry it and what each phone may do. A phone can never do what its person may not do at the bench.

34.2 Who can use it

You can……if your role holds
Pair your own phone and use the app's Branches, Alerts and Settings tabsLink the program to one's phone (Clarus Manager)
Use the phone only to sign in (the code and the approval)Sign in with the phone
Switch the app on or off, choose the road, set the days of absence, and remove anyone's phone (from inside the laboratory)Manage user accounts
Change which roles hold the app's permissionsManage settings

The permissions of the group Manager app are ticked in the tab Roles and permissions of the screen Chapter 33: Users and permissions. The administrator's role holds all of them; no other role holds any until it is ticked.

Figure 34-1: The roles matrix, at the group Manager app: 1 the group's heading, 2 one of its permissions, 3 a role's column.
Figure 34-1: The roles matrix, at the group Manager app: 1 the group's heading, 2 one of its permissions, 3 a role's column.
  1. The group Manager app.
  2. A permission: each of the group's permissions has a line of its own.
  3. A role's column. Tick a line to give that role the permission.

Each action on the phone needs two things together: the phone permission below and the program permission behind it.

Phone permissionWhat it opens in the appThe program permission it also needs
Send messages to the screens from the phoneThe tab MessagesSend messages to the program's screens
Verify results from the phoneActions, the section for results waiting for approvalVerify results
Approve a discount or a refund from the phoneActions, the section for discounts and refundsManage billing
Suspend a user or end their sessions from the phoneActions, the section for usersManage user accounts
Switch outside access off from the phoneActions, the switch for access from outsideManage settings
Send a result to the patient from the phoneThe button that sends a result to the patient, on an order's pagePublish the portal and communications

The tab Actions appears when at least one of its four sections is allowed. The search for a patient in the app follows Read patient files, and the money figures follow the same rule as the program's statistics.

34.3 Install and pair

The app is downloaded straight from the vendor's website, not from an app store, and it is installed from the file. Once installed it offers its own updates, signed by the vendor; nothing is installed without the person's tap.

The pairing window shows everything you need. It opens from My account, which you reach by pressing your name in the bar (see Chapter 2: Getting started). Pairing is done from inside the laboratory only.

Figure 34-2: The pairing window: 1 the code to download the app, 2 the pairing code, 3 the line that says the program is waiting for the phone.
Figure 34-2: The pairing window: 1 the code to download the app, 2 the pairing code, 3 the line that says the program is waiting for the phone.
  1. 1. Download the app: a code for the phone's camera. It leads to the app's page on the vendor's site.
  2. 2. Pair the phone: the pairing code. It works once and for ten minutes.
  3. The waiting line: Waiting for the phone, then The phone is paired. when the phone has taken the code.

The first screen of the app, before it is paired, is the welcome screen.

Figure 34-3: The app's welcome screen: 1 the language button, 2 the line that says what the app is for and what to do, 3 the phone's name, 4 the button that scans the pairing code, 5 the button that pastes it instead.
Figure 34-3: The app's welcome screen: 1 the language button, 2 the line that says what the app is for and what to do, 3 the phone's name, 4 the button that scans the pairing code, 5 the button that pastes it instead.
  1. The language button. The app opens in the phone's language when it is one of the program's eleven; the person changes it here or later in the settings.
  2. What the app is for, and what to do. It says to show the pairing code from My account in the program and scan it. The code is valid for ten minutes and once.
  3. The phone's name (optional). It is the name by which the laboratory lists this phone; left empty, the phone's model is used.
  4. Scan the pairing code, the main button.
  5. Paste the pairing code, for a phone whose camera cannot read a screen.

34.3.1 Task 1 — Pair a phone

You need your own computer inside the laboratory and the phone in your hand.

  1. In the program, press your name in the bar. In My account, under My phone, press Pair a phone.
  2. On the phone, point the camera at the first code and open the page it leads to. Download the file, open it and install it. Android may ask you to allow your browser to install apps: allow it.
  3. Open the app. Its first screen is the welcome screen, described above.
  4. Type a name for the phone if you wish, press Scan the pairing code and point the camera at the second code in the program's window. If the camera cannot read a screen, press Paste the pairing code and paste the code's text.
  5. The program says The phone is paired. and the app opens. The phone's own screen lock opens it (see below). The first time, the app explains why a small icon stays in the notification bar and asks for the notifications and for the exemption from battery saving. Allow both: without them the phone may stop the app and the alerts do not arrive.

The code works once, for ten minutes. If it has expired or was already used, close the window and open it again for a new one. The window may also say that a phone cannot reach this computer yet; open the server to the laboratory's network in Chapter 27: Branches and linking or turn on the intermediary server, then try again.

34.4 The road from the phone to the laboratory

The code carries the roads the phone may use, and the phone tries them in turn.

The roadWhat it needs
Directly, inside the laboratoryThe server opened to the laboratory's network in Chapter 27: Branches and linking, and the phone on that network
Directly, from outsideA fixed secure address the laboratory declares, or a private network such as Tailscale
Clarus LinkThe laboratory's program reaching the vendor's server. The vendor's server only joins the two ends and reads nothing

The administrator chooses among Directly, Clarus Link and Both, and Both is the choice until the laboratory chooses. While a phone is on Clarus Link it tries the direct roads again about every minute, so it comes back to the direct road when its person returns to the laboratory. In the app's settings, the row Reached through says which road is in use, and a red line says why Clarus Link refuses, when it does.

34.5 The phone's lock and its permanent icon

The app has no password of its own. When it opens it asks for the phone's own screen lock, fingerprint or code, and it locks again after five minutes away. A phone with no screen lock cannot open it. The small icon in the notification bar is the app following the laboratory; it keeps one question open to the laboratory, and that is how an alert reaches the phone without any push service. Do not switch it off.

34.6 The tabs of the app

The bottom bar shows five tabs at most, and a person sees only those the roles matrix allows. If the person follows two or more branches, a button at the top of the tabs chooses the branch, and urgent alerts keep arriving from all of them.

34.6.1 Branches

Figure 34-4: The Branches tab: 1 the period, 2 the headline card, 3 the things that need attention, 4 the comparison of the branches.
Figure 34-4: The Branches tab: 1 the period, 2 the headline card, 3 the things that need attention, 4 the comparison of the branches.
  1. The period: Today, Yesterday, Week, Month or Year, compared with the previous one. The choice is remembered.
  2. The headline card: one sentence says whether something needs attention now, whether things are waiting, or whether all runs smoothly.
  3. Things that need attention: open critical results, results waiting for approval, discounts or refunds waiting for a decision, stopped analyzers, open quality control, and stock. A tap goes to the right tab, or says that the matter is handled in the program.
  4. The branches: when the person follows several branches and has not chosen one, a chart compares their requests today and each branch has a line of its own with its figures. Further down come the main figures (requests, patients, results released, those on time, the median turnaround and rejected samples), the money figures for a person who may see money, with a button that hides them, and the work waiting now.

34.6.2 Alerts

Figure 34-5: The Alerts tab: 1 the button that mutes sounds for an hour, 2 the sections, 3 an alert that asks for a decision.
Figure 34-5: The Alerts tab: 1 the button that mutes sounds for an hour, 2 the sections, 3 an alert that asks for a decision.
  1. Mute for one hour, and beside it the button Alerts I receive, where the person chooses which kinds reach the phone and sets quiet hours.
  2. The sections: waiting for your decision, critical and open, needs attention, and for your information.
  3. An alert: its severity, its time, its branch and a few lines that never name a patient. A critical result offers Open the result and Seen.

A critical result rings with its own sound and repeats until it is opened. The alerts the person can receive follow the roles matrix and the person's own switches. If the phone has not heard from the laboratory for a while, a red banner says so, with a button that checks whether alerts can reach the phone.

34.6.3 Actions

Figure 34-6: The Actions tab: 1 the header, with the line that says the phone acts with the person's permissions in the program, 2 the sections still closed, each opened on its own.
Figure 34-6: The Actions tab: 1 the header, with the line that says the phone acts with the person's permissions in the program, 2 the sections still closed, each opened on its own.
  1. The header: the laboratory's name and the line that says the phone acts with the person's own permissions in the program.
  2. The other sections, closed here, shown only for the permissions the person holds: results waiting for approval, money approvals, users, and access from outside the laboratory.

Approving a result is one decision at a time: the phone shows the result and its flags, offers an approval note (printed in the report or kept for the laboratory), and has no bulk approval. A discount or a refund is approved or declined, and a decline needs a written reason. Suspending a person's account, or ending their sessions, also needs a written reason, which is recorded under the manager's name. The switch for access from outside the laboratory is shown only when access is open, and it asks before it acts.

34.6.4 Messages

Figure 34-7: The Messages tab: 1 the conversations, 2 the button for a new message.
Figure 34-7: The Messages tab: 1 the conversations, 2 the button for a new message.
  1. The conversations: what the person sent to the program's screens and what the program wrote to the management, with who has read each.
  2. New message: choose how it appears (a notice, a band or an urgent message), to whom (branches, people or devices), write it and choose how long it is shown. An urgent message stays on the screen until it is marked read or answered.

34.6.5 Settings

Figure 34-8: The Settings tab: 1 appearance, 2 alerts and sounds, 3 updates, 4 this phone and the button that unpairs it.
Figure 34-8: The Settings tab: 1 appearance, 2 alerts and sounds, 3 updates, 4 this phone and the button that unpairs it.
  1. Appearance: light, dark or as the phone; and below it the app's own language.
  2. Alerts and sounds: mute, the sound of each kind, quiet hours, and a check that tells whether alerts can reach the phone.
  3. Updates: the version in use and the button that looks for a newer one.
  4. This phone: the laboratory, the account, the road in use, and the red button that unpairs the phone.

A person who may use the sign-in code or the scan also sees a section Sign-in with this phone with those two rows, which are described below.

34.7 Signing in with the phone

A phone whose person holds Sign in with the phone can help sign in to the program from outside the laboratory.

  • The code. The app shows a six-digit code that changes every thirty seconds. Type it when the program asks for the verification code. The laboratory hands the secret over only from inside the laboratory, and the app asks for it while the phone is on the laboratory's network.
  • The approval. When someone signs in from outside, an alert reaches the phone and rings whatever the sound settings are. Choose the number the computer shows. The request lasts about a minute. Not me refuses it and tells the laboratory's managers.
  • The scan. The app can scan the code on the program's sign-in page and confirm the sign-in after asking.

A person who holds only the sign-in permission sees just two tabs, the code and the settings.

34.8 Removing a phone

  • From the phone. In the settings, press the red button that unpairs the phone and confirm. The phone forgets the laboratory and returns to the welcome screen. If the laboratory cannot be reached, the phone is forgotten anyway and the administrator can remove its entry.
  • From your account. In My account, under My phone, press Remove beside your own phone.
  • By the administrator. In the tab Phones and screens of Chapter 33: Users and permissions, the card Paired phones lists the paired phones with their owner and device name, and Remove removes one.
  • By the program. A phone that is not heard from for more than the number of days set in the same tab is removed (30 by default). Nobody is told; the person finds out when the app says that the phone was removed from the laboratory and must be paired again. A person who loses both app permissions loses all their phones.

A removed phone is refused at its next request, and to use it again its person pairs it again with a new code.

Figure 34-9: The tab Phones and screens: 1 the switch that turns the app on, 2 the road, 3 the days after which a silent phone is removed, 4 the paired phones.
Figure 34-9: The tab Phones and screens: 1 the switch that turns the app on, 2 the road, 3 the days after which a silent phone is removed, 4 the paired phones.
  1. The app is on: off, every phone is stopped and no new code can be made.
  2. How phones reach the laboratory.
  3. The days of absence, for a phone and for a screen with no name.
  4. Paired phones, with a remove button for each.

All of this is saved at once, and only from inside the laboratory.

34.9 Keeping the app up to date

When a newer signed version exists, a blue strip appears above the tabs and the settings offer the update. Nothing downloads without a tap, and Android always asks the person to confirm the installation. If the laboratory no longer accepts an old version, the whole app is replaced by a screen that asks for the update.

34.10 Messages and what to do

The app or the program saysWhat it meansWhat to do
The pairing code has expired, or was already usedThe code works once and for ten minutesClose the pairing window and open it again
A phone cannot reach this computer yetThe code carries no road the phone can useOpen the server to the laboratory's network in Chapter 27: Branches and linking, or turn on the intermediary server
The laboratory could not be reachedThe phone is not on a road that reaches the laboratoryCheck the phone's connection, and the program's computer
This phone was removed from the laboratoryAn administrator, the person or the days of absence removed itPair the phone again from My account
The manager app is switched off for this laboratoryThe switch in the tab Phones and screens is offThe administrator switches it on
Update the appThe laboratory no longer accepts this versionInstall the newer version
Last contact with the laboratory… alerts may not reach youThe phone has not heard from the laboratory for over a minutePress the check button and follow what it says

34.11 See also

Chapter 33: Users and permissions, Chapter 27: Branches and linking, Chapter 2: Getting started, Chapter 28: Linking branches and computers, Chapter 41: Questions and problems

ڕاپۆرتکردنی هەڵەی وەرگێڕان
WhatsApp بەستەری داگرتن بۆ کۆمپیوتەرەکەت بنێرە