Receive RSV and Pertussis Vaccinations via Digital Medicines and Pharmacy FHIR Payload
- Alan Gordon
ID | RM239 |
|---|---|
Version | 2.0.0 |
Type | Roadmap Item |
Contracting Vehicle(s) |
Title | Receive RSV and Pertussis Vaccinations via Digital Medicines and Pharmacy FHIR Payload |
|---|---|
Description | RSV and Pertussis Vaccination information for Patients to be received via the existing Digital Medicines and Pharmacy FHIR Payload |
Date Added | Jun 11, 2024 |
Standards and Capabilities | |
Change Route | Managed Capacity - Minor/Patch uplifts |
Change Type | Uplift |
Status | Published |
Publication Date | Jul 18, 2024 |
Effective Date | Oct 18, 2024 |
Incentives / Funding | TBC |
Incentive / Funding Dates | TBC |
Background
To protect the population (particularly older adults and infants) this winter, a new immunisation programme against Respiratory Syncytial Virus (RSV) is being introduced in September 2024. RSV is a leading cause of GP appointments, hospitalisations, ICU stays and deaths every year in the UK.
To address the increasing number of vaccine-avoidable Pertussis (whooping cough) infant deaths, there will be a range of catch-up activities to drive uptake of the vaccination in pregnant women and improve records of these events.
Both programmes will be carried out in a range of clinical settings, meaning that we must have a way to flow a record of a vaccination from Data Processing Service (DPS) to Patients’ registered GP Practices by the start of the RSV campaign in September. This will enable accurate records, including to support the response to vaccine adverse reaction and help avoid duplicate vaccination of Patients.
Planned strategic data flow developments will not be in place to meet the needs of these programmes, so we need an alternative in place for September.Â
We have applied updates to the Requirements and Documentation sections inline with the updated structure for DSIC Standards.
Outline Plan
Existing GP Practice Solutions to receive RSV and Pertussis Vaccinations via Digital Medicines and Pharmacy FHIR Payload for ingestion, by 01/09/2024
Please allow 1 month for NHSE assurance.
NHSE Vaccination Digital Services (VDS) team to send a sample file to the Suppliers by 01/07/2024 followed by additional files to support assurance once the full list of Product and Procedure Codes are defined, currently targeting end 31/07/2024.
The Digital Medicines and Pharmacy FHIR Payload specification remains unchanged and therefore, RSV and Pertussis will look the same as COVID and Flu, with the exception of two new titles, a new Procedure, Product Terms and Codes.
<title value="RSV Vaccination Record"/>
<title value="Pertussis Vaccination Record"/>
Note: this change is for Suppliers of services which ARE currently deployed into an operational environment only.
Summary of Change
Digital Medicines and Pharmacy FHIR Payload: Requirement DMPF1 and DMPF2 updated | ||
ID | Requirement | Level |
DMPF1 | Pharmacy Immunisation Vaccination Administration Implement and maintain the vaccination Digital Medicines and Pharmacy FHIR Payload inline with the latest specification version A to receive notifications of the FHIR Document used to notify a Patient’s registered GP Practice on the administration of vaccinations to a Patient at a Pharmacy another Health or Care Organisation. The following vaccinations to be supported:
| MUST |
DMPF2 | Pharmacy Emergency Medication SupplyÂImplement and maintain the Pharmacy Emergency Medication Supply Digital Medicines and Pharmacy FHIR Payload inline with the latest specification version to receive notifications of A FHIR Document used to notify a Patient’s registered GP Practice of emergency medication(s) supplied to a Patient at a Pharmacy. | MUST |
Digital Medicines and Pharmacy FHIR Payload: Documentation updated |
The latest version of Digital Medicines specifications can be accessed here: Digital Medicine - FHIR - NHS England Digital  (Reference links: API and integration catalogue - NHS England Digital). The first stage of the standard is now published and details the information that should be recorded for vaccinations administered and emergency medicines supplied by community pharmacists. The MVP states that Suppliers are expected to process the unstructured messages upon entry to the framework in order to compliantly implement any use cases. However, there will be a future requirement for Suppliers to further enhance their Solutions to ensure the messages are processed in a structured format. |
Full Specification
Digital Medicines and Pharmacy FHIR Payload v3.0.0
Assurance Approach
Digital Medicines and Pharmacy FHIR Payload FHIR Vaccinations flow – NHS England to GP Practice Solution
In Scope
Assure that the GP Practice Solution can auto-ingest new vaccination records into their system, displaying them correctly and uncorrupted.
Assure uploading of information to Summary Care Record (SCR).
Assure that the GP Practice Solution can ingest vaccination records into their system, allowing relevant staff to assess the updates and perform ingestion.
Update of clinical safety documentation and complete clinical assurance to secure Clinical Authority To Release (CATR).
Out-of-Scope for NHS England central assurance but expected to be in-scope of Supplier’s own internal testing and assurance Â
Non-functional assurance e.g. can the Suppliers support the expected volumes due to the additional load of RSV and Pertussis Vaccinations data. Supplier expected to provide self-certifying statement(s) as confirmatory evidence.
Transfer of RSV and Pertussis Vaccinations data in the GP2GP transfers. Supplier expected to provide self-certifying statement(s) as confirmatory evidence.
Provisioning of the RSV and Pertussis Vaccinations data to the consumer suppliers through the existing GP Connect API capabilities and IM1 capabilities. Supplier expected to provide self-certifying statement(s) as confirmatory evidence.
Migration of the RSV and Pertussis Vaccinations data in the data extracts for GP Practice migrations. Supplier expected to provide self-certifying statement(s) as confirmatory evidence.
Regression testing to confirm no adverse impact on compliance of the existing capabilities, overarching standards and interoperability standards. Supplier expected to provide self-certifying statement(s) as confirmatory evidence.
Any other data flows downstream of the GP Practice.
Â