The Care Team includes all the people and organizations who plan to participate in the coordination and delivery of care for a patient.

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.

Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element.

This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.

An Extension

R5: CareTeam.telecom (new:ContactPoint)

Element CareTeam.telecom has a context of CareTeam based on following the parent source element upwards and mapping to CareTeam. Element CareTeam.telecom has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). The ContactPoint.use code of home is not appropriate to use. These contacts are not the contact details of individual care team members.

May be used to represent additional information that is not part of the basic definition of the resource, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order 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 is allowed to 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.

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.

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.

Indicates the status of the care team.

R5: CareTeam.telecom (new:ContactPoint)

Element CareTeam.telecom has a context of CareTeam based on following the parent source element upwards and mapping to CareTeam. Element CareTeam.telecom has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). The ContactPoint.use code of home is not appropriate to use. These contacts are not the contact details of individual care team members.

R5: CareTeam.subject additional types from child elements (display, identifier, reference, type)

Element CareTeam.subject is mapped to FHIR STU3 element CareTeam.subject as SourceIsBroaderThanTarget. The mappings for CareTeam.subject do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element CareTeam.subject with unmapped reference targets: Group, Patient. Use Group for care provision to all members of the group (e.g. group therapy). Use Patient for care provision to an individual patient.

R5: CareTeam.participant.coverage[x] (new:Period, Timing)

Element CareTeam.participant.coverage[x] has a context of CareTeam.participant based on following the parent source element upwards and mapping to CareTeam. Element CareTeam.participant.coverage[x] has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). This is populated while creating / managing the CareTeam to ensure there is coverage when servicing CarePlan activities from the Schedule.

R5: CareTeam.participant.member

Element CareTeam.participant.member is mapped to FHIR STU3 element CareTeam.participant.member as SourceIsBroaderThanTarget. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element CareTeam.participant.member with unmapped reference targets: CareTeam, Organization, Patient, Practitioner, PractitionerRole, RelatedPerson. 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.

R5: CareTeam.participant.onBehalfOf additional types from child elements (display, identifier, reference, type)

Element CareTeam.participant.onBehalfOf is mapped to FHIR STU3 element CareTeam.participant.onBehalfOf as SourceIsBroaderThanTarget. The mappings for CareTeam.participant.onBehalfOf do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element CareTeam.participant.onBehalfOf with unmapped reference targets: Organization.

R5: CareTeam.managingOrganization additional types from child elements (display, identifier, reference, type)

Element CareTeam.managingOrganization is mapped to FHIR STU3 element CareTeam.managingOrganization as SourceIsBroaderThanTarget. The mappings for CareTeam.managingOrganization do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element CareTeam.managingOrganization with unmapped reference targets: Organization.

The Care Team includes all the people and organizations who plan to participate in the coordination and delivery of care for a patient.

The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

The only time that a resource does not have an id is when it is being submitted to the server using a create operation.

The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource.

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.

Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element.

This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.

The base language in which the resource is written.

Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).

Unless not suitable, these codes SHALL be taken from Common Languages
(extensible to http://hl7.org/fhir/ValueSet/languages|3.0.2)

A human language.

A human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.

Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded in formation is added later.

These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.

This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again.

An Extension

R5: CareTeam.telecom (new:ContactPoint)

Element CareTeam.telecom has a context of CareTeam based on following the parent source element upwards and mapping to CareTeam. Element CareTeam.telecom has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). The ContactPoint.use code of home is not appropriate to use. These contacts are not the contact details of individual care team members.

May be used to represent additional information that is not part of the basic definition of the resource, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order 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 is allowed to 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.

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.

This records identifiers associated with this care team that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate.

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.

Indicates the status of the care 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.

Indicates the type of care team.

Used for filtering what teams(s) are retrieved and displayed to different types of users.

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 . ).

Identifies the patient or group whose intended care is handled by the team.

Allows the team to care for a group (e.g. marriage) therapy.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: CareTeam.subject additional types from child elements (display, identifier, reference, type)

Element CareTeam.subject is mapped to FHIR STU3 element CareTeam.subject as SourceIsBroaderThanTarget. The mappings for CareTeam.subject do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element CareTeam.subject with unmapped reference targets: Group, Patient. Use Group for care provision to all members of the group (e.g. group therapy). Use Patient for care provision to an individual patient.

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

The encounter or episode of care that establishes the context for this care team.

Indicates when the team did (or is intended to) come into effect and end.

Allows tracking what team(s) are in effect at a particular time.

Identifies all people and organizations who are expected to be involved in the care team.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: CareTeam.participant.coverage[x] (new:Period, Timing)

Element CareTeam.participant.coverage[x] has a context of CareTeam.participant based on following the parent source element upwards and mapping to CareTeam. Element CareTeam.participant.coverage[x] has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). This is populated while creating / managing the CareTeam to ensure there is coverage when servicing CarePlan activities from the Schedule.

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 that contains it. Usually modifier elements provide negation or qualification. In order 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 is allowed to 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.

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.

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.

Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc.

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.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: CareTeam.participant.member

Element CareTeam.participant.member is mapped to FHIR STU3 element CareTeam.participant.member as SourceIsBroaderThanTarget. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element CareTeam.participant.member with unmapped reference targets: CareTeam, Organization, Patient, Practitioner, PractitionerRole, RelatedPerson. 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.

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

The organization of the practitioner.

Practitioners can be associated with multiple organizations. This element indicates which organization they were acting on behalf of.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: CareTeam.participant.onBehalfOf additional types from child elements (display, identifier, reference, type)

Element CareTeam.participant.onBehalfOf is mapped to FHIR STU3 element CareTeam.participant.onBehalfOf as SourceIsBroaderThanTarget. The mappings for CareTeam.participant.onBehalfOf do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element CareTeam.participant.onBehalfOf with unmapped reference targets: Organization.

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

Indicates when the specific member or organization did (or is intended to) come into effect and end.

Describes why the care team exists.

Indicates the reason for the care team.

Condition(s) that this care team addresses.

The organization responsible for the care team.

Allows for multiple organizations to collaboratively manage cross-organizational, longitudinal care plan.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: CareTeam.managingOrganization additional types from child elements (display, identifier, reference, type)

Element CareTeam.managingOrganization is mapped to FHIR STU3 element CareTeam.managingOrganization as SourceIsBroaderThanTarget. The mappings for CareTeam.managingOrganization do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element CareTeam.managingOrganization with unmapped reference targets: Organization.

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

Comments made about the CareTeam.