Generated Narrative: StructureDefinition CareTeamMemberAct version: 5; Last updated: 2023-07-11 23:41:50+0000 Name Flags Card. Type Description & Constraints Act <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-text-ref-value )">C 1..1 Act 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-text-ref-value #xD; Slices for templateId 1..* II Slice: Unordered, Open by value:root, value:extension #xD; templateId:care-team-member-act 1..1 II #xD; @root 1..1 oid, uuid, ruid Required Pattern: 2.16.840.1.113883.10.20.22.4.500.1 #xD; @extension 1..1 st Required Pattern: 2024-05-01 #xD; @classCode 1..1 cs Fixed Value: PCPR #xD; @moodCode 1..1 cs Fixed Value: EVN #xD; code 1..1 CD Care team information panel #xD; @code 1..1 cs Required Pattern: 92707-9 #xD; @codeSystem 1..1 oid, uuid, ruid LOINC Required Pattern: 2.16.840.1.113883.6.1 #xD; text <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-text-ref-value )">C 0..1 ED SHOULD reference the portion of section narrative text corresponding to this entry #xD; reference <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 ( value-starts-octothorpe )">C 0..1 TEL Constraints: value-starts-octothorpe #xD; statusCode 1..1 CS #xD; @nullFlavor 0..0 #xD; @code 1..1 cs Binding: ActStatus (required) #xD; effectiveTime 1..1 IVL_TS #xD; low 1..1 IVXB_TS #xD; high 0..1 IVXB_TS #xD; performer 1..1 Performer2 #xD; sdtcFunctionCode 0..1 CE XML Namespace: urn:hl7-org:sdtc 헨?헦?헖?헗?헜?: Care Team Member Role - This sdtc:functionCode represents the function or role of the member on the care team. For example, the care team member roles on the care team can be a caregiver and a professional nurse or a primary care provider and the care coordinator. XML: functionCode (urn:hl7-org:sdtc) Binding: Care Team Member Function (preferred) #xD; assignedEntity <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 ( 4515-180, should-addr, should-telecom, should-assignedPerson )">C 1..1 AssignedEntity Constraints: 4515-180, should-addr, should-telecom, should-assignedPerson #xD; id 1..* II 헨?헦?헖?헗?헜?: Care Team Member Identifier #xD; @root C 0..1 oid, uuid, ruid Constraints: should-npi #xD; sdtcSpecialty 0..* CE Binding: PracticeSettingCodeValueSet (preferred) #xD; addr 0..* USRealmAddress 헨?헦?헖?헗?헜?: Care Team Member Location #xD; telecom 0..* TEL 헨?헦?헖?헗?헜?: Care Team Member Telecom #xD; assignedPerson 0..1 Person 헨?헦?헖?헗?헜?: Care Team Member Name #xD; name 1..1 USRealmPersonNamePNUSFIELDED #xD; representedOrganization 0..1 Organization #xD; telecom 1..* TEL #xD; addr 1..* USRealmAddress #xD; Slices for participant 0..* Participant2 Slice: Unordered, Open by value:typeCode #xD; participant:location 0..* Participant2 This participant represents the location where the care team member provides the service. #xD; @typeCode 1..1 cs Fixed Value: LOC #xD; participantRole 1..1 ParticipantRole #xD; participant:addl-functions 0..* Participant2 This participant is used to express additional care team functions performed by this member of the team. Include additional participant to record additional roles (functionCode) this Care Team member plays. #xD; @typeCode 1..1 cs Fixed Value: IND #xD; sdtcFunctionCode 1..1 CE sdtc:functionCode Binding: Care Team Member Function (required) #xD; participantRole 1..1 ParticipantRole #xD; @nullFlavor 1..1 cs Required Pattern: NA #xD; Slices for entryRelationship 0..* EntryRelationship Slice: Unordered, Open by profile:observation, profile:act, exists:encounter, exists:observation, exists:act #xD; entryRelationship:encounter 0..* EntryRelationship entryRelationship #xD; @typeCode 1..1 cs Fixed Value: REFR #xD; act 0..0 #xD; encounter C 1..1 Encounter Constraints: 4515-90 #xD; id 1..1 II #xD; observation 0..0 #xD; entryRelationship:note 0..* EntryRelationship This is the note activity to narratively describe information about the member on the care team. #xD; @typeCode 1..1 cs Fixed Value: REFR #xD; act 1..1 NoteActivity #xD; encounter 0..0 #xD; observation 0..0 #xD; entryRelationship:schedule 0..* EntryRelationship This is the schedule of when or how frequently the care team member participates (or provides care to the patient) on the care team. #xD; @typeCode 1..1 cs Fixed Value: REFR #xD; act 0..0 #xD; encounter 0..0 #xD; observation 1..1 CareTeamMemberScheduleObservation #xD; Documentation for this format
HL7 International - Structured Documents
This template is used to represent a member of the care team. Care team members can include healthcare and community services providers, caregivers, relatives, the patient themselves, etc. A care team member can be another care team or an organization. Care team member attributes include the following: Care team member status on the care team Care team member time (e.g. duration, point-in-time, etc.) on the care team Schedule of the care team member describing when the care team member usually participates on the care team Care team member function on the care team such as the care team member specialty, relationship to the patient, and also role on the care team Care team member name, address, telecom, organization, etc. Care team member information (narrative description about the care team member) The performer/assignedEntity/id may be set equal to (a pointer to) an id on a performer elsewhere in the document (header or entries) or a new performer can be described here. If the id is pointing to a performer already described elsewhere in the document, assignedEntity/id is sufficient to identify this performer and none of the remaining details of assignedEntity are required to be set. Application Software must be responsible for resolving the identifier back to its original object and then rendering the information in the correct place in the containing section's narrative text. This id must be a pointer to another Performer. #### Templates Used Although open templates may contain any valid CDA content, the following templates are specifically called out by this template: **Optional EntryRelationships**: [CareTeamMemberScheduleObservation](StructureDefinition-CareTeamMemberScheduleObservation.html), [NoteActivity](StructureDefinition-NoteActivity.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.
SHALL contain exactly one [1..1] @classCode="PCPR" Provision of Care (CONF:4515-53).
SHALL contain exactly one [1..1] @moodCode="EVN" Event (CONF:4515-54).
SHALL contain exactly one [1..1] code (CONF:4515-27).
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.
SHOULD reference the portion of section narrative text corresponding to this entry
Indicates whether the raw byte data is compressed, and what compression algorithm was used.
The integrity check is a short binary value representing a cryptographically strong checksum that is calculated over the binary data. The purpose of this property, when communicated with a reference is for anyone to validate later whether the reference still resolved to the same data that the reference resolved to when the encapsulated data value with reference was created.
Specifies the algorithm used to compute the integrityCheck value. The cryptographically strong checksum algorithm Secure Hash Algorithm-1 (SHA-1) is currently the industry standard. It has superseded the MD5 algorithm only a couple of years ago, when certain flaws in the security of MD5 were discovered. Currently the SHA-1 hash algorithm is the default choice for the integrity check algorithm. Note that SHA-256 is also entering widespread usage.
For character based information the language property specifies the human language of the text.
Identifies the type of the encapsulated data and identifies a method to interpret or render the data.
Allows for mixed text content. If @representation='B64', this SHALL be a base64binary string.
Data that is primarily intended for human interpretation or for further machine processing is outside the scope of HL7. This includes unformatted or formatted written language, multimedia data, or structured information as defined by a different standard (e.g., XML-signatures.)
This element is represented in XML as textual content. The actual name "xmlText" will not appear in a CDA instance.
A telecommunication address (TEL), such as a URL for HTTP or FTP, which will resolve to precisely the same binary data that could as well have been provided as inline data.
If reference/@value is present, it SHALL begin with a '#' and SHALL point to its corresponding narrative
value.exists() implies value.startsWith('#')
An abbreviated rendition of the full data. A thumbnail requires significantly fewer resources than the full data, while still maintaining some distinctive similarity with the full data. A thumbnail is typically used with by-reference encapsulated data. It allows a user to select data more efficiently before actually downloading through the reference.
Thumbnails cannot contain their own thumbnails
SHALL contain exactly one [1..1] statusCode (CONF:4515-62).
SHALL contain exactly one [1..1] effectiveTime (CONF:4515-33).
A quantity specifying a point on the axis of natural time. A point in time is most often represented as a calendar expression.
A code specifying whether the set component is included (union) or excluded (set-difference) from the set, or other set operations with the current set component and the set as constructed from the representation stream up to the current point.
This effectiveTime SHALL contain exactly one [1..1] low (CONF:4515-167).
The arithmetic mean of the interval (low plus high divided by 2). The purpose of distinguishing the center as a semantic property is for conversions of intervals from and to point values.
The difference between high and low boundary. The purpose of distinguishing a width property is to handle all cases of incomplete information symmetrically. In any interval representation only two of the three properties high, low, and width need to be stated and the third can be derived.
This effectiveTime MAY contain zero or one [0..1] high (CONF:4515-168).
SHALL contain exactly one [1..1] performer (CONF:4515-160)
𝗨𝗦𝗖𝗗𝗜: Care Team Member Role - This sdtc:functionCode represents the function or role of the member on the care team. For example, the care team member roles on the care team can be a caregiver and a professional nurse or a primary care provider and the care coordinator.
MAY contain zero or one [0..1] sdtc:functionCode, which SHOULD be selected from ValueSet Care Team Member Function urn:oid:2.16.840.1.113762.1.4.1099.30 DYNAMIC (CONF:4515-161).
SHALL contain exactly one [1..1] assignedEntity (CONF:4515-175).
If the assignedEntity/id is not referencing a Performer elsewhere in the document with an assignedPerson populated, this assignedEntity SHALL contain exactly one [1..1] assignedPerson (CONF:4515-180).
assignedPerson.exists() or (%resource.descendants().ofType(CDA.Performer2).where(assignedEntity.assignedPerson.exists() and assignedEntity.id.exists($this.root = %context.id.first().root and $this.extension ~ %context.id.first().extension)))
This assignedEntity SHALL contain at least one [1..*] id (CONF:4515-176).
Such ids SHOULD contain zero or one [0..1] @root="2.16.840.1.113883.4.6" National Provider Identifier (CONF:4515-177).
This assignedEntity SHOULD contain zero or more [0..*] addr (CONF:4515-182).
This assignedEntity SHOULD contain zero or more [0..*] telecom (CONF:4515-183).
This assignedEntity SHOULD contain zero or one [0..1] assignedPerson (CONF:4515-178).
The assignedPerson, if present, SHALL contain exactly one [1..1] US Realm Person Name (PN.US.FIELDED) (identifier: urn:oid:2.16.840.1.113883.10.20.22.5.1.1) (CONF:4515-179).
The desc extension allows multimedia depictions of patients, healthcare providers, or other individuals to be included in a CDA document.
Each participant role other than an informant/relatedEntity may have zero or more relationship roles with the patient. Each of these roles can be expressed with an asPatientRelationship element which further describes the type of role using a code element.
This assignedEntity MAY contain zero or one [0..1] representedOrganization (CONF:4515-181).
MAY contain zero or more [0..*] participant (CONF:4515-171) such that it
This participant represents the location where the care team member provides the service.
SHALL contain exactly one [1..1] @typeCode="LOC" Location (CodeSystem: HL7ParticipationType urn:oid:2.16.840.1.113883.5.90) (CONF:4515-174).
SHALL contain exactly one [1..1] participantRole (CONF:4515-173).
This participant is used to express additional care team functions performed by this member of the team. Include additional participant to record additional roles (functionCode) this Care Team member plays.
MAY contain zero or more [0..*] participant (CONF:4515-76) such that it
SHALL contain exactly one [1..1] @typeCode="IND" Indirect Target (CodeSystem: HL7ParticipationType urn:oid:2.16.840.1.113883.5.90) (CONF:4515-78).
SHALL contain exactly one [1..1] sdtc:functionCode, which SHALL be selected from ValueSet Care Team Member Function urn:oid:2.16.840.1.113762.1.4.1099.30 DYNAMIC (CONF:4515-169).
This participantRole SHALL contain exactly one [1..1] @nullFlavor="NI" No Information. (CONF:4515-172).
MAY contain zero or one [0..1] entryRelationship (CONF:4515-94) such that it
MAY contain zero or more [0..*] entryRelationship (CONF:4515-86) such that it
SHALL contain exactly one [1..1] @typeCode="REFR" Refers to (CodeSystem: HL7ActRelationshipType urn:oid:2.16.840.1.113883.5.1002) (CONF:4515-87).
The entryRelationship.inversionInd can be set to "true" to indicate that the relationship should be interpreted as if the roles of the source and target entries were reversed.
The entryRelationship.contextConductionInd differs from the otherwise common use of this attribute in that in all other cases where this attribute is used, the value is fixed at "true", whereas here the value is defaulted to "true", and can be changed to "false" when referencing an entry in the same document. Setting the context conduction to false when referencing an entry in the same document keeps clear the fact that the referenced object retains its original context.
SHALL contain exactly one [1..1] encounter (CONF:4515-88).
If the first id does not match an encounter/id from an encounter elsewhere within the same document and the id does not contain @nullFlavor="NA", then this entry SHALL conform to the Encounter Activity (identifier: urn:hl7ii:2.16.840.1.113883.10.20.22.4.49:2015-08-01) (CONF:4515-90).
id.first().nullFlavor = 'NA' or (%resource.descendants().ofType(CDA.Encounter).where(hasTemplateIdOf('http://hl7.org/cda/us/ccda/StructureDefinition/EncounterActivity') and id.exists($this.root = %context.id.first().root and $this.extension ~ %context.id.first().extension)))
This encounter SHALL contain exactly one [1..1] id (CONF:4515-89).
This is the note activity to narratively describe information about the member on the care team.
MAY contain zero or more [0..*] entryRelationship (CONF:4515-91) such that it
SHALL contain exactly one [1..1] @typeCode="REFR" Refers to (CodeSystem: HL7ActRelationshipType urn:oid:2.16.840.1.113883.5.1002) (CONF:4515-92).
This is the schedule of when or how frequently the care team member participates (or provides care to the patient) on the care team.
SHALL contain exactly one [1..1] @typeCode="REFR" Refers to (CodeSystem: HL7ActRelationshipType urn:oid:2.16.840.1.113883.5.1002) (CONF:4515-96).
SHALL contain exactly one [1..1] Care Team Member Schedule Observation (identifier: urn:hl7ii:2.16.840.1.113883.10.20.22.4.500.3:2022-06-01) (CONF:4515-95).