OptikamPad — fitting measurements from Optikam Cloud

OptikamPad is the tablet the optician uses to take eyewear-fitting measurements — heights, PD and so on — with the patient wearing the frame. The pad keeps every measurement session in the practice's own Optikam Cloud.

SightHub does not talk to the pad. It goes to Optikam Cloud and pulls the sessions from there, using the practice's API key. That key is the whole setup: no device pairing, no username, no password.

You find the page at Settings → General → Integrations → OptikamPad — in the left-hand list, or the OptikamPad tile on the Integrations start page.

What you need first

The page lists it in the setup guide under Before you start:

an active Optikam Cloud subscription — no subscription, no key, no integration;
access to the Optikam Cloud Portal for the practice;
a SightHub account with the Setting permission.

Setting it up

The Setup guide — one-time, usually done by a manager panel, collapsed above the Account Details card, opens to the same steps as below.

Generate the API key in the Optikam Cloud Portal. Log in at portal.optikam.com, open ACCOUNT in the top menu, then the KEYS tab, and press Generate. A key that looks like xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx appears next to API Key — copy it. You can come back and generate a fresh one at any time.
Pick the store. In the OptikamPad Account Details card, choose the store from the Store dropdown. The key is saved per store: a practice with several stores enters a key for each one.
Paste the key and press Enable. Paste it into Optikam Cloud API key and press Enable. The button reads Checking the key… while SightHub tries the key against Optikam Cloud.
Repeat for every store that uses an OptikamPad.

When the key works you get OptikamPad enabled, and the store shows a green Enabled badge with Key valid — Cloud subscription active.

If Optikam turns it down, a red message appears (for example Optikam rejected this API key) and the store stays Not enabled. The usual reasons are a mistyped key or an expired Cloud subscription. Generate a new key in the portal and enter it again.

The Account Details card

Status line — before a store is picked it says Select a store to see its status. After that: Enabled or Not enabled, the reason when it is not enabled, and Last check — when SightHub last tried the key.
Store — only shop locations are listed. Warehouses are left out, since nobody fits glasses in a warehouse.
Optikam Cloud API key — hidden like a password. The eye icon at the end shows or hides what you typed. Once a store is enabled the box says Enter to replace, and the button changes to Update key.
Checklist — under the form, a short list of what this store still needs, each item with a tick or a cross. If the key did not check out, it says Re-enter a working key below.

How the measurements come in

Once a store is enabled, SightHub pulls new measurement sessions from Optikam Cloud by itself, every few minutes. Nobody has to press anything.

To pull right now, use Sync now in the Measurement sessions box. It brings in the store's new sessions and their marked-up photos. You can press it as often as you like — sessions that were already imported are skipped, not doubled.

Sync now stays greyed out until the store is enabled (Enable the integration first — a sync on a location with no key is refused.).

After a sync, five numbers appear:

Found in Optikam — how many sessions Optikam Cloud has for this store.
Newly imported — how many of those were new this time.
Matched to a patient — how many were linked to a patient.
Photos stored — how many photos were saved with them.
Already imported — skipped because they came in earlier. This is normal, not an error.

The toast tells you the short version: Imported 3 measurement session(s) or Nothing new to import. If some sessions could not be imported, an amber box says how many and lists the reason for each.

Getting the measurement onto the lab ticket

SightHub links a session to the right job through the lab ticket number:

Open the patient's lab ticket. Its number is shown at the right end of the button row — Ticket # followed by the number.
On the pad, the optician types that number in as the order / customer number before taking the measurement.
When the session arrives in SightHub, it is tied to that lab ticket and its patient.
Back on the lab ticket, press Apply Optikam.

Apply Optikam takes the newest measurement for this ticket and writes it into the ticket: Seg Ht, Dt and Nr (the monocular PD) and BVD for each eye, plus any frame values the session carries. The toast says how many fields were filled — Optikam measurement applied (7 fields).

Only those fields change. Anything else you had typed on the ticket but not saved yet stays as it is — press Save as usual to keep it.

If nothing has come in for this ticket yet, you get No Optikam measurement for this ticket yet. Wait for the next automatic pull, or press Sync now on the settings page, and try again.

If something is not right

These are the same tips the page shows under If something's not right:

Still "Not enabled" after Enable — the key is wrong or the Cloud subscription is not active. Generate a fresh key in the portal (ACCOUNT | KEYS) and paste it again.
The key went on the wrong store — the key is saved to whatever store is picked in the dropdown. Pick the right store before you press Enable.
"Sync refused" / "not configured" — that store has no key yet. Enter it first, then sync.
A measurement did not show up on the ticket — check that the optician typed the correct lab ticket number as the order number on the pad.

Good to know

One key per store. Switching the store in the dropdown clears the key box and the last sync numbers — they belong to the store that was picked before.
The key lives only as long as the subscription. The page says it plainly: no subscription, no key, no integration. If the store shows Not enabled after it used to work, check the Optikam Cloud subscription first, then enter a fresh key.
The checklist borrows wording from TriZetto. Its badge says Ready to bill / Not ready to bill, and a missing item adds claims from this location will be refused. On this page, read that as "ready to pull measurements" or not — no claims are involved.
The link at the bottom of the setup guide (Optikam Integration on the SightHub wiki) opens the technical article. This page is the staff version.