This
page
is
part
of
the
FHIR
Specification
(v5.0.0:
R5
-
STU
v6.0.0-ballot2:
Release
6
Ballot
(2nd
Draft)
(see
Ballot
Notes
).
This
is
the
The
current
published
version
in
it's
permanent
home
(it
will
always
be
available
at
this
URL).
is
5.0.0
.
For
a
full
list
of
available
versions,
see
the
Directory
of
published
versions
.
Page
versions:
R5
R4B
R4
R3
Careteam.shex
Raw
ShEx
ShEx
statement
for
careteam
PREFIX fhir: <http://hl7.org/fhir/>
PREFIX fhirvs: <http://hl7.org/fhir/ValueSet/>
PREFIX xsd: <http://www.w3.org/2001/XMLSchema#>
PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
IMPORT <code.shex>
IMPORT <Group.shex>
IMPORT <string.shex>
IMPORT <Period.shex>
IMPORT <Timing.shex>
IMPORT <Patient.shex>
IMPORT <Reference.shex>
IMPORT <Identifier.shex>
IMPORT <Annotation.shex>
IMPORT <ContactPoint.shex>
IMPORT <Organization.shex>
IMPORT <Practitioner.shex>
IMPORT <RelatedPerson.shex>
IMPORT <DomainResource.shex>
IMPORT <CodeableConcept.shex>
IMPORT <BackboneElement.shex>
IMPORT <PractitionerRole.shex>
IMPORT <CodeableReference.shex>
start=@<CareTeam> AND {fhir:nodeRole [fhir:treeRoot]}
# Planned participants in the coordination and delivery of care
<CareTeam> EXTENDS @<DomainResource> CLOSED {
a [fhir:CareTeam]?;
fhir:nodeRole [fhir:treeRoot]?;
fhir:identifier @<OneOrMore_Identifier>?; # External Ids for this team
fhir:status @<code> AND
{fhir:v @fhirvs:care-team-status}?; # proposed | active | suspended |
# inactive | entered-in-error
fhir:category @<OneOrMore_CodeableConcept>?; # Type of team
fhir:name @<string>?; # Name of the team, such as crisis
# assessment team
fhir:subject @<Reference> AND {fhir:link
@<Group> OR
@<Patient> ? }?; # Who care team is for
fhir:period @<Period>?; # Time period team covers
fhir:participant @<OneOrMore_CareTeam.participant>?; # Members of the team
fhir:reason @<OneOrMore_CodeableReference>?; # Why the care team exists
fhir:managingOrganization @<OneOrMore_Reference_Organization>?; # Organization responsible for the
# care team
fhir:telecom @<OneOrMore_ContactPoint>?; # A contact detail for the care team
# (that applies to all members)
fhir:note @<OneOrMore_Annotation>?; # Comments made about the CareTeam
}
# Members of the team
<CareTeam.participant> EXTENDS @<BackboneElement> CLOSED {
fhir:role @<CodeableConcept>?; # Type of involvement
fhir:member @<Reference> AND {fhir:link
@<CareTeam> OR
@<Organization> OR
@<Patient> OR
@<Practitioner> OR
@<PractitionerRole> OR
@<RelatedPerson> ? }?; # Who is involved
fhir:onBehalfOf @<Reference> AND {fhir:link
@<Organization> ? }?; # Organization of the practitioner
fhir:coverage @<Period> OR
@<CareTeam> OR
@<Organization> OR
@<Patient> OR
@<Practitioner> OR
@<PractitionerRole> OR
@<RelatedPerson> ? }?; # Entity that the participant is
# acting as a proxy of, or an agent
# of, or in the interest of, or as a
# representative of
fhir:effective @<Period> OR
@<Timing> ?; # When the member is generally
# available within this care team
}
#---------------------- Cardinality Types (OneOrMore) -------------------
<OneOrMore_Identifier> CLOSED {
rdf:first @<Identifier> ;
rdf:rest [rdf:nil] OR @<OneOrMore_Identifier>
}
<OneOrMore_CodeableConcept> CLOSED {
rdf:first @<CodeableConcept> ;
rdf:rest [rdf:nil] OR @<OneOrMore_CodeableConcept>
}
<OneOrMore_CareTeam.participant> CLOSED {
rdf:first @<CareTeam.participant> ;
rdf:rest [rdf:nil] OR @<OneOrMore_CareTeam.participant>
}
<OneOrMore_CodeableReference> CLOSED {
rdf:first @<CodeableReference> ;
rdf:rest [rdf:nil] OR @<OneOrMore_CodeableReference>
}
<OneOrMore_Reference_Organization> CLOSED {
rdf:first @<Reference> AND {fhir:link
@<Organization> } ;
rdf:rest [rdf:nil] OR @<OneOrMore_Reference_Organization>
}
<OneOrMore_ContactPoint> CLOSED {
rdf:first @<ContactPoint> ;
rdf:rest [rdf:nil] OR @<OneOrMore_ContactPoint>
}
<OneOrMore_Annotation> CLOSED {
rdf:first @<Annotation> ;
rdf:rest [rdf:nil] OR @<OneOrMore_Annotation>
}
#---------------------- Value Sets ------------------------
# Indicates the status of the care team.
fhirvs:care-team-status ["proposed" "active" "suspended" "inactive" "entered-in-error"]
Usage
note:
every
effort
has
been
made
to
ensure
that
the
ShEx
files
are
correct
and
useful,
but
they
are
not
a
normative
part
of
the
specification.