, home
Customer access Request an enterprise demo
Request an enterprise demo Customer access

Healthcare

Patient Referral & Triage Coordination

Organise referral intake, administrative completeness, clinician prioritisation, appointment confirmation and receiving-team handover.

Request a tailored demonstrationExplore the interface

13 workspace menus · 5 role profiles · Connected records

Designed for hospital outpatient services directors

Patient Referral & Triage Coordination workspace interface preview; illustrative records and figures.
Patient Referral & Triage Coordination — operational workspaceInterface preview · Illustrative dataView full interface →

Explore the system interface.

Operational workspace and record review. Select a screen to inspect it in full.

Patient Referral & Triage Coordination workspace interface preview; illustrative records and figures.
Patient Referral & Triage Coordination — operational workspaceInterface preview · Illustrative dataView full interface →
Patient Referral & Triage Coordination record interface preview; illustrative records and figures.
Patient Referral & Triage Coordination — record and workflow reviewInterface preview · Illustrative dataView full interface →

Operational dashboards and work queues.

Operational views

Review work, evidence, exceptions and authorised decisions within a defined operating scope.

Service / care teamPeriodAssigned teamReview state

Dashboard measures

  • Active delivery records
    Count of all records in the selected workspace.
  • Review queue
    Records at the third stage of the business workflow.
  • Needs attention
    Records with an assigned review requirement.
  • Final-stage records
    Records in the fourth business workflow stage.

Business workflow and operating scope

Organise referral intake, administrative completeness, clinician prioritisation, appointment confirmation and receiving-team handover. A referral can wait without a clear owner when missing documents, administrative checks and clinical review are mixed together. The system makes each handover visible and separates completeness checking from clinician prioritisation, helping outpatient teams track the path to a confirmed appointment.

Operational visibility

  • Referral to first appointment time
  • Open cases by priority and ageing
  • Service level / cycle time dashboard
  • Escalation and exception report
  • Resolution outcomes and rework

Operations

Operational overview

Review the work position and priority actions.

Referral intake

Coordinate referral intake with assigned responsibilities, linked records and review history.

Patient identity checks

Coordinate patient identity checks with assigned responsibilities, linked records and review history.

Document completeness

Coordinate document completeness with assigned responsibilities, linked records and review history.

Clinician review queue

Coordinate clinician review queue with assigned responsibilities, linked records and review history.

Appointment coordination

Coordinate appointment coordination with assigned responsibilities, linked records and review history.

Handover records

Coordinate handover records with assigned responsibilities, linked records and review history.

Referral ageing reports

Coordinate referral ageing reports with assigned responsibilities, linked records and review history.

Completeness checking

Coordinate completeness checking with assigned responsibilities, linked records and review history.

Insights

Reports and saved views

Review the reporting scope and export agreed operational views.

Governance

Approvals and exceptions

Review delegated decisions, exceptions and recorded conditions.

Audit history

Trace accepted changes, decisions and accountable actions.

Access and configuration

Manage the agreed role permissions and configurable operating rules.

The end-to-end business journey.

From intake to authorised completion, with evidence at each decision.

01

Receive the referral

Receive referral and records.

02

Check completeness

Check administrative completeness.

03

Route clinical review

Route for clinician prioritisation.

04

Confirm the handover

Confirm appointment and handover.

Governance and control

  • Every case must have an owner, priority and status.
  • Sensitive records must be visible only to authorised roles.
  • Escalation rules must be configurable by severity and elapsed time.
  • Decisions that affect entitlement, safety or payment require accountable human approval.
  • Closed cases may reopen only through a controlled path that preserves history.
  • Jurisdiction-, regulator- or authority-specific rules must be configurable and validated by an authorised domain owner before production use.

Accountable roles

Referral coordinator
Administrative reviewer
Authorised clinician
Scheduling officer
Receiving service

Permissions are configured and tested for the agreed responsibilities.

Data, interfaces and operating requirements.

Core records

Case / requestPerson / customerService / issue typeTaskAssignmentDecisionEvidence / communicationResolution

Systems and interfaces

  • Patient identity services
  • Approved health-record interfaces
  • Appointment and secure communication services

Interface scope, data mapping and testing are agreed for each engagement.

Implementation requirements
Clinical triage remains clinician controlled; requires patient identity, health record integration and jurisdiction-specific privacy controls.

Mobile and tablet access

Provide authorised reviewers with referral status and administrative tasks, subject to the organisation's patient-data access rules.

Access approved workflows through the Dalfin mobile app. Device tasks and permissions are confirmed for the deployment.

Apple App Store ↗Google Play ↗

AI extensions

Summarise administrative documents for an authorised reviewer. Clinical prioritisation remains clinician controlled.

AI extensions are scoped around the required data, business outcome and review controls.

Engineered with Genesis.

Structured application engineering

Connect requirements, roles, records, workflows and interfaces through the agreed Genesis engineering process.

Controlled changes

Review dependency impact and validation requirements. Context Memory supports governed changes and accepted application revisions.

Deployment and support

Agree customer cloud or on-premises requirements, device access, implementation acceptance and ongoing engineering support.

An example operating scenario

See the process, its exception and the evidence.

A referral is missing a required record. The coordinator obtains it and routes the completed package to the clinician, who records the priority. Scheduling confirms the appointment and the receiving team acknowledges the handover. No clinical priority is generated autonomously.

What to review

  • A saved end-to-end transaction
  • An exception and its authorised resolution
  • Different operator, approver and reviewer permissions
  • Final records, history and the relevant report
Discuss this solution

Questions before implementation.

How is this system adapted to our organisation?

Roles, approval authority, business rules, records and reporting are configured around your operating model. Scope definition connects the required business outcome to workflows, interfaces and acceptance criteria.

How are approvals and responsibilities defined?

Operators, reviewers and authorised decision makers have defined responsibilities. Approval limits, exception handling and access permissions are agreed with your business owners and tested against the selected workflows.

Can it connect with our existing systems?

Interface requirements cover your existing business systems, data ownership, mapping and authentication. Connection design and testing form part of the agreed implementation scope.

What will we review in a solution walkthrough?

Start with a relevant business transaction, then review its approvals, an exception, role permissions and final records. Discuss the integrations, reporting and operating requirements that matter to your organisation.