NoteActivity

Note Activity

draftC-CDA Templates4.0.0logical20 key elements

The Note Activity represents a clinical note. Notes require authorship, authentication, timing information, and references to other discrete data such as encounters. Similar to the Comment Activity, the Note Activity permits a more specific code to characterize the type of information available in the note. The Note Activity template SHOULD NOT be used in place of a more specific C-CDA entry. Note information included needs to be relevant and pertinent to the information being communicated in the document. When the note information augments data represented in a more specific entry template, the Note Activity can be used in an entryRelationship to the associated standard C-CDA entry. For example, a Procedure Note added as an entryRelationship to a Procedure Activity Procedure entry). The Note Activity template can be used as a standalone entry within a standard C-CDA section (e.g., a note about various procedures which have occurred during a visit as an entry in the Procedures Section) when it does not augment another standard entry. It may also be used to provide additional data about the source of a currently narrative-only section, such as Hospital Course. Finally, if the type of data in the note is not known or no single C-CDA section is appropriate enough, the Note Activity should be placed in a Notes Section. (e.g., a free-text consultation note or a note which includes subjective, objective, assessment, and plan information combined). An alternative is to place the Note Activity as an entryRelationship to an Encounter Activity entry in the Encounters Section, but implementers may wish to group notes categorically into a separate location in CDA documents rather than overloading the Encounters Section.

The narrative Clinical Notes required in USCDI, along with their associated LOINC codes, are outlined below. These note types are included in the Note Types Value Set, which is bound to Act.code.translation.

  • Consultation Note (LOINC: 11488-4)
  • Discharge Summary (LOINC: 18842-5)
  • History & Physical Note (LOINC: 34117-2)
  • Procedures Note (LOINC: 28570-0)
  • Progress Note (LOINC: 11506-3)
  • Surgical Operation Note (Operative Note) (LOINC: 11504-8)
  • Emergency Department Note (LOINC: 34111-5)

Metadata

hl7.org/fhir
Canonical URL
http://hl7.org/cda/us/ccda/StructureDefinition/NoteActivity
ID
NoteActivity
Type
Base Definition
Act
Derivation
constraint
Mandatory and Must-Support Elements

Elements with cardinality > 0 or marked as Must Support (S)

PathCard.TypeFlagsDescription
templateId
1+
:note-activity1..1
1+
templateId.root
1+
templateId.extension
1+
code.code
1+
code.codeSystem
1+
text
1+
SHOULD reference the portion of section narrative text corresponding to this entry
text.reference
1+
text.reference.value
1+
statusCode
1+
Indicates the status of the note. The most common statusCode is completed indicating the note is signed and finalized.
effectiveTime
1+
The effectiveTime represents the clinically relevant time of the note. The precise timestamp of creation / updating should be conveyed in author/time.
author
http://hl7.org/cda/stds/core/StructureDefinition/Author
1+
Represents the person(s) who wrote the note.
participant.time
http://hl7.org/cda/stds/core/StructureDefinition/IVL-TS
1+
Indicates the time of signing the note.
participant.participantRole.id
1+
This may be the ID of the note author. If so, no additional information in this participant is required.
participant.participantRole.playingEntity.name
http://hl7.org/cda/stds/core/StructureDefinition/PN
1+
entryRelationship.inversionInd
1+
entryRelationship.encounter
1+
entryRelationship.encounter.id
1+
reference.externalDocument
1+
reference.externalDocument.id1..1
1+