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

Healthcare / APPLICATION BLUEPRINT

Patient Referral & Triage Coordination

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

Start generatingExplore illustrative interface

13 workspace menus · 13 business workflows · 5 role profiles

Application blueprint only. This is a proposed design, not a deployed or production-tested system. Screens and sample figures are illustrative; workflows, business rules, approvals, permissions and integrations require confirmation before build.

Designed for Hospital outpatient services director

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

Explore an illustrative interface.

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

Patient Referral & Triage Coordination workspace interface preview; illustrative records and figures.
Patient Referral & Triage Coordination — operational workspaceIllustrative interface · Sample dataView full interface →
Patient Referral & Triage Coordination record interface preview; illustrative records and figures.
Patient Referral & Triage Coordination — record and workflow reviewIllustrative interface · Sample 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.

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.

Business workflows

Select a workflow to review the steps, responsibilities, approval and exception handling.

01 · Separate completeness checking

Coordinate completeness checking within Patient referral and triage coordination.

Trigger
Completeness checking requires a new record, an agreed review or a controlled change.

Responsible role
Referral coordinator

  • Register completeness checking and its operating scope
  • Identify continuing obligations and dependencies
  • Obtain receiving-owner acceptance
  • Record the authorised transfer and follow-up

Approval
Scheduling officer records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
The receiving team declines an obligation or a dependency remains open.

Outcome
Accepted responsibility, transfer evidence and retained follow-up obligations.

02 · Coordinate referral intake

Coordinate referral intake within Patient referral and triage coordination.

Trigger
Referral intake requires a new record, an agreed review or a controlled change.

Responsible role
Referral coordinator

  • Register referral intake and its operating scope
  • Assign the accountable owner and required actions
  • Review the relevant evidence and unresolved conditions
  • Confirm the accepted outcome and retain its history

Approval
Scheduling officer records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Required information or responsibility is missing, or an operating condition changes.

Outcome
A completed operating record with its linked evidence and remaining obligations.

03 · Coordinate patient identity checks

Coordinate patient identity checks within Patient referral and triage coordination.

Trigger
Patient identity checks requires a new record, an agreed review or a controlled change.

Responsible role
Referral coordinator

  • Register patient identity checks and its operating scope
  • Assign the accountable owner and required actions
  • Review the relevant evidence and unresolved conditions
  • Confirm the accepted outcome and retain its history

Approval
Scheduling officer records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Required information or responsibility is missing, or an operating condition changes.

Outcome
A completed operating record with its linked evidence and remaining obligations.

04 · Coordinate document completeness

Coordinate document completeness within Patient referral and triage coordination.

Trigger
Document completeness requires a new record, an agreed review or a controlled change.

Responsible role
Referral coordinator

  • Register document completeness and its operating scope
  • Coordinate the required specialist and business review
  • Accept the release version and permitted recipients
  • Record distribution, acknowledgement and later revisions

Approval
Scheduling officer records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Content conflicts, missing review or a changed recipient permission prevents release.

Outcome
An accepted content version with distribution and revision history.

05 · Coordinate clinician review queue

Coordinate clinician review queue within Patient referral and triage coordination.

Trigger
Clinician review queue requires a new record, an agreed review or a controlled change.

Responsible role
Authorised clinician

  • Register clinician review queue and its operating scope
  • Collect the linked records and qualified evidence
  • Assign the responsible reviewer and record findings
  • Accept the outcome or assign corrective follow-up

Approval
Scheduling officer records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Evidence is incomplete, disputed, expired or outside the reviewer’s authority.

Outcome
A review finding, its accepted evidence and any accountable corrective actions.

06 · Coordinate appointment coordination

Coordinate appointment coordination within Patient referral and triage coordination.

Trigger
Appointment coordination requires a new record, an agreed review or a controlled change.

Responsible role
Referral coordinator

  • Register appointment coordination and its operating scope
  • Compare suitable capacity and existing commitments
  • Confirm the provider, service window and accepted conditions
  • Track fulfilment, cancellation and capacity release

Approval
Scheduling officer records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Demand exceeds suitable capacity or a provider withdraws its commitment.

Outcome
An accepted capacity commitment with service conditions and completion evidence.

07 · Coordinate handover records

Coordinate handover records within Patient referral and triage coordination.

Trigger
Handover records requires a new record, an agreed review or a controlled change.

Responsible role
Referral coordinator

  • Register handover records and its operating scope
  • Identify continuing obligations and dependencies
  • Obtain receiving-owner acceptance
  • Record the authorised transfer and follow-up

Approval
Scheduling officer records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
The receiving team declines an obligation or a dependency remains open.

Outcome
Accepted responsibility, transfer evidence and retained follow-up obligations.

08 · Coordinate referral ageing reports

Coordinate referral ageing reports within Patient referral and triage coordination.

Trigger
Referral ageing reports requires a new record, an agreed review or a controlled change.

Responsible role
Referral coordinator

  • Register referral ageing reports and its operating scope
  • Assign the accountable owner and required actions
  • Review the relevant evidence and unresolved conditions
  • Confirm the accepted outcome and retain its history

Approval
Scheduling officer records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Required information or responsibility is missing, or an operating condition changes.

Outcome
A completed operating record with its linked evidence and remaining obligations.

09 · Register the operating requirement

Coordinate operating requirement within Patient referral and triage coordination.

Trigger
Operating requirement requires a new record, an agreed review or a controlled change.

Responsible role
Referral coordinator

  • Register operating requirement and its operating scope
  • Compare options, dependencies and operating constraints
  • Review the selected option with its accountable owners
  • Accept the plan and track its delivery conditions

Approval
Scheduling officer records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
An assumption changes, prerequisites are missing or stakeholders cannot accept the proposed commitment.

Outcome
An approved operating plan and owned actions for its accepted conditions.

10 · Resolve operating exceptions

Coordinate operating exceptions within Patient referral and triage coordination.

Trigger
Operating exceptions requires a new record, an agreed review or a controlled change.

Responsible role
Referral coordinator

  • Register operating exceptions and its operating scope
  • Gather the relevant evidence and review options
  • Route the case to the delegated decision owner
  • Record the outcome, conditions and follow-up obligations

Approval
Scheduling officer records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
The case exceeds delegation, contains a conflict or has disputed evidence.

Outcome
An authorised decision or escalation with accountable resolution actions.

11 · Verify completion and follow-up

Coordinate completion and follow-up within Patient referral and triage coordination.

Trigger
Completion and follow-up requires a new record, an agreed review or a controlled change.

Responsible role
Authorised clinician

  • Register completion and follow-up and its operating scope
  • Collect the linked records and qualified evidence
  • Assign the responsible reviewer and record findings
  • Accept the outcome or assign corrective follow-up

Approval
Scheduling officer records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Evidence is incomplete, disputed, expired or outside the reviewer’s authority.

Outcome
A review finding, its accepted evidence and any accountable corrective actions.

12 · Review controlled operating changes

Coordinate controlled operating changes within Patient referral and triage coordination.

Trigger
Controlled operating changes requires a new record, an agreed review or a controlled change.

Responsible role
Authorised clinician

  • Register controlled operating changes and its operating scope
  • Collect the linked records and qualified evidence
  • Assign the responsible reviewer and record findings
  • Accept the outcome or assign corrective follow-up

Approval
Scheduling officer records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Evidence is incomplete, disputed, expired or outside the reviewer’s authority.

Outcome
A review finding, its accepted evidence and any accountable corrective actions.

13 · Prepare scoped operational reports

Coordinate scoped operational reports within Patient referral and triage coordination.

Trigger
Scoped operational reports requires a new record, an agreed review or a controlled change.

Responsible role
Referral coordinator

  • Register scoped operational reports and its operating scope
  • Assign the accountable owner and required actions
  • Review the relevant evidence and unresolved conditions
  • Confirm the accepted outcome and retain its history

Approval
Scheduling officer records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Required information or responsibility is missing, or an operating condition changes.

Outcome
A completed operating record with its linked evidence and remaining obligations.

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.
Operating rules by business workflow
  • For completeness checking, a receiving owner, evidence of acceptance and unresolved obligations are recorded before a handover closes.
  • For referral intake, the record retains an accountable owner, its supporting evidence and accepted outcome.
  • For patient identity checks, the record retains an accountable owner, its supporting evidence and accepted outcome.
  • For document completeness, the released version and authorised audience remain traceable to the accepted review.
  • For clinician review queue, evidence, reviewer authority and acceptance conditions are visible before a reviewed outcome is accepted.
  • For appointment coordination, capacity is committed only after prerequisites and the responsible provider are confirmed.
  • For handover records, a receiving owner, evidence of acceptance and unresolved obligations are recorded before a handover closes.
  • For referral ageing reports, the record retains an accountable owner, its supporting evidence and accepted outcome.
  • For operating requirement, the accepted plan records assumptions, rejected alternatives, dependencies and conditions.
  • For operating exceptions, a decision retains its authority, reason, supporting evidence and resulting obligations.
  • For completion and follow-up, evidence, reviewer authority and acceptance conditions are visible before a reviewed outcome is accepted.
  • For controlled operating changes, evidence, reviewer authority and acceptance conditions are visible before a reviewed outcome is accepted.
  • For scoped operational reports, the record retains an accountable owner, its supporting evidence and accepted outcome.

Data, interfaces and operating requirements.

Core records

Case / requestPerson / customerService / issue typeTaskAssignmentDecisionEvidence / communicationResolution
Record fields and linked information
  • Record identifier — Stable reference for the operating transaction.
  • Service / care team — Business scope used for responsibility and reporting.
  • Operating subject — The request, commitment or work item being handled.
  • Accountable owner — Named responsibility for the next action.
  • Workflow stage — Current position in the agreed business journey.
  • Review requirement — Required review and outstanding decision.
  • Due or review date — Agreed action window or review trigger.
  • Linked evidence — Source records supporting the operating decision.
  • Decision authority — The delegated authority relevant to the accepted outcome.
  • Accepted outcome — Recorded decision and its business consequences.
  • Follow-up obligation — Remaining responsibilities after an accepted action.
  • Revision history — Trace of accepted changes and their evidence.
  • Referral intake reference — Link the relevant referral intake to the operating transaction and its decision evidence.
  • Patient identity checks reference — Link the relevant patient identity checks to the operating transaction and its decision evidence.
  • Document completeness reference — Link the relevant document completeness to the operating transaction and its decision evidence.
  • Clinician review queue reference — Link the relevant clinician review queue to the operating transaction and its decision evidence.
  • Appointment coordination reference — Link the relevant appointment coordination to the operating transaction and its decision evidence.

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

What to validate in a scoped demonstration.

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.