Downloaded 12 times
Uploaded byIan McNicoll
UK Dose syntax and medication archetypes apr 2015
This document discusses developing a standardized computable "dose syntax" for representing community medication information across different healthcare systems. It proposes a solution that combines an openEHR archetype structural model with a parsable syntax to capture dose amounts and timings. Examples of the syntax are provided to represent prescriptions like "10mg twice daily" in a way that is computable. The goal is to improve medication reconciliation at care transitions by making prescription data electronically exchangeable and analyzable across primary, community, and secondary care settings. Feedback is sought on implementing this approach.
More Related Content
Similar to UK Dose syntax and medication archetypes apr 2015
UK Dose syntax and medication archetypes apr 2015
- 1. A Dose syntaxfor community medication? Dr Ian McNicoll SCIMP HANDIHealth openEHR Gyle meeting April 2015
- 2. Introduction Former Clydebank GP HealthInformatician since 2000 freshEHR Clinical Informatics Co-chair openEHR Board SCIMP HANDIHealth Commercial software developer ‘GP Accounts’
- 3. Community medication stakeholders GPs Nursing Mental healthteams, Pharmacy Secondary care inpatients Secondary care outpatients Nursing homes Unscheduled care Patients GP prescriptions anticipatory care supply repeat dispensing transitions of care own supply patient access patient-led reconciliation
- 4. Current position No clearvisibility of other prescribers actions Patient often only the knows the whole picture No clear governance Non- standardised representation of medication between systems
- 5. What’s the solution? ‘Closingthe Loop’ commission ‘patient medication record’ ‘community’ record Inpatient prescribing excluded other than at transitions of care
- 6.
- 7. Danish single medicationrecord database
- 8. The interoperability challenges Howdo we resolve the ‘wicked’ interoperability issues? Standardised, computable ‘medication models’ ‘Medication event’ vs. ‘Medication statement’ Product vs. dose based prescriptions Computable dose amounts / timings’
- 9. NHSS Medication Models Basedon GP2GP medication models merge in requirements for ECS / KIS / ePharmacy / SCI-GW Other UK models : SCR, IHR, EPS2 Aligned with PRSB / RCP Headings Can we persuade systems suppliers to adopt?
- 10. Modelling approach Based onopenEHR but technology neutral models of ‘clinical content’ Exchange -> messages / APIs SCI-XML, GP2GP, HL7 FHIR inte can be used natively inside openEHR-based systems Aligned with dm+d, CUI
- 11. open, shared datamodels - ‘Archetypes • Clinically-led + collaboratively authored – open-source ‘crowd-sourcing’ methodology – Shared open repository ‘CC-BY-SA’ licence • Agility in response to continually changing clinical demand – Clear ownership, change request mechanism – Tight version control
- 12. GP2GP ‘medication item’archetype
- 13. Product vs dosebased prescribing Unavoidable due to difference in the process of inpatient vs. outpatient prescribing Dose: Product:
- 14. Dose syntax?? How canwe capture a prescription like … “Co-codamol 8mg/500mg/5ml oral suspension 5- 10mls 4-6hourly for 7 days for pain, maximum 40mls daily” that makes the drug name, dose amount, timing and maximum dosage computable
- 15. Dose syntax -aims GP, outpatient, community, transitions of care prescriptions support automated medicines reconciliation at transitions of care calculate Total Daily Dose for quality assessment purposes explore usage as data entry method Out of scope inpatient prescriptions complex GP prescriptions patient usage instructions ‘before meals, ‘take with water’
- 16. Dose syntax -sources Blue Wave / English NHS /CfH Dose syntax work Comprehensive, complex Low uptake Uni. Dundee ‘EBNF’ Dose syntax Successful use as research tool Confined to GP prescriptions
- 17.
- 18. CFH Abstract DoseSyntax
- 19. Uni. Dundee Parsabledose syntax
- 20. Archetype + Dose syntax Proposedsolution is a mix of archetype’ structural model + parsable syntax which carries dose amount + timing “10mg td” “3 n”
- 21.
- 22. “1 n:3d;1 m+pm& 2 n:4d"
- 23.
- 24.
- 29. IDCR Transfer ofCare Summary
- 30.
- 31. What’s next? Implementer feedback? Isthis implementable? Reference parser GUI challenge
- 32.