HL7 Terminology (THO)
6.1.0 - Publication
This page is part of the HL7 Terminology (v6.1.0: Release) based on FHIR (HL7® FHIR® Standard) v5.0.0. 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
Official URL: http://terminology.hl7.org/ValueSet/v3-ActClassComposition | Version: 3.0.0 | |||
Active as of 2014-03-26 | Responsible: Health Level Seven International | Computable Name: ActClassComposition | ||
Other Identifiers: OID:2.16.840.1.113883.1.11.19442 | ||||
Copyright/Legal: This material derives from the HL7 Terminology THO. THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html |
A context representing a grouped commitment of information to the EHR. It is considered the unit of modification of the record, the unit of transmission in record extracts, and the unit of attestation by authorizing clinicians.
A composition represents part of a patient record originating from a single interaction between an authenticator and the record.
Unless otherwise stated all statements within a composition have the same authenticator, apply to the same patient and were recorded in a single session of use of a single application.
A composition contains organizers and entries.
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
Generated Narrative: ValueSet v3-ActClassComposition
Language: en
http://terminology.hl7.org/CodeSystem/v3-ActClass
where concept is-a COMPOSITION
Generated Narrative: ValueSet
Language: en
Expansion based on codesystem ActClass v4.0.0 (CodeSystem)
This value set contains 4 concepts
Level | Code | System | Display | Definition |
1 | COMPOSITION | http://terminology.hl7.org/CodeSystem/v3-ActClass | composition | A context representing a grouped commitment of information to the EHR. It is considered the unit of modification of the record, the unit of transmission in record extracts, and the unit of attestation by authorizing clinicians. A composition represents part of a patient record originating from a single interaction between an authenticator and the record. Unless otherwise stated all statements within a composition have the same authenticator, apply to the same patient and were recorded in a single session of use of a single application. A composition contains organizers and entries. |
2 | DOC | http://terminology.hl7.org/CodeSystem/v3-ActClass | document | The notion of a document comes particularly from the paper world, where it corresponds to the contents recorded on discrete pieces of paper. In the electronic world, a document is a kind of composition that bears resemblance to their paper world counter-parts. Documents typically are meant to be human-readable. HL7's notion of document differs from that described in the W3C XML Recommendation, in which a document refers specifically to the contents that fall between the root element's start-tag and end-tag. Not all XML documents are HL7 documents. |
3 | DOCCLIN | http://terminology.hl7.org/CodeSystem/v3-ActClass | clinical document | A clinical document is a documentation of clinical observations and services, with the following characteristics:
|
4 | CDALVLONE | http://terminology.hl7.org/CodeSystem/v3-ActClass | CDA Level One clinical document | A clinical document that conforms to Level One of the HL7 Clinical Document Architecture (CDA) |
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
Date | Action | Custodian | Author | Comment |
2023-11-14 | revise | TSMG | Marc Duteau | Add standard copyright and contact to internal content; up-476 |
2022-10-18 | revise | TSMG | Marc Duteau | Fixing missing metadata; up-349 |
2020-05-06 | revise | Vocabulary WG | Ted Klein | Migrated to the UTG maintenance environment and publishing tooling. |
2014-03-26 | revise | 2014T1_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 |