Date

 

Chair
StatusPlanned
Comments

Dial-in Number

  • One tap mobile
    +13126266799,,3231998494# US (Chicago)
    +13462487799,,3231998494# US (Houston)
  • Dial by your location
    +1 312 626 6799 US (Chicago)
    +1 346 248 7799 US (Houston)
    +1 669 900 6833 US (San Jose)
    +1 929 436 2866 US (New York)
    +1 253 215 8782 US
    +1 301 715 8592 US
    Meeting ID: 323 199 8494
    Find your local number: https://zoom.us/u/aLIcTlITh

Web session

Attendees

NameOrganization
Melva Peters (Chair)

Jenaker Consulting

Peter SergentHL7 New Zealand
John HatemIndependent Consultant
Tim McNeilSurescript
Shelly SpiroPharmacy HIT Collaborative
Danielle Bancroft
Jean DuteauDuteau Design
Dave HillMITRE
Corey SpearsMITRE

Agenda Items and Notes

Meeting Notes from previous meeting

Project Review

Project Proposals

Project Scope Statements

New Work Group Formation Request

Discussion of MedicationKnowledge and possible issues for CDS

  • Jean working on getting Francois and Bryn's requirements incorporated - hope to have it in by the end of week
  • may need to include insurance plan in the MedKnowledge - to be able to specify what drugs are covered under a specific plan - need to come back to this discussion

Catalog Updates (John Hatem)

Workflow Update (John Hatem) 

  •  - Review tracker notes for #29261. 
    • The impact to Pharmacy is that we will need to remove both instantiatesUri and instantiatesCanonical.  The replacement will a series of elements that will modeled as Extensions.  

Healthcare Product Update (John Hatem)

    • Vote on Biologically Derived Product tracker 33068.  This tracker passed and represents the creation of the BDP resource as an Instance type resource.  There were other changes in moving various elements around within the resource.  This tracker passed.  I believe that this is consistent with Jean D's feedback .  See tracker notes. 
      • Will be an instance type resource 
      • Pharmacy will need to be able reference biologically derived product on a MedicationRequest
    • Other discussions today were related to Device and Device Definition trackers. 

NCPDP Updates (NCPDP Members)

NCPDP Task Group working on Patient Consent - for specialty prescribing -  Frank McKinney

Standardized Medication Profile - Standardized Medication Profile Jean Duteau

MTM - create FHIR IG Scott M. Robertson

  • revisit this discussion after MCC eCare plan is published (2023)

RealTime Pharmacy Benefit Check for Consumers (Tim McNeil/Frank McKinney)

  • met today
  • need to determine if this was mentioned in regulation
  • testing in January 2022 Connectathon

Consultant Pharmacist Task Force

  • proposal out for review
  • next step will be PSS

Global Supply Chain Project (Scott)

  • no discussion

Medication List Guidance project

  • targeting August 30th for discussion

PDex Formulary

  • want to move toward STU Update
  • 1 tracker may need to be approved
  • 5 items are compative,substantive and others are non-substantive
  • 20210823 - Formulary STU 1.1 Issues.pptx
  • FHIR-31031 - remove from examples 
    • Motion to approve - Dave Hill - Corey Spears - 8-0-0 Carried
  • Next Steps
    • Draft list of issues
    • email to stakeholders, Zulip, Pharmacy List - give them a 2 week review period - add comments to Jira trackers - add grouping to the specific issues
    • Motion to proceed with an STU Update - Dave Hill - Corey Spears -  
      • provide latest version of the list of 22 Jira issues
      • all have been approved on PDex Implementers call
      • 8-0-0 Carried
  • Structure of formulary for STU2 - will discuss on Catalog call on Friday
    • will add to Pharmacy agenda for next week - start the discussion

FHIR (Group)

Trackers - link to pharmacy unresolved Jira trackers 

Any Other Business

  • specifying "Port" by name in MedicationRequest - Zulip - https://chat.fhir.org/#narrow/stream/294552-Patient-Care.20WG/topic/Tracking.20drains.2C.20catheters.2C.20etc.2E - no discussion
    • When ordering a med admin, the order MAY occasionally specify the port by name (e.g. proximal port) -- but this seemed to PC as a potential gap in MedicationRequest since we couldn't locate a Device reference (need Pharmacy @Melva Peters to weigh in). In many cases, the MedRequest doesn't need to specify the port due to policy or clinical knowledge about where to administer (e.g. TPN)
    • For MedAdmin documentation, there is a MedicationAdministration.device, dosage.site, and/or bodySite (BodyStructure) extension available.
  • WGM Agenda

Next meeting

  • August 30, 2021 - 4pm Eastern
    • publication request for NHSN