FHIR Chat · Previous and Current General Practitioner/Practice · implementers

Stream: implementers

Topic: Previous and Current General Practitioner/Practice


view this post on Zulip Dave Barnet (Nov 14 2017 at 15:32):

I have a requirement to model a Patient's new and previous General Practitioner in a message. Is there a best practice to do this? I see that STU3 Patient profile allows many generalPractitioner references, but there doesn't seem to be a way of saying one is the new practitioner and one the former practitioner. I can see that you could link a Patient to a Practitioner to a PractitionerRole and use a role of General Practitioner and then use period to bound the dates for the previous and new Practitiner. However, in the UK patients are generally registered with Practice rather than practitioner, so this wouldn't work.

As I only have a requirement for new and previous Practitioner, I could use the Patient.link mechanism, creating a patient record linking to the current General Practitioner/Practice, then link to another patient record (for the same patient) detailing their previous General Practitioner/Practice (using link type "replaces").

Or do I use the EpisodeOfCare resource to hold 2 episodes of care (one for the previous GP/Practice, and one for the new GP/Practice with relevant dates etc.)?Previous and Current General Practitioner

view this post on Zulip Grahame Grieve (Nov 14 2017 at 15:33):

this sounds like a patch operation on the sly?

view this post on Zulip Lloyd McKenzie (Nov 14 2017 at 16:38):

Patient.link is about duplicate patients. Patient isn't designed to track anything other than the current practitioners. If you want historical ones, you'll need to use an extension. (Or look at Patient history)

view this post on Zulip Peter Scholz (Nov 14 2017 at 18:58):

Different EpisodeOfCare entities seems to be the closest one, if different practices are envolved.
Otherwise I would think of different encounters,

view this post on Zulip Peter Scholz (Nov 14 2017 at 19:04):

Patient isn't designed to track anything other than the current practitioners.

Am I the only one missing some kind of information qualifying the practitioner(s). What does it mean if a patient has more than one practitioner ?

view this post on Zulip Richard Townley-O'Neill (Nov 14 2017 at 23:06):

If I frequently move between two locations I may have a usual GP in each location.

view this post on Zulip Lloyd McKenzie (Nov 15 2017 at 09:18):

You might also have a GP, a dentist and a psychiatrist. All could be listed.

view this post on Zulip Peter Scholz (Nov 15 2017 at 09:34):

agreed, but how do I distinguish ? For now it's JBOP (just a bunch of practitioners). Which puts me back to my initial question: Is nobody missing information qualifying the practitioner in his relation to the patient, which IMHO can't be an attribute of the practitioner but belongs to the relation.

view this post on Zulip Lloyd McKenzie (Nov 15 2017 at 10:58):

If you want to start to identify specific relationships, then you're looking at CareTeam. with Patient.practitioner, you just have to infer based on what PractitionerRoles that Practitioner has.

view this post on Zulip Kevin Mayfield (Nov 15 2017 at 11:14):

I prefer the EpisodeOfCare with ManagingOrganisation being the practice and current GP being the CareManager but it doesn't show history of GP within an organisation. Wonder if this could be done with an extension allowing sub EpisodeOfCare (or Consultant Episodes within an episode/spell)

view this post on Zulip Kevin Mayfield (Nov 15 2017 at 11:16):

type being 100 if using Uk/England codes

view this post on Zulip Dave Barnet (Nov 15 2017 at 14:24):

OK - thanks for all your input. What seems most sensible is that I use Patient.generalPractitioner for the (new) current practitioner, as that's what would be expected to be held in this field (I can use Organization for just a Practice, or Practitioner linked to Oragnization for the General Practitioner). For the previous Practice/General Parctitioner I'll use EpisodeOfCare (managingOrganization & careManager) as suggested (with period.end set & period.start if that's available). Wouldn't want to be accused of creating a patch operation on the sly !?!


Last updated: Apr 12 2022 at 19:14 UTC