1 / 12

EMIS dm+d Implementation

EMIS dm+d Implementation. Dr Jonathan Meadows. Current EMIS Database. Lists all currently available UK licensed products including Drug Tariff of England & Wales Each preparation description : approved name + form + strength eg ‘Amoxicillin’ + ‘Tablets’ + ‘500 mg’

jens
Download Presentation

EMIS dm+d Implementation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EMIS dm+d Implementation Dr Jonathan Meadows

  2. Current EMIS Database • Lists all currently available UK licensed products including Drug Tariff of England & Wales Each preparation description : approved name + form + strength eg ‘Amoxicillin’ + ‘Tablets’ + ‘500 mg’ • This allows grouping under approved names or within the EMIS Drug Groups (similar to BNF hierarchy) • Each supported by constituents (also coded) • Considerable number of attributes for prescribing and dispensing

  3. EMIS Database Maintenance • Database managed by qualified team. Application allows rapid updating. • New data requests are added to the central database and can be placed on the distribution update system (EMIS Patch) within 8 hours. • Within 48 hours 75% of sites will have a new addition or other field property change (GV & PCS 100% in 24 hours) • Approximately 15,000 GP’s collect update within 7 working days

  4. EMIS Data Model

  5. EMIS – dm+d Implementation Phase I, Mapping Exercise

  6. Automation of dm+d Processing • Automate wherever possible • Scheduled collection of each weekly update of the dm+d release from the PPA web server, with processing into an EMIS staging database using SQL Server Data Transformation Services • Unmatched VMP and AMP’s are fed into the Drug Matching Application

  7. EMIS Mapping Exercise • Qualified pharmaceutical & clinical staff • Specific mapping tool developed with implicit rules • One to one mapping enforced • Retirement of unmatchable EMIS preparations • New additions to EMIS of equivalent dm+d descriptions • QA exercise, every mapping is scrutinised by two clinical teams operating independently within the Department of Coding and Drug Information. • Further validation by PPA, possible extension of the NHSIA Read Map Validation Service – IA-03-0214 to apply to dm+d • Following validation process commitment of each approved mapping will then made into the distributed Clinical Systems

  8. EMIS Drug Match Utility

  9. EMIS Phase I Implementation • Phase I has little impact on existing clinical system algorithms and application code that relies on: • BNF Group and Emis Drug Group codes • Approved name / Drug form / preparation codes • Manipulation of existing codes provides user picking lists, alerts, interaction checking, pack and price and decision support information (BNF) • Phase I will allow FP10 dm+d coding as specified in the Implementation Guidelines using both the dictionary long name and SNOMED CT identifier

  10. Interoperability (FP10) and the PPA For each FP10 item: (current proposal) • On a separate line: Right Justified SNOMED CT identifier • Followed by the dictionary long name • Dosage and quantity information

  11. Phase I Progress • 60% - 3107/5173 VMP’s (5995) • Multi-constituent generic descriptions • Generic appliances/dressings • 43% - 4915/11321 AMP’s (14025) • ACBS products • Appliances • Actual generic products (Name + Manufacturer) • Target for June 2004: • Full Mapping at VMP/AMP level • SNOMED CT code on FP10

  12. EMIS Phase II Implementation • Full integration of the dm+d into the EMIS products • Mapping of constituents • Forms • packs Why? • Enable clinical system interoperability between diverse clinical systems for exchange of information on medicines and devices. • To bring in benefit from the additional information elements • Decrease the required maintenance of the EMIS Drug Database by using a nationally recognised product • Latter half of 2004

More Related