iPCV Flavours

iPCV is delivered through a range of “flavours” — predefined or custom-configured schemas that define the data scope, source systems and level of privacy applied. Organisations have different governance, privacy and analytical requirements; flavours enable the same iPCV platform to support a range of approved use cases while maintaining a consistent modelling approach.

Flavours are categorised as Standard Flavours or Bespoke Flavours and tailored to customers’ requirements in line with the applicable legal basis for data access.

Standard Flavours

Standard flavours provide the complete iPCV schema containing the full suite of clinical data models. They are fully identifiable, with no patient or clinical event filters applied.

• iPCV Vanilla: The schema for primary care data from EMIS Web.
• iPCV Foundation: The schema for primary care data from multiple GP system suppliers, providing a unified view across different systems and geographical footprints.
• iPCV Themis: Functionally identical to Vanilla but restricted to a specific cohort. This flavour enables a customer to load a defined list of patients, with iPCV processing and presenting the electronic health records only for those matching individuals.

Bespoke Flavours

Bespoke flavours are tailored implementations of iPCV, configured to meet specific governance, privacy and analytical requirements that are not covered by the Standard Flavours.

Configuration Capabilities

The configuration of an iPCV flavour is based on the requirements and instructions provided by the requesting customer. The customer provides the details needed to create and configure the flavour, which may include:

• Data Transformation: Converting personal data into pseudonymised or anonymised formats using hashing, masking, or obfuscation techniques.
• Schema Refinement: Removing specific data models or columns that are not required for a particular use case.
• Governance Filtering: Applying patient- or event-level exclusions, such as the National Data Opt-Out (NDOP) or the filtering of sensitive and confidential clinical codes.

Where these instructions align with pre-defined schemas, a Standard Flavour (such as Vanilla, Foundation, or Themis) is deployed. Where unique requirements are identified — such as specific hashing or column-level restrictions — a Bespoke Flavour is developed to meet those individual specifications.

Exclusions are applied as binary (include/exclude) selections. Requests for custom filters beyond standard configuration options are reviewed by the Product team.

Compliance and Data Stewardship

As data processor, EMIS implements the requirements provided by the requesting customer for the relevant iPCV flavour. The requesting customer is responsible for ensuring that these requirements are lawful and consistent with the legal basis and permissions agreed with the relevant data controllers for access to their patients’ electronic health records. This includes:

• Ensuring that the requested data access and configuration remain within that legal basis.
• Obtaining appropriate clinical, information governance and legal approval.
• Confirming that all instructions provided are consistent with the specific agreements held between the requesting customer and the data controller.

Governance and Authorisation

Following execution of a contract with the requesting customer, an iPCV flavour is surfaced only when both the technical configuration and legal processing authorisation are in place:

1. Customer Instructions: The requesting customer provides the technical configuration details required to build the flavour for its intended analytical purpose.
2. Data Controller Authorisation: The relevant data controllers activate a Data Sharing Agreement (DSA) in the source supplier system, providing the formal legal authorisation to process and surface the electronic health records to the customer.