Skip to main content

Onboarding disease types and vaccines

The vaccination digital services programme key focus is on strategic disease type delivery and the value this will create to stakeholders. 

Overview

The vaccination Digital Services programme and the Capture and Flow tribe key focus is on strategic disease type delivery, and the value that this will realise across the landscape.

A framework is required that will enable the expansion of the FHIR® API capability to all S7a vaccines and create a repeatable consistent way to engage with stakeholders that will allow us to highlight constraints that may impact length of delivery.


Outcomes

  • clear set of definition of ready statements for each disease type
    • streamlining the process and providing a consistent set of pre-requisite documentation
    • allows clear due-diligence to be performed for new disease types from delivery models, to legal agreements
  • the new framework enables the imms FHIR API consumers quicker access to real time vaccination data upstream and downstream.
    • the benefit of this enabler will be realised by each of the consumers depending on their outcomes
  • the new imms v5 format consistency provides standardised data in a central location with a minimum level of data quality
    • this means consumers can create one solution to support all consistent disease types
  • a faster and consistent onboarding process for new disease types
    • allows consumers to quickly get access to data they have a commercial, legal and clinical right to

Value stream

Pre-requisites
  • JVCI engagement
  • Define definition of ready
Pre-requisites...
Ingestion
  • Disease type ingestion into DPS
Ingestion...
Migration
  • Disease type migration into Imms FHIR API
Migration...
Onboarding
  • Upstream & downstream consumers
Onboarding...
Value stream highlighting the different stages from engagement to onboarding

Prerequsites

National Policy Clinical Cell endorsement
National Policy Clin...
Agree direct care and/or reporting use cases
Agree direct care an...
Define stakeholder list and engage
Define stakeholder l...
Define national seasonal/campaign requirements
Define national seaso...
Define data entry points for a disease type
Define data entry po...
Define reporting output for a disease type
Define reporting out...
Define extended attribute requirements above the default imms 5.0 format
Define extended attribute...
Define existance and requirement to migrate historic disease type data
Define existance and r...
Define indicative timelines (if required)
Define indicative ti...
DoR Statements
DoR Statements
Document delivery model approval
Document delivery mo...
Document legal & commercial approval
Document legal & com...
Document funding stream approval for vaccine re-imbursement
Document funding stre...
Document governance approval
Document governance...
Document delivery timeline approval (if required)
Document delivery ti...
Document report approval
Document report appr...
Prerequisites for publishing DoR statements

Ingestion

Official request with DoR artefacts
Official request wit...
Front door process with resource allocated to the delivery roadmap
Front door process w...
Engagement with current ownersof historic vaccination event data
Engagement with curr...
Analysis of historic vaccination event data
Analysis of historic...
Data quality scoring and optional uplift
Data quality scoring...
Data store created in DPS
Data store created i...
Data migration into DPS
Data migration into...
Ingestionexception handling process and data storage
Ingestionexception h...
Verification of vaccination event data for reporting
Verification of vacc...
Statements, governance
& policy
Statements, governance...
DoR Statements
DoR Statements
Front door acceptance 
Front door accep...
Agreed commitments
Agreed commitmen...
GO/NO GO result
GO/NO GO result
Analysis output
Analysis output
Quality output
Quality output
Data store definition
Data store defin...
Source data
Source data
DPS data store
DPS data s...
Ingestion guidelines for disease types and vaccines

Migration

API teams informed of the new disease type migration
API teams informed o...
API configured to accommodate the new disease type
API configured to ac...
API sync process uplifted to include the new disease type data store in DPS
API sync process upl...
API one off migration defined from the results of volume analysis
API one off migratio...
API test migrations carried
API test migrations...
API migration takes place with full reconciliation
API migration takes...
DoR Statements
DoR Statements
Agreed config
Agreed config
DPS data store
DPS data s...
Reconciliation report
Reconciliation r...
IEDS
IEDS
Migration process for disease types and vaccines

Onboarding

Discuss uplift notice sent to registered consumers
Discuss uplift notic...
Consumer populates or updates 'Notification of Intent' form
Consumer populates...
Disease access team uses 'Notification of Intent' for onboarding
Disease access team...
Successful application adds to development sprint to uplift configuration
Successful applicatio...
Notification of intent
Notification of...
Comms
Comms
IEDS
IEDS
Yes
Yes
No
No
Success?
Success?
Onboarding process for disease types and vaccines

Last edited: 31 March 2025 3:02 pm