This page is part of the Situational Awareness for Novel Epidemic Response (v1.0.0: STU 1) 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
Summary
Defining URL: | http://hl7.org/fhir/uv/saner/ValueSet/SourceRoles |
Version: | 1.0.0 |
Name: | SourceRoles |
Status: | Active as of 2021-09-07T19:08:29+00:00 |
Definition: | Roles for communication source in AuditEvent |
Publisher: | HL7 International Public Health Workgroup |
Source Resource: | XML / JSON / Turtle |
References
This value set includes codes based on the following rules:
http://dicom.nema.org/resources/ontology/DCM
Code | Display | Definition |
110153 | Source Role ID | Audit participant role ID of the sender of data |
110155 | Source Media | Audit participant role ID of media providing data during an import |
http://terminology.hl7.org/CodeSystem/contractsignertypecodes
Code | Display | Definition |
PRIMAUTH | Primary Author | An entity that is the primary or sole author of information content. In the healthcare context, there can be only one primary author of health information content in a record entry or document. |
AMENDER | Amender | A person who has corrected, edited, or amended pre-existing information. |
COAUTH | Co-author | The entity that co-authored content. There can be multiple co-authors of content, which may take such forms as a contract, a healthcare record entry or document, a policy, or a consent directive. |
SOURCE | Source | An automated data source that generates a signature along with content. Examples: (1) the signature for an image that is generated by a device for inclusion in the patient record; (2) the signature for an ECG derived by an ECG system for inclusion in the patient record; (3) the data from a biomedical monitoring device or system that is for inclusion in the patient record. |
http://terminology.hl7.org/CodeSystem/v3-ParticipationType
Code | Display | Definition |
AUT | Author | **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. |
CST | Custodian | An entity (person, organization or device) that is in charge of maintaining the information of this act (e.g., who maintains the report or the master service catalog item, etc.). |
This value set contains 8 concepts
Expansion based on:
Code | System | Display | Definition |
110153 | http://dicom.nema.org/resources/ontology/DCM | Source Role ID | Audit participant role ID of the sender of data |
110155 | http://dicom.nema.org/resources/ontology/DCM | Source Media | Audit participant role ID of media providing data during an import |
PRIMAUTH | http://terminology.hl7.org/CodeSystem/contractsignertypecodes | Primary Author | An entity that is the primary or sole author of information content. In the healthcare context, there can be only one primary author of health information content in a record entry or document. |
AMENDER | http://terminology.hl7.org/CodeSystem/contractsignertypecodes | Amender | A person who has corrected, edited, or amended pre-existing information. |
COAUTH | http://terminology.hl7.org/CodeSystem/contractsignertypecodes | Co-author | The entity that co-authored content. There can be multiple co-authors of content, which may take such forms as a contract, a healthcare record entry or document, a policy, or a consent directive. |
SOURCE | http://terminology.hl7.org/CodeSystem/contractsignertypecodes | Source | An automated data source that generates a signature along with content. Examples: (1) the signature for an image that is generated by a device for inclusion in the patient record; (2) the signature for an ECG derived by an ECG system for inclusion in the patient record; (3) the data from a biomedical monitoring device or system that is for inclusion in the patient record. |
AUT | http://terminology.hl7.org/CodeSystem/v3-ParticipationType | Author | **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. |
CST | http://terminology.hl7.org/CodeSystem/v3-ParticipationType | Custodian | An entity (person, organization or device) that is in charge of maintaining the information of this act (e.g., who maintains the report or the master service catalog item, etc.). |
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 |
Source | 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 |