HL7 Terminology (THO)
5.3.0 - Publication International flag

This page is part of the HL7 Terminology (v5.3.0: Release) based on FHIR R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

ValueSet: ActClassContainer

Official URL: http://terminology.hl7.org/ValueSet/v3-ActClassContainer Version: 2.0.0
Active as of 2014-03-26 Computable Name: ActClassContainer
Other Identifiers: id: urn:oid:2.16.840.1.113883.1.11.19445

Used to group a set of acts sharing a common context. Container structures can nest within other context structures - such as where a document is contained within a folder, or a folder is contained within an EHR extract.

Open issue: There is a clear conflict between this act and the use of the more general “component” ActRelationship. The question that must be resolved is what should be the class code of the parent (or containing) Act.

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)

 

Expansion

This value set contains 5 concepts

Expansion based on codesystem ActClass v3.1.1 (CodeSystem)

LevelCodeSystemDisplayDefinition
1  CONTAINERhttp://terminology.hl7.org/CodeSystem/v3-ActClassrecord container

Description: Container of clinical statements. Navigational. No semantic content. Knowledge of the section code is not required to interpret contained observations. Represents a heading in a heading structure, or "container tree".

The record entries relating to a single clinical session are usually grouped under headings that represent phases of the encounter, or assist with layout and navigation. Clinical headings usually reflect the clinical workflow during a care session, and might also reflect the main author's reasoning processes. Much research has demonstrated that headings are used differently by different professional groups and specialties, and that headings are not used consistently enough to support safe automatic processing of the E H R.

2    CATEGORYhttp://terminology.hl7.org/CodeSystem/v3-ActClasscategory

A group of entries within a composition or topic that have a common characteristic - for example, Examination, Diagnosis, Management OR Subjective, Objective, Analysis, Plan.

The distinction from Topic relates to value sets. For Category there is a bounded list of things like "Examination", "Diagnosis" or SOAP categories. For Topic the list is wide open to any clinical condition or reason for a part of an encounter.

A CATEGORY MAY CONTAIN ENTRIES.

2    DOCBODYhttp://terminology.hl7.org/CodeSystem/v3-ActClassdocument body

A context that distinguishes the body of a document from the document header. This is seen, for instance, in HTML documents, which have discrete <head> and <body> elements.

2    DOCSECThttp://terminology.hl7.org/CodeSystem/v3-ActClassdocument section

A context that subdivides the body of a document. Document sections are typically used for human navigation, to give a reader a clue as to the expected content. Document sections are used to organize and provide consistency to the contents of a document body. Document sections can contain document sections and can contain entries.

2    TOPIChttp://terminology.hl7.org/CodeSystem/v3-ActClasstopic

A group of entries within a composition that are related to a common clinical theme - such as a specific disorder or problem, prevention, screening and provision of contraceptive services.

A topic may contain categories and entries.

Explanation of the columns that may appear on this page:

Level A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
System The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code The code (used as the code in the resource instance)
Display The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition An explanation of the meaning of the concept
Comments Additional notes about how to use the code

History

DateActionCustodianAuthorComment
2022-10-18reviseTSMGMarc DuteauFixing missing metadata; up-349
2020-05-06reviseVocabulary WGTed KleinMigrated to the UTG maintenance environment and publishing tooling.
2014-03-26revise2014T1_2014-03-26_001283 (RIM release ID)Vocabulary (Woody Beeler) (no record of original request)Lock all vaue sets untouched since 2014-03-26 to trackingId 2014T1_2014_03_26