Situational Awareness for Novel Epidemic Response
1.0.0 - STU Release

Situational Awareness for Novel Epidemic Response, published by HL7 International Public Health Workgroup. This is not an authorized publication; it is the continuous build for version 1.0.0). This version is based on the current content of https://github.com/HL7/fhir-saner/ and changes regularly. See the Directory of published versions

ValueSet: SourceOrDestinationRoles

Summary

Defining URL:http://hl7.org/fhir/uv/saner/ValueSet/SourceOrDestinationRoles
Version:1.0.0
Name:SourceOrDestinationRoles
Status:Active as of 2021-09-24T13:39:04+00:00
Definition:

Roles for human requestors in an AuditEvent

Publisher:HL7 International Public Health Workgroup
Source Resource:XML / JSON / Turtle

References

Logical Definition (CLD)

This value set includes codes based on the following rules:

 

Expansion

This value set contains 21 concepts

CodeSystemDisplayDefinition
110153http://dicom.nema.org/resources/ontology/DCMSource Role ID
110155http://dicom.nema.org/resources/ontology/DCMSource Media
PRIMAUTHhttp://terminology.hl7.org/CodeSystem/contractsignertypecodesPrimary AuthorAn 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.
AMENDERhttp://terminology.hl7.org/CodeSystem/contractsignertypecodesAmenderA person who has corrected, edited, or amended pre-existing information.
COAUTHhttp://terminology.hl7.org/CodeSystem/contractsignertypecodesCo-authorThe 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.
SOURCEhttp://terminology.hl7.org/CodeSystem/contractsignertypecodesSourceAn 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.
AUThttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypeAuthor**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.
CSThttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypeCustodianAn 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.).
110152http://dicom.nema.org/resources/ontology/DCMDestination Role ID
110154http://dicom.nema.org/resources/ontology/DCMDestination Media
IRCPhttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypeInformation RecipientA party, who may or should receive or who has recieved the Act or subsequent or derivative information of that Act. Information recipient is inert, i.e., independent of mood." Rationale: this is a generalization of a too diverse family that the definition can't be any more specific, and the concept is abstract so one of the specializations should be used.
NOThttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypeUgent Notification ContactAn information recipient to notify for urgent matters about this Act. (e.g., in a laboratory order, critical results are being called by phone right away, this is the contact to call; or for an inpatient encounter, a next of kin to notify when the patient becomes critically ill).
PRCPhttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypePrimary Information RecipientInformation recipient to whom an act statement is primarily directed. E.g., a primary care provider receiving a discharge letter from a hospitalist, a health department receiving information on a suspected case of infectious disease. Multiple of these participations may exist on the same act without requiring that recipients be ranked as primary vs. secondary.
REFBhttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypeReferred ByA participant (e.g. provider) who has referred the subject of an act (e.g. patient). Typically, a referred by participant will provide a report (e.g. referral).
REFThttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypeReferred toThe person who receives the patient
TRChttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypeTrackerA secondary information recipient, who receives copies (e.g., a primary care provider receiving copies of results as ordered by specialist).
AUCGhttp://terminology.hl7.org/CodeSystem/v3-ParticipationFunctionCaregiver Information Receiver**Description:**Caregiver authorized to receive patient health information.
AULRhttp://terminology.hl7.org/CodeSystem/v3-ParticipationFunctionLegitimate Relationship Information Receiver**Description:**Provider with legitimate relationship authorized to receive patient health information.
AUTMhttp://terminology.hl7.org/CodeSystem/v3-ParticipationFunctionCare Team Information Receiver**Description:**Member of care team authorized to receive patient health information.
AUWAhttp://terminology.hl7.org/CodeSystem/v3-ParticipationFunctionWork Area Information Receiver**Description:**Entities within specified work area authorized to receive patient health information.
humanuserhttp://terminology.hl7.org/CodeSystem/extra-security-role-typeHuman UserThe human user that has participated.

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