Consolidated CDA (C-CDA)
4.0.0-ballot - STU4 Ballot United States of America flag

Consolidated CDA (C-CDA), published by Health Level Seven. This guide is not an authorized publication; it is the continuous build for version 4.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/CDA-ccda/ and changes regularly. See the Directory of published versions

Logical Model: HandoffCommunicationParticipants - Detailed Descriptions

Draft as of 2024-12-19

Definitions for the HandoffCommunicationParticipants logical model.

Guidance on how to interpret the contents of this table can be found here

0. Act
Logical ContainerClinicalDocument (CDA Class)
ValidationInstance of this type are validated by templateId
XML FormatIn the XML format, this property has the namespace urn:hl7-org:v3.
Invariantsshould-text-ref-value: SHOULD contain text/reference/@value (text.reference.value.exists())
2. Act.templateId
Control1..?
SlicingThis element introduces a set of slices on Act.templateId. The slices areUnordered and Open, and can be differentiated using the following discriminators:
  • value @ root
  • 4. Act.templateId:handoff-comm-participants
    Slice Namehandoff-comm-participants
    Control1..1
    6. Act.templateId:handoff-comm-participants.root
    Control1..?
    Pattern Value2.16.840.1.113883.10.20.22.4.141
    8. Act.templateId:handoff-comm-participants.extension
    Control0..0
    10. Act.classCode
    Comments

    SHALL contain exactly one [1..1] @classCode="ACT" Act (CodeSystem: HL7ActClass urn:oid:2.16.840.1.113883.5.6 STATIC) (CONF:1098-30832).

    Fixed ValueACT
    12. Act.moodCode
    Comments

    SHALL contain exactly one [1..1] @moodCode="EVN" (CodeSystem: HL7ActMood urn:oid:2.16.840.1.113883.5.1001) (CONF:1098-30833).

    Fixed ValueEVN
    14. Act.code
    Comments

    SHALL contain exactly one [1..1] code (CONF:1098-30836).

    16. Act.code.code
    Comments

    This code SHALL contain exactly one [1..1] @code="432138007" handoff communication (procedure) (CONF:1098-30837).

    Control1..?
    Pattern Value432138007
    18. Act.code.codeSystem
    Comments

    This code SHALL contain exactly one [1..1] @codeSystem="2.16.840.1.113883.6.96" (CodeSystem: SNOMED CT urn:oid:2.16.840.1.113883.6.96) (CONF:1098-30838).

    Control1..?
    Pattern Value2.16.840.1.113883.6.96
    20. Act.text
    ShortSHOULD reference the portion of section narrative text corresponding to this entry
    22. Act.text.reference
    Invariantsvalue-starts-octothorpe: If reference/@value is present, it SHALL begin with a '#' and SHALL point to its corresponding narrative (value.exists() implies value.startsWith('#'))
    24. Act.statusCode
    Comments

    SHALL contain exactly one [1..1] statusCode (CONF:1098-31668).

    Control1..?
    26. Act.statusCode.code
    Comments

    This statusCode SHALL contain exactly one [1..1] @code="completed" Completed (CodeSystem: HL7ActStatus urn:oid:2.16.840.1.113883.5.14) (CONF:1098-31669).

    Control1..?
    Fixed Valuecompleted
    28. Act.effectiveTime
    ShortThe effective time is the time when the handoff process took place between the sender and receiver of the patient information. This could be the time the information was transmitted, released, or verbally communicated to the next clinician.
    Comments

    SHALL contain exactly one [1..1] effectiveTime (CONF:1098-31670).

    Control1..?
    30. Act.author
    ShortThe Author Participant contains the sender's contact information and is a resource for the Information Recipient for any follow-up questions.
    Comments

    SHALL contain at least one [1..*] Author Participation (identifier: urn:oid:2.16.840.1.113883.10.20.22.4.119) (CONF:1098-31672).

    Control1..?
    Typehttp://hl7.org/cda/stds/core/StructureDefinition/Author(Author Participation)
    32. Act.participant
    ShortDocumentation of the Information Recipient's name and address verifies that the information was exchanged.
    Control1..?
    SlicingThis element introduces a set of slices on Act.participant. The slices areUnordered and Open, and can be differentiated using the following discriminators:
    • value @ typeCode
    • 34. Act.participant:infoRecipient
      Slice NameinfoRecipient
      Comments

      SHALL contain at least one [1..*] participant (CONF:1098-31673) such that it

      Control1..*
      36. Act.participant:infoRecipient.typeCode
      Comments

      SHALL contain exactly one [1..1] @typeCode="IRCP" Information Recipient (CodeSystem: HL7RoleClass urn:oid:2.16.840.1.113883.5.110) (CONF:1098-31674).

      Fixed ValueIRCP
      38. Act.participant:infoRecipient.participantRole
      Comments

      SHALL contain exactly one [1..1] participantRole (CONF:1098-31675).

      Invariantsshould-code: SHOULD contain code (code.exists())
      40. Act.participant:infoRecipient.participantRole.id
      Comments

      This participantRole SHALL contain at least one [1..*] id (CONF:1098-32422).

      Control1..?
      42. Act.participant:infoRecipient.participantRole.code
      Comments

      This participantRole SHOULD contain zero or one [0..1] code, which SHOULD be selected from ValueSet Healthcare Provider Taxonomy urn:oid:2.16.840.1.114222.4.11.1066 DYNAMIC (CONF:1098-31676).

      BindingThe codes SHOULD be taken from Healthcare Provider Taxonomy .
      (preferred to http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.114222.4.11.1066)
      44. Act.participant:infoRecipient.participantRole.addr
      Comments

      This participantRole SHALL contain at least one [1..*] addr (CONF:1098-32392).

      Control1..?
      Typehttp://hl7.org/cda/stds/core/StructureDefinition/AD(US Realm Address)
      46. Act.participant:infoRecipient.participantRole.playingEntity
      Comments

      This participantRole MAY contain zero or one [0..1] playingEntity (CONF:1098-32393).

      48. Act.participant:infoRecipient.participantRole.playingEntity.name
      Comments

      The playingEntity, if present, SHALL contain at least one [1..*] name (CONF:1098-32394).

      Control1..?