FHIR Chat · Attester in Immunization · implementers

Stream: implementers

Topic: Attester in Immunization


view this post on Zulip Maximilian Reith (Nov 19 2019 at 13:36):

Hey,
i'm trying to integrate an attester in the immunization resource, in detail: a practitioner which is legal responsible for the content of the immunization resource. What is the best way for doing this? Extending the valueset http://hl7.org/fhir/ValueSet/immunization-function by attesting Provider might be a solution, but is the one who is attesting really a performer? or should i create an extension for a attester like composition.attester?

regards Max

view this post on Zulip Lloyd McKenzie (Nov 19 2019 at 14:57):

@Craig Newman @Joginder Madra

view this post on Zulip Craig Newman (Nov 19 2019 at 20:09):

The Public Health WG has talked about this one already. We approved a change for R5 (notes are available at https://confluence.hl7.org/display/PHWG/gForge+tickets+15696+and+20327 - we approved Option B). I'm pretty sure I implemented this in current build already. But basically we allow a reference to a practitioner as the "information source". Not sure how this would be done in R4 or earlier versions.

view this post on Zulip Maximilian Reith (Nov 21 2019 at 11:39):

I have no permission to enter your area in gforge, but do you mean the extension solution by " - we approved Option B" ?

view this post on Zulip Craig Newman (Nov 21 2019 at 14:22):

Proposal B
• Leave Immunization.primarySource as a Boolean to indicate if the content of the resource is based on firsthand knowledge of the immunization event
o Update the Definition
 From: An indication that the content of the record is based on information from the person who administered the vaccine. This reflects the context under which the data was originally recorded.
 To: Indicates if this record was captured as a secondary 'reported' record rather than as an original primary source-of-truth record.
 The new description is copied from Event.reported[x]
o Cardinality remains at 0..1
o primarySource is being kept separate so that even for a primary report, an “attester” can still be captured for a primary record
• Rename reportOrigin to informationSource and enhance it to have a choice of data type
o The short description will be updated to read:
 Indicates the source of a reported record
o The definition will be updated to read:
 Typically the source of the data when the report of the immunization event is not based on information from the person who administered the vaccine.
o The Comments will be updated to read:
 Typically will not be populated if primarySource = True, not required even if primarySource = False.
o informationSourceCodeableConcept - CodeableConcept data type with the existing example value setoinformationSource.Reference - Reference data type (Patient | Practitioner | PractitionerRole | RelatedPerson | Organization)
 Note that while some other resources don’t include Organization, it may be useful in Immunization if the source of data is a school, pharmacy, other IIS, etc
o Cardinality remains at 0..1
o The name will be the same as MedicationStatement and is broader than “asserter” given that a general code may be selected if specific asserter information is not available

view this post on Zulip Lloyd McKenzie (Nov 21 2019 at 15:15):

@Maximilian Reith As of a few days ago, no-one has permission to look at gForge. We've transitioned from gForge to Jira and, unfortunately, gForge has no ability to provide 'read' access without also providing 'create' access, so we had to yank both. You can see the information about those two tickets in Jira here: J#15696 and J#20327. (And you can find any arbitrary gForge item by using the URL http://jira.hl7.org/browse/FHIR-[your tracker# here])

view this post on Zulip Maximilian Reith (Nov 22 2019 at 07:06):

Proposal B
• Leave Immunization.primarySource as a Boolean to indicate if the content of the resource is based on firsthand knowledge of the immunization event
o Update the Definition
 From: An indication that the content of the record is based on information from the person who administered the vaccine. This reflects the context under which the data was originally recorded.
 To: Indicates if this record was captured as a secondary 'reported' record rather than as an original primary source-of-truth record.
 The new description is copied from Event.reported[x]
o Cardinality remains at 0..1
o primarySource is being kept separate so that even for a primary report, an “attester” can still be captured for a primary record
• Rename reportOrigin to informationSource and enhance it to have a choice of data type
o The short description will be updated to read:
 Indicates the source of a reported record
o The definition will be updated to read:
 Typically the source of the data when the report of the immunization event is not based on information from the person who administered the vaccine.
o The Comments will be updated to read:
 Typically will not be populated if primarySource = True, not required even if primarySource = False.
o informationSourceCodeableConcept - CodeableConcept data type with the existing example value setoinformationSource.Reference - Reference data type (Patient | Practitioner | PractitionerRole | RelatedPerson | Organization)
 Note that while some other resources don’t include Organization, it may be useful in Immunization if the source of data is a school, pharmacy, other IIS, etc
o Cardinality remains at 0..1
o The name will be the same as MedicationStatement and is broader than “asserter” given that a general code may be selected if specific asserter information is not available

Hey Craig,

just for information: i would like to refer to an attestor (for completness) even if primary Source is true , since the attestor is not necessarily a performer and i got no other options to refer to a practitioner.

Thanks Max

view this post on Zulip Maximilian Reith (Nov 22 2019 at 07:07):

Maximilian Reith As of a few days ago, no-one has permission to look at gForge. We've transitioned from gForge to Jira and, unfortunately, gForge has no ability to provide 'read' access without also providing 'create' access, so we had to yank both. You can see the information about those two tickets in Jira here: J#15696 and J#20327. (And you can find any arbitrary gForge item by using the URL http://jira.hl7.org/browse/FHIR-[your tracker# here])

Ok Thank you for the information

view this post on Zulip Craig Newman (Nov 25 2019 at 15:40):

So starting in R5, you should be able to indicate the primarySource as True and still reference the provider in informationSourceReference. For R4 or other previous versions, maybe you just create an informationSourceReference extension.


Last updated: Apr 12 2022 at 19:14 UTC