MEDICATION RECONCILIATION Using PH-Doc June 12, 2012 Presented by

1. MEDICATION RECONCILIATION Using PH-Doc June 12, 2012 Presented by Daniel Jensen, Associate Director of Public Health, Olmsted County Deb Castellanos, Technical Manager/Project Manager, Xerox Corporation

2. Powerpoint and Demo of the “PH-Doc” software Intellectual property of MCCC, powered by Xerox Corp.

3. Software installed in 28 local public health agencies in South East Minnesota What is local public health in MINNESOTA?

4. Public Health DocumentationSystem Software application owned and managed by the users long-standing relationship with the developers First program written in 1984 “Re-engineered” several times over 28 years Electronic Chart and Practice Management System

5. Years 2008 - 2012 “re-engineering for interoperability” when along came the SE Minnesota Beacon Project Community of hospitals, clinics, counties and schools sharing clinical health information Mayo Clinic – GE’s EMR Mayo Health Systems – Cerner’s EMR Olmsted Medical Center – Med3000’s EMR Winona Health – Cerner’s EMR Allina Health – Epic’s EMR 11 counties in SE MN – PH-Doc Health Record 46 school districts in SE MN - PH-Doc Portal

6. SE Minnesota Beacon Project April 2010 – April 2013 • These clinics, hospitals and counties are exchanging clinical data using the National Health Information “NwHIN” specifications and open source software; GATEWAY at each site with the ability to perform peer-to-peer communications • Uses SOAP webservices over HTTPS • Wraps payload in SAML assertions • Includes auditing and logging • Enables the exchange of CDA Documents

7. What is a CDA Document? Structured XML document based on the HL7 V3 RIM activities, entities, participants, roles, moods Standard HEADER section patient information, title, date, author, custodian, authenticator Sections of clinical content – preferably structured and coded medications, allergies, problems, immunizations, vital signs, procedures, advance directives, payers, results, plan of care, family history, social history, pregnancy, visit notes, comments

11. Under the Beacon project … several enhancements were made to PH-Doc o  structured medications and allergies RXNORM, UNI, NUI, Snomedo  structured CDA documents Summary of Care, Laboratory Studies, Asthma Action Plans Public Health CDA (environmental, social factors, behavioral factors) o  live feeds to Regenstrief Institute patient visits and quality of life indicators

12. Under the Beacon project … infrastructure was added to each county to host its gateway An appliance (from Mirth corporation) was ordered for each of the 11 counties

13. Mirth Appliance The appliance hosts communication services; SFTP, HTTP, WebServices, LLP … … and includes the Aurion Gateway … ‘open source’ with support

14. Mayo Clinic Mayo Health Olmsted Medical PH-Doc Application Server DMZ Winona Health Allina Health MIRTH • Connect • Gateway • Patient Correlation • Security and Authentication • Audits and Logs Internet Public Health Nurse 14

15. Outgoing REQUEST – one per patient • Patient Demographics – used to match at destination site • Requestor – name and Role • Purpose for request • Destination Gateway(s) – based on Release of Information • Type of document(s)

17. Each request becomes a thread Don’t want to tie up the nurse. Depending on number of documents and gateways, could take a few minutes ALERT when the request has finished processing Status of documents that have been pulled Each document stored as XML with stylesheet Each document rendered/stored as PDF Each document parsed for structured data

20. Parsing the Coded Data .NET shop Used C# and XPATH Specifications from HITSP C32 C83 C80 C154

21. Parsing the CCD Mayo Mayo Details from HITSP C80/C83 Structured data elements & code tables To develop our parsing rules 21

22. Parsing the CCD Details from HITSP C80/C83 Structured data elements & code tables To develop our parsing rules 22

23. 23

24. Now that we have parsed data… able to tackle “reconciliation” As defined by the JACHO, medication reconciliation is "the process of comparing a patient's medication orders to all of the medications that the patient has been taking. This reconciliation is done to avoid medication errors such as omissions, duplications, dosing errors, or drug interactions. It should be done at every transition of care in which new medications are ordered or existing orders are rewritten. Transitions in care include changes in setting, service, practitioner or level of care. “

25. … we’ve done it before … • Designed as an INTERACTIVE process • nurses working with the patient in the home/school/jail • Our first reconciliation screen dealt with IMMUNIZATION data coming from the state of Minnesota’s IMMUNIZATION registry • Used a secure webservice to request data. We used the codes • we received from the state and mapped to CPT/CVX codes.

27. Design Standards Side by side presentation of two lists Pink coding identifies information missing from PH-Doc Easy drag and drop (or click multiples and press ARROW)

28. Medication Reconciliation • Even better …. • RXNORM codes • Multiple sources • More data – dosing, physician, reaction, text • Current and History

30. Medication Reconciliation • Nurse works with the patient to reconcile the two lists • Sometime multiple sources - pull most recent and show others • Pull to current vs pull to history • “History” – requires REASON – only text today. Hope to make this more robust, able to share these reasons with clinicians • “Too expensive” • “Upsets my stomach” • “Heard rumors about possible side effects”

31. Once an accurate medication list has been documented … hopefully all associated with RXNORM codes Time for DRUG-TO-DRUG interactions check

35. Allergy Reconciliation • Same concept for reconciling allergies • Request external documents • Parse data and store in ‘auxiliary tables’ • Present side-by-side • Allow external data to be merged with existing data