Skip to end of metadata
Go to start of metadata



Dial-in Number

  • 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:

Web session


Melva Peters (Chair)Jenaker Consulting
Jean DuteauDuteau Design
John HatemIndependent Consultant
Scott RobertsonKaiser Permanente
Frank McKinneyPOCP
Danielle BancroftFRED IT
Maggie BuchingerSurescripts
Peter SergentHL7 New Zealand
Shelly SpiroHIT Collaborative
Daniel ZhangEpic

Agenda Items and Notes

Catalogue Project

  • June 8, 2020
  • May 11, 2020
    • meeting last Friday - planning for Connectathon
  • May 4, 2020
    • Proposed Use Cases - John will share with the Catalog Project - will discuss on our call next week.

      • A health care organization maintains its medication formulary to support prescribing, dispensing and medication administration and shares it internally in applications
      • A health care organization or government organization maintains its medication formulary and shares it externally with patients and care givers to allow them to know what medications are covered and not covered for their plan
      • A health care organization or government organization maintains its medication formulary and allows a patient or their care giver to retrieve a catalogue of medications are covered for their plan
      • A vendor maintains clinical drug knowledge and shares it to organizations to support the retrieval of drug information by health care practitioners
      • A vendor maintains drug knowledge and shares it online to support the retrieval of drug information by patients and consumers
      • An organization maintains a standardized medication terminology for all medications licensed for use within a jurisdiction to support prescribing, dispensing and administration of medications by health care professionals and consumption of medications by patients
  • April 27, 2020 - no discussion
  • April 20, 2020
    • Use cases - Medications 

      • This section lists the use cases for using catalogs of medications.

        • A health care organization maintains its medication formulary and shares it to the applications used by its physicians, nurses and pharmacists to support medication prescription, dispense and administration.
        • A content vendor publishes the general catalog of medications authorized to a national market. Health care organizations of the country import subsets of this general catalog so as to synchronize their local medication formularies.
        • Variant 1: In addition to the general catalog of medications, the content vendor hosts the medication formularies of each of its client organizations who interact with the server to use their own medication formulary in their medication workflows, as well as to maintain this medication formulary over time (inserting/updating/retiring items).
        • A health care organization provides medication formularies to its patients for educational purposes.
        • An organization exposes the set of standardized vocabularies needed to support full semantic interoperability for prescription, dispense and administration of medications within a jurisdiction (e.g. a country). This reference set is represented as a generic catalog of all the medications that are usable within the jurisdiction. This generic catalog is imported in whole or in parts by the applications of the prescribers, carers and dispensers of the jurisdiction.
      • Pharmacy has been asked to review and provide updates to the use cases
      • Team is working on lab use cases - likely September ballot cycle.  Pharmacy content will follow on
      • Review of Interaction Framework 
        • 3 actors - catalog owner, catalogue custodian, Catalogue consumer
      • Use Cases - review notes
        • A health care organization maintains its medication formulary and shares it to the applications used by its physicians, nurses and pharmacists to support medication prescription, dispense and administration.
          • presume this is within an institution
          • provides a list of medications that are orderable - limited scope
          • not typically based on a specific patient's coverage for the inpatient setting
          • there may be a flag on the formulary that would indicate - need pre-authorization or if high cost
        • Patient - want to see medications that I'm insured for - there could be more than 1 of these per organization - varies by conditions, employer groups
          • may include medications that are not covered
        • Consumer or provider facing drug information - 
          • provide drug information - compendium
          • catalogue of information - could construct using a FHIR construct
        • Knowledge Base Vendors - need to flesh out this and see if it is a use case to be included
          • List of list of drugs maintained by a Knowledge Base Vendor
            • Scott has reached out to 3 Knowledge Base vendors and their interest in catalogues - First Data Bank, Elsevier, Wolters Kluwer
            • Scott will summarize and add to the minutes
          • Decision Support Modules - 
            • there may be catalogues for this - give me all drug interactions for a given drug; or indications for a give drug; patient education monographs; professional monographs
        • List of National formularies
          • Health Canada has a searchable database - not FHIR, but could be
          • Australia - national terminology server - FHIR based
            • looking at how MedicationKnowledge could be used
          • Scott to reach out to NLM regarding RxNorm
      • Melva to review use cases in IG and provide updated wording for review
      • Need to have a discussion with Catalogue project with updated wording and the possibility of a separate FHIR IG
        • could try to bring vendors to the discussion for the medication work
        • will schedule after we review updated wording
  • April 13, 2020
    • reviewing current IG
    • will review use cases and then notify Francois when ready for review
  • Review Use Cases

Updates from Workflow

  • June 8, 2020
    • Attended: Meeting focused on Business Process change proposal
    • No impact to pharmacy at this point
  • June 1, 2020
    • no discussion
  • May 11, 2020
    • no discussion
  • April 27, 2020
    • no discussion

Healthcare Product

  • June 8, 2020
    • Attended: UDI DAM ballot reconciliation 
    • No impact to pharmacy at this point
  • May 11, 2020
    • commercialBrand - apparently passed - has been added to Device Resource
      • to support various levels of "brands" - business name (this is the new element) →brand name → sub-brands → product names (these would be added device names)
      • will have to see if it impacts Pharmacy medication resources
  • May 4, 2020 - 
    • will be creating a new element - commercialbrand
  • April 27, 2020
    • requirement for a "commercial brand" - different brand names with different manufacturers
      • this use case may exists in medication
    • SubstanceDefinition - BR&R
      • no discussion

NCPDP Updates

  • Specialty Medication Prescribing PSS update - Specialty Medications
    • June 8, 2020
      • participated in the Connectathon in May
      • not as much turn out as would have hoped
      • general workflow discussion that will be included
      • found people that will participate
      • IG under development
      • Plan for next week to do a review of the IG
      • NCPDP task group meeting tomorrow
        • will be discussing code systems
          • will lean toward SNOMED-CT for allergies and ICD-10 for diagnosis/condition
            • if payment is linked - will need to be coded - claim.diagnosis - binds to ICD-10
            • US Core - allows ICD-9, ICD-10 and SNOMED-CT
    • May 11, 2020
      • task group meets tomorrow
      • Frank helping to write the IG
      • questions about data elements that have been identified 
      • participating in the Connectathon - want to get feedback - will be doing overviews
      • There will be a schedule posted
      • IG is ready to do a review with Pharmacy
      • plan to ballot in September cycle
      • Add review to agenda for June 1st
    • May 4, 2020 - no discussion
    • April 27, 2020
      • task group meeting held - reviewed some questions
      • Frank worked on creating the guide
      • Working through requirements
      • Spreadsheet being maintained in NCPDP but linked from NCPDP 
      • Schedule a review of the IG on May 4th conference call
  • Standardized Medication List - Standardized Medication Profile
    • June 8, 2020
      • group at NCPDP is meeting sporadically
      • have engaged the Research Triangle Institute who did the original study 
      • Will finish the White Paper - 
        • needs to be balloted at HL7
        • Shelly to work on new projected dates - January 2021 balloting
      • Next steps - there will be a FHIR IG created
        • will need a new project to move forward
    • May 11, 2020
      • there have been meetings - next meeting TBD - 
      • Scott to update links in project page
    • May 4, 2020 - no discussion
    • April 27, 2020
      • call on Wednesday
      • Jean to provide an update after that call

V2-FHIR Mapping


  • Real Time Pharmacy Benefit Check

    • FHIR IG has been updated based on ballot comments and accepted dispositions
    • has been out for review for the last week or 2
    • final items that need to be completed have to do with US Core and binding to NDC-11
      • NDC
        • have had calls with Vocab and HTA
        • need to determine code system URL
          • will point at existing NDA codesystem
      • US Core - met with Cross Project WG
        • patient profile variance accepted
        • MedicationRequest profile - variances
          • absence in IG of dosage instruction element 
            • information needed is part of dispenseRequest
          • authoredOn - may be approximate
          • hope to reach a conclusion by next CGP call on Thursday
          • encounter - is must support in US Core
    • Ballot Reconciliation Spreadsheet
      • some issues with export of ballot comments - Melva will look at the issue
    • 1 build error that needs to be resolved - Grahame reviewing
    • Will start the publication request
      • Melva to create and send Frank the link
    • Frank to send the link to the Pharmacy List Serve - and ask for the review
  • Medication List Guidance
    • June 8, 2020
    • Previous discussion
      • Scheduling calls to work on - May 7 and May 14 - 5-7pm Eastern
        • will work on the pages - 
        • Check HL7 Conference Center for details
      • Confluence Pages: Patient Medication List Guidance
        • Melva reviewed the context page
        • will be starting to put some words around the content
        • Danielle will help with content
        • Melva to start FHIR IG Proposal
      • Universal need for doing e-prescribing over FHIR
      • focus on use cases for e-prescribing IG - have an plan to create an IG
        • there are some AU requirements from e-prescribing - that can feed in to next project
      • FHIR IG Proposal has been approved
      • Medication list FHIR IG approved


Trackers - link to pharmacy unresolved Jira trackers 

  • See JIRA


  • New NCPDP Projects
    • Standardized Medication Profile FHIR IG
    • MTM CCDA IG - create FHIR IG

Next meeting

  • June 15th
  • June 22nd
    • Specialty Medication IG Overview -  30 minutes

Action Items

  • Melva Petersto send Frank the link to the Publication Request for the RTPBC IG
  • Melva Peters will look at issue with RTPBC ballot reconciliation spreadsheet item