Generated Narrative: StructureDefinition CareTeamsSection Name Flags Card. Type Description & Constraints Section <a style="padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;; padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;" href="http://hl7.org/fhir/R5/conformance-rules.html#constraints" title="This element has or is affected by constraints ( should-care-team-org )">C 1..1 Section XML Namespace: urn:hl7-org:v3 Base for all types and resources Instance of this type are validated by templateId Logical Container: ClinicalDocument (CDA Class) Constraints: should-care-team-org #xD; Slices for templateId 1..* II Slice: Unordered, Open by value:root, value:extension #xD; templateId:section 1..1 II #xD; @root 1..1 oid, uuid, ruid Required Pattern: 2.16.840.1.113883.10.20.22.2.500 #xD; @extension 1..1 st Required Pattern: 2022-06-01 #xD; code 1..1 CE Patient Care team information #xD; @code 1..1 cs Required Pattern: 85847-2 #xD; @codeSystem 1..1 oid, uuid, ruid Required Pattern: 2.16.840.1.113883.6.1 #xD; title 1..1 ST Label of a section #xD; text 1..1 xhtml Narrative to be rendered #xD; Slices for entry 0..* Entry Slice: Unordered, Open by profile:organizer #xD; entry:primary <a style="padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;; padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;" href="http://hl7.org/fhir/R5/conformance-rules.html#constraints" title="This element has or is affected by constraints ( should-care-team-org )">C 0..* Entry entry #xD; organizer 1..1 CareTeamOrganizer #xD; Documentation for this format
HL7 International - Structured Documents
The Care Teams Section is used to share historical and current Care Team information. The Care Team Section may be included in any type of C-CDA structured document that is an open template. An individual can have more than one Care Team. A Care Team can exist over time such as a longitudinal care team which includes historical members that may be active or inactive on the care team as needed. Or a Care Team, such as a rehabilitation team, may exist to address a person's needs associated with a particular care event, or a team can be based on addressing a specific condition. The Care Team Organizer entry template used in the C-CDA Care Teams Section is meant to support the foundation of effective communication, interaction channels and maintenance of current clinical context awareness for the patient, caregivers and care providers to promote care coordination. #### Templates Used Although open templates may contain any valid CDA content, the following templates are specifically called out by this template: **Recommended Entries**: [CareTeamOrganizer](StructureDefinition-CareTeamOrganizer.html)
Defines the basic properties of every data value. This is an abstract type, meaning that no value can be just a data value without belonging to any concrete type. Every concrete type is a specialization of this general abstract DataValue type.
If a value is an exceptional value (NULL-value), this specifies in what way and why proper information is missing.
When valued in an instance, this attribute signals the imposition of realm-specific constraints. The value of this attribute identifies the realm in question
When valued in an instance, this attribute signals the imposition of constraints defined in an HL7-specified message type. This might be a common type (also known as CMET in the messaging communication environment), or content included within a wrapper. The value of this attribute provides a unique identifier for the type in question.
An II instance must have either a root or an nullFlavor.
A human readable name or mnemonic for the assigning authority. The Assigning Authority Name has no computational value. The purpose of a Assigning Authority Name is to assist an unaided human interpreter of an II value to interpret the authority. Note: no automated processing must depend on the assigning authority name to be present in any form.
Specifies if the identifier is intended for human display and data entry (displayable = true) as opposed to pure machine interoperation (displayable = false).
Identifies the type as an HL7 Registered model
A character string as a unique identifier within the scope of the identifier root.
When valued in an instance, this attribute signals the imposition of a set of template-defined constraints. The value of this attribute provides a unique identifier for the templates in question
A unique identifier that guarantees the global uniqueness of the instance identifier. The root alone may be the entire instance identifier.
Can serve as a target of a linkHtml reference
Unique instance identifier of a particular document section
The plain code symbol defined by the code system. For example, "784.0" is the code symbol of the ICD-9 code "784.0" for headache.
Specifies the code system that defines the code.
If applicable, a version descriptor defined specifically for the given code system.
A name or title for the code, under which the sending system shows the code value to its users.
The valueSet extension adds an attribute for elements with a CD dataType which indicates the particular value set constraining the coded concept.
The valueSetVersion extension adds an attribute for elements with a CD dataType which indicates the version of the particular value set constraining the coded concept.
The text or phrase used as the basis for the coding.
Specifies additional codes that increase the specificity of the the primary code.
A set of other concept descriptors that translate this concept descriptor into other code systems.
If valued, it is to be rendered as part of the narrative content of the clinical document body.
Also referred to as the CDA Narrative Block
Controls the disclosure of information in this section
A value for Section.confidentialityCode overrides the value propagated from StructuredBody.
A value for Section.languageCode overrides the value propagated from StructuredBody.
Primary target of the entries recorded in a section
Most of the time the subject is the same as the recordTarget, but need not be, for instance when the subject is a fetus observed in an obstetrical ultrasound.
The subject participant can be ascribed to a CDA section or a CDA entry. It propagates to nested components, unless overridden. The subject of a document is presumed to be the patient.
The author participant can be ascribed to a CDA section, where it overrides the value(s) propagated from the CDA header.
The informant participant can be ascribed to a CDA section where it overrides the value(s) propagated from the CDA header.
SHOULD contain zero or more [0..*] entry (CONF:4515-1) such that it
Drawn from concept domain DocumentSectionType