Professional Associations that bring together competing entities, such as HL7, 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 activities, 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).
We’d previously added instantiatesCanonical and instantiatesUri to Immunization and ImmunizationRecommendation resources in R5 to point to the standard of care / source material referenced for administering / recommending that immunization
Current thinking is no longer to use “instantiates” elements and instead use standard extensions (e.g., "workflow-adheresTo”)
New proposal is to remove the “instantiates” elements and provide guidance to use the extensions for the same purpose
Similar to previous ticket – for the ImmunizationEvaluation resource, we need to identify a protocol (e.g., ACIP recommendations) used to evaluate a previous immunization administration
Proposal now is to allow "workflow-adheresTo" and "workflow-generatedFrom" extensions to ImmunizationEvaluation
Proposal is add "supportingInformation" element to Immunization resource to capture relevant info that’s not specifically a reason to administer (indication), nor a reason not to administer (contraindication)
Other similar resources (e.g., MedicationAdministration) have this element already
"primarySource" element indicates whether the Immunization resource represents the original administration vs. a secondary report of a previously-administered immunization (a.k.a. a historical record)
"informationSource" represents the source of a secondary report when "primarySource" is false
Proposal is to update the narrative description of "primarySource" for better clarity
This ticket is about some of the components of the "education" element in the Immunization resource
In
FHIR-32396
-
Getting issue details...STATUS
, we will be removing the "education" element in favor of a reference to a Communication resource – that will make this ticket moot
Proposal is to dispose as "Not persuasive with modification"
All 5 tickets' dispositions were approved together 28-0-0 (motion: Craign, second: Nathan)
10 min.
MedMorph RA IG Review and Request for Publication
Dragon
There are a couple outstanding questions before publishing the Reference Architecture IG:
What is the process to change the title from "Making EHR Data...." to "Making Electronic Data....?"
We discussed this recently but haven't formally approved the change as WG yet
Becky had reached out to Dave Hamill, who indicated he changed the title in the PSS and in Project Insight
not sure if changes were fully applied (the "Project Name" field was updated in the PSS but not the page title)
are any other approvals needed?
Co-chairs will follow up with Dave
In case it's needed, the WG formally approved the name change 25-0-0 (motion: Maria, second: Genny)
Based on some previous Jira tickets (e.g.,
FHIR-30317
-
Getting issue details...STATUS
), the names of some actors have been updated in the IG
"Backend Services App" renamed to "Health Data Exchange App"
"Public Health Agency / Research Organization" renamed to "Data Receiver"
