Path | Short | Definition | Comments |
---|---|---|---|
Planned participants in the coordination and delivery of care for a patient or group | The Care Team includes all the people and organizations who plan to participate in the coordination and delivery of care for a patient. | ||
identifier | External Ids for this team | Business identifiers assigned to this care team by the performer or other systems which remain constant as the resource is updated and propagates from server to server. | This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number. |
status | proposed | active | suspended | inactive | entered-in-error | Indicates the current state of the care team. | This element is labeled as a modifier because the status contains the code entered-in-error that marks the care team as not currently valid. |
category | Type of team | Identifies what kind of team. This is to support differentiation between multiple co-existing teams, such as care plan team, episode of care team, longitudinal care team. | There may be multiple axis of categorization and one team may serve multiple purposes. |
name | Name of the team, such as crisis assessment team | A label for human use intended to distinguish like teams. E.g. the "red" vs. "green" trauma teams. | The meaning/purpose of the team is conveyed in CareTeam.category. This element may also convey semantics of the team (e.g. "Red trauma team"), but its primary purpose is to distinguish between identical teams in a human-friendly way. ("Team 18735" isn't as friendly.). |
subject | Who care team is for | Identifies the patient or group whose intended care is handled by the team. | |
encounter | Encounter created as part of | The Encounter during which this CareTeam was created or to which the creation of this record is tightly associated. | This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter. |
period | Time period team covers | Indicates when the team did (or is intended to) come into effect and end. | |
participant | Members of the team | Identifies all people and organizations who are expected to be involved in the care team. | |
participant.id | Unique id for inter-element referencing | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
participant.extension | Additional content defined by implementations | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
participant.modifierExtension | Extensions that cannot be ignored even if unrecognized | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
participant.role | Type of involvement | Indicates specific responsibility of an individual within the care team, such as "Primary care physician", "Trained social worker counselor", "Caregiver", etc. | Roles may sometimes be inferred by type of Practitioner. These are relationships that hold only within the context of the care team. General relationships should be handled as properties of the Patient resource directly. |
participant.member | Who is involved | The specific person or organization who is participating/expected to participate in the care team. | Patient only needs to be listed if they have a role other than "subject of care". Member is optional because some participants may be known only by their role, particularly in draft plans. |
participant.onBehalfOf | Organization of the practitioner | The organization of the practitioner. | |
participant.period | Time period of participant | Indicates when the specific member or organization did (or is intended to) come into effect and end. | |
reasonCode | Why the care team exists | Describes why the care team exists. | |
reasonReference | Why the care team exists | Condition(s) that this care team addresses. | |
managingOrganization | Organization responsible for the care team | The organization responsible for the care team. | |
telecom | A contact detail for the care team (that applies to all members) | A central contact detail for the care team (that applies to all members). | The ContactPoint.use code of home is not appropriate to use. These contacts are not the contact details of individual care team members. |
note | Comments made about the CareTeam | Comments made about the CareTeam. |
The CareTeam includes all the people, teams, and organizations who plan to participate in the coordination and delivery of care for a single patient or a group (such as a married couple in therapy or a support group). CareTeam can also be organizationally assigned without a subject in context, such as a code blue team or emergency response team. This is not limited to practitioners, but may include other caregivers such as family members, guardians, the patient themself, or others. The Care Team, depending on where used, may include care team members specific to a particular care plan, an episode, an encounter, or may reflect all known team members across these perspectives. An individual's CareTeam can be dynamic over time, such that there can be transience of team members, such as a rehabilitation team.
Care Team is distinct from Group. Group is patient-independent and identifies an undifferentiated set of individuals who are intended to be the target of one or more clinical activities (e.g. set of clinical trial participants, set of individuals impacted by or at risk of a public health event, a herd or flock, etc.) The CareTeam resource establishes a set of relationships and roles and is specific to a particular Patient. The actors are the individual members or organized group of individuals. CareTeam can be referenced by EpisodeOfCare, Encounter, or CarePlan to identify the set of individuals (and their respective roles) who are intended to be involved in providing the care defined by those resources.
The Provenance resource can be used for detailed review information, such as when the care team was last reviewed and by whom.
category | Type of team | CareTeam.category |
encounter | Encounter created as part of | CareTeam.encounter |
participant | Who is involved | CareTeam.participant.member |
status | proposed | active | suspended | inactive | entered-in-error | CareTeam.status |
subject | Who care team is for | CareTeam.subject |