Screening operations

Today at a glance

Live operational status across all programs.

Program operations

Screening performance

Monitor movement through screening and find follow-up that needs action.

Live operational dataLoading latest snapshot…

Screening funnel

Patients enrolled during the selected period

Weekly movement

New enrolments and first survey responses.

EnrolledSurveyed

Program performance

Counts reconcile to the selected enrolment cohort.

Team workload

Open follow-up by assigned owner.

Data quality

Signals that affect operational trust and traceability.

Follow-up requiring action

Open tasks ordered by due date.

Open work queue

Temporal automation

Scheduled reporting

Save a filtered view, deliver it on a recurring schedule, and monitor every attempt.

Saved views

Recurring schedules

Delivery history

Temporal retries failed deliveries up to three times.

Screening pathway

Each program follows one operating rhythm while keeping its own questions, rules and content.

1
EnrolConfirm program
2
AssessCollect answers
3
ArrangeBook or refer
4
Follow upRemind and check
5
CompleteSet next step

Patient registry

Search the shared registry and open one complete patient record.

Work queue

Assign, prioritize and complete follow-up items.

Patient communication

Conversation inbox

Review new messages, staff handoffs, and program-specific context.

Unified patient profile

Patient

Active

Screening programs

Every enrolment and its current pathway position.

Open work

Tasks requiring staff attention.

Latest activity

Screening programs

Published patient journeys running on the shared platform.

Program studio

Design and maintain screening programs

Work safely in a draft, validate the journey, then publish an immutable version.

Program

Patient questionnaire

Questions are presented one at a time in WhatsApp or through the patient form.

Survey title

Patient instructions

Conversation flow

Bind an approved message to the response it expects, then choose the next message deterministically.

How it works

When a workflow sends a message used by a step, the chatbot waits for the configured answer. The answer is saved as a program variable, emits a conversation.response event, and follows the matching branch. Educational RAG is used only when no configured step is waiting.

Default completion message

FormSG connection

Use an existing FormSG form for this program while keeping responses in the patient record.

Not connected

FormSGOfficial signature authentication and end-to-end decryption relay

Enable

Form ID

Shown in the FormSG form address and webhook payload.

Patient form link

This is the link sent to patients by WhatsApp.

Answer mapping Optional JSON

{}

No active relay credential for this form.

Form secret key

For security, an existing key is never shown. Enter a key only to activate or replace it.

Patient phone field ID

Enrollment field ID Optional

Official FormSG webhook URL

How responses arrive

The self-hosted relay verifies FormSG's signature against this exact URL, rejects stale or mismatched identities, decrypts with the form secret key, and sends only normalized answers into the patient journey.

No unsaved changes

Standalone system control

Platform settings

Choose runtime services here. Credentials remain in the deployment environment and are never displayed in the portal.

Standalone authentication

Model gateway

Controls educational RAG generation and document embeddings. Deterministic clinical rules never use the model.

Provider

AWS runtime region

Fixed to Asia Pacific (Singapore).

Global inference profile

Invoked from Singapore through AWS global cross-Region routing. AWS may process requests in another supported commercial Region.

Embedding inference profile

The global Cohere Embed v4 profile indexes approved text, uploaded images, and rendered PDF pages.

Embedding size

Re-index documents after changing model or size.

Response variation

Used by compatible models; Sonnet 5 and Opus 5 use their Bedrock default.

Maximum answer tokens

Saved choices apply to new requests immediately.

LIVE

Core services

Live connectivity checks for the services that hold and orchestrate patient operations.

CFG

External connections

Configuration status is shown without revealing secret values.

Standalone access

This installation does not require organizational SSO. Local staff accounts, roles, program scope and the deployment administrator key protect access.

Manage staff access

Staff access

Roles and program access for the care team.

Recent activity

Traceable operational and configuration changes.

WhatsApp integration

Twilio configuration, webhooks, and delivery health.

Sign in