STU3 Candidate

This page is part of the FHIR Specification (v1.8.0: STU 3 Draft). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

4.3.1.903 Value Set http://hl7.org/fhir/ValueSet/consent-actor-role

This is a value set defined by the FHIR project.

Summary

Defining URL:http://hl7.org/fhir/ValueSet/consent-actor-role
Name:Consent Actor Roles
Definition:This value set includes sample Consent Type codes.
Committee:Community Based Collaborative Care Work Group
OID:2.16.840.1.113883.4.642.2.903 (for OID based terminology systems)
Copyright:This is an example set.
Source ResourceXML / JSON

This value set is used in the following places:


This value set includes codes from the following code systems:

  • Include these codes as defined in http://hl7.org/fhir/v3/ParticipationType
    CodeDisplay
    REFreferrerA person having referred the subject of the service to the performer (referring physician). Typically, a referring physician will receive a report.
    AUTauthor (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.
    INFinformantA source of reported information (e.g., a next of kin who answers questions about the patient's history). For history questions, the patient is logically an informant, yet the informant of history questions is implicitly the subject.
    SBJsubjectThe principle target on which the action happens.
    Examples: The patient in physical examination, a specimen in a lab observation. May also be a patient's family member (teaching) or a device or room (cleaning, disinfecting, housekeeping).
    UsageNotes: Not all direct targets are subjects. Consumables and devices used as tools for an act are not subjects. However, a device may be a subject of a maintenance action.
    PRCPprimary 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.
    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.).

 

See the full registry of value sets defined as part of FHIR.


Explanation of the columns that may appear on this page:

LevelA 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
SourceThe source of the definition of the code (when the value set draws in codes defined elsewhere)
CodeThe code (used as the code in the resource instance)
DisplayThe 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
DefinitionAn explanation of the meaning of the concept
CommentsAdditional notes about how to use the code