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).
Welcome, agenda review, meeting minute approval
No new agenda items
Meeting minutes from last week approved as posted by consensus
Danny assumed Chair role.
Discussion of FHIR Immunization JIRA tickets
FHIR-37722 - Imunization.primarySource is misrepresenting intention TRIAGED
Indicate the context in which the information about the Imm event was captured. Whether the record was captured as an original primary source of truth record or a secondary or reported (historical in V2)
Added a value of true that this is a primary record, collected by the person who administered it.
IN base resource, cardinality is 0..1
US Core has a profile on Immunization, must support 1..1
Suggest renaming the element to Immunization.patientCaregiverReported, anything else is believed to be provenance, though there doesn’t seem to be consensus on this.
There is also Immunization.informationSource. This is used to indicate who provided the info when not from who administered the vax directly.
The IIS community doesn’t really use informationSource. They usually only use primarySource in data reported to the IIS, and will usually document everything as historical in IIS to IIS communications.
IN R4, it’s a codable concept, in R5 it will be a codable reference
Complexity around the longitudinal nature of provenance as information is passed from system to system.
Possibly need to extend the primarySource description of the true value, and the description of the informationSource
The V2 IIS spec is used primarily in the US to communicate from the EHR to the IIS and this concept is used to indicate whether the administration information is from the person administering vs someone else like patient or parent reported.
Seems like there may be two or three different definitions that folks are using for this and this needs to be clarified.
Proposal- will discuss on the Imm Friday call tomorrow to confirm use of primarySource and will try to come up with updated wording and will circulate with Gay (commenter) and the workgroup.
FHIR-32396 - documentType data type doesn't match definition TRIAGED
In R4, add ability to document education material presented to the patient. Added in backbone element including documentType
How we documented what was given was unclear.
Documenting education as a part of the Immunizaiton resource may not have been the best idea in the first place.
There is a Communication Resource is more appropriate.
Would remove education backbone and then add content to boundaries and relationships narrative indicating that Communication can be used to document issuance of educational materials.
Within Immunization resource you could have a contained Communication resource
So you wouldn’t needed to have a standard alone Communication resource, rather imbed it the Imm resource. This was reviewed and supported by Lloyd.
Similar conversations in V2 space regarding the continuation of pushing VIS i
Motion- Craig moves to approve as not persuasive with mod as documented.
Retiring the v2.6 VRDR IG
STU period as expired
NCHS is focusing on FHIR
Implementers are being encouraged to implement FHIR not V2.