FHIR Cross-Version Extensions package for FHIR R4 from FHIR R5 - Version 0.0.1-snapshot-2. See the Directory of published versions
Official URL: http://hl7.org/fhir/5.0/ValueSet/R5-v3-ParticipationAuthorOriginator-for-R4 | Version: 0.0.1-snapshot-2 | |||
Standards status: Informative | Maturity Level: 0 | Computable Name: R5_v3_ParticipationAuthorOriginator_for_R4 |
This cross-version ValueSet represents concepts from http://terminology.hl7.org/ValueSet/v3-ParticipationAuthorOriginator | 2.0.0 for use in FHIR R4. Concepts not present here have direct equivalent mappings crossing all versions from R5 to R4. |
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
http://terminology.hl7.org/CodeSystem/v3-ParticipationType
version 4.0.0
Code | Display | Definition |
AUT | author (originator) | **Definition:** A party that originates the Act and therefore has responsibility for the information given in the Act and ownership of this Act. **Example:** the report writer, the person writing the act definition, the guideline author, the placer of an order, the EKG cart (device) creating a report etc. Every Act should have an author. Authorship is regardless of mood always actual authorship. Examples of such policies might include: * The author and anyone they explicitly delegate may update the report; * All administrators within the same clinic may cancel and reschedule appointments created by other administrators within that clinic; A party that is neither an author nor a party who is extended authorship maintenance rights by policy, may only amend, reverse, override, replace, or follow up in other ways on this Act, whereby the Act remains intact and is linked to another Act authored by that other party. |
This value set expansion contains 1 concepts.
Code | System | Display | Definition |
AUT | http://terminology.hl7.org/CodeSystem/v3-ParticipationType | author (originator) | Definition: A party that originates the Act and therefore has responsibility for the information given in the Act and ownership of this Act. Example: the report writer, the person writing the act definition, the guideline author, the placer of an order, the EKG cart (device) creating a report etc. Every Act should have an author. Authorship is regardless of mood always actual authorship. Examples of such policies might include:
A party that is neither an author nor a party who is extended authorship maintenance rights by policy, may only amend, reverse, override, replace, or follow up in other ways on this Act, whereby the Act remains intact and is linked to another Act authored by that other party. |
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 |