/
Merge Cross-organisation Capabilities with non Cross-organisation versions

Merge Cross-organisation Capabilities with non Cross-organisation versions

ID

RM278

Version

1.0.0

Type

Roadmap Item

Contracting Vehicle(s)

Title

Merge Cross-organisation Capabilities with non Cross-organisation versions

Description

To merge Cross-organisation Custom Workflows with Custom Workflows and Cross-organisation Reporting with Reporting

Date Added

Oct 16, 2025

Standards and Capabilities

Custom Workflows, Reporting, Cross-organisation Custom Workflows, Cross-organisation Reporting

Change Route

Managed Capacity - Minor/Patch uplift

Change Type

Uplift

Status

Closed

Publication Date

Nov 25, 2025

Effective Date

Nov 25, 2025

Incentives / Funding

No

Incentive / Funding Dates

N/A

Background

Overlaps between the cross-organisation and non cross-organisation versions of the Custom Workflows and Reporting Capabilities have been identified. It has been determined that these Capabilities should be merged to reduce duplicated functionality and to consolidate the Capabilities and Standards model.

The Cross-organisation Custom Workflows and Cross-organisation Reporting Capabilities will be retired and the MUST Epics from these Capabilities will be added to the Custom Workflows and Reporting Capabilities as MAY Epics.

Outline Plan

N/A

Summary of Change

Cross-organisation Reporting: Status updated to Retired

ID

C26

Version

1.1.0

Type

Capability

Category

Reporting and data analytics

Status

Effective Retired

Effective Date

Mar 20, 2024

Contracting Vehicle(s)

Cross-organisation Custom Workflow: Status updated to Retired

ID

C24

Version

1.1.0

Type

Capability

Category

Health or care organisation management

Status

Effective Retired

Effective Date

Mar 26, 2024

Contracting Vehicle(s)

Custom Workflows: MAY Epic added

E00528 - manage cross-organisation custom Workflows

As a Health or Care Professional

I want to manage cross-organisation custom Workflows

So that I can manage Workflows that are customised across multiple Health or Care Organisations

Acceptance criterion 1: create a cross-organisation custom Workflow

Given the Health or Care Professional is permitted to manage cross-organisation custom Workflows

When the Health or Care Professional selects to create a cross-organisation custom Workflow

Then the cross-organisation custom Workflow is created

Acceptance criterion 2: view a cross-organisation custom Workflow

Given the Health or Care Professional is permitted to manage cross-organisation custom Workflows

When the Health or Care Professional selects to view a cross-organisation custom Workflow

Then the cross-organisation custom Workflow is displayed

Acceptance criterion 3: amend a cross-organisation custom Workflow

Given the Health or Care Professional is permitted to manage cross-organisation custom Workflows

When the Health or Care Professional selects to amend a cross-organisation custom Workflow

Then the cross-organisation custom Workflow is amended

Acceptance criterion 4: delete a cross-organisation custom Workflow

Given the Health or Care Professional is permitted to manage cross-organisation custom Workflows

When the Health or Care Professional selects to delete a cross-organisation custom Workflow

Then the cross-organisation custom Workflow is deleted

E00528 - Supporting Information

  • Examples of cross-organisation custom Workflows MAY include, but are not limited to:

    • The delivery of a Shared Care Plan across a range of service provider teams  

    • The review of a document (e.g. Care Plan) by all appropriate staff/organisations involved

    • The assessment of arrangements to support the transfer of a Patient (e.g. discharge from hospital to home)

    • An assessment by one or more Health or Care Professionals in different organisations which may trigger a subsequent referral of a Patient to external services

  • Examples of cross-organisation custom Workflow data MAY include, but are not limited to:

    • Workflow type

    • Workflow description

    • Creator

    • Creation date and time

    • Status (e.g. To Do, In Progress or Complete)

    • Workflow Event(s), including:

      • Sequential

      • Parallel 

      • Conditional

      • Manual

      • Automated time based (e.g. automatic updating of event after a certain time period has passed)

      • Automated data driven (e.g. automatic triggering of event based on data being recorded)

    • Supporting information (e.g. a link to a document or URL to external website)

    • Expected duration (e.g. time from generation to expected completion)

    • Assignee(s)

    • Priority

Reporting: MAY Epic added

Reporting: MAY Epic added

E00491 - reporting on data from multiple Health or Care Organisations

As a Health or Care Professional

I want to run reports based on data from multiple Health or Care Organisations

So that I can identify trends and track performance across multiple Health or Care Organisations

Acceptance criterion 1: define criteria for reporting on data from multiple Health or Care Organisations

Given the Health or Care Professional is permitted to create reports that cover multiple Health or Care Organisations

When the Health or Care Professional selects to define the criteria for a report

Then the Health or Care Professional can select from a range of data items

Acceptance criterion 2: view results from reports that cover multiple Health or Care Organisations

Given the Health or Care Professional is permitted to view report results that cover multiple Health or Care Organisations

When the Health or Care Professional selects to view a report that covers multiple Health or Care Organisations

Then the report results are displayed

E00491 - Additional Implementation Details

Solutions MUST comply with the following when implementing this Epic:

  • Provide the ability to report on a range of data items provided by achieving compliance with multiple different Capabilities (data items can be provided by one or more Solutions)

E00491 - Supporting Information

  • Examples of reports MAY include, but are not limited to:

    • Profit-analysis per Health or Care Organisation

    • Number of medicine reviews completed

    • Comparing Patient/Service User feedback metrics against target feedback ratings

    • Identifying trends such as the relationship between the timing of home visits and subsequent A&E attendance

  • Report criteria MAY include, but are not limited to:

    • Any combination of coded or structured data held within or linked to the Patient/Service User Record

    • Historic and future dates or date ranges (to allow for reports to be setup ahead of time to report on future events)

    • Defined time periods (e.g. in the last 6 months)

    • Inclusion or exclusion of deceased or inactive Patients/Service Users

    • Data items which are no longer active or are prevented from ongoing use in Patient/Service User Records

  • It is recommended that reporting functions are available at all times when the Solution is available for use

  • It is recommended that data used in reporting is fully up to date to enable decisions to be made without compromising Patient/Service User care

  • For coded data, see Data Standards for requirements

Full Specification

The updated Custom Workflows and Reporting Capabilities will be added at a later date. Proposed changes can be viewed in the Summary of Change above.

Assurance Approach

New MAY requirements have been added in the form of MAY Epics which describe additional functionality. MAY Epics describe additional functionality and these can be selected by Suppliers, but are not mandatory. If selected, Suppliers will be assessed against this Epic as per the Capability Assessment process and this will be a high level assessment based on the Acceptance Criteria defined.