FHIR Cross-Version Extensions package for FHIR R5 from FHIR R3 - Version 0.0.1-snapshot-2. See the Directory of published versions
| Official URL: http://hl7.org/fhir/3.0/ValueSet/R3-v3-ActClassDocument-for-R5 | Version: 0.0.1-snapshot-2 | |||
| Standards status: Informative | Maturity Level: 0 | Computable Name: R3_v3_ActClassDocument_for_R5 | ||
| This cross-version ValueSet represents concepts from http://hl7.org/fhir/ValueSet/v3-ActClassDocument | 2014-03-26 for use in FHIR R5. Concepts not present here have direct equivalent mappings crossing all versions from R3 to R5. |
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
http://hl7.org/fhir/v3/ActClass version 2016-11-11| Code | Display | Definition |
| CDALVLONE | CDA Level One clinical document | A clinical document that conforms to Level One of the HL7 Clinical Document Architecture (CDA) |
| DOCCLIN | clinical document | A clinical document is a documentation of clinical observations and services, with the following characteristics: Persistence - A clinical document continues to exist in an unaltered state, for a time period defined by local and regulatory requirements; Stewardship - A clinical document is maintained by a person or organization entrusted with its care; Potential for authentication - A clinical document is an assemblage of information that is intended to be legally authenticated; Wholeness - Authentication of a clinical document applies to the whole and does not apply to portions of the document without the full context of the document; Human readability - A clinical document is human readable. |
| DOC | 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. |
This value set expansion contains 3 concepts.
| Code | System | Display | Definition |
| CDALVLONE | http://hl7.org/fhir/v3/ActClass | CDA Level One clinical document | A clinical document that conforms to Level One of the HL7 Clinical Document Architecture (CDA) |
| DOCCLIN | http://hl7.org/fhir/v3/ActClass | clinical document | A clinical document is a documentation of clinical observations and services, with the following characteristics:
|
| DOC | http://hl7.org/fhir/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.
|
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 |