Stream: implementers
Topic: AllergyIntolerance recorder - Organization?
Jose Costa Teixeira (Jun 10 2021 at 10:12):
We were discussing how to express that the recorder of an allergy is an organization (or, maybe better, "someone in an organization").
We notice that AllergyIntolerance.recorder does not include Organization.
Jose Costa Teixeira (Jun 10 2021 at 10:14):
One way to implement this would be use a practitionerRole just with an Organization. However, there is a discrepancy between resources which seem to have the same intent:
Jose Costa Teixeira (Jun 10 2021 at 10:15):
- Observation.performer can be an Organization.
- DiagnosticReport (which is not as flexible as Organization) does allow performer and resultsInterpreter to be a Organization.
Lloyd McKenzie (Jun 10 2021 at 14:49):
I think Organization is reasonable. Sometimes you might just know that a given allergy record came from XYZ hospital or ABC payer and nothing more. Care to submit a change request?
Jose Costa Teixeira (Jun 15 2021 at 22:26):
FHIR-32916 created
Jose Costa Teixeira (Jun 15 2021 at 22:28):
we don't have a recorder in Observation. Do we presume that performer = recorder?
Jose Costa Teixeira (Jun 15 2021 at 22:29):
for Immunization, the same, but I presume that is what .informationsource is for? @Craig Newman
Eric Haas (Jun 16 2021 at 00:50):
Jose Costa Teixeira said:
we don't have a recorder in Observation. Do we presume that performer = recorder?
http://hl7.org/fhir/StructureDefinition/event-performerFunction
Craig Newman (Jun 16 2021 at 13:07):
Immunization.informationSource is where data came from if not from the the person/organization who administered the vaccine. So if an immunization registry in a different jurisdiction supplies the event data, that source can be recorded. For new vaccine administrations, It would be .performer that records who gave the vaccine (which I suppose may or may not be who actually records the data in the EHR). Is recorder a Provenance type concept?
Jose Costa Teixeira (Jun 17 2021 at 20:29):
Well, it would think that informationSource is more akin to Provenance.
Jose Costa Teixeira (Jun 17 2021 at 20:29):
Recorder is the person(/entity) that put this on the record
John Moehrke (Jun 17 2021 at 20:52):
Provenance can always be used to record more rich Provenance. Some of Provenance functionality is built into the core resource definitions when that functionality is dominantly needed by that resource.
we call this "Five Ws" http://build.fhir.org/fivews
Last updated: Apr 12 2022 at 19:14 UTC
