Clinical Document Architecture
2.0.0-sd - release

Clinical Document Architecture, published by Health Level 7. This guide is not an authorized publication; it is the continuous build for version 2.0.0-sd built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/CDA-core-sd/ and changes regularly. See the Directory of published versions

ValueSet: CDARoleClassMutualRelationship

Official URL: http://hl7.org/cda/stds/core/ValueSet/CDARoleClassMutualRelationship Version: 2.0.0-sd
Draft as of 2024-05-16 Computable Name: CDARoleClassMutualRelationship

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

Logical Definition (CLD)

  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-RoleClass
    CodeDisplayDefinition
    LIClicensed entityA 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).
    NOTnotary public
    PROVhealthcare providerAn Entity (player) that is authorized to provide health care services by some authorizing agency (scoper).
    CONcontactA person or an organization (player) which provides or receives information regarding another entity (scoper). Examples; patient NOK and emergency contacts; guarantor contact; employer contact.
    ECONemergency contactAn entity to be contacted in the event of an emergency.
    NOKnext of kinAn individual designated for notification as the next of kin for a given entity.
    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.
    COMPARcommissioning partyAn Entity that is authorized to issue or instantiate permissions, privileges, credentials or other formal/legal authorizations.
    SGNOFFsigning authority or officerThe role of a person (player) who is the officer or signature authority for of a scoping entity, usually an organization (scoper).
    AGNTagentAn entity (player) that acts or is authorized to act on behalf of another entity (scoper).
    GUARDguardianGuardian of a ward
    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.)
    MILmilitary personA 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.)
    INVSBJInvestigation SubjectAn entity that is the subject of an investigation. This role is scoped by the party responsible for the investigation.
    CASESBJ
    RESBJresearch 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.
    CITcitizenCitizen of apolitical entity
    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.
    CRINVclinical research investigatorA 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.
    CRSPNSRclinical research sponsorA 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.
    GUARguarantorA person or organization (player) that serves as a financial guarantor for another person or organization (scoper).
    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.
    PAYEEpayeeThe 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.
    PAYORinvoice payorThe 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.
    POLHOLDpolicy holderA 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.
    QUALqualified entityAn 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.
    SPNSRcoverage sponsorA 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.
    STDstudentA role played by an individual who is a student of a school, which is the scoping entity.
    UNDWRTunderwriterA 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
    CAREGIVERcaregiverA person responsible for the primary care of a patient at home.
    PRSpersonal relationshipLinks 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.

 

Expansion

Expansion based on codesystem RoleClass v3.1.0 (CodeSystem)

This value set contains 30 concepts.

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

  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.

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

  AGNThttp://terminology.hl7.org/CodeSystem/v3-RoleClassagent

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

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

Guardian of a ward

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

  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.

  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.

  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.

  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.

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

A person or organization (player) that serves as a financial guarantor for another person or organization (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.


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