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

Healthcare / APPLICATION BLUEPRINT

Medicines Reconciliation & Discharge Coordination

Coordinates collection of existing medication information and pharmacist-led reconciliation.

Start generatingExplore illustrative interface

11 workspace menus · 10 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 care coordinators and the responsible business owners

Medicines Reconciliation & Discharge Coordination workspace interface preview; illustrative records and figures.
Medicines Reconciliation & Discharge 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.

Medicines Reconciliation & Discharge Coordination workspace interface preview; illustrative records and figures.
Medicines Reconciliation & Discharge Coordination — operational workspaceIllustrative interface · Sample dataView full interface →
Medicines Reconciliation & Discharge Coordination record interface preview; illustrative records and figures.
Medicines Reconciliation & Discharge 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 reconciliation items
    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

Coordinates collection of existing medication information and pharmacist-led reconciliation. Tracks discrepancies requiring prescriber review, records approved changes and confirms discharge handovers, with clear responsibility for outstanding questions and traceability of the information provided to receiving care teams.

Operations

Operational overview

Review the work position and priority actions.

Collection of existing medication information

Coordinate collection of existing medication information with assigned responsibilities, linked records and review history.

Pharmacist-led reconciliation

Coordinate pharmacist-led reconciliation with assigned responsibilities, linked records and review history.

Discrepancies requiring prescriber review

Coordinate discrepancies requiring prescriber review with assigned responsibilities, linked records and review history.

Changes

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

Discharge handovers

Coordinate discharge handovers with assigned responsibilities, linked records and review history.

Work register

Coordinate work register 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

Collect source records

Establish the scope of collection of existing medication information, capture the required records and assign the accountable team.

02

Reconcile the position

Coordinate pharmacist-led reconciliation, discrepancies requiring prescriber review, with linked evidence and visible outstanding actions.

03

Authorise adjustments

Review the relevant conditions and exceptions. Record the authorised outcome and its supporting evidence.

04

Close outstanding items

Confirm the resulting records and handovers. Track remaining obligations, later changes and follow-up actions.

Business workflows

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

01 · Coordinate collection of existing medication information

Coordinate collection of existing medication information within Medicines Reconciliation and Discharge Coordination.

Trigger
Collection of existing medication information requires a new record, an agreed review or a controlled change.

Responsible role
Care coordinator

  • Register collection of existing medication information 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
Service authoriser 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.

02 · Coordinate pharmacist-led reconciliation

Coordinate pharmacist-led reconciliation within Medicines Reconciliation and Discharge Coordination.

Trigger
Pharmacist-led reconciliation requires a new record, an agreed review or a controlled change.

Responsible role
Clinical reviewer

  • Register pharmacist-led reconciliation and its operating scope
  • Compare amounts, attribution and accepted conditions
  • Route differences to the accountable finance reviewer
  • Record authorised adjustments and the accepted position

Approval
Service authoriser records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Amounts, ownership or allocation evidence do not agree.

Outcome
A reconciled position, approved adjustments and separately owned outstanding items.

03 · Track discrepancies requiring prescriber review

Coordinate discrepancies requiring prescriber review within Medicines Reconciliation and Discharge Coordination.

Trigger
Discrepancies requiring prescriber review requires a new record, an agreed review or a controlled change.

Responsible role
Clinical reviewer

  • Register discrepancies requiring prescriber review 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
Service authoriser 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.

04 · Record approved changes

Coordinate approved changes within Medicines Reconciliation and Discharge Coordination.

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

Responsible role
Care coordinator

  • Register approved changes 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
Service authoriser 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.

05 · Confirm discharge handovers

Coordinate discharge handovers within Medicines Reconciliation and Discharge Coordination.

Trigger
Discharge handovers requires a new record, an agreed review or a controlled change.

Responsible role
Care coordinator

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

Approval
Service authoriser 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.

06 · Register the operating requirement

Coordinate operating requirement within Medicines Reconciliation and Discharge Coordination.

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

Responsible role
Care 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
Service authoriser 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.

07 · Resolve operating exceptions

Coordinate operating exceptions within Medicines Reconciliation and Discharge Coordination.

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

Responsible role
Care 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
Service authoriser 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.

08 · Verify completion and follow-up

Coordinate completion and follow-up within Medicines Reconciliation and Discharge Coordination.

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

Responsible role
Clinical reviewer

  • 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
Service authoriser 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.

09 · Review controlled operating changes

Coordinate controlled operating changes within Medicines Reconciliation and Discharge Coordination.

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

Responsible role
Clinical reviewer

  • 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
Service authoriser 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.

10 · Prepare scoped operational reports

Coordinate scoped operational reports within Medicines Reconciliation and Discharge Coordination.

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

Responsible role
Care 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
Service authoriser 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

  • Role permissions reflect the agreed responsibilities and restricted record access.
  • Sensitive information is restricted to the agreed roles and permitted sharing scope.
  • Required information and evidence are checked before the relevant decision or handover.
  • Exceptions have a named owner, recorded reason and an authorised resolution.
  • Approved changes retain their previous values, accountable decisions and linked evidence.
  • Integration mappings, business rules and acceptance criteria are reviewed with the customer.
Operating rules by business workflow
  • For collection of existing medication information, the record retains an accountable owner, its supporting evidence and accepted outcome.
  • For pharmacist-led reconciliation, adjustments require source evidence, a recorded reason and authorised financial review.
  • For discrepancies requiring prescriber review, evidence, reviewer authority and acceptance conditions are visible before a reviewed outcome is accepted.
  • For approved changes, a decision retains its authority, reason, supporting evidence and resulting obligations.
  • For discharge handovers, a receiving owner, evidence of acceptance and unresolved obligations are recorded before a handover closes.
  • 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

Reconciliation itemCollection of existing medication informationPharmacist-led reconciliationDiscrepancies requiring prescriber reviewChangesDischarge handoversDecisionSupporting evidenceActivity history
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.
  • Collection of existing medication information reference — Link the relevant collection of existing medication information to the operating transaction and its decision evidence.
  • Pharmacist-led reconciliation reference — Link the relevant pharmacist-led reconciliation to the operating transaction and its decision evidence.
  • Discrepancies requiring prescriber review reference — Link the relevant discrepancies requiring prescriber review to the operating transaction and its decision evidence.
  • Changes reference — Link the relevant changes to the operating transaction and its decision evidence.
  • Discharge handovers reference — Link the relevant discharge handovers to the operating transaction and its decision evidence.

Systems and interfaces

  • Patient administration and care records
  • Approved booking, clinical or service interfaces
  • Identity and role-based access services
  • Approved document and communication services

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

Implementation requirements
Confirm the operating boundaries, collection of existing medication information, responsible roles, review authority, record retention, interface mappings and acceptance scenarios.

Mobile and tablet access

Authorised users can review collection of existing medication information, supporting records and assigned actions through mobile and tablet access. The relevant tasks and permissions are agreed for the deployment.

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

Apple App Store ↗Google Play ↗

AI extensions

Core workflows and approval rules are defined with your business owners. Operational AI can be assessed separately against a specific business outcome and review requirements.

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.

Start with collection of existing medication information and follow the record through reconcile the position. Introduce a missing item or operating exception, record the authorised resolution and inspect the final handover, evidence and history.

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.

What can we review in a tailored demonstration?

Review a representative reconciliation item, its workflow stages, accountable roles, an exception and the resulting operational report. Bring the business process and existing system requirements that matter to your organisation.

How is the solution adapted to our organisation?

The operating scope covers your records, role permissions, review authority, business rules and integration boundaries. These requirements are agreed with the responsible business owners.

How does the solution connect with existing systems?

Connection design defines interfaces, data ownership, mapping, authentication and exception handling. The agreed implementation includes validation against the selected systems and workflows.

How are subsequent changes controlled?

The agreed engineering approach covers review of change impact, bounded implementation, validation and accepted revisions. Discuss the relevant Genesis Context Memory and support requirements during solution scoping.