Page tree
Skip to end of metadata
Go to start of metadata

Chair:  Jean Duteau

Scribe: Floyd Eisenberg  

NOTE - This call is rescheduled from July 23, 2020.  The originally scheduled call for August 6, 2020 is also rescheduled for Thursday, July 30, 2020.

Thus, the next two calls are Thursday July 16 from 1-2 PM ET and Thursday July 30 from 1-2 PM ET

Join Zoom Meeting

Meeting ID: 915 0605 8769

One tap mobile

+13126266799,,91506058769# US (Chicago)

+16465588656,,91506058769# US (New York)

Meeting ID: 915 0605 8769

Find your local number:

Dial by your location

        +1 312 626 6799 US (Chicago)

        +1 646 558 8656 US (New York)

        +1 301 715 8592 US (Germantown)

        +1 346 248 7799 US (Houston)

        +1 669 900 9128 US (San Jose)

        +1 253 215 8782 US (Tacoma)

NOTE: This attendance applies if you are present at the related meeting/call, regardless if you have signed a different attendance for your WG. 


Previous Meeting: 2020-07-09 Meeting Minutes/Agenda2020-07-16 Meeting Minutes/Agenda

Minutes Approved as Presented 

This is to approve minutes via general consent. "You have received the minutes. Are there any corrections to the minutes? (pause) Hearing none, if there are no objections, the minutes are approved as printed."

Agenda Topics

Agenda Outline

Agenda Item

Meeting Minutes from Discussion

Decision Link(if not child)


Minutes Approval (note - 09 July and 16 July minutes need approval)

Reminder: Co-Chair Election open until July 31, 2020

Project Proposal - FAIRness for FHIR

FAIRness for FHIR Proposal:  PSS-1657 - FAIRness for FHIR IN REVIEW   

Work with the Research Data Alliance to provide guidance on supporting data FAIRness with HL7 FHIR. In particular describe how FHIR can help in supporting the FAIR (Findability, Accessibility, Interoperability and Reusability) principles ( and the proposed RDA recommendations on FAIR data maturity model indicators.

Follow up from July 9, 2020 discussion - Awaiting follow up from FHIR-I and SOA.

Military History Project

Report from Military History Project team 

Confluence page: Military Service History and Status FHIR Profiles Project Page  Document

Plans to go to the September Connectathon for HL7 FHIR. Consider whether the API can be used for veteran status for DaVinci use cases.

US Core Methodology

Publication Request - Re: HL7 FHIR® US Core Implementation Guide STU3 Release 3.1.1. The changes for this errata package

The Co-Chair list serve received notification of the errata package on 15 July 2020 with indication that the comment period will ent on 29 July 2020. 

Consider comments on errata package:

  • Jira tracker addresses the question:  FHIR-28079 - Comment on errata 3.1.1: Smoking Status value set and binding TRIAGED   - Group consensus agreed to a current resolution (16 July 2020) to roll back the binding to preferred with a Max binding in the current errata package. And to consider the appropriate set of codes going forward. As informational - the Max binding extension elementdefinition.maxValueSet - I.e., use the preferred set but requires SNOMED (the Max).  The tracker FHIR-28079 remains open looking for future development of appropriate codes for the value set. Therefore, the group did not vote directly on the resolution but no one voice disagreement with this resolution.
    • Should CGP vote on resolution and create a new tracker for future development of appropriate codes?
  • Additional trackers: 

Publication Request

CTO Errata Letter

Deferred from prior calls (not errata-related):

  • J#27857 Add Reference to US Core Patient in Vitals Signs Profiles (Brett.Marquard) Persuasive
    • Deferred for clarification
  • J#27117 ICD-10-PCS: Note ownership and availability for Use. Include Codes. (saul_kravitz) Persuasive with Modification
    • Deferred - the copyright for the value set is owned by US Realm Steering Committee - request clarification from commenter.

Also deferred but reviewed in the US Realm Steering Committee and determined acceptable:

FHIR-27732 US Core MedicationRequest variance – encounter

FHIR-27731 US Core Patient variance – Patient.telecom

FHIR-27730 US Core Patient variance – Patient.communication.language

FHIR-27729 US Core Patient variance - us-core-birthsex

FHIR-27728 US Core Patient variance – us-core-ethnicity

FHIR-27727 US Core Patient variance – us-core-race

Briefly discussed on June 18 call and will require additional work:

FHIR-27770 - Need to work with Vocabulary and HTA since the current publication indicates reference to only one license year (2014) and CPT has a new license every year.  Need a reasonable way to manage the code system version. The version is based on the date of service. The OID, code and reference does not change but the version changes with every year of service.

Next Steps for US Core Errata

Details to follow.

Road to US Core Discussion

For consideration on the May 28, 2020: Additional US Core FHIR Trackers (Frank McKinney) regarding Real-Time Pharmacy Benefit Check (RTPBC) Implementation Guide - variance for profiles regarding Patient and MedicationRequest (see Tracker links bullet below). 

Current expectations: Expecting errata package for US Core toward the end of June 2020 for a 2-week comment period followed by a vote for approval and publication in early July 2020.

Jira Issue Summary (Reporter) Resolution

  1. J#27867 add reaction to allergies (ehaas) Persuasive
  2. J#27857 Add Reference to US Core Patient in Vitals Signs Profiles (Brett.Marquard) Persuasive
  3. J#27846 US Core Pulse Oximetry Profile: observation.value and component.value constraints are different (emmanurse) Persuasive with Modification
  4. J#27836 Expand Procedure Codes Value Set to include ICD-10 PCS codes (ekivemark) Persuasive
  5. J#27117 ICD-10-PCS: Note ownership and availability for Use. Include Codes. (saul_kravitz) Persuasive with Modification
  6. J#27116 Change Description of ICD-10-PCS Value Set (saul_kravitz) Persuasive
  7.  J#27876 - Remove Must Support References to non US Core Profiles (Brett.Marquard) Persuasive

The WG reviewed FHIR trackers on the errata package:

FHIR-28079 Persuasive with Modification - Brett Marquard/Eric Haas: 10-0-1

FHIR-28161 - Technical correction - no vote required
FHIR-28129 - Persuasive - add guidance - Eric Haas/Jean Duteau: 11-0-0

FHIR-28156 - Not Persuasive - Jean Duteau/Eric Haas: 9-0-2

Encounter-specific issues:
 - Persuasive - Correction - Floyd Eisenberg/Brett Marquard: 9-1-1

FHIR-28075 - Definitional issue for Encounter.location that needs evaluation with Patient Administration. Deferred as it is bigger than an errata issue.

FHIR-28102 - Deferred as future issue

FHIR-28090 - Deferred as future issue

Publication Request reviewed and approved - Eric Haas/Floyd Eisenberg: 10-0-0

Errata Letter reviewed and confirms changes in the Publication Request. No need to have a formal vote on the Errata Letter.

Public Health IG Recommendations for US Core (Craig Newman)Public Health sponsored FHIR IGs (Birth and Fetal Death reporting and Birth Defect reporting) and noticed a good number of data elements in common; I.e., a potential to share a number of profiles including patient (probably), mother/father/relatedPerson and a number of observations about the pregnancy and delivery (plurality, number of previous live births, LMP, etc). Public Health is looking at making a “common public health” FHIR IG that defines these profiles and that their individual IGs can reference. Particularly for the observations, a lot of these concepts go beyond public health and could be used by a number of different systems. Public Health requests discussion with CGP to get a feel for whether or not CGP should be pursing adding profiles to US Core or some sort of IG that maybe has more visibility than a “public health” IG might get. (Craig Newman, John Loonsk, Cynthia Bush, Sarah Gaunt)Craig Newman briefly reviewed the concepts for Birth and Fetal Death Reporting and Birth Defect Reporting. The CGP WG briefly discussed that the project can work through Public Health and if desired, CGP could co-sponsor. To assure consistency across profiles using resources to define required elements, work with other WGs is needed. Public Health will present to CQI tomorrow as well.  The project was approved by FMG yesterday.  Craig will bring back further information at a future meeting.I
September Virtual WGM Agenda

September HL7 Virtual WGM schedule - Monday, September 21 noon ET through Friday, September 25 at 6:00 PM ET (2 hour slots on a 24 hour basis through the week).

CGP is relatively new and "usually" has one quarter identified as well as co-chair joining the USRealm session. Is Thursday, September 24 from 2:00 - 4:00 PM ET acceptable? ( Do we need joint meetings with other WGs?

The CGP agreed to meet Thursday, September 23 from 2-4 PM and the item entered in the WGM Doodle poll.
ANSI Survey

ANSI Opens Survey: Standardization Empowering AI-enabled Systems in Health Care
The American National Standards Institute (ANSI) has released a survey on standardization empowering artificial intelligence (AI)-enabled systems in health care. ANSI seeks feedback from interested stakeholders on related standardization issues, solutions, efforts, and the role of standardization in the governance and regulation. Survey responses are requested by July 31, 2020 , and the results will be used to inform the discussion at a public-private virtual workshop hosted by ANSI on September 14, 2020. ANSI will provide details for the workshop in the near future. ANSI Survey - Standardization Empowering AI-Enabled Systems in Health Care

Not discussed

Informational for CGP: The canonical url for NUCC Provider Terminology includes abstract code categories in the content loaded into the FHIR Terminology Server. These USCoreProviderSpecialityNucc value set abstract code categories may need to be removed but the value set does not need to change because it is all codes in the code system. The expansion is incorrect. This is a FHIR tooling issue and once fixed, the US Core reference to the value set will inherit the change. Related Zulip chat:

Not discussed
The meeting was adjourned at 2:03 PM ET.

Supporting Documents

Outline Reference

Supporting Document

Minute Approval


Write a comment…

  • No labels