Process for consent template updates

The majority of Concentric deployments use the core version of the Concentric Ontology, often with the addition of local, supplementary patient information leaflets to the Concentric consent templates (read about the process of adding local patient information).

Where local updates are required to the Concentric ontology these can be requested and are done in collaboration with the Concentric team. Requests should be managed centrally by the internal project manager as the single point of contact for content updates.

Requests are categorised into both size and priority by clinicians on the Concentric team.

Category examples


  • Small: Limited to a single template or a limited patient info (hyperlink) update
  • Medium: Updates to up to 10 templates or up to 5 new templates
  • Large: Updates to 10-20 templates or 5-10 new templates (larger requests should be broken down into smaller packages of work)


  • Low priority: Rarely used templates or easily configurable by user, e.g change indication on template
  • Medium priority: Relevant specialty go-live within 1 month, or common procedure but can be configured.
  • High priority: Significant clinical safety risk posed (e.g core risk omission)

Target delivery timeframes

The following are target delivery timeframes (based on size and priority) once all relevant information is shared with the Concentric team, in an agreed format, and for updates that fit within the existing structure of the Concentric application.

Low priority Medium priority High priority
Small 2 weeks 1 week 2 working days
Medium 4 weeks 2 weeks 1 week
Large 8 weeks 4 weeks 2 weeks

Concurrent requests

Content updates are subject to quality assurance and review processes as outlined in our standards and guidelines conformance statement. So that these processes can be met across all requests received from teams using Concentric globally, there is a maximum number of active requests that can be active from any organisation at any time. The maximum number of active requests is based on the organisation’s pricing tier.

Pricing tier Maximum active requests
Small 1
Medium 2
Large 3
Extra large 4