Cortex setup, device and image verification

Cortex is an independent service on the clinic computer and may keep running when Desktop closes. Computer-clinic binding, device connectivity and clinical confirmation are separate stages.

Installation and clinic approval

Desktop offers installation if Cortex is absent. Complete the official installer and OS administrator approval. Choose the correct Platform account/clinic for enrollment; do not assume readiness before binding succeeds.

Settings → General → Reauthorize renews the existing same-clinic connection. It may stop the service; cancellation/expiry can leave it stopped. Complete approval with the same clinic and verify state. This is not a silent clinic-rebinding path. Do not reset device/queue settings to work around connectivity.

Add a device

1. Open device setup in Platform and select the connected computer.
2. Select exact manufacturer/model and supported connection. Read research/unsupported reasons instead of substituting a similar model.
3. Follow the offered guide for device LIS/destination configuration within authorized clinic networking.
4. In listen/verify, send a test result from the selected computer/device. Discovery alone is not a device result.
5. Inspect patient/sample, values, units and result; finalize only after successful verification, then check active devices and diagnostics.

Experimental choices may need explicit opt-in. A protocol/model family in software does not establish support for every device. Model, firmware, licensed option and transport must match. Do not force activation without an eligible profile and verified data.

Results and images

Receiving, delivering, assigning to a patient and clinically confirming are different states. Check source device, patient/sample, time, values/units and confirmed revision. Read durable queued work after disconnect; resending a test does not prove the first failed.

Opening an existing image differs from new device image intake. The current Cortex laboratory release does not establish DICOM receive/worklist/delivery as ordinary production device support. Viewing previously uploaded images is assessed separately.

If your Desktop version offers local folder settings, choose the folder in the OS picker, verify service read access and new-files/existing-archive scope. Save differs from Save and apply, which may require service restart confirmation. Development-only folder inbox is not a general user workflow.

Automatic image opening and recovery

Check the supported Desktop automatic-opening preference. Verify new ready images against current clinic/patient/revision. Inspect unexpected/older images and distinguish manual opening from automatic ready notifications. Browser notifications differ from Desktop focus changes.

Separate offline, reauthorization-required and revoked states. Provide model/version, selected computer, visible status and time to support without patient data or connection keys.

Synthetic acceptance

Track the same anonymous result while connected and after interruption. Expect one correctly assigned clinical result with proper units. Physical-device and installed-OS acceptance is required before claiming support.