Chair: @Bryn Rhodes
Scribe: @Isaac Vetter
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.
|ICF for today|
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)|
May 2023 Ballot Cycle
September 2023 Ballot Cycle
January 2024 Ballot Cycle
|Project Proposals||CDS does not need to be involved in the proposed project.|
Review of WGM agenda.
|PlanDefinition modeling question from Vadim Peretokin|
$apply produces a CarePlan. Vadim wants a RequestGroup.
In R5, $apply is changed to return bundle including a RequestGroup / RequestOrchestration per implementer request for less optionality and more simplicity.
In R4, the $apply operation returns a CarePlan.
Implementations are already returning a requestgroup, though. Let's look at backporting this behavior of the R5 $apply in the CPG IG.
|FHIR R5 Trackers||No trackers|
|EBM update from Chris|