Situational Awareness for Novel Epidemic Response, published by HL7 International / Public Health. This guide is not an authorized publication; it is the continuous build for version 1.0.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhir-saner/ and changes regularly. See the Directory of published versions
Official URL: http://hl7.org/fhir/uv/saner/ValueSet/SourceOrDestinationRoles | Version: 1.0.1 | |||
Active as of 2024-05-18 | Computable Name: SourceOrDestinationRoles | |||
Other Identifiers: OID:2.16.840.1.113883.4.642.40.42.48.41 |
Roles for human requestors in an AuditEvent
References
This value set includes codes based on the following rules:
http://terminology.hl7.org/CodeSystem/extra-security-role-type
Code | Display | Definition |
humanuser | Human User | The human user that has participated. |
Expansion based on:
This value set has 13 codes in it. In order to keep the publication size manageable, only a selection (21 codes) of the whole set of codes is shown.
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:
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.). |
110152 | http://dicom.nema.org/resources/ontology/DCM | Destination Role ID | Audit participant role ID of the receiver of data |
110154 | http://dicom.nema.org/resources/ontology/DCM | Destination Media | Audit participant role ID of media receiving data during an export |
IRCP | http://terminology.hl7.org/CodeSystem/v3-ParticipationType | Information Recipient | A 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. |
NOT | http://terminology.hl7.org/CodeSystem/v3-ParticipationType | Ugent Notification Contact | An 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). |
PRCP | http://terminology.hl7.org/CodeSystem/v3-ParticipationType | Primary Information Recipient | Information 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. |
REFB | http://terminology.hl7.org/CodeSystem/v3-ParticipationType | Referred By | A 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). |
REFT | http://terminology.hl7.org/CodeSystem/v3-ParticipationType | Referred to | The person who receives the patient |
TRC | http://terminology.hl7.org/CodeSystem/v3-ParticipationType | Tracker | A secondary information recipient, who receives copies (e.g., a primary care provider receiving copies of results as ordered by specialist). |
AUCG | http://terminology.hl7.org/CodeSystem/v3-ParticipationFunction | Caregiver Information Receiver | **Description:**Caregiver authorized to receive patient health information. |
AULR | http://terminology.hl7.org/CodeSystem/v3-ParticipationFunction | Legitimate Relationship Information Receiver | **Description:**Provider with legitimate relationship authorized to receive patient health information. |
AUTM | http://terminology.hl7.org/CodeSystem/v3-ParticipationFunction | Care Team Information Receiver | **Description:**Member of care team authorized to receive patient health information. |
AUWA | http://terminology.hl7.org/CodeSystem/v3-ParticipationFunction | Work Area Information Receiver | **Description:**Entities within specified work area authorized to receive patient health information. |
humanuser | http://terminology.hl7.org/CodeSystem/extra-security-role-type | Human User | The 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 |
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 |