PDMP & HITI IG Development Workgroup Session August 14, 2014

Meeting Etiquette Remember: If you are not speaking keep your phone on mute Do not put your phone on hold – if you need to take a call, hang up and dial in again when finished with your other call – Hold = Elevator Music = very frustrated speakers and participants This meeting, like all of our meeting is being recorded – Another reason to keep your phone on mute when not speaking Feel free to use the “Chat” feature for questions, comments or any items you would like the moderator or participants to know. NOTE: This meeting is being recorded and will be posted on the Meeting Artifacts Wiki page after the meeting From S&I Framework to Participants: Hi everyone: remember to keep your phone on mute 2

Agenda 1.Review transformation detail sections for SCRIPT, HL7 V2, and ASAP Web Services 2.Review identified gaps for NCPDP SCRIPT and HL7 V2 a)Determine gap mitigation 3.Discuss message structure, conformance statements, & coded examples for HL7 V2 4.Discuss Roles & Role ID value set

Harmonization Weekly Timeline (cont’d) Week Target Date (2014) All Hands + IG WG Meeting Tasks Review & Comments from Community via Wiki page (Due End of Week on Friday) 1-153/25-7/8Completed Harmonization Kick-off through Solution Planning 167/15 Finalize: Introduction of IG (Section 1) Introduce: Pre-conditions/Post-conditions (Section 1.6) & Implementation Approach Solution Plan (2.1) Review: Pre-conditions/Post-Conditions; Solution Plan (Overview and Standards) Review: Data Element Request/Response Mappings to PMIX-NIEM 177/22 Finalize: Request Data Element Mappings Introduce: Standards and Request Transactions Review: Response Data Element Mappings & supporting IG content Request Details 187/29 Review: Request Transaction Details in IG & Response Data Element Mappings Introduce: Response Transaction Details Review: Response Transaction Details 198/5 Finalize: Request details /Response Data Elements Introduce: Transformation Details (Request) Review: Request Transformation Details between NCPDP, HL7 V2.0, ASAP to PMIX-NIEM; Identify/document gaps 208/12 Finalize: Request Transformation Details Review: Response Mappings & Transformation details Review: Response Mappings/Transformation Details 218/19 Introduce: Conformance Statements Introduce: Transport/Security Introduce : Suggested Enhancements (Section 3) Review: Conformance Statements, Transport/Security, & Suggested Enhancements 228/26Begin: End-to-End Community Review of Implementation GuideReview: Implementation Guide (End-to-End)

Gap Mitigation for Request Translation/ D.E. Mappings StandardData Element Gaps IdentifiedMitigation ASAP Web Services Requestor Requestor Role Disclosing States Requesting State Request ID Option 1: Add required elements to transport layer envelope Option 2: Propose modifications as suggested enhancements to ASAP Web Service specification NCPDP SCRIPT Requestor Requestor Role Disclosing States* Requesting State/State code of Requesting Facility* Request ID (“Message ID”) Facility Name (“Pharmacy name”) Option 1: Propose modifications as suggested enhancements to SCRIPT Medication History standard in new iteration of NCPDP SCRIPT 10.6 Option 2: Include data elements within wrapper transport layer (not favorable) **Requesting state will be consumed by State code of facility (look to pilot feedback for modifications) HL7 V2.7 Requestor Requestor Role Disclosing States Requesting State Request Date/Timestamp Option 1: Add required elements to transport layer envelope Option 2: Propose modifications as new HL7V2.7 Z Segment QBP message elements

Gap Mitigation for Response Translation/ D.E. Mappings StandardData Element Gaps IdentifiedMitigation ASAP Web Services Refills Authorized AI: Bill Lockwood to verify Option 1: Add required elements to transport layer envelope Option 2: Propose modifications as suggested enhancements to ASAP Web Service specification NCPDP SCRIPT Patient ID (State of License, Passport, Military, Tribal) Would be dropped Partial Fill Indicator* To be added to new version (long-term solution) Method of Payment* Option 1: Propose modifications as suggested enhancements to SCRIPT Medication History standard in new version of NCPDP SCRIPT Option 2: Include data elements within wrapper transport layer (not favorable) *To be discussed with task group HL7 V2.7 Method of Payment Response Date/Timestamp Responding States Request ID Option 1: Add required elements to transport layer envelope Option 2: Propose modifications as new HL7V2.7 Z Segment QBP message elements

Outstanding Questions Routing Information data elements –Requestor, Requestor Role, Disclosing States, Requesting States, Request ID How are these handled in SCRIPT and V2? What is the message structure for each of these standards? Request ID is sent back in the Response –Requestor, Requestor Role, and Requested States are not sent back Role & Role ID List of Roles Accepted by PDMP Hubs Physician Pharmacist Pharmacist with prescriptive authority Nurse Practitioner Psychologist with prescriptive authority Optometrist with prescriptive authority Dentist Naturopathic physician with prescriptive authority Physician assistant with prescriptive authority Medical resident with prescriptive authority Medical intern with prescriptive authority

Next Steps Review: Implementation Approach – Transformation Details, Coded Examples, Conformance Statements Next All Hands meeting is Tuesday, 8/19 from 12:00 pm to 1:30 pm ET o Review IG content Next IG Development Workgroup Session is Thursday, 8/21 from 12:00 pm to 1:30 pm ET Reminder: All PDMP & HIT Integration Announcements, Meeting Schedules, Agendas, Minutes, Reference Materials, Harmonization materials, Use Case, Project Charter and general information will be posted on the PDMP Wiki page – Homepagehttp://wiki.siframework.org/PDMP+%26+Health+IT+Integration+ Homepage