ChairScott Robertson
Commentsoverlapped with NCPDP VBA Stakeholder meeting

Dial-in Number

phone: 669-900-6833, meeting 3231998494#

voip/iOS/Android:  tel:+16699006833,,3231998494#  US (San Jose CA)

Find your local number:

Web session


Scott Robertson

Kaiser Permanente NCPDP/HL7x

Cathy Graeff


Kristol ChismChange Healthcarekristol.chism@changehealthcare.comNCPDP
Margaret WeikerNCPDPmweiker@ncpdp.orgNCPDP
Kristina McCannCoverMyMedskmccann@covermymeds.comNCPDP
Leann LewisEHR Dataleann.lewis@ehrdata.comNCPDP
Susan M RhodusGeriMed, Inc.srhodus@gerimedgso.comNCPDP
Shelly SpiroPharmacy HIT Collaborativeshelly@pharmacyhit.orgNCPDP/HL7
Gary SchoettmerNetRx LLCgary@netrx.orgNCPDP
Sandi MitchellVASandra.mitchell@va.govHL7
Scotty Armstead
John HatemIndependent Consultant
Joe QuinnSmile CDRjoseph.quinn@smilecdr.comHL7


FHIR IG vs Guidance Document

  • During the HL7 May 2022 WGM, Pharmacy WG strongly suggested to create a FHIR IG rather than a guidance document.  The thought being that a FHIR IG would be more visible to the vendors using FHIR.
  • Subsequently, I started the paperwork to alter the PSS and establish a FHIR IG
  • It was pointed out to me that I agreed to the IG, but the group was not asked
  • On the June 2nd Consultant Pharmacist Interoperability call, the group discussed the issue and decided to stay with a guidance document


Editorial Issues

  •  review/change LTPAC-specific language to be more general (not within use cases) (sections 1-3) - Gary
    •  Sections 1-3

FHIR IG Progress

  • create FHIR development environment
    • establish FHIR repository
    • update PSS
      • draft 
      • Pharmacy approval
      • StrucDoc approval
      • open review
      • TSC approval
    • FHIR IG request
      • draft
      • Pharmacy approval
      • StrucDoc approval
      • open review
      • FHIR-I approval

Review for the correct mapping to CCDA and FHIR

vocabulary and constraint issues

  • identify all code sets/vocabularies (section 5) - where a field is assigned to a specific set of terms.  are these SNOMED, LOINC, HL7, NCPDP
  • identify all constraints (section 5) - where a field is set to a (one and only one) specific value.  are these SNOMED, LOINC, HL7, NCPDP

New use cases

  • senior living 

  • specialty pharmacy 
  • pharmacy clinic (geriatric, CHF, diabetes, etc.)
  • pharmacogenomics
  • potentially Part D MTM:  CMR patient take-away format specified by CMS.  no consult note required, no regulatory requirement to communicate output to other clinicians; some?/most?/all? Programs have some type of reporting (similar to a consultation note).  Is this something to include/suggest in the document.

How does information blocking apply?

  • the information must be provided (available) to the patient
  • if appropriately asked (other than patient - payer, clinician, etc.), information must be provided
    • includes routine "search requests" for information that may be available
  • is it "blocking" if the information is not generally released??  If you don't know where to send the information, is it blocking?
  • information can/should/must be provided in a form that addresses USCDI data classes and clinical document types 
  • Do we need to include something about information blocking in our document?
    • not at this time

Any Other Business

Next meeting

Monday, June 27, 2022  1 pm ET / 10 am PT

  • No labels