Current Build

4.3.1.978 Value Set http://hl7.org/fhir/ValueSet/security-role-type

Vocabulary Work Group Maturity Level: 1Trial Use Use Context: Not Intended for Production use

This is a value set defined by the FHIR project.

Summary

Defining URL:http://hl7.org/fhir/ValueSet/security-role-type
Name:SecurityRoleType
Definition:

This example FHIR value set is comprised of example Actor Type codes, which can be used to value FHIR agents, actors, and other role elements such as those specified in financial transactions. The FHIR Actor value set is based on DICOM Audit Message, C402; ASTM Standard, E1762-95 [2013]; selected codes and derived actor roles from HL7 RoleClass OID 2.16.840.1.113883.5.110; HL7 Role Code 2.16.840.1.113883.5.111, including AgentRoleType; HL7 ParticipationType OID: 2.16.840.1.113883.5.90; and HL7 ParticipationFunction codes OID: 2.16.840.1.113883.5.88. This value set includes, by reference, role codes from external code systems: NUCC Health Care Provider Taxonomy OID: 2.16.840.1.113883.6.101; North American Industry Classification System [NAICS]OID: 2.16.840.1.113883.6.85; IndustryClassificationSystem 2.16.840.1.113883.1.11.16039; and US Census Occupation Code OID: 2.16.840.1.113883.6.243 for relevant recipient or custodian codes not included in this value set. If no source is indicated in the definition comments, then these are example FHIR codes. It can be extended with appropriate roles described by SNOMED as well as those described in the HL7 Role Based Access Control Catalog and the HL7 Healthcare (Security and Privacy) Access Control Catalog. In Role-Based Access Control (RBAC), permissions are operations on an object that a user wishes to access. Permissions are grouped into roles. A role characterizes the functions a user is allowed to perform. Roles are assigned to users. If the user's role has the appropriate permissions to access an object, then that user is granted access to the object. FHIR readily enables RBAC, as FHIR Resources are object types and the CRUDE events (the FHIR equivalent to permissions in the RBAC scheme) are operations on those objects. In Attribute-Based Access Control (ABAC), a user requests to perform operations on objects. That user's access request is granted or denied based on a set of access control policies that are specified in terms of attributes and conditions. FHIR readily enables ABAC, as instances of a Resource in FHIR (again, Resources are object types) can have attributes associated with them. These attributes include security tags, environment conditions, and a host of user and object characteristics, which are the same attributes as those used in ABAC. Attributes help define the access control policies that determine the operations a user may perform on a Resource (in FHIR) or object (in ABAC). For example, a tag (or attribute) may specify that the identified Resource (object) is not to be further disclosed without explicit consent from the patient.

Committee:??
OID:2.16.840.1.113883.4.642.3.978 (for OID based terminology systems)
Copyright:This is an example FHIR value set based on ASTM Standard, E1762-95 (2013) HL7 RoleClass OID 2.16.840.1.113883.5.110, HL7 Role Code 2.16.840.1.113883.5.111, HL7 ParticipationType OID: 2.16.840.1.113883.5.90, HL7 ParticipationFunction codes at OID: 2.16.840.1.113883.5.88, and HL7 Security and Privacy Domain Analysis Model roles classes. These codes are excerpted from Digital Imaging and Communications in Medicine (DICOM) Standard, Part 16: Content Mapping Resource, Copyright © 2011 by the National Electrical Manufacturers Association.
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://www.hl7.org/fhir/contractsignertypecodes
    CodeDisplay
    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 such as a contract, a healthcare record entry or document, a policy, or a consent directive.
    CONTContactA person or an organization that provides or receives information regarding another entity. Examples; patient NOK and emergency contacts; guarantor contact; employer contact.
    EVTWITEvent WitnessA person who attests to observing an occurrence. For example, the witness has observed a procedure and is attesting to this fact.
    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.
    REVIEWERReviewerA person, device, or algorithm that has used approved criteria for filtered data for inclusion into the patient record. Examples: (1) a medical records clerk who scans a document for inclusion in the medical record, enters header information, or catalogues and classifies the data, or a combination thereof; (2) a gateway that receives data from another computer system and interprets that data or changes its format, or both, before entering it into the patient record.
    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.
    TRANSTranscriberAn entity entering the data into the originating system. This includes the transcriptionist for dictated text transcribed into electronic form.
    VALIDValidatorA person who validates a health information document for inclusion in the patient record. For example, a medical student or resident is credentialed to perform history or physical examinations and to write progress notes. The attending physician signs the history and physical examination to validate the entry for inclusion in the patient's medical record.
    VERFVerifierA person who asserts the correctness and appropriateness of an act or the recording of the act, and is accountable for the assertion that the act or the recording of the act complies with jurisdictional or organizational policy. For example, a physician is required to countersign a verbal order that has previously been recorded in the medical record by a registered nurse who has carried out the verbal order.
  • Include these codes as defined in http://hl7.org/fhir/v3/RoleClass
    CodeDisplay
    AFFLaffiliatePlayer of the Affiliate role has a business/professional relationship with scoper. Player and scoper may be persons or organization. The Affiliate relationship does not imply membership in a group, nor does it exist for resource scheduling purposes.
    Example: A healthcare provider is affiliated with another provider as a business associate.
    AGNTagentAn entity (player) that acts or is authorized to act on behalf of another entity (scoper).
    ASSIGNEDassigned entityAn agent role in which the agent is an Entity acting in the employ of an organization. The focus is on functional role on behalf of the organization, unlike the Employee role where the focus is on the 'Human Resources' relationship between the employee and the organization.
    CLAIMclaimantDescription: A role played by a party making a claim for coverage under a policy or program. A claimant must be either a person or organization, or a group of persons or organizations. A claimant is not a named insured or a program eligible.
    Discussion: With respect to liability insurance such as property and casualty insurance, a claimant must file a claim requesting indemnification for a loss that the claimant considers covered under the policy of a named insured. The claims adjuster for the policy underwriter will review the claim to determine whether the loss meets the benefit coverage criteria under a policy, and base any indemnification or coverage payment on that review. If a third party is liable in whole or part for the loss, the underwriter may pursue third party liability recovery. A claimant may be involved in civil or criminal legal proceedings involving claims against a defendant party that is indemnified by an insurance policy or to protest the finding of a claims adjustor. With respect to life insurance, a beneficiary designated by a named insured becomes a claimant of the proceeds of coverage, as in the case of a life insurance policy. However, a claimant for coverage under life insurance is not necessarily a designated beneficiary.
    Note: A claimant is not a named insured. However, a named insured may make a claim under a policy, e.g., an insured driver may make a claim for an injury under his or her comprehensive automobile insurance policy. Similarly, a program eligible may make a claim under program, e.g., an unemployed worker may claim benefits under an unemployment insurance program, but parties playing these covered party role classes are not, for purposes of this vocabulary and in an effort to clearly distinguish role classes, considered claimants.
    In the case of a named insured making a claim, a role type code INSCLM (insured claimant) subtypes the class to indicate that either a named insured or an individual insured has filed a claim for a loss. In the case of a program eligible, a role type code INJWKR (injured worker) subtypes the class to indicate that the covered party in a workers compensation program is an injured worker, and as such, has filed a "claim" under the program for benefits. Likewise, a covered role type code UNEMP (unemployed worker) subtypes the program eligible class to indicate that the covered party in an unemployment insurance program has filed a claim for unemployment benefits.
    Example: A claimant under automobile policy that is not the named insured.
    COVPTYcovered partyA role class played by a person who receives benefit coverage under the terms of a particular insurance policy. The underwriter of that policy is the scoping entity. The covered party receives coverage because of some contractual or other relationship with the holder of that policy.
    Discussion:This reason for coverage is captured in 'Role.code' and a relationship link with type code of indirect authority should be included using the policy holder role as the source, and the covered party role as the target.
    Note that a particular policy may cover several individuals one of whom may be, but need not be, the policy holder. Thus the notion of covered party is a role that is distinct from that of the policy holder.
    DEPENdependentDescription: A role played by a person covered under a policy or program based on an association with a subscriber, which is recognized by the policy holder.
    Note: The party playing the role of a dependent is not a claimant in the sense conveyed by the RoleClassCoveredParty CLAIM (claimant). However, a dependent may make a claim under a policy, e.g., a dependent under a health insurance policy may become the claimant for coverage under that policy for wellness examines or if injured and there is no liable third party. In the case of a dependent making a claim, a role type code INSCLM (insured claimant) subtypes the class to indicate that the dependent has filed a claim for services covered under the health insurance policy.
    Example: The dependent has an association with the subscriber such as a financial dependency or personal relationship such as that of a spouse, or a natural or adopted child. The policy holder may be required by law to recognize certain associations or may have discretion about the associations. For example, a policy holder may dictate the criteria for the dependent status of adult children who are students, such as requiring full time enrollment, or may recognize domestic partners as dependents. Under certain circumstances, the dependent may be under the indirect authority of a responsible party acting as a surrogate for the subscriber, for example, if the subscriber is differently abled or deceased, a guardian ad Lidem or estate executor may be appointed to assume the subscriberaTMs legal standing in the relationship with the dependent.
    ECONemergency contactAn entity to be contacted in the event of an emergency.
    EMPemployeeA relationship between a person or organization and a person or organization formed for the purpose of exchanging work for compensation. The purpose of the role is to identify the type of relationship the employee has to the employer, rather than the nature of the work actually performed. (Contrast with AssignedEntity.)
    GUARDguardianGuardian of a ward
    INVSBJInvestigation SubjectAn entity that is the subject of an investigation. This role is scoped by the party responsible for the investigation.
    NAMEDnamed insuredDescription: A role played by a party to an insurance policy to which the insurer agrees to indemnify for losses, provides benefits for, or renders services. A named insured may be either a person, non-person living subject, or an organization, or a group of persons, non-person living subjects, or organizations.
    Discussion: The coded concept NAMED should not be used where a more specific child concept in this Specializable value set applies. In some cases, the named insured may not be the policy holder, e.g., where a policy holder purchases life insurance policy in which another party is the named insured and the policy holder is the beneficiary of the policy.
    Note: The party playing the role of a named insured is not a claimant in the sense conveyed by the RoleClassCoveredParty CLAIM (claimant). However, a named insured may make a claim under a policy, e.g., e.g., a party that is the named insured and policy holder under a comprehensive automobile insurance policy may become the claimant for coverage under that policy e.g., if injured in an automobile accident and there is no liable third party. In the case of a named insured making a claim, a role type code INSCLM (insured claimant) subtypes the class to indicate that a named insured has filed a claim for a loss.
    Example: The named insured under a comprehensive automobile, disability, or property and casualty policy that is the named insured and may or may not be the policy holder.
    NOKnext of kinAn individual designated for notification as the next of kin for a given entity.
    PATpatientA Role of a LivingSubject (player) as an actual or potential recipient of health care services from a healthcare provider organization (scoper).
    Usage Note: Communication about relationships between patients and specific healthcare practitioners (people) is not done via scoper. Instead this is generally done using the CareProvision act. This allows linkage between patient and a particular healthcare practitioner role and also allows description of the type of care involved in the relationship.
    PROVhealthcare providerAn Entity (player) that is authorized to provide health care services by some authorizing agency (scoper).
    NOTnotary publicnotary public
  • Include these codes as defined in http://hl7.org/fhir/v3/RoleCode
    CodeDisplay
    CLASSIFIERclassifierAn individual authorized to assign an original classification to information, including compilations of unclassified information, based on a determination that the information requires protection against unauthorized disclosure. The individual marks the information with immutable, computable, and human readable security labels in accordance with applicable security labeling policies. The labeling policies provide instructions on whether and if so how the security labels may be later reclassified [i.e., upgraded, downgraded, used in derivative classification, or declassified] in a manner that preserves the overridden original classification binding and provenance.
    CONSENTERconsenterAn entity or an entity's delegatee who is the grantee in an agreement such as a consent for services, advanced directive, or a privacy consent directive in accordance with jurisdictional, organizational, or patient policy.
    CONSWITconsent witnessAn entity which has witnessed and attests to observing another entity being counseled about an agreement such as a consent for services, advanced directive, or a privacy consent directive.
    COPARTco-participantAn entity which participates in the generation of and attest to veracity of content, but is not an author or coauthor. For example a surgeon who is required by institutional, regulatory, or legal rules to sign an operative report, but who was not involved in the authorship of that report.
    DECLASSIFIERdeclassifierAn individual which is authorized to declassify information based on a determination that the information no longer requires protection against unauthorized disclosure. The individual marks the information being declassified using computable and human readable security labels indicating that this is copy of previously classified information is unclassified in accordance with applicable security labeling policies. The labeling policies provide instructions on whether and if so how the security labels may be later reclassified [i.e., upgraded or used in derivative classification] in a manner that preserves the overridden original classification binding and provenance.
    DELEGATEEdelegateeA party to whom some right or authority is granted by a delegator.
    DELEGATORdelegatorA party that grants all or some portion its right or authority to another party.
    DOWNGRDERdowngraderAn individual authorized to lower the classification level of labeled content and provide rationale for doing so as directed by a classification guide.
    DPOWATTdurable power of attorneyA relationship between two people in which one person authorizes another, usually a family member or relative, to act for him or her in a manner which is a legally binding upon the person giving such authority as if he or she personally were to do the acts that is often limited in the kinds of powers that can be assigned. Unlike ordinary powers of attorney, durable powers can survive for long periods of time, and again, unlike standard powers of attorney, durable powers can continue after incompetency.
    EXCESTexecutor of estateThe role played by a person acting as the estate executor for a deceased subscriber or policyholder who was the responsible party
    GRANTEEgranteeAn entity which accepts certain rights or authority from a grantor.
    GRANTORgrantorAn entity which agrees to confer certain rights or authority to a grantee.
    GTGuarantorAn individual or organization that makes or gives a promise, assurance, pledge to pay or has paid the healthcare service provider.
    GUADLTMguardian ad lidemThe role played by a person appointed by the court to look out for the best interests of a minor child during the course of legal proceedings.
    HPOWATThealthcare power of attorneyA relationship between two people in which one person authorizes another to act for him or her in a manner which is a legally binding upon the person giving such authority as if he or she personally were to do the acts that continues (by its terms) to be effective even though the grantor has become mentally incompetent after signing the document.
    INTPRTERinterpreterAn entity which converts spoken or written language into the language of key participants in an event such as when a provider is obtaining a patient's consent to treatment or permission to disclose information.
    POWATTpower of attorneyA relationship between two people in which one person authorizes another to act for him in a manner which is a legally binding upon the person giving such authority as if he or she personally were to do the acts.
    RESPRSNresponsible partyThe role played by a party who has legal responsibility for another party.
    SPOWATTspecial power of attorneyA relationship between two people in which one person authorizes another to act for him or her in a manner which is a legally binding upon the person giving such authority as if he or she personally were to do the acts that is often limited in the kinds of powers that can be assigned.
  • Include codes from http://hl7.org/fhir/v3/RoleCode where concept is-a _CitizenRoleType
  • Include these codes as defined in http://hl7.org/fhir/v3/ParticipationFunction
    CodeDisplay
    AUCGcaregiver information receiverDescription:Caregiver authorized to receive patient health information.
    AULRlegitimate relationship information receiverDescription:Provider with legitimate relationship authorized to receive patient health information.
    AUTMcare team information receiverDescription:Member of care team authorized to receive patient health information.
    AUWAwork area information receiverDescription:Entities within specified work area authorized to receive patient health information.
    PROMSKauthorized provider masking authorDefinition:Provider authorized to mask information to protect the patient, a third party, or to ensure that the provider has consulted with the patient prior to release of this information.
  • Include these codes as defined in http://hl7.org/fhir/v3/ParticipationType
    CodeDisplay
    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.
    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.).
    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.
    IRCPinformation 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.
    LAlegal authenticatorA verifier who legally authenticates the accuracy of an act. An example would be a staff physician who sees a patient and dictates a note, then later signs it. Their signature constitutes a legal authentication.
    IRCPinformation 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.
    TRCtrackerA secondary information recipient, who receives copies (e.g., a primary care provider receiving copies of results as ordered by specialist).
    WITwitnessOnly with service events. A person witnessing the action happening without doing anything. A witness is not necessarily aware, much less approves of anything stated in the service event. Example for a witness is students watching an operation or an advanced directive witness.
  • Include all codes defined in http://hl7.org/fhir/extra-security-role-type
  • Include these codes as defined in http://dicom.nema.org/resources/ontology/DCM
    CodeDisplay
    110150ApplicationAudit participant role ID of software application
    110151Application LauncherAudit participant role ID of software application launcher, i.e., the entity that started or stopped an application
    110152Destination Role IDAudit participant role ID of the receiver of data
    110153Source Role IDAudit participant role ID of the sender of data
    110154Destination MediaAudit participant role ID of media receiving data during an export
    110155Source MediaAudit participant role ID of media providing data during an import

 

This expansion generated 20 Jun 2018


This value set contains 76 concepts

Expansion based on http://www.hl7.org/fhir/contractsignertypecodes version 3.4.0, http://hl7.org/fhir/v3/RoleClass version 2018-04-01, http://hl7.org/fhir/v3/ParticipationType version 2018-04-01, http://hl7.org/fhir/extra-security-role-type version 3.4.0, http://hl7.org/fhir/v3/RoleCode version 2018-04-01, http://hl7.org/fhir/v3/ParticipationFunction version 2018-04-01, DICOM version 01

CodeSystemDisplayDefinition
AMENDERhttp://www.hl7.org/fhir/contractsignertypecodesAmenderA person who has corrected, edited, or amended pre-existing information.
COAUTHhttp://www.hl7.org/fhir/contractsignertypecodesCo-AuthorThe entity that co-authored content. There can be multiple co-authors of content,which may take such forms as a such as a contract, a healthcare record entry or document, a policy, or a consent directive.
CONThttp://www.hl7.org/fhir/contractsignertypecodesContactA person or an organization that provides or receives information regarding another entity. Examples; patient NOK and emergency contacts; guarantor contact; employer contact.
EVTWIThttp://www.hl7.org/fhir/contractsignertypecodesEvent WitnessA person who attests to observing an occurrence. For example, the witness has observed a procedure and is attesting to this fact.
PRIMAUTHhttp://www.hl7.org/fhir/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.
REVIEWERhttp://www.hl7.org/fhir/contractsignertypecodesReviewerA person, device, or algorithm that has used approved criteria for filtered data for inclusion into the patient record. Examples: (1) a medical records clerk who scans a document for inclusion in the medical record, enters header information, or catalogues and classifies the data, or a combination thereof; (2) a gateway that receives data from another computer system and interprets that data or changes its format, or both, before entering it into the patient record.
SOURCEhttp://www.hl7.org/fhir/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.
TRANShttp://www.hl7.org/fhir/contractsignertypecodesTranscriberAn entity entering the data into the originating system. This includes the transcriptionist for dictated text transcribed into electronic form.
VALIDhttp://www.hl7.org/fhir/contractsignertypecodesValidatorA person who validates a health information document for inclusion in the patient record. For example, a medical student or resident is credentialed to perform history or physical examinations and to write progress notes. The attending physician signs the history and physical examination to validate the entry for inclusion in the patient's medical record.
VERFhttp://www.hl7.org/fhir/contractsignertypecodesVerifierA person who asserts the correctness and appropriateness of an act or the recording of the act, and is accountable for the assertion that the act or the recording of the act complies with jurisdictional or organizational policy. For example, a physician is required to countersign a verbal order that has previously been recorded in the medical record by a registered nurse who has carried out the verbal order.
AFFLhttp://hl7.org/fhir/v3/RoleClassaffiliatePlayer of the Affiliate role has a business/professional relationship with scoper. Player and scoper may be persons or organization. The Affiliate relationship does not imply membership in a group, nor does it exist for resource scheduling purposes. Example: A healthcare provider is affiliated with another provider as a business associate.
AGNThttp://hl7.org/fhir/v3/RoleClassagentAn entity (player) that acts or is authorized to act on behalf of another entity (scoper).
ASSIGNEDhttp://hl7.org/fhir/v3/RoleClassassigned entityAn agent role in which the agent is an Entity acting in the employ of an organization. The focus is on functional role on behalf of the organization, unlike the Employee role where the focus is on the 'Human Resources' relationship between the employee and the organization.
CLAIMhttp://hl7.org/fhir/v3/RoleClassclaimantDescription: A role played by a party making a claim for coverage under a policy or program. A claimant must be either a person or organization, or a group of persons or organizations. A claimant is not a named insured or a program eligible. Discussion: With respect to liability insurance such as property and casualty insurance, a claimant must file a claim requesting indemnification for a loss that the claimant considers covered under the policy of a named insured. The claims adjuster for the policy underwriter will review the claim to determine whether the loss meets the benefit coverage criteria under a policy, and base any indemnification or coverage payment on that review. If a third party is liable in whole or part for the loss, the underwriter may pursue third party liability recovery. A claimant may be involved in civil or criminal legal proceedings involving claims against a defendant party that is indemnified by an insurance policy or to protest the finding of a claims adjustor. With respect to life insurance, a beneficiary designated by a named insured becomes a claimant of the proceeds of coverage, as in the case of a life insurance policy. However, a claimant for coverage under life insurance is not necessarily a designated beneficiary. Note: A claimant is not a named insured. However, a named insured may make a claim under a policy, e.g., an insured driver may make a claim for an injury under his or her comprehensive automobile insurance policy. Similarly, a program eligible may make a claim under program, e.g., an unemployed worker may claim benefits under an unemployment insurance program, but parties playing these covered party role classes are not, for purposes of this vocabulary and in an effort to clearly distinguish role classes, considered claimants. In the case of a named insured making a claim, a role type code INSCLM (insured claimant) subtypes the class to indicate that either a named insured or an individual insured has filed a claim for a loss. In the case of a program eligible, a role type code INJWKR (injured worker) subtypes the class to indicate that the covered party in a workers compensation program is an injured worker, and as such, has filed a "claim" under the program for benefits. Likewise, a covered role type code UNEMP (unemployed worker) subtypes the program eligible class to indicate that the covered party in an unemployment insurance program has filed a claim for unemployment benefits. Example: A claimant under automobile policy that is not the named insured.
COVPTYhttp://hl7.org/fhir/v3/RoleClasscovered partyA role class played by a person who receives benefit coverage under the terms of a particular insurance policy. The underwriter of that policy is the scoping entity. The covered party receives coverage because of some contractual or other relationship with the holder of that policy. Discussion:This reason for coverage is captured in 'Role.code' and a relationship link with type code of indirect authority should be included using the policy holder role as the source, and the covered party role as the target. Note that a particular policy may cover several individuals one of whom may be, but need not be, the policy holder. Thus the notion of covered party is a role that is distinct from that of the policy holder.
DEPENhttp://hl7.org/fhir/v3/RoleClassdependentDescription: A role played by a person covered under a policy or program based on an association with a subscriber, which is recognized by the policy holder. Note: The party playing the role of a dependent is not a claimant in the sense conveyed by the RoleClassCoveredParty CLAIM (claimant). However, a dependent may make a claim under a policy, e.g., a dependent under a health insurance policy may become the claimant for coverage under that policy for wellness examines or if injured and there is no liable third party. In the case of a dependent making a claim, a role type code INSCLM (insured claimant) subtypes the class to indicate that the dependent has filed a claim for services covered under the health insurance policy. Example: The dependent has an association with the subscriber such as a financial dependency or personal relationship such as that of a spouse, or a natural or adopted child. The policy holder may be required by law to recognize certain associations or may have discretion about the associations. For example, a policy holder may dictate the criteria for the dependent status of adult children who are students, such as requiring full time enrollment, or may recognize domestic partners as dependents. Under certain circumstances, the dependent may be under the indirect authority of a responsible party acting as a surrogate for the subscriber, for example, if the subscriber is differently abled or deceased, a guardian ad Lidem or estate executor may be appointed to assume the subscriberaTMs legal standing in the relationship with the dependent.
ECONhttp://hl7.org/fhir/v3/RoleClassemergency contactAn entity to be contacted in the event of an emergency.
EMPhttp://hl7.org/fhir/v3/RoleClassemployeeA relationship between a person or organization and a person or organization formed for the purpose of exchanging work for compensation. The purpose of the role is to identify the type of relationship the employee has to the employer, rather than the nature of the work actually performed. (Contrast with AssignedEntity.)
GUARDhttp://hl7.org/fhir/v3/RoleClassguardianGuardian of a ward
INVSBJhttp://hl7.org/fhir/v3/RoleClassInvestigation SubjectAn entity that is the subject of an investigation. This role is scoped by the party responsible for the investigation.
NAMEDhttp://hl7.org/fhir/v3/RoleClassnamed insuredDescription: A role played by a party to an insurance policy to which the insurer agrees to indemnify for losses, provides benefits for, or renders services. A named insured may be either a person, non-person living subject, or an organization, or a group of persons, non-person living subjects, or organizations. Discussion: The coded concept NAMED should not be used where a more specific child concept in this Specializable value set applies. In some cases, the named insured may not be the policy holder, e.g., where a policy holder purchases life insurance policy in which another party is the named insured and the policy holder is the beneficiary of the policy. Note: The party playing the role of a named insured is not a claimant in the sense conveyed by the RoleClassCoveredParty CLAIM (claimant). However, a named insured may make a claim under a policy, e.g., e.g., a party that is the named insured and policy holder under a comprehensive automobile insurance policy may become the claimant for coverage under that policy e.g., if injured in an automobile accident and there is no liable third party. In the case of a named insured making a claim, a role type code INSCLM (insured claimant) subtypes the class to indicate that a named insured has filed a claim for a loss. Example: The named insured under a comprehensive automobile, disability, or property and casualty policy that is the named insured and may or may not be the policy holder.
NOKhttp://hl7.org/fhir/v3/RoleClassnext of kinAn individual designated for notification as the next of kin for a given entity.
PAThttp://hl7.org/fhir/v3/RoleClasspatientA Role of a LivingSubject (player) as an actual or potential recipient of health care services from a healthcare provider organization (scoper). Usage Note: Communication about relationships between patients and specific healthcare practitioners (people) is not done via scoper. Instead this is generally done using the CareProvision act. This allows linkage between patient and a particular healthcare practitioner role and also allows description of the type of care involved in the relationship.
PROVhttp://hl7.org/fhir/v3/RoleClasshealthcare providerAn Entity (player) that is authorized to provide health care services by some authorizing agency (scoper).
NOThttp://hl7.org/fhir/v3/RoleClassnotary publicnotary public
CLASSIFIERhttp://hl7.org/fhir/v3/RoleCodeclassifierAn individual authorized to assign an original classification to information, including compilations of unclassified information, based on a determination that the information requires protection against unauthorized disclosure. The individual marks the information with immutable, computable, and human readable security labels in accordance with applicable security labeling policies. The labeling policies provide instructions on whether and if so how the security labels may be later reclassified [i.e., upgraded, downgraded, used in derivative classification, or declassified] in a manner that preserves the overridden original classification binding and provenance.
CONSENTERhttp://hl7.org/fhir/v3/RoleCodeconsenterAn entity or an entity's delegatee who is the grantee in an agreement such as a consent for services, advanced directive, or a privacy consent directive in accordance with jurisdictional, organizational, or patient policy.
CONSWIThttp://hl7.org/fhir/v3/RoleCodeconsent witnessAn entity which has witnessed and attests to observing another entity being counseled about an agreement such as a consent for services, advanced directive, or a privacy consent directive.
COPARThttp://hl7.org/fhir/v3/RoleCodeco-participantAn entity which participates in the generation of and attest to veracity of content, but is not an author or coauthor. For example a surgeon who is required by institutional, regulatory, or legal rules to sign an operative report, but who was not involved in the authorship of that report.
DECLASSIFIERhttp://hl7.org/fhir/v3/RoleCodedeclassifierAn individual which is authorized to declassify information based on a determination that the information no longer requires protection against unauthorized disclosure. The individual marks the information being declassified using computable and human readable security labels indicating that this is copy of previously classified information is unclassified in accordance with applicable security labeling policies. The labeling policies provide instructions on whether and if so how the security labels may be later reclassified [i.e., upgraded or used in derivative classification] in a manner that preserves the overridden original classification binding and provenance.
DELEGATEEhttp://hl7.org/fhir/v3/RoleCodedelegateeA party to whom some right or authority is granted by a delegator.
DELEGATORhttp://hl7.org/fhir/v3/RoleCodedelegatorA party that grants all or some portion its right or authority to another party.
DOWNGRDERhttp://hl7.org/fhir/v3/RoleCodedowngraderAn individual authorized to lower the classification level of labeled content and provide rationale for doing so as directed by a classification guide.
DPOWATThttp://hl7.org/fhir/v3/RoleCodedurable power of attorneyA relationship between two people in which one person authorizes another, usually a family member or relative, to act for him or her in a manner which is a legally binding upon the person giving such authority as if he or she personally were to do the acts that is often limited in the kinds of powers that can be assigned. Unlike ordinary powers of attorney, durable powers can survive for long periods of time, and again, unlike standard powers of attorney, durable powers can continue after incompetency.
EXCESThttp://hl7.org/fhir/v3/RoleCodeexecutor of estateThe role played by a person acting as the estate executor for a deceased subscriber or policyholder who was the responsible party
GRANTEEhttp://hl7.org/fhir/v3/RoleCodegranteeAn entity which accepts certain rights or authority from a grantor.
GRANTORhttp://hl7.org/fhir/v3/RoleCodegrantorAn entity which agrees to confer certain rights or authority to a grantee.
GThttp://hl7.org/fhir/v3/RoleCodeGuarantorAn individual or organization that makes or gives a promise, assurance, pledge to pay or has paid the healthcare service provider.
GUADLTMhttp://hl7.org/fhir/v3/RoleCodeguardian ad lidemThe role played by a person appointed by the court to look out for the best interests of a minor child during the course of legal proceedings.
HPOWATThttp://hl7.org/fhir/v3/RoleCodehealthcare power of attorneyA relationship between two people in which one person authorizes another to act for him or her in a manner which is a legally binding upon the person giving such authority as if he or she personally were to do the acts that continues (by its terms) to be effective even though the grantor has become mentally incompetent after signing the document.
INTPRTERhttp://hl7.org/fhir/v3/RoleCodeinterpreterAn entity which converts spoken or written language into the language of key participants in an event such as when a provider is obtaining a patient's consent to treatment or permission to disclose information.
POWATThttp://hl7.org/fhir/v3/RoleCodepower of attorneyA relationship between two people in which one person authorizes another to act for him in a manner which is a legally binding upon the person giving such authority as if he or she personally were to do the acts.
RESPRSNhttp://hl7.org/fhir/v3/RoleCoderesponsible partyThe role played by a party who has legal responsibility for another party.
SPOWATThttp://hl7.org/fhir/v3/RoleCodespecial power of attorneyA relationship between two people in which one person authorizes another to act for him or her in a manner which is a legally binding upon the person giving such authority as if he or she personally were to do the acts that is often limited in the kinds of powers that can be assigned.
_CitizenRoleTypehttp://hl7.org/fhir/v3/RoleCodeCitizenRoleTypeA role type used to qualify a person's legal status within a country or nation.
CAShttp://hl7.org/fhir/v3/RoleCodeasylum seekerA person who has fled his or her home country to find a safe place elsewhere.
CASMhttp://hl7.org/fhir/v3/RoleCodesingle minor asylum seekerA person who is someone of below legal age who has fled his or her home country, without his or her parents, to find a safe place elsewhere at time of categorization.
CNhttp://hl7.org/fhir/v3/RoleCodenationalA person who is legally recognized as a member of a nation or country, with associated rights and obligations.
CNRPhttp://hl7.org/fhir/v3/RoleCodenon-country member without residence permitA foreigner who is present in a country (which is foreign to him/her) unlawfully or without the country's authorization (may be called an illegal alien).
CNRPMhttp://hl7.org/fhir/v3/RoleCodenon-country member minor without residence permitA person who is below legal age present in a country, without his or her parents, (which is foreign to him/her) unlawfully or without the country's authorization.
CPCAhttp://hl7.org/fhir/v3/RoleCodepermit card applicantA non-country member admitted to the territory of a nation or country as a non-resident for an explicit purpose.
CRPhttp://hl7.org/fhir/v3/RoleCodenon-country member with residence permitA foreigner who is a resident of the country but does not have citizenship.
CRPMhttp://hl7.org/fhir/v3/RoleCodenon-country member minor with residence permitA person who is a resident below legal age of the country without his or her parents and does not have citizenship.
AUCGhttp://hl7.org/fhir/v3/ParticipationFunctioncaregiver information receiverDescription:Caregiver authorized to receive patient health information.
AULRhttp://hl7.org/fhir/v3/ParticipationFunctionlegitimate relationship information receiverDescription:Provider with legitimate relationship authorized to receive patient health information.
AUTMhttp://hl7.org/fhir/v3/ParticipationFunctioncare team information receiverDescription:Member of care team authorized to receive patient health information.
AUWAhttp://hl7.org/fhir/v3/ParticipationFunctionwork area information receiverDescription:Entities within specified work area authorized to receive patient health information.
PROMSKhttp://hl7.org/fhir/v3/ParticipationFunctionauthorized provider masking authorDefinition:Provider authorized to mask information to protect the patient, a third party, or to ensure that the provider has consulted with the patient prior to release of this information.
AUThttp://hl7.org/fhir/v3/ParticipationTypeauthor (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.
CSThttp://hl7.org/fhir/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.).
INFhttp://hl7.org/fhir/v3/ParticipationTypeinformantA 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.
IRCPhttp://hl7.org/fhir/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.
LAhttp://hl7.org/fhir/v3/ParticipationTypelegal authenticatorA verifier who legally authenticates the accuracy of an act. An example would be a staff physician who sees a patient and dictates a note, then later signs it. Their signature constitutes a legal authentication.
TRChttp://hl7.org/fhir/v3/ParticipationTypetrackerA secondary information recipient, who receives copies (e.g., a primary care provider receiving copies of results as ordered by specialist).
WIThttp://hl7.org/fhir/v3/ParticipationTypewitnessOnly with service events. A person witnessing the action happening without doing anything. A witness is not necessarily aware, much less approves of anything stated in the service event. Example for a witness is students watching an operation or an advanced directive witness.
authserverhttp://hl7.org/fhir/extra-security-role-typeauthorization serverAn entity providing authorization services to enable the electronic sharing of health-related information based on resource owner's preapproved permissions. For example, an UMA Authorization Server[UMA]
datacollectorhttp://hl7.org/fhir/extra-security-role-typedata collectorAn entity that collects information over which the data subject may have certain rights under policy or law to control that information's management and distribution by data collectors, including the right to access, retrieve, distribute, or delete that information.
dataprocessorhttp://hl7.org/fhir/extra-security-role-typedata processorAn entity that processes collected information over which the data subject may have certain rights under policy or law to control that information's management and distribution by data processors, including the right to access, retrieve, distribute, or delete that information.
datasubjecthttp://hl7.org/fhir/extra-security-role-typedata subjectA person whose personal information is collected or processed, and who may have certain rights under policy or law to control that information's management and distribution by data collectors or processors, including the right to access, retrieve, distribute, or delete that information.
humanuserhttp://hl7.org/fhir/extra-security-role-typehuman userThe human user that has participated.
110150http://dicom.nema.org/resources/ontology/DCMApplicationAudit participant role ID of software application
110151http://dicom.nema.org/resources/ontology/DCMApplication LauncherAudit participant role ID of software application launcher, i.e., the entity that started or stopped an application
110152http://dicom.nema.org/resources/ontology/DCMDestination Role IDAudit participant role ID of the receiver of data
110153http://dicom.nema.org/resources/ontology/DCMSource Role IDAudit participant role ID of the sender of data
110154http://dicom.nema.org/resources/ontology/DCMDestination MediaAudit participant role ID of media receiving data during an export
110155http://dicom.nema.org/resources/ontology/DCMSource MediaAudit participant role ID of media providing data during an import

 

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


Explanation of the columns that may appear on this page:

LvlA few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - see Code System for further information
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). If the code is in italics, this indicates that the code is not selectable ('Abstract')
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