Stream: implementers
Topic: careteam with multiple encounters
rekha (Nov 26 2018 at 12:24):
Hi all,
In an Organization we have multiple CareTeams, who are working on different Patients.
If a CareTeam resource work on a Patient Encounter, from day 1 to day 10 encounters total count 10 encounters. How can we capture these encounters info in CareTeam resource? Similarly same CareTeam resource worked on different Patients encounter’s.
Lloyd McKenzie (Nov 26 2018 at 15:11):
What is your objective in linking the CareTeam to the encounters? What involvement did the CareTeam have with the encounters?
rekha (Nov 27 2018 at 06:49):
@Lloyd McKenzie We have to create documentation based on Care team who spent time on Patient based on Encounters which are they involved.
Lloyd McKenzie (Nov 27 2018 at 07:09):
Typically involvement is captured at a more granular level. So a particular member of a care team performed a particular Procedure that was part of the Encounter. You could aggregate to figure out which Care Teams were involved, but you won't typically find raw data captured that way.
rekha (Nov 27 2018 at 13:41):
We have multiple care teams which contains different types of Practitioners (Attendee’s, Medical Student, Personal Attendees etc) . These care teams working on Patients Encounters.
Example there are 3 CareTeam resources,
CareTeam1,
CareTeam2,
CareTeam3.
Worked on Patient on Day1. We are capturing each CareTeam work on Patient consider as one Encounter. Then we are taking 3 encounters for each CareTeam. Now on Day 2 same CareTeam’s working on same Patient. So we are capturing 3 more Encounters on Day 2 for each CareTeam. But as per http://build.fhir.org/careteam.html , We are able to capture single Encounter object with CareTeam resource. How can we group these Encounters info. Do we need to capture any other way instead of CareTeams?
IMG_20181127_190355.jpg
Lloyd McKenzie (Nov 27 2018 at 16:32):
That seems to be an uncommon way to handle encounters. An encounter is generally a visit from a patient to a particular hospital or clinic or a particular department within a hospital. It's a single encounter regardless how how many practitioners engage with them or what teams those practitioners are part of.
Lloyd McKenzie (Nov 27 2018 at 16:33):
The CareTeam.encounter is intended to say "This is the patient's care team for the course of this encounter". If CareTeam.encounter is specified, the CareTeam must be patient-specific.
Mounika (Nov 28 2018 at 14:11):
That seems to be an uncommon way to handle encounters. An encounter is generally a visit from a patient to a particular hospital or clinic or a particular department within a hospital. It's a single encounter regardless how how many practitioners engage with them or what teams those practitioners are part of.
Okay@Lloyd McKenzie That is for Admission Encounter part. How to implement the Encounter for Hospitalized patient.
We have Encounters like for each day. How to implement that?
Jeffrey Danford (Nov 28 2018 at 14:42):
Wouldn't that be an EpisodeOfCare? It seems that resource would be a better match to what you're trying to track.
Mounika (Nov 29 2018 at 13:29):
Episode of Care is for diagnosis. That is a bundling concept. We want to capture Encounters of day1, day2,..etc and which Care Teams were involved.
Brian Postlethwaite (Dec 03 2018 at 10:27):
Episode of care can be more than grouping diagnosis, can be for other types of bundling too. But this sounds more like an addmssion encounter, and partof encounters. Not sure where the care team is coming in here, if the practitioners are different each time, then I would have expected you to enter them into the encounter, rather than the care team reference.
René Spronk (Dec 10 2018 at 13:08):
Billing/financial rules cause a lot of differences as to how one views and records encounters. In this case there seem to be administrative/financial rules for wishing to track these encounters. Nothing wrong with creating encounters to track the (patient, careTeam) relationship, and to create a new encounter each and every day. Common: no. But we've seen stranger things..
Last updated: Apr 12 2022 at 19:14 UTC
