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: SourceRoles

Summary

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

Roles for communication source in 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:

  • Include these codes as defined in http://dicom.nema.org/resources/ontology/DCM
    CodeDisplay
    110153Source Role ID
    110155Source Media
  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/contractsignertypecodes
    CodeDisplayDefinition
    PRIMAUTHPrimary 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.
    AMENDERAmenderA person who has corrected, edited, or amended pre-existing information.
    COAUTHCo-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.
    SOURCESourceAn 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.
  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-ParticipationType
    CodeDisplayDefinition
    AUTAuthor**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.
    CSTCustodianAn 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.).

 

Expansion

This value set contains 8 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.).

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