HL7 Terminology (THO)
5.2.0 - Publication International flag

This page is part of the HL7 Terminology (v5.2.0: Release) based on FHIR R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

ValueSet: RoleClassMutualRelationship

Official URL: http://terminology.hl7.org/ValueSet/v3-RoleClassMutualRelationship Version: 2.0.0
Active as of 2014-03-26 Computable Name: RoleClassMutualRelationship
Other Identifiers: id: urn:oid:2.16.840.1.113883.1.11.19316

A relationship that is based on mutual behavior of the two Entities as being related. The basis of such relationship may be agreements (e.g., spouses, contract parties) or they may be de facto behavior (e.g. friends) or may be an incidental involvement with each other (e.g. parties over a dispute, siblings, children).

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)

This value set includes codes based on the following rules:

This value set excludes codes based on the following rules:

  • Exclude these codes as defined in http://terminology.hl7.org/CodeSystem/v3-RoleClass
    CodeDisplayDefinition
    _RoleClassMutualRelationshipRoleClassMutualRelationshipA relationship that is based on mutual behavior of the two Entities as being related. The basis of such relationship may be agreements (e.g., spouses, contract parties) or they may be *de facto* behavior (e.g. friends) or may be an incidental involvement with each other (e.g. parties over a dispute, siblings, children).

 

Expansion

This value set contains 39 concepts

Expansion based on RoleClass v3.1.0 (CodeSystem)

CodeSystemDisplayDefinition
  _RoleClassRelationshipFormalhttp://terminology.hl7.org/CodeSystem/v3-RoleClassRoleClassRelationshipFormal

A relationship between two entities that is formally recognized, frequently by a contract or similar agreement.

  AFFLhttp://terminology.hl7.org/CodeSystem/v3-RoleClassaffiliate

Player 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://terminology.hl7.org/CodeSystem/v3-RoleClassagent

An entity (player) that acts or is authorized to act on behalf of another entity (scoper).

  ASSIGNEDhttp://terminology.hl7.org/CodeSystem/v3-RoleClassassigned entity

An 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.

  COMPARhttp://terminology.hl7.org/CodeSystem/v3-RoleClasscommissioning party

An Entity that is authorized to issue or instantiate permissions, privileges, credentials or other formal/legal authorizations.

  SGNOFFhttp://terminology.hl7.org/CodeSystem/v3-RoleClasssigning authority or officer

The role of a person (player) who is the officer or signature authority for of a scoping entity, usually an organization (scoper).

  CONhttp://terminology.hl7.org/CodeSystem/v3-RoleClasscontact

A person or an organization (player) which provides or receives information regarding another entity (scoper). Examples; patient NOK and emergency contacts; guarantor contact; employer contact.

  ECONhttp://terminology.hl7.org/CodeSystem/v3-RoleClassemergency contact

An entity to be contacted in the event of an emergency.

  NOKhttp://terminology.hl7.org/CodeSystem/v3-RoleClassnext of kin

An individual designated for notification as the next of kin for a given entity.

  GUARDhttp://terminology.hl7.org/CodeSystem/v3-RoleClassguardian

Guardian of a ward

  CIThttp://terminology.hl7.org/CodeSystem/v3-RoleClasscitizen

Citizen of apolitical entity

  COVPTYhttp://terminology.hl7.org/CodeSystem/v3-RoleClasscovered party

A 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.

  CLAIMhttp://terminology.hl7.org/CodeSystem/v3-RoleClassclaimant

Description: 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.

  NAMEDhttp://terminology.hl7.org/CodeSystem/v3-RoleClassnamed insured

Description: 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.

  DEPENhttp://terminology.hl7.org/CodeSystem/v3-RoleClassdependent

Description: 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.

  INDIVhttp://terminology.hl7.org/CodeSystem/v3-RoleClassindividual

Description: A role played by a party covered under a policy as the policy holder. An individual may be either a person or an organization.

Note: The party playing the role of an individual 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., 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 if injured in an automobile accident and there is no liable third party. In the case of an individual insured making a claim, a role type code INSCLM (insured claimant) subtypes the class to indicate that an individual insured has filed a claim for a loss.

Example: The individual insured under a comprehensive automobile, disability, or property and casualty policy that is the policy holder.

  SUBSCRhttp://terminology.hl7.org/CodeSystem/v3-RoleClasssubscriber

Description: A role played by a person covered under a policy based on association with a sponsor who is the policy holder, and whose association may provide for the eligibility of dependents for coverage.

Discussion: The policy holder holds the contract with the policy or program underwriter. The subscriber holds a certificate of coverage under the contract. In legal proceedings concerning the policy or program, the terms of the contract takes precedence over the terms of the certificate of coverage if there are any inconsistencies.

Note: The party playing the role of a subscriber is not a claimant in the sense conveyed by the RoleClassCoveredParty CLAIM (claimant). However, a subscriber may make a claim under a policy, e.g., a subscriber 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 subscriber making a claim, a role type code INSCLM (insured claimant) subtypes the class to indicate that the subscriber has filed a claim for services covered under the health insurance policy.

Example: An employee or a member of an association.

  PROGhttp://terminology.hl7.org/CodeSystem/v3-RoleClassprogram eligible

Description: A role played by a party that meets the eligibility criteria for coverage under a program. A program eligible may be either a person, non-person living subject, or an organization, or a group of persons, non-person living subjects, or organizations.

Discussion: A program as typically government administered coverage for parties determined eligible under the terms of the program.

Note: The party playing a program eligible is not a claimant in the sense conveyed by the RoleClassCoveredParty CLAIM (claimant). However 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 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 party meeting eligibility criteria related to health or financial status, e.g., in the U.S., persons meeting health, demographic, or financial criteria established by state and federal law are eligible for Medicaid.

  CRINVhttp://terminology.hl7.org/CodeSystem/v3-RoleClassclinical research investigator

A role played by a provider, always a person, who has agency authority from a Clinical Research Sponsor to direct the conduct of a clinical research trial or study on behalf of the sponsor.

  CRSPNSRhttp://terminology.hl7.org/CodeSystem/v3-RoleClassclinical research sponsor

A role played by an entity, usually an organization, that is the sponsor of a clinical research trial or study. The sponsor commissions the study, bears the expenses, is responsible for satisfying all legal requirements concerning subject safety and privacy, and is generally responsible for collection, storage and analysis of the data generated during the trial. No scoper is necessary, as a clinical research sponsor undertakes the role on its own authority and declaration. Clinical research sponsors are usually educational or other research organizations, government agencies or biopharmaceutical companies.

  EMPhttp://terminology.hl7.org/CodeSystem/v3-RoleClassemployee

A 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.)

  MILhttp://terminology.hl7.org/CodeSystem/v3-RoleClassmilitary person

A role played by a member of a military service. Scoper is the military service (e.g. Army, Navy, Air Force, etc.) or, more specifically, the unit (e.g. Company C, 3rd Battalion, 4th Division, etc.)

  GUARhttp://terminology.hl7.org/CodeSystem/v3-RoleClassguarantor

A person or organization (player) that serves as a financial guarantor for another person or organization (scoper).

  INVSBJhttp://terminology.hl7.org/CodeSystem/v3-RoleClassInvestigation Subject

An entity that is the subject of an investigation. This role is scoped by the party responsible for the investigation.

  CASEBJhttp://terminology.hl7.org/CodeSystem/v3-RoleClassCase Subject

A person, non-person living subject, or place that is the subject of an investigation related to a notifiable condition (health circumstance that is reportable within the applicable public health jurisdiction)

  RESBJhttp://terminology.hl7.org/CodeSystem/v3-RoleClassresearch subject

**Definition:**Specifies the administrative functionality within a formal experimental design for which the ResearchSubject role was established.

Examples: Screening - role is used for pre-enrollment evaluation portion of the design; enrolled - role is used for subjects admitted to the experimental portion of the design.

  LIChttp://terminology.hl7.org/CodeSystem/v3-RoleClasslicensed entity

A relationship in which the scoper certifies the player ( e. g. a medical care giver, a medical device or a provider organization) to perform certain activities that fall under the jurisdiction of the scoper (e.g., a health authority licensing healthcare providers, a medical quality authority certifying healthcare professionals).

  NOThttp://terminology.hl7.org/CodeSystem/v3-RoleClassnotary public
  PROVhttp://terminology.hl7.org/CodeSystem/v3-RoleClasshealthcare provider

An Entity (player) that is authorized to provide health care services by some authorizing agency (scoper).

  PAThttp://terminology.hl7.org/CodeSystem/v3-RoleClasspatient

A 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.

  PAYEEhttp://terminology.hl7.org/CodeSystem/v3-RoleClasspayee

The role of an organization or individual designated to receive payment for a claim against a particular coverage. The scoping entity is the organization that is the submitter of the invoice in question.

  PAYORhttp://terminology.hl7.org/CodeSystem/v3-RoleClassinvoice payor

The role of an organization that undertakes to accept claims invoices, assess the coverage or payments due for those invoices and pay to the designated payees for those invoices. This role may be either the underwriter or a third-party organization authorized by the underwriter. The scoping entity is the organization that underwrites the claimed coverage.

  POLHOLDhttp://terminology.hl7.org/CodeSystem/v3-RoleClasspolicy holder

A role played by a person or organization that holds an insurance policy. The underwriter of that policy is the scoping entity.

*Discussion:*The identifier of the policy is captured in 'Role.id' when the Role is a policy holder.

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.

  QUALhttp://terminology.hl7.org/CodeSystem/v3-RoleClassqualified entity

An entity (player) that has been recognized as having certain training/experience or other characteristics that would make said entity an appropriate performer for a certain activity. The scoper is an organization that educates or qualifies entities.

  SPNSRhttp://terminology.hl7.org/CodeSystem/v3-RoleClasscoverage sponsor

A role played by an entity, usually an organization that is the sponsor of an insurance plan or a health program. A sponsor is the party that is ultimately accountable for the coverage by employment contract or by law. A sponsor can be an employer, union, government agency, or association. Fully insured sponsors establish the terms of the plan and contract with health insurance plans to assume the risk and to administer the plan. Self-insured sponsors delegate coverage administration, but not risk, to third-party administrators. Program sponsors designate services to be covered in accordance with statute. Program sponsors may administer the coverage themselves, delegate coverage administration, but not risk to third-party administrators, or contract with health insurance plans to assume the risk and administrator a program. Sponsors qualify individuals who may become

  1. a policy holder of the plan;
  2. where the sponsor is the policy holder, who may become a subscriber or a dependent to a policy under the plan; or
  3. where the sponsor is a government agency, who may become program eligibles under a program.

The sponsor role may be further qualified by the SponsorRole.code. Entities playing the sponsor role may also play the role of a Coverage Administrator.

Example: An employer, union, government agency, or association.

  STDhttp://terminology.hl7.org/CodeSystem/v3-RoleClassstudent

A role played by an individual who is a student of a school, which is the scoping entity.

  UNDWRThttp://terminology.hl7.org/CodeSystem/v3-RoleClassunderwriter

A role played by a person or an organization. It is the party that

  1. accepts fiscal responsibility for insurance plans and the policies created under those plans;
  2. administers and accepts fiscal responsibility for a program that provides coverage for services to eligible individuals; and/or
  3. has the responsibility to assess the merits of each risk and decide a suitable premium for accepting all or part of the risk. If played by an organization, this role may be further specified by an appropriate RoleCode.

Example:

  1. A health insurer;
  2. Medicaid Program;
  3. Lloyd's of London
  CAREGIVERhttp://terminology.hl7.org/CodeSystem/v3-RoleClasscaregiver

A person responsible for the primary care of a patient at home.

  PRShttp://terminology.hl7.org/CodeSystem/v3-RoleClasspersonal relationship

Links two entities with classCode PSN (person) in a personal relationship. The character of the relationship must be defined by a PersonalRelationshipRoleType code. The player and scoper are determined by PersonalRelationshipRoleType code as well.

  SELFhttp://terminology.hl7.org/CodeSystem/v3-RoleClassself

The "same" roleclass asserts an identity between playing and scoping entities: that they are in fact instances of the same entity and, in the case of discrepancies (e.g different DOB, gender), that one or both are in error.

Usage:

playing and scoping entities must have same classcode, but need not have identical attributes or values.

Example:

a provider registry maintains sets of conflicting demographic data for what is reported to be the same individual.


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

History

DateActionAuthorCustodianComment
2022-10-18reviseMarc DuteauTSMGFixing missing metadata; up-349
2020-05-06reviseTed KleinVocabulary WGMigrated to the UTG maintenance environment and publishing tooling.
2014-03-26reviseVocabulary (Woody Beeler) (no record of original request)2014T1_2014-03-26_001283 (RIM release ID)Lock all vaue sets untouched since 2014-03-26 to trackingId 2014T1_2014_03_26