Id2.16.840.1.113883.1.11.13856
ref
ad2bbr-
Effective Date2014‑03‑26
Statusfinal FinalVersion LabelDEFN=UV=VO=1360-20160323
NameActClassRootDisplay NameActClassRoot
Description

History description 2014-03-26: Lock all vaue sets untouched since 2014-03-26 to trackingId 2014T1_2014_03_26

description:

A record of something that is being done, has been done, can be done, or is intended or requested to be done.

Examples: The kinds of acts that are common in health care are (1) a clinical observation, (2) an assessment of health condition (such as problems and diagnoses), (3) healthcare goals, (4) treatment services (such as medication, surgery, physical and psychological therapy), (5) assisting, monitoring or attending, (6) training and education services to patients and their next of kin, (7) and notary services (such as advanced directives or living will), (8) editing and maintaining documents, and many others.

Discussion and Rationale: Acts are the pivot of the RIM; all domain information and processes are represented primarily in Acts. Any profession or business, including healthcare, is primarily constituted of intentional and occasionally non-intentional actions, performed and recorded by responsible actors. An Act-instance is a record of such an action.

Acts connect to Entities in their Roles through Participations and connect to other Acts through ActRelationships. Participations are the authors, performers and other responsible parties as well as subjects and beneficiaries (which includes tools and material used in the performance of the act, which are also subjects). The moodCode distinguishes between Acts that are meant as factual records, vs. records of intended or ordered services, and the other modalities in which act can appear.

One of the Participations that all acts have (at least implicitly) is a primary author, who is responsible of the Act and who "owns" the act. Responsibility for the act means responsibility for what is being stated in the Act and as what it is stated. Ownership of the act is assumed in the sense of who may operationally modify the same act. Ownership and responsibility of the Act is not the same as ownership or responsibility of what the Act-object refers to in the real world. The same real world activity can be described by two people, each being the author of their Act, describing the same real world activity. Yet one can be a witness while the other can be a principal performer. The performer has responsibilities for the physical actions; the witness only has responsibility for making a true statement to the best of his or her ability. The two Act-instances may even disagree, but because each is properly attributed to its author, such disagreements can exist side by side and left to arbitration by a recipient of these Act-instances.

In this sense, an Act-instance represents a "statement" according to Rector and Nowlan (1991) [Foundations for an electronic medical record. Methods Inf Med. 30.] Rector and Nowlan have emphasized the importance of understanding the medical record not as a collection of facts, but "a faithful record of what clinicians have heard, seen, thought, and done." Rector and Nowlan go on saying that "the other requirements for a medical record, e.g., that it be attributable and permanent, follow naturally from this view." Indeed the Act class is this attributable statement, and the rules of updating acts (discussed in the state-transition model, see Act.statusCode) versus generating new Act-instances are designed according to this principle of permanent attributable statements.

Rector and Nolan focus on the electronic medical record as a collection of statements, while attributed statements, these are still mostly factual statements. However, the Act class goes beyond this limitation to attributed factual statements, representing what is known as "speech-acts" in linguistics and philosophy. The notion of speech-act includes that there is pragmatic meaning in language utterances, aside from just factual statements; and that these utterances interact with the real world to change the state of affairs, even directly cause physical activities to happen. For example, an order is a speech act that (provided it is issued adequately) will cause the ordered action to be physically performed. The speech act theory has culminated in the seminal work by Austin (1962) [How to do things with words. Oxford University Press].

An activity in the real world may progress from defined, through planned and ordered to executed, which is represented as the mood of the Act. Even though one might think of a single activity as progressing from planned to executed, this progression is reflected by multiple Act-instances, each having one and only one mood that will not change along the Act-instance life cycle. This is because the attribution and content of speech acts along this progression of an activity may be different, and it is often critical that a permanent and faithful record be maintained of this progression. The specification of orders or promises or plans must not be overwritten by the specification of what was actually done, so as to allow comparing actions with their earlier specifications. Act-instances that describe this progression of the same real world activity are linked through the ActRelationships (of the relationship category "sequel").

Act as statements or speech-acts are the only representation of real world facts or processes in the HL7 RIM. The truth about the real world is constructed through a combination (and arbitration) of such attributed statements only, and there is no class in the RIM whose objects represent "objective state of affairs" or "real processes" independent from attributed statements. As such, there is no distinction between an activity and its documentation. Every Act includes both to varying degrees. For example, a factual statement made about recent (but past) activities, authored (and signed) by the performer of such activities, is commonly known as a procedure report or original documentation (e.g., surgical procedure report, clinic note etc.). Conversely, a status update on an activity that is presently in progress, authored by the performer (or a close observer) is considered to capture that activity (and is later superceded by a full procedure report). However, both status update and procedure report are acts of the same kind, only distinguished by mood and state (see statusCode) and completeness of the information.

Source Code System
2.16.840.1.113883.5.6 - ActClass - FHIR: http://terminology.hl7.org/CodeSystem/v3-ActClass
Level/ TypeCodeDisplay NameCode System
0‑S
ACT
act
ActClass
1‑A
_ActClassRecordOrganizer
record organizer
ActClass
2‑S
COMPOSITION
composition Attestable unit
ActClass
3‑S
DOC
document
ActClass
4‑S
DOCCLIN
clinical document
ActClass
5‑L
CDALVLONE
CDA Level One clinical document
ActClass
2‑S
CONTAINER
record container
ActClass
3‑L
CATEGORY
category
ActClass
3‑L
DOCBODY
document body
ActClass
3‑L
DOCSECT
document section Section
ActClass
3‑L
TOPIC
topic
ActClass
2‑S
EXTRACT
extract
ActClass
3‑L
EHR
electronic health record
ActClass
2‑L
FOLDER
folder
ActClass
2‑S
GROUPER
grouper
ActClass
3‑L
CLUSTER
Cluster
ActClass
1‑L
ACCM
accommodation
ActClass
1‑L
ACCT
account
ActClass
1‑L
ACSN
accession
ActClass
1‑L
ADJUD
financial adjudication financial adjudication results
ActClass
1‑S
CACT
control act
ActClass
2‑L
ACTN
action
ActClass
2‑L
INFO
information
ActClass
2‑L
STC
state transition control
ActClass
1‑S
CNTRCT
contract
ActClass
2‑S
FCNTRCT
financial contract
ActClass
3‑L
COV
coverage
ActClass
1‑S
CONC
concern
ActClass
2‑L
HCASE
public health case
ActClass
2‑L
OUTBR
outbreak
ActClass
1‑L
CONS
consent
ActClass
1‑L
CONTREG
container registration
ActClass
1‑L
CTTEVENT
clinical trial timepoint event
ActClass
1‑L
DISPACT
disciplinary action
ActClass
1‑S
EXPOS
exposure
ActClass
2‑L
AEXPOS
acquisition exposure
ActClass
2‑L
TEXPOS
transmission exposure
ActClass
1‑L
INC
incident
ActClass
1‑L
INFRM
inform
ActClass
1‑L
INVE
invoice element
ActClass
1‑L
LIST
working list
ActClass
1‑L
MPROT
monitoring program
ActClass
1‑S
OBS
observation
ActClass
2‑A
_ActClassROI
ActClassROI
ActClass
3‑L
ROIBND
bounded ROI
ActClass
3‑L
ROIOVL
overlay ROI
ActClass
2‑A
_SubjectPhysicalPosition
subject physical position
ActClass
3‑A
_SubjectBodyPosition
subject body position
ActClass
4‑L
LLD
left lateral decubitus
ActClass
4‑L
PRN
prone
ActClass
4‑L
RLD
right lateral decubitus
ActClass
4‑L
SFWL
Semi-Fowler's
ActClass
4‑L
SIT
sitting
ActClass
4‑L
STN
standing
ActClass
4‑S
SUP
supine
ActClass
5‑L
RTRD
reverse trendelenburg
ActClass
5‑L
TRD
trendelenburg
ActClass
2‑L
ALRT
detected issue
ActClass
2‑L
BATTERY
battery
ActClass
2‑L
CLNTRL
clinical trial
ActClass
2‑L
CNOD
Condition Node
ActClass
2‑S
COND
Condition
ActClass
3‑S
CASE
public health case
ActClass
4‑L
OUTB
outbreak
ActClass
2‑L
DGIMG
diagnostic image
ActClass
2‑S
GEN
genomic observation
ActClass
3‑L
DETPOL
determinant peptide
ActClass
3‑L
EXP
expression level
ActClass
3‑L
LOC
locus
ActClass
3‑L
PHN
phenotype
ActClass
3‑L
POL
polypeptide
ActClass
3‑L
SEQ
bio sequence
ActClass
3‑L
SEQVAR
bio sequence variation
ActClass
2‑L
INVSTG
investigation
ActClass
2‑S
OBSSER
observation series
ActClass
3‑L
OBSCOR
correlated observation sequences
ActClass
2‑S
POS
position
ActClass
3‑L
POSACC
position accuracy
ActClass
3‑L
POSCOORD
position coordinate
ActClass
2‑L
SPCOBS
specimen observation ActClassSpecObs
ActClass
2‑L
VERIF
Verification
ActClass
1‑S
PCPR
care provision
ActClass
2‑L
ENC
encounter
ActClass
1‑S
POLICY
policy
ActClass
2‑L
JURISPOL
jurisdictional policy
ActClass
2‑L
ORGPOL
organizational policy
ActClass
2‑L
SCOPOL
scope of practice policy
ActClass
2‑L
STDPOL
standard of practice policy
ActClass
1‑S
PROC
procedure
ActClass
2‑L
SBADM
substance administration
ActClass
2‑S
SBEXT
Substance Extraction
ActClass
3‑L
SPECCOLLECT
Specimen Collection
ActClass
1‑L
REG
registration
ActClass
1‑L
REV
review
ActClass
1‑L
SPCTRT
specimen treatment
ActClass
1‑S
SPLY
supply
ActClass
2‑L
DIET
diet
ActClass
1‑L
STORE
storage
ActClass
1‑L
SUBST
Substitution
ActClass
1‑L
TRFR
transfer
ActClass
1‑L
TRNS
transportation
ActClass
1‑L
XACT
financial transaction
ActClass

Legenda: Type L=leaf, S=specializable, A=abstract, D=deprecated. NullFlavor OTH (other) suggests text in originalText. HL7 V3: NullFlavors to appear in @nullFlavor attribute instead of @code.
downloadXML JSON CSV SQL SVS