-
Notifications
You must be signed in to change notification settings - Fork 0
Home
The aim of this project was to find a mapping from DM+D codes to BNF chapters. We've used an available mapping published by NHS to evaluate it's accuracy on our project specific data. https://www.nhsbsa.nhs.uk/prescription-data/understanding-our-data/bnf-snomed-mapping
This guidance has been updated to reflect the move to a single drug databse aligned to dm+d.
The BNF / Snomed mapping file published by the NHS Business Services Authority (NHSBSA) represents mapping of BNF Codes to Dictionary of Medicines and Devices (dm+d) Snomed codes.
The dataset shows one row for every VMP / AMP / VMPP / AMPP record and a field showing which BNF code this maps to. The data published early April 2020 contains information relating to January 2020 and we plan to continue to publish refreshed data on a monthly basis thereafter with the data relating to the latest available dispensing months data in ePACT2 at the time of publication, for example data published by the end of April 2020 containing data relating to February 2020 dispensed prescriptions.
What the document contains
The BNF Snomed mapping document contains:
- Indication of presentation / pack level
- Indication of VMP/AMP/VMPP/AMPP level
- BNF Code
- BNF Description at presentation level
- Snomed code at VMP/AMP/VMPP/AMPP level
- dm+d description at presentation and pack level
- Strength
- Unit of Measure
- Pack
- Sub pack
The Presentation / Pack level column and VMP / VMPP / AMP / AMPP column indicates if the row of data relates to a virtual (“VMP”) or actual (“AMP”) product.
The BNF description is used for reporting purposes and is truncated to be no longer than 60 characters for drugs and 100 characters for appliances.
Typically BNF codes are mapped to VMPs and AMPs but the corresponding BNF code is also mapped to a related VMPP/AMPP. In the mapping some records will not hold a BNF code or a BNF Description , these are typically parallel imports or secondary care products.
Please note that dm+d is subject to change via the normal processes and refreshed mapping data will reflect this.