Name Flags Card. Type Description & Constraints doco
. . CareTeam TU DomainResource Planned participants in the coordination and delivery of care for a patient or group
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
CareTeamStatus ( Required)
. . . category Σ 0..* CodeableConcept Type of team
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
. . . encounter Σ 0..1 Reference( Encounter) Encounter created as part of
. . . period Σ 0..1 Period Time period team covers
. . . participant I 0..* BackboneElement Members of the team
+ Rule: CareTeam.participant.onBehalfOf can only be populated when CareTeam.participant.member is a Practitioner
. . . . role Σ 0..* CodeableConcept Type of involvement
Participant Roles ( Example)
. . . . member Σ 0..1 Reference( Practitioner | PractitionerRole | RelatedPerson | Patient | Organization | CareTeam) Who is involved
. . . . onBehalfOf Σ 0..1 Reference( Organization) Organization of the practitioner
. . . . period 0..1 Period Time period of participant
. . . reasonCode 0..* CodeableConcept Why the care team exists
SNOMED CT Clinical Findings ( Example)
. . . reasonReference 0..* Reference( Condition) Why the care team exists
. . . 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

doco Documentation for this format