Chair: @Bryn Rhodes
Scribe: @Bryn Rhodes
Professional Associations, such as HL7, which bring together competing entities are subject to strict
scrutiny under applicable antitrust laws. HL7 recognizes that the antitrust laws were enacted to promote
fairness in competition and, as such, supports laws against monopoly and restraints of trade and their
enforcement. Each individual participating in HL7 meetings and conferences, regardless of venue, is
responsible for knowing the contents of and adhering to the HL7 Antitrust Policy as stated in §05.01 of
the Governance and Operations Manual (GOM).
NOTE: This attendance applies if you are present at the related meeting/call, regardless if you have signed a different attendance for your WG.
University of Utah
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."
Meeting Minutes from Discussion
|Decision Link(if not child)|
The Centers for Medicare & Medicaid Services (CMS) invites you to attend the Cooking with Clinical Quality Language (CQL), Quality Data Model (QDM), and Fast Healthcare Interoperability Resources (FHIR) webinar. The webinar series provides an interactive environment for measure developers. The upcoming sessions will feature open discussion from subject matter experts and will show examples on how to express eCQMs using CQL and FHIR as well as how QDM concepts can be represented using FHIR resources and take questions from the audience.
The next webinar will take place on Thursday, March 23, 2023 at 4:00 pm ET.
May 2023 Ballot Cycle
September 2023 Ballot Cycle
January 2024 Ballot Cycle
CRMI IG For Comment Ballot:
Canonical Resource Management Infrastructure: http://build.fhir.org/ig/HL7/crmi-ig
Motion to approve CRMI-IG content as ready for for comment ballot in the May cycle: Howard Strasberg/Greg White: 14-0-0
FHIR Trackers to reopen:
|Tracker re-opened and discussed, new disposition recorded and voted in the Jira tracker|
FHIR Resource Maturity Votes:
Motion to approve maturity level 1 for ArtifactAssessment: Brian Alper/Joanne Dehnbostel: 14-0-0
Motion to approve maturity level 1 for Citation: Brian Alper/Joanne Dehnbostel: 14-0-0
Motion to approve maturity level 4 for Library, ActivityDefinition, PlanDefinition, RequestOrchestration: Howard Strasberg/Greg White: 14-0-0
This is a request for your HL7 comments on ONC’s Draft USCDI Version 4. A number of Work Groups have been formulating responses. We look forward to your feedback by April 6. Please send comments to firstname.lastname@example.org.
Official comments are due to ONC by April 17 and they will release the final USCDI v4 in July 2023. Draft USCDI Version 4 includes 20 new data elements and one new data class. Particular focus is on equity, diversity, and access to healthcare. Note, comments on the Interoperability Standards Advisory (ISA) are also received on a rolling basis in addition to a late summer/early fall comment period, so if you have any feedback on the ISA at this time, you can include that as well.
Relevant information and links that will help you are below.
Draft USCDI Version 4
Current USCDI information can be found at:
A narrative overview of changes in Draft USCDI Version 4 can be found at:
Interoperability Standards Advisory (ISA)
Full information about the ISA contents and items can be found at:
Note that MedicationAdherence is one of the proposed data elements in USCDI v4. We might want to comment on this data element because there are extensive decision support and quality measurement use cases that make use of this information (cumulative medication duration, opioid decision support, among others)
Seems like MedicationAdherence is an "inference" rather than an actual data element, should potentially make comments on this.
Is USCDI basically a set of requirements for US Core?
There is a roadmap for USCDI and USCore that is stewarded by the Cross Group Projects Work Group. Basically the classes are identified by USCDI, and when the final content is published for each USCDI version, the USCore team works with the implementer community to understand how those data elements are represented in vendor systems to incorporate those requirements as profiles and requirements in USCore. There are things that are in USCore that are not in USCDI, but it is in general a set of base requirements to inform content in USCore.