Stream: implementers
Topic: Custom Patient Resource
Ahmad Ramin (Sep 07 2020 at 12:57):
Hey guys, so I have some patient data which has the following fields (name, age, image, sex, hasDementia, hospitalID). I want to create a FHIR resource out of it. most fields are in base FHIR patient resource, but I don't know how to deal with custom fields (such as hasDementia, hospitalID ) if anyone has an example would be great. I am using JSON
Mareike Przysucha (Sep 07 2020 at 13:01):
Hi Ahmad.
The hospitalID is one of the identifiers of the patient. You need to define a naming system for the hospitalIDs, and the then you can use this as system. The ID is the value.
Whether or not a patient has dementia is a Condition. The dementia is the code and the presence is verification status (you might also have a look at the clinicalStatus).
Mareike Przysucha (Sep 07 2020 at 13:04):
I would not recommend the use of an extension for the dementia for a simple reason: Then others might think it's a good option to do that, and then all the "problems" a patient might have, extensions might be used in addition to conditions. It leads to double documentation which might lead to inconsistencies. And: Extensions might not be known by servers getting the data. Therefore the information might get lost, which would be a pity.
Ahmad Ramin (Sep 07 2020 at 13:09):
Thanks, but in our case hospitalID is an identifier for a hospital where a patient relates to.
Mareike Przysucha (Sep 07 2020 at 13:16):
Sorry, misunderstanding. The hospital caring for a patient is an organization. If the hospital is custodian of the data, then you can reference this organization via "managingOrganization" in Patient.
Ahmad Ramin (Sep 07 2020 at 13:21):
how about another field called userID, which respresent a person caring for the patient?
Mareike Przysucha (Sep 07 2020 at 13:23):
If it is a health care professional, it is a practitioner. If it is a relative or a friend, it's a relatedPerson.
Ahmad Ramin (Sep 07 2020 at 13:32):
ok thanks, but relatedPerson is not defined in FHIR patient resource. is it?
Mareike Przysucha (Sep 07 2020 at 13:33):
you can link via link.other.
Ahmad Ramin (Sep 07 2020 at 13:42):
Thank you @Mareike Przysucha
Craig Newman (Sep 08 2020 at 15:51):
Is that the right use for link.other? I thought any references in in Patient.link had to be the same person as the Patient (to point to other Patient records for the same person or the case where the person is a RelatedPerson for someone else (eg. a Mother is a Patient but also a RelatedPerson to her newborn infant)). RelatedPerson.patient (which is 1..1) points back from the RelatedPerson to the Patient.
Lloyd McKenzie (Sep 08 2020 at 16:32):
@Brian Postlethwaite
Vassil Peytchev (Sep 08 2020 at 16:39):
It looks like the only way to express that a person is a caregiver is through CareTeam:
CareTeam.participant[i].member -> RelatedPerson
RelatedPerson.patient -> Patient
Brian Postlethwaite (Sep 09 2020 at 07:16):
link goes from RelatedPerson to Patient, not other way around. (as noted by Craig above)
Brian Postlethwaite (Sep 09 2020 at 07:18):
has Dementia is more likely going to be represented by the existence of an EpisodeOfCare relating to the dementia (which you can then use to track data related to that), or possibly the existence of a condition for the dementia.
It's not really something you'd expect to find on the patient resource itself.
Brian Postlethwaite (Sep 09 2020 at 07:18):
And yes, the caregiver can be on the team, or it could be through the values in the RelatedPerson.relationship - depends what you really want to say about it.
Last updated: Apr 12 2022 at 19:14 UTC
