Release
4B
5
Clinical
Summary
This
page
is
part
of
the
FHIR
Specification
(v4.3.0:
R4B
(v5.0.0:
R5
-
STU
).
The
This
is
the
current
published
version
which
supercedes
in
it's
permanent
home
(it
will
always
be
available
at
this
version
is
5.0.0
.
URL).
For
a
full
list
of
available
versions,
see
the
Directory
of
published
versions
.
Page
versions:
R5
R4B
R5
R4B
R4
R3
|
Patient
Care
Work
Group
|
Maturity Level : 2 | Trial Use | Security Category : Patient |
Compartments
:
|
The
Care
Team
includes
all
the
people
and
organizations
who
plan
to
participate
in
the
coordination
and
delivery
of
care
for
a
patient.
care.
The
CareTeam
includes
all
the
people,
teams,
people
and
organizations
who
plan
to
participate
in
the
coordination
and
delivery
of
care
for
and
is
assigned
to:
Care Team 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
participants
within
a
particular
Patient.
The
actors
CareTeam
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.
Structure
| Name | Flags | Card. | Type |
Description
&
Constraints
|
|---|---|---|---|---|
CareTeam
|
TU | DomainResource |
Planned
participants
in
the
coordination
and
delivery
of
care
Elements defined in Ancestors: id , meta , implicitRules , language , text , contained , extension , modifierExtension |
|
identifier
|
Σ | 0..* | Identifier |
External
Ids
for
this
team
|
status
|
?! Σ | 0..1 | code |
proposed
|
active
|
suspended
|
inactive
|
entered-in-error
Binding: |
|
category
|
Σ | 0..* | CodeableConcept |
Type
of
team
Binding: Care Team category ( Example ) |
|
name
|
Σ | 0..1 | string |
Name
of
the
team,
such
as
crisis
assessment
team
|
subject
|
Σ | 0..1 | Reference ( Patient | Group ) |
Who
care
team
is
for
|
|
period
|
Σ | 0..1 |
|
Time
period
team
covers
|
participant
|
|
0..* | BackboneElement |
Members
of
the
team
+ Rule: CareTeam.participant.onBehalfOf can only be populated when CareTeam.participant.member is a Practitioner + Warning: CareTeam.participant.role or CareTeam.participant.member exists |
role
|
Σ C | 0..1 | CodeableConcept |
Type
of
involvement
Binding: Participant Roles ( Example ) |
|
member
|
Σ C | 0..1 | Reference ( Practitioner | PractitionerRole | RelatedPerson | Patient | Organization | CareTeam ) |
Who
is
involved
|
|
onBehalfOf
|
Σ C | 0..1 | Reference ( Organization ) |
Organization
of
the
practitioner
|
coverage[x]
|
0..1 |
When
the
member
is
generally
available
within
this
care
team
| ||
coveragePeriod
|
|
Period | ||
coverageTiming
|
|
|
||
|
|
0..* |
|
Why
the
care
team
exists
Binding: SNOMED CT Clinical Findings ( Example ) |
|
|
managingOrganization
|
Σ | 0..* | Reference ( Organization ) |
Organization
responsible
for
the
care
team
|
|
telecom
|
0..* | ContactPoint |
A
contact
detail
for
the
care
team
(that
applies
to
all
members)
|
|
|
note
|
0..* | Annotation |
Comments
made
about
the
CareTeam
|
|
|
Documentation
for
this
format
|
||||
See the Extensions for this resource
UML Diagram ( Legend )
XML Template
<<CareTeam xmlns="http://hl7.org/fhir"><!-- from Resource: id, meta, implicitRules, and language --> <!-- from DomainResource: text, contained, extension, and modifierExtension --> <identifier><!-- 0..* Identifier External Ids for this team --></identifier> <status value="[code]"/><!-- 0..1 proposed | active | suspended | inactive | entered-in-error --> <category><!-- 0..* CodeableConcept Type of team --></category> <name value="[string]"/><!-- 0..1 Name of the team, such as crisis assessment team --> <subject><!-- 0..1 Reference(Group|Patient) Who care team is for --></subject>
<</encounter><period><!-- 0..1 Period Time period team covers --></period>< <</role> <|<participant> <!-- 0..* Members of the team --> <role><!-- I 0..1 CodeableConcept Type of involvement --></role> <member><!-- I 0..1 Reference(CareTeam|Organization|Patient|Practitioner| PractitionerRole|RelatedPerson) Who is involved --></member><</onBehalfOf> <</period><onBehalfOf><!-- I 0..1 Reference(Organization) Organization of the practitioner --></onBehalfOf> <coverage[x]><!-- 0..1 Period|Timing When the member is generally available within this care team --></coverage[x]> </participant><</reasonCode> <</reasonReference><reason><!-- 0..* CodeableReference(Condition) Why the care team exists --></reason> <managingOrganization><!-- 0..* Reference(Organization) Organization responsible for the care team --></managingOrganization> <telecom><!-- 0..* ContactPoint A contact detail for the care team (that applies to all members) --></telecom> <note><!-- 0..* Annotation Comments made about the CareTeam --></note> </CareTeam>
JSON Template
{
"resourceType" : "",
"resourceType" : "CareTeam",
// from Resource: id, meta, implicitRules, and language
// from DomainResource: text, contained, extension, and modifierExtension
"identifier" : [{ Identifier }], // External Ids for this team
"status" : "<code>", // proposed | active | suspended | inactive | entered-in-error
"category" : [{ CodeableConcept }], // Type of team
"name" : "<string>", // Name of the team, such as crisis assessment team
"subject" : { Reference(Group|Patient) }, // Who care team is for
"
"period" : { Period }, // Time period team covers
"
"
"participant" : [{ // Members of the team
"role" : { CodeableConcept }, // I Type of involvement
"member" : { Reference(CareTeam|Organization|Patient|Practitioner|
"
"
PractitionerRole|RelatedPerson) }, // I Who is involved
"onBehalfOf" : { Reference(Organization) }, // I Organization of the practitioner
// coverage[x]: When the member is generally available within this care team. One of these 2:
"coveragePeriod" : { Period },
"coverageTiming" : { Timing }
}],
"
"
"reason" : [{ CodeableReference(Condition) }], // Why the care team exists
"managingOrganization" : [{ Reference(Organization) }], // Organization responsible for the care team
"telecom" : [{ ContactPoint }], // A contact detail for the care team (that applies to all members)
"note" : [{ Annotation }] // Comments made about the CareTeam
}
Turtle Template
@prefix fhir: <http://hl7.org/fhir/> .[ a fhir:;[ a fhir:CareTeam; fhir:nodeRole fhir:treeRoot; # if this is the parser root # from Resource: .id, .meta, .implicitRules, and .language # from DomainResource: .text, .contained, .extension, and .modifierExtensionfhir: fhir: fhir: fhir: fhir: fhir: fhir: fhir: fhir: fhir: fhir: fhir: ], ...; fhir: fhir: fhir: fhir: fhir:fhir:identifier ( [ Identifier ] ... ) ; # 0..* External Ids for this team fhir:status [ code ] ; # 0..1 proposed | active | suspended | inactive | entered-in-error fhir:category ( [ CodeableConcept ] ... ) ; # 0..* Type of team fhir:name [ string ] ; # 0..1 Name of the team, such as crisis assessment team fhir:subject [ Reference(Group|Patient) ] ; # 0..1 Who care team is for fhir:period [ Period ] ; # 0..1 Time period team covers fhir:participant ( [ # 0..* Members of the team fhir:role [ CodeableConcept ] ; # 0..1 I Type of involvement fhir:member [ Reference(CareTeam|Organization|Patient|Practitioner|PractitionerRole|RelatedPerson) ] ; # 0..1 I Who is involved fhir:onBehalfOf [ Reference(Organization) ] ; # 0..1 I Organization of the practitioner # coverage[x] : 0..1 When the member is generally available within this care team. One of these 2 fhir:coverage [ a fhir:Period ; Period ] fhir:coverage [ a fhir:Timing ; Timing ] ] ... ) ; fhir:reason ( [ CodeableReference(Condition) ] ... ) ; # 0..* Why the care team exists fhir:managingOrganization ( [ Reference(Organization) ] ... ) ; # 0..* Organization responsible for the care team fhir:telecom ( [ ContactPoint ] ... ) ; # 0..* A contact detail for the care team (that applies to all members) fhir:note ( [ Annotation ] ... ) ; # 0..* Comments made about the CareTeam ]
Changes
since
from
both
R4
and
R4B
| CareTeam | |
| CareTeam.participant.role |
|
| CareTeam.participant.coverage[x] |
|
| CareTeam.reason |
|
| CareTeam.encounter |
|
| CareTeam.participant.period |
|
| CareTeam.reasonCode |
|
| CareTeam.reasonReference |
|
See the Full Difference for further information
This
analysis
is
available
for
R4
as
XML
or
JSON
.
Conversions
between
R3
and
R4
for
R4B
as
XML
or
JSON
.
See
R3
<-->
R4
<-->
R5
Conversion
Maps
(status
=
1
test
that
all
execute
ok.
All
tests
pass
round-trip
testing
and
1
r3
resources
are
invalid
(0
errors).
)
See
Conversions
Summary
.)
Structure
| Name | Flags | Card. | Type |
Description
&
Constraints
|
|---|---|---|---|---|
|
CareTeam
|
TU | DomainResource |
Planned
participants
in
the
coordination
and
delivery
of
care
Elements defined in Ancestors: id , meta , implicitRules , language , text , contained , extension , modifierExtension |
|
|
identifier
|
Σ | 0..* | Identifier |
External
Ids
for
this
team
|
|
status
|
?! Σ | 0..1 | code |
proposed
|
active
|
suspended
|
inactive
|
entered-in-error
Binding: |
|
category
|
Σ | 0..* | CodeableConcept |
Type
of
team
Binding: Care Team category ( Example ) |
|
name
|
Σ | 0..1 | string |
Name
of
the
team,
such
as
crisis
assessment
team
|
|
subject
|
Σ | 0..1 | Reference ( Patient | Group ) |
Who
care
team
is
for
|
|
period
|
Σ | 0..1 |
|
Time
period
team
covers
|
|
participant
|
|
0..* | BackboneElement |
Members
of
the
team
+ Rule: CareTeam.participant.onBehalfOf can only be populated when CareTeam.participant.member is a Practitioner + Warning: CareTeam.participant.role or CareTeam.participant.member exists |
|
role
|
Σ C | 0..1 | CodeableConcept |
Type
of
involvement
Binding: Participant Roles ( Example ) |
|
member
|
Σ C | 0..1 | Reference ( Practitioner | PractitionerRole | RelatedPerson | Patient | Organization | CareTeam ) |
Who
is
involved
|
|
onBehalfOf
|
Σ C | 0..1 | Reference ( Organization ) |
Organization
of
the
practitioner
|
|
coverage[x]
|
0..1 |
When
the
member
is
generally
available
within
this
care
team
|
||
|
coveragePeriod
|
|
Period | ||
|
coverageTiming
|
|
|
||
|
|
0..* |
|
Why
the
care
team
exists
Binding: SNOMED CT Clinical Findings ( Example ) |
|
|
managingOrganization
|
Σ | 0..* | Reference ( Organization ) |
Organization
responsible
for
the
care
team
|
|
telecom
|
0..* | ContactPoint |
A
contact
detail
for
the
care
team
(that
applies
to
all
members)
|
|
|
note
|
0..* | Annotation |
Comments
made
about
the
CareTeam
|
|
|
Documentation
for
this
format
|
||||
See the Extensions for this resource
XML Template
<<CareTeam xmlns="http://hl7.org/fhir"><</encounter><period><!-- 0..1 Period Time period team covers --></period>< <</role> <|<participant> <!-- 0..* Members of the team --> <role><!-- I 0..1 CodeableConcept Type of involvement --></role> <member><!-- I 0..1 Reference(CareTeam|Organization|Patient|Practitioner| PractitionerRole|RelatedPerson) Who is involved --></member><</onBehalfOf> <</period><onBehalfOf><!-- I 0..1 Reference(Organization) Organization of the practitioner --></onBehalfOf> <coverage[x]><!-- 0..1 Period|Timing When the member is generally available within this care team --></coverage[x]> </participant><</reasonCode> <</reasonReference><reason><!-- 0..* CodeableReference(Condition) Why the care team exists --></reason> <managingOrganization><!-- 0..* Reference(Organization) Organization responsible for the care team --></managingOrganization> <telecom><!-- 0..* ContactPoint A contact detail for the care team (that applies to all members) --></telecom> <note><!-- 0..* Annotation Comments made about the CareTeam --></note> </CareTeam>
JSON Template
{
"resourceType" : "",
"resourceType" : "CareTeam",
// from Resource: id, meta, implicitRules, and language
// from DomainResource: text, contained, extension, and modifierExtension
"identifier" : [{ Identifier }], // External Ids for this team
"status" : "<code>", // proposed | active | suspended | inactive | entered-in-error
"category" : [{ CodeableConcept }], // Type of team
"name" : "<string>", // Name of the team, such as crisis assessment team
"subject" : { Reference(Group|Patient) }, // Who care team is for
"
"period" : { Period }, // Time period team covers
"
"
"participant" : [{ // Members of the team
"role" : { CodeableConcept }, // I Type of involvement
"member" : { Reference(CareTeam|Organization|Patient|Practitioner|
"
"
PractitionerRole|RelatedPerson) }, // I Who is involved
"onBehalfOf" : { Reference(Organization) }, // I Organization of the practitioner
// coverage[x]: When the member is generally available within this care team. One of these 2:
"coveragePeriod" : { Period },
"coverageTiming" : { Timing }
}],
"
"
"reason" : [{ CodeableReference(Condition) }], // Why the care team exists
"managingOrganization" : [{ Reference(Organization) }], // Organization responsible for the care team
"telecom" : [{ ContactPoint }], // A contact detail for the care team (that applies to all members)
"note" : [{ Annotation }] // Comments made about the CareTeam
}
Turtle Template
@prefix fhir: <http://hl7.org/fhir/> .[ a fhir:;[ a fhir:CareTeam; fhir:nodeRole fhir:treeRoot; # if this is the parser root # from Resource: .id, .meta, .implicitRules, and .language # from DomainResource: .text, .contained, .extension, and .modifierExtensionfhir: fhir: fhir: fhir: fhir: fhir: fhir: fhir: fhir: fhir: fhir: fhir: ], ...; fhir: fhir: fhir: fhir: fhir:fhir:identifier ( [ Identifier ] ... ) ; # 0..* External Ids for this team fhir:status [ code ] ; # 0..1 proposed | active | suspended | inactive | entered-in-error fhir:category ( [ CodeableConcept ] ... ) ; # 0..* Type of team fhir:name [ string ] ; # 0..1 Name of the team, such as crisis assessment team fhir:subject [ Reference(Group|Patient) ] ; # 0..1 Who care team is for fhir:period [ Period ] ; # 0..1 Time period team covers fhir:participant ( [ # 0..* Members of the team fhir:role [ CodeableConcept ] ; # 0..1 I Type of involvement fhir:member [ Reference(CareTeam|Organization|Patient|Practitioner|PractitionerRole|RelatedPerson) ] ; # 0..1 I Who is involved fhir:onBehalfOf [ Reference(Organization) ] ; # 0..1 I Organization of the practitioner # coverage[x] : 0..1 When the member is generally available within this care team. One of these 2 fhir:coverage [ a fhir:Period ; Period ] fhir:coverage [ a fhir:Timing ; Timing ] ] ... ) ; fhir:reason ( [ CodeableReference(Condition) ] ... ) ; # 0..* Why the care team exists fhir:managingOrganization ( [ Reference(Organization) ] ... ) ; # 0..* Organization responsible for the care team fhir:telecom ( [ ContactPoint ] ... ) ; # 0..* A contact detail for the care team (that applies to all members) fhir:note ( [ Annotation ] ... ) ; # 0..* Comments made about the CareTeam ]
Changes
since
Release
4
from
both
R4
and
R4B
| CareTeam | |
| CareTeam.participant.role |
|
| CareTeam.participant.coverage[x] |
|
| CareTeam.reason |
|
| CareTeam.encounter |
|
| CareTeam.participant.period |
|
| CareTeam.reasonCode |
|
| CareTeam.reasonReference |
|
See the Full Difference for further information
This
analysis
is
available
for
R4
as
XML
or
JSON
.
Conversions
between
R3
and
R4
for
R4B
as
XML
or
JSON
.
See
R3
<-->
R4
<-->
R5
Conversion
Maps
(status
=
1
test
that
all
execute
ok.
All
tests
pass
round-trip
testing
and
1
r3
resources
are
invalid
(0
errors).
)
See
Conversions
Summary
.)
See
the
Profiles
&
Extensions
and
the
alternate
Additional
definitions:
Master
Definition
XML
+
JSON
,
XML
Schema
/
Schematron
+
JSON
Schema
,
ShEx
(for
Turtle
)
+
see
the
extensions
,
the
spreadsheet
version
&
the
dependency
analysis
| Path |
|
Type |
|
|---|---|---|---|
| CareTeam.status | CareTeamStatus | Required |
Indicates the status of the care team. |
| CareTeam.category | CareTeamCategory | Example |
Indicates the type of care team. |
| CareTeam.participant.role | ParticipantRoles | Example |
Roles of participants that may be included in a care team. Defined as: Healthcare professional (occupation) or Services (qualifier value). |
|
|
SNOMEDCTClinicalFindings | Example |
This
value
set
includes
all
the
"Clinical
finding"
SNOMED
CT
|
|
|
Level | Location | Description | Expression |
ctm-1
|
Rule | CareTeam.participant | CareTeam.participant.onBehalfOf can only be populated when CareTeam.participant.member is a Practitioner |
onBehalfOf.exists()
implies
|
|
ctm-2
| Warning | CareTeam.participant | CareTeam.participant.role or CareTeam.participant.member exists | role.exists() or member.exists() |
The Provenance resource can be used for detailed review information, such as when the care team was last reviewed and by whom.
Search parameters for this resource. See also the full list of search parameters for this resource , and check the Extensions registry for search parameters on extensions related to this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.
| Name | Type | Description | Expression | In Common |
| category | token | Type of team | CareTeam.category | |
| date | date |
|
|
27 Resources |
|
|
|
|
|
65 Resources |
|
|
|
|
|
|
| participant | reference | Who is involved |
CareTeam.participant.member
( Practitioner , Organization , CareTeam , Patient , PractitionerRole , RelatedPerson ) |
|
| patient | reference | Who care team is for |
CareTeam.subject.where(resolve()
is
Patient)
( Patient ) |
66 Resources |
| status | token | proposed | active | suspended | inactive | entered-in-error | CareTeam.status | |
| subject | reference | Who care team is for |
CareTeam.subject
( Group , Patient ) |
FHIR
®©
HL7.org
2011+.
FHIR
Release
4B
(v4.3.0)
hl7.fhir.r4b.core#4.3.0
R5
hl7.fhir.core#5.0.0
generated
on
Sat,
May
28,
2022
12:54+1000.
Sun,
Mar
26,
2023
15:24+1100.
Links:
Search
|
Version
History
|
Table
of
Contents
|
Glossary
|
QA
Page
|
Compare
to
R4
|
Compare
to
R4B
|
|
Propose
a
change