...

Capabilities are the distinct functions a business needs, and often directly map to modules or functions which a Solution may provide. This is a step change away from having Principal and Subsidiary systems. The introduction of Capabilities for GP IT Futures is intended to allow Suppliers to innovate by being less prescriptive and also to segment the requirements in a way to allow more flexibility and choice for buyers. The scope of what historically made up the Principal Clinical Systems has now been broken down into Capabilities.

Structure of a Capability

Each Capability will have an ID, title, description, outcomes, epics and acceptance criteria and then potentially other elements to give more detail as necessary. This section describes the structure of a Capability and the information within it.

Capability ID

Each Capability has a unique identifier composed of one letter followed by a number. The letter C indicates a Capability. The number is arbitrary and does not have any additional meaning such as priority, sequence or inter-relationships. This allows for the identification of Capabilities in a consistent manner.

...

Each Capability has a version number. Version numbers will iterate depending on the nature of the change (e.g. major, minor, patch) impacting the Capability. There is no relationship between the version numbers of different Capabilities and Standards.

...

A concise description of the purpose of the Capability.

Outcomes

This describes the main users of the Capability and the outcomes they want to achieve from using the Solution.

Epics and acceptance criteria

These describe the requirements of the Capability at a high level and will be used to assess the suitability of Solutions from suppliers at the Capabilities Assessment stage of onboarding.

The Epics are written as high level user stories with Acceptance Criteria describing the conditions which can be demonstrated for the user stories to be considered achieved.  The collection of Epics which make up the qualifying component of each Capability description, simply describe the minimum functions that a Catalogue Solution must be able to demonstrate in order to be classified as achieving the Capability in question.

Suppliers will be assessed against 'Must' Epics only. 'May' Epics may be detailed for information.

...

A set of Foundation Capabilities have been identified which will be the access point for GMS funding. These are a subset of the wider set of Capabilities mandated in the NHS England GP IT Operating Model.  The Foundation Capabilities are clearly identified on the Capability and Standards Model.  Suppliers do not have to supply any of the Foundation Capabilities and can choose to provide one or more.  Buyers will have to take all of the Foundation Capabilities in order to access central funding.

Standards

...

1. Overarching Standards (e.g. Information Governance) 
   These will be applicable to all Supplier Solutions and are NHS Digital Standards reasonably agnostic of care setting.
2. Capability Specific Standards (e.g. Appointments Management - GP)
   These are only applicable to Supplier Solutions delivering a particular Capability and may contain business rules, data items and best practice.  
3. Context Specific Standards - these Standards are only applicable to some Supplier Solutions depending on the implementation and scope of Capabilities they are supporting.  Suppliers will have to go through compliance against these Standards per Solution offering.  These include:
   1. Interoperability Standards (e.g. GP Connect APIs, IM1, PDS, eRS and ePS integration etc.). These cover various mechanisms for interoperability and national integration.  Each entry will be mapped to one or many Capabilities. 
   2. Common Reporting - applicable to any Solution providing a Capability that has reporting requirements.
   3. Management Information Reporting - supports the collection and submission of information to NHS Digital.
   4. Citizen Access - applicable to any Solution providing Citizen facing Capabilities.

...

Each Standard has a version number. Version numbers will iterate depending on the nature of the change (e.g. major, minor, patch) impacting the Standard. There is no relationship between the version numbers of different Capabilities and Standards.

...

As defined in RFC 2119.1, the Change Management and Roadmap Content ancillary document and the Master Glossary

Use of Standards

Standards will be used by:

...

The Capabilities and Standards Model represents the scope of the first GP IT Futures Framework.  It is represented in a clickable form on the Confluence Overview page in order for all stakeholders to navigate through.

...

The live site can be accessed GP IT Futures Capabilities and Standards - Home

Change Management

...

The GP IT Futures Standards and Capabilities Roadmap ('the Roadmap') will provide a single, summary view of all the changes and opportunities for Suppliers regarding new and uplifted Standards and Capabilities, whichever route they are to be progressed through. This includes 'Horizon' items which GP IT Futures are aware of and are expecting to be progressed via the defined change routes at some point further into the future, but which have not yet been formally requested and may not materialise. The Roadmap will be the only mechanism by which changes in the Managed Capacity route will be commissioned. Changes following other routes will be commissioned via separate mechanisms as described abovein the Change Management and Roadmap Content ancillary document, but will still be displayed on the Roadmap for information purposes and to bring as much information as possible into one place. Further detail regarding the changes specified on the Roadmap, such as the parameters of open competitions, draft and final specifications and the change backlogs will be made available elsewhere, such as on Confluence.

Wherever possible, Standards with an Effective Date within the lifecycle of a Framework will be added to the Roadmap in advance of the commencement of that Framework to ensure Suppliers:

• have sufficient notice to be able to plan and complete development activities and achieve compliance
• can calculate the amount of capacity they will need to reserve and set a List Price for that Framework accordingly

However, additional Standards can also be added to the Roadmap at any time throughout the lifecycle of the Framework. If the agreed Effective Date falls within the lifecycle of that Framework there are commercial mechanisms available under the terms of the Catalogue and Framework Agreements for the Supplier to adjust their List Price if required.  If the Effective Date falls within the lifecycle of a subsequent Framework, then the capacity required for delivery of that Standard should be accounted for within the List Price set for that Framework. Changes progressing through any of the other change routes may also be added to the Roadmap at any point.

What information will be shown on the Roadmap?

The overarching Roadmap will . .

What information will be shown on the Roadmap?

The overarching Roadmap will include a summary of information to ensure Suppliers are fully aware of the changes that are required and the opportunities which are available to them. Some of the data items are common to all change routes, and other data items are specific to a particular change route. The table below sets out the information to be included. Horizon items are not included in this table as they will not have been assigned to a change route and there is likely to be limited information available about the change. Dependent on the final form presentation of the Roadmap, certain information, sch such as the change route, may not be given in distinct fields and may instead be represented in an alternate format, such as in labelled swim lanes or with colour coding or sections.

...

In addition to the overarching Roadmap, each Capability and Standard on Confluence contains a Roadmap section linking to a page which details any Roadmap items related to that Capability or Standard and the details of that change.  There is also a central Roadmap page on Confluence where a full list of Roadmap items will be available with a summary of information similar to the above.

Roadmap Content

The actual content and change items to be Effective for Day 1 and to be included on the Roadmap in the defined change routes is presented in tabular format on the Standards and Capabilities Roadmap pageThe Roadmap area of Confluence presents the details of the items on the Roadmap.