Release 5 Preview #2

V3-RoleClass.cs.xml

Vocabulary Work GroupMaturity Level: N/AStandards Status: Informative

Raw XML (canonical form + also see XML Format Specification)

Codes for the Role class hierarchy. The values in this hierarchy, represent a Role which is an association or relationship between two entities - the entity that plays the role and the entity that scopes the role. Roles names are derived from the name of the playing entity in that role. The role hierarchy stems from three core concepts, or abstract domains: RoleClassOntological is an abstract domain that collects roles in which the playing entity is defined or specified by the scoping entity. RoleClassPartitive collects roles in which the playing entity is in some sense a "part" of the scoping entity. RoleClassAssociative collects all of the remaining forms of association between the playing entity and the scoping entity. This set of roles is further partitioned between: RoleClassPassive which are roles in which the playing entity is used, known, treated, handled, built, or destroyed, etc. under the auspices of the scoping entity. The playing entity is passive in these roles in that the role exists without an agreement from the playing entity. RoleClassMutualRelationship which are relationships based on mutual behavior of the two entities. The basis of these relationship may be formal agreements or they may bede facto behavior. Thus, this sub-domain is further divided into: RoleClassRelationshipFormal in which the relationship is formally defined, frequently by a contract or agreement. Personal relationship which inks two people in a personal relationship. The hierarchy discussed above is represented In the current vocabulary tables as a set of abstract domains, with the exception of the "Personal relationship" which is a leaf concept. OpenIssue: Description copied from Concept Domain of same name. Must be verified.

<?xml version="1.0" encoding="UTF-8"?>

<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="v3-RoleClass"/> 
  <meta> 
    <lastUpdated value="2019-07-31T00:00:00.000+00:00"/> 
  </meta> 
  <text> 
    <status value="generated"/> 
    <div xmlns="http://www.w3.org/1999/xhtml">
      <p> Release Date: 2019-07-31</p> 

      <table class="grid">
 
        <tr> 
          <td> 
            <b> Level</b> 
          </td> 
          <td> 
            <b> Code</b> 
          </td> 
          <td> 
            <b> Display</b> 
          </td> 
          <td> 
            <b> Definition</b> 
          </td> 
        </tr> 
 
        <tr> 
          <td> 1</td> 
          <td> ROL
            <a name="v3-RoleClass-ROL"> </a> 
          </td> 
          <td> role</td> 
          <td> 
                        Corresponds to the Role class
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 2</td> 
          <td>   
            <span style="color: grey">
              <i> (_RoleClassAssociative)</i> 
            </span>  
            <b> 
              <i> Abstract</i> 
            </b> 
          </td> 
          <td> 
            <a name="v3-RoleClass-_RoleClassAssociative"> </a> 
          </td> 
          <td> 
                        A general association between two entities that is neither partitive
               nor ontological.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 3</td> 
          <td>     
            <span style="color: grey">
              <i> (_RoleClassMutualRelationship)</i> 
            </span>  
            <b> 
              <i> Abstract</i> 
            </b> 
          </td> 
          <td> 
            <a name="v3-RoleClass-_RoleClassMutualRelationship"> </a> 
          </td> 
          <td> 
                        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).
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 4</td> 
          <td>       
            <span style="color: grey">
              <i> (_RoleClassRelationshipFormal)</i> 
            </span>  
            <b> 
              <i> Abstract</i> 
            </b> 
          </td> 
          <td> 
            <a name="v3-RoleClass-_RoleClassRelationshipFormal"> </a> 
          </td> 
          <td> 
                        A relationship between two entities that is formally recognized,
               frequently by a contract or similar agreement.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 5</td> 
          <td>         AFFL
            <a name="v3-RoleClass-AFFL"> </a> 
          </td> 
          <td> affiliate</td> 
          <td> 
                        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.
            <br/>  

                        
                           Example: A healthcare provider is affiliated with another provider
               as a business associate.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 5</td> 
          <td>         AGNT
            <a name="v3-RoleClass-AGNT"> </a> 
          </td> 
          <td> agent</td> 
          <td> 
                        An entity (player) that acts or is authorized to act on behalf
               of another entity (scoper).
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 6</td> 
          <td>           ASSIGNED
            <a name="v3-RoleClass-ASSIGNED"> </a> 
          </td> 
          <td> assigned entity</td> 
          <td> 
                        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.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 7</td> 
          <td>             COMPAR
            <a name="v3-RoleClass-COMPAR"> </a> 
          </td> 
          <td> commissioning party</td> 
          <td> 
                        An Entity that is authorized to issue or instantiate permissions,
               privileges, credentials or other formal/legal authorizations.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 7</td> 
          <td>             SGNOFF
            <a name="v3-RoleClass-SGNOFF"> </a> 
          </td> 
          <td> signing authority or officer</td> 
          <td> 
                        The role of a person (player) who is the officer or signature
               authority for of a scoping entity, usually an organization (scoper).
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 6</td> 
          <td>           CON
            <a name="v3-RoleClass-CON"> </a> 
          </td> 
          <td> contact</td> 
          <td> 
                        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.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 7</td> 
          <td>             ECON
            <a name="v3-RoleClass-ECON"> </a> 
          </td> 
          <td> emergency contact</td> 
          <td> 
                        An entity to be contacted in the event of an emergency.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 7</td> 
          <td>             NOK
            <a name="v3-RoleClass-NOK"> </a> 
          </td> 
          <td> next of kin</td> 
          <td> 
                        An individual designated for notification as the next of kin for
               a given entity.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 6</td> 
          <td>           GUARD
            <a name="v3-RoleClass-GUARD"> </a> 
          </td> 
          <td> guardian</td> 
          <td> 
                        Guardian of a ward
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 5</td> 
          <td>         CIT
            <a name="v3-RoleClass-CIT"> </a> 
          </td> 
          <td> citizen</td> 
          <td> 
                        Citizen of apolitical entity
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 5</td> 
          <td>         COVPTY
            <a name="v3-RoleClass-COVPTY"> </a> 
          </td> 
          <td> covered party</td> 
          <td> 
                        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.
            <br/>  

                        
                           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.
            <br/>  

                        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.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 6</td> 
          <td>           CLAIM
            <a name="v3-RoleClass-CLAIM"> </a> 
          </td> 
          <td> claimant</td> 
          <td> 
                        
                           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.
            <br/>  

                        
                           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.
            <br/>  

                        
                           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.
            <br/>  

                        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
               &quot;claim&quot; 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.
            <br/>  

                        
                           Example: A claimant under automobile policy that is not the
               named insured.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 6</td> 
          <td>           NAMED
            <a name="v3-RoleClass-NAMED"> </a> 
          </td> 
          <td> named insured</td> 
          <td> 
                        
                           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.
            <br/>  

                        
                           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.
            <br/>  

                        
                           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.
            <br/>  

                        
                           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.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 7</td> 
          <td>             DEPEN
            <a name="v3-RoleClass-DEPEN"> </a> 
          </td> 
          <td> dependent</td> 
          <td> 
                        
                           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.
            <br/>  

                        
                           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.
            <br/>  

                        
                           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.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 7</td> 
          <td>             INDIV
            <a name="v3-RoleClass-INDIV"> </a> 
          </td> 
          <td> individual</td> 
          <td> 
                        
                           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.
            <br/>  

                        
                           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.
            <br/>  

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

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 7</td> 
          <td>             SUBSCR
            <a name="v3-RoleClass-SUBSCR"> </a> 
          </td> 
          <td> subscriber</td> 
          <td> 
                        
                           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.
            <br/>  

                        
                           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.
            <br/>  

                        
                           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.
            <br/>  

                        
                           Example: An employee or a member of an association.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 6</td> 
          <td>           PROG
            <a name="v3-RoleClass-PROG"> </a> 
          </td> 
          <td> program eligible</td> 
          <td> 
                        
                           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.
            <br/>  

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

                        
                           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.
            <br/>  

                        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 &quot;claim&quot; 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.
            <br/>  

                        
                           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.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 5</td> 
          <td>         CRINV
            <a name="v3-RoleClass-CRINV"> </a> 
          </td> 
          <td> clinical research investigator</td> 
          <td> 
                        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.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 5</td> 
          <td>         CRSPNSR
            <a name="v3-RoleClass-CRSPNSR"> </a> 
          </td> 
          <td> clinical research sponsor</td> 
          <td> 
                        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.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 5</td> 
          <td>         EMP
            <a name="v3-RoleClass-EMP"> </a> 
          </td> 
          <td> employee</td> 
          <td> 
                        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.)
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 6</td> 
          <td>           MIL
            <a name="v3-RoleClass-MIL"> </a> 
          </td> 
          <td> military person</td> 
          <td> 
                        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.)
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 5</td> 
          <td>         GUAR
            <a name="v3-RoleClass-GUAR"> </a> 
          </td> 
          <td> guarantor</td> 
          <td> 
                        A person or organization (player) that serves as a financial guarantor
               for another person or organization (scoper).
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 5</td> 
          <td>         INVSBJ
            <a name="v3-RoleClass-INVSBJ"> </a> 
          </td> 
          <td> Investigation Subject</td> 
          <td> 
                        An entity that is the subject of an investigation. This role is
               scoped by the party responsible for the investigation.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 6</td> 
          <td>           CASEBJ
            <a name="v3-RoleClass-CASEBJ"> </a> 
          </td> 
          <td> Case Subject</td> 
          <td> 
                        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)
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 6</td> 
          <td>           RESBJ
            <a name="v3-RoleClass-RESBJ"> </a> 
          </td> 
          <td> research subject</td> 
          <td> 
                        
                           Definition:Specifies the administrative functionality within
               a formal experimental design for which the ResearchSubject role was established.
            <br/>  

                        
                           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.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 5</td> 
          <td>         LIC
            <a name="v3-RoleClass-LIC"> </a> 
          </td> 
          <td> licensed entity</td> 
          <td> 
                        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).
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 6</td> 
          <td>           NOT
            <a name="v3-RoleClass-NOT"> </a> 
          </td> 
          <td> notary public</td> 
          <td/>  
        </tr> 
 
        <tr> 
          <td> 6</td> 
          <td>           PROV
            <a name="v3-RoleClass-PROV"> </a> 
          </td> 
          <td> healthcare provider</td> 
          <td> 
                        An Entity (player) that is authorized to provide health care services
               by some authorizing agency (scoper).
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 5</td> 
          <td>         PAT
            <a name="v3-RoleClass-PAT"> </a> 
          </td> 
          <td> patient</td> 
          <td> 
                        A Role of a LivingSubject (player) as an actual or potential recipient
               of health care services from a healthcare provider organization (scoper).
            <br/>  

                        
                           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.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 5</td> 
          <td>         PAYEE
            <a name="v3-RoleClass-PAYEE"> </a> 
          </td> 
          <td> payee</td> 
          <td> 
                        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.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 5</td> 
          <td>         PAYOR
            <a name="v3-RoleClass-PAYOR"> </a> 
          </td> 
          <td> invoice payor</td> 
          <td> 
                        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.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 5</td> 
          <td>         POLHOLD
            <a name="v3-RoleClass-POLHOLD"> </a> 
          </td> 
          <td> policy holder</td> 
          <td> 
                        A role played by a person or organization that holds an insurance
               policy.  The underwriter of that policy is the scoping entity.
            <br/>  

                        
                           Discussion:The identifier of the policy is captured in 'Role.id'
               when the Role is a policy holder.
            <br/>  

                        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.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 5</td> 
          <td>         QUAL
            <a name="v3-RoleClass-QUAL"> </a> 
          </td> 
          <td> qualified entity</td> 
          <td> 
                        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.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 5</td> 
          <td>         SPNSR
            <a name="v3-RoleClass-SPNSR"> </a> 
          </td> 
          <td> coverage sponsor</td> 
          <td> 
                        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 
            <br/>  

                        
                           
                              a policy holder of the plan;
            <br/>  

                           
                           
                              where the sponsor is the policy holder, who may become a
               subscriber or a dependent to a policy under the plan; or
            <br/>  

                           
                           
                              where the sponsor is a government agency, who may become
               program eligibles under a program. 
            <br/>  

                           
                        
                        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.
            <br/>  

                        
                           Example: An employer, union, government agency, or association.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 5</td> 
          <td>         STD
            <a name="v3-RoleClass-STD"> </a> 
          </td> 
          <td> student</td> 
          <td> 
                        A role played by an individual who is a student of a school, which
               is the scoping entity.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 5</td> 
          <td>         UNDWRT
            <a name="v3-RoleClass-UNDWRT"> </a> 
          </td> 
          <td> underwriter</td> 
          <td> 
                        A role played by a person or an organization.  It is the party
               that 
            <br/>  

                        
                           
                              accepts fiscal responsibility for insurance plans and the
               policies created under those plans;
            <br/>  

                           
                           
                              administers and accepts fiscal responsibility for a program
               that provides coverage for services to eligible individuals; and/or
            <br/>  

                           
                           
                              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.
            <br/>  

                           
                        
                        
                           Example:
                        
            <br/>  

                        
                           
                              A health insurer; 
            <br/>  

                           
                           
                              Medicaid Program;
            <br/>  

                           
                           
                              Lloyd's of London
            <br/>  

                           
                        
                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 4</td> 
          <td>       CAREGIVER
            <a name="v3-RoleClass-CAREGIVER"> </a> 
          </td> 
          <td> caregiver</td> 
          <td> 
                        A person responsible for the primary care of a patient at home.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 4</td> 
          <td>       PRS
            <a name="v3-RoleClass-PRS"> </a> 
          </td> 
          <td> personal relationship</td> 
          <td> 
                        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.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 4</td> 
          <td>       SELF
            <a name="v3-RoleClass-SELF"> </a> 
          </td> 
          <td> self</td> 
          <td> 
                        The &quot;same&quot; 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.
            <br/>  

                        
                           Usage:
                        
            <br/>  

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

                        
                           Example: 
                        
            <br/>  

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

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 3</td> 
          <td>     
            <span style="color: grey">
              <i> (_RoleClassPassive)</i> 
            </span>  
            <b> 
              <i> Abstract</i> 
            </b> 
          </td> 
          <td> 
            <a name="v3-RoleClass-_RoleClassPassive"> </a> 
          </td> 
          <td> 
                        An association for a playing Entity that is used, known, treated,
               handled, built, or destroyed, etc. under the auspices of the scoping Entity. The playing
               Entity is passive in these roles (even though it may be active in other roles), in the
               sense that the kinds of things done to it in this role happen without an agreement from
               the playing Entity.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 4</td> 
          <td>       ACCESS
            <a name="v3-RoleClass-ACCESS"> </a> 
          </td> 
          <td> access</td> 
          <td> 
                        A role in which the playing entity (material) provides access
               to another entity. The principal use case is intravenous (or other bodily) access lines
               that preexist and need to be referred to for medication routing instructions.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 4</td> 
          <td>       ADJY
            <a name="v3-RoleClass-ADJY"> </a> 
          </td> 
          <td> adjacency</td> 
          <td> 
                        A physical association whereby two Entities are in some (even
               lose) spatial relationship with each other such that they touch each other in some way.
            <br/>  

                        
                           Examples: the colon is connected (and therefore adjacent) to
               the jejunum; the colon is adjacent to the liver (even if not actually connected.)
            <br/>  

                        
                           UsageConstraints: Adjacency is in principle a symmetrical connection,
               but scoper and player of the role should, where applicable, be assigned to have scoper
               be the larger, more central Entity and player the smaller, more distant, appendage.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 5</td> 
          <td>         CONC
            <a name="v3-RoleClass-CONC"> </a> 
          </td> 
          <td> connection</td> 
          <td> 
                        An adjacency of two Entities held together by a bond which attaches
               to each of the two entities. 
            <br/>  

                        
                           Examples: biceps brachii muscle connected to the radius bone,
               port 3 on a network switch connected to port 5 on a patch panel.
            <br/>  

                        
                           UsageConstraints: See Adjacency for the assignment of scoper
               (larger, more central) and player (smaller, more distant).
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 6</td> 
          <td>           BOND
            <a name="v3-RoleClass-BOND"> </a> 
          </td> 
          <td> molecular bond</td> 
          <td> 
                        A connection between two atoms of a molecule.
            <br/>  

                        
                           Examples: double bond between first and second C in ethane,
               peptide bond between two amino-acid, disulfide bridge between two proteins, chelate and
               ion associations, even the much weaker van-der-Waals bonds can be considered molecular
               bonds.
            <br/>  

                        
                           UsageConstraints: See connection and adjacency for the assignment
               of player and scoper.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 6</td> 
          <td>           CONY
            <a name="v3-RoleClass-CONY"> </a> 
          </td> 
          <td> continuity</td> 
          <td> 
                        A connection between two regional parts.
            <br/>  

                        
                           Examples:  the connection between ascending aorta and the aortic
               arc, connection between descending colon and sigmoid.
            <br/>  

                        
                           UsageConstraints: See connection and adjacency for the assignment
               of player and scoper.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 4</td> 
          <td>       ADMM
            <a name="v3-RoleClass-ADMM"> </a> 
          </td> 
          <td> Administerable Material</td> 
          <td> 
                        A material (player) that can be administered to an Entity (scoper).
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 4</td> 
          <td>       BIRTHPL
            <a name="v3-RoleClass-BIRTHPL"> </a> 
          </td> 
          <td> birthplace</td> 
          <td> 
                        Relates a place (playing Entity) as the location where a living
               subject (scoping Entity) was born.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 4</td> 
          <td>       DEATHPLC
            <a name="v3-RoleClass-DEATHPLC"> </a> 
          </td> 
          <td> place of death</td> 
          <td> 
                        Definition: Relates a place (playing Entity) as the location where
               a living subject (scoping Entity) died.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 4</td> 
          <td>       DST
            <a name="v3-RoleClass-DST"> </a> 
          </td> 
          <td> distributed material</td> 
          <td> 
                        A material (player) distributed by a distributor (scoper) who
               functions between a manufacturer and a buyer or retailer.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 5</td> 
          <td>         RET
            <a name="v3-RoleClass-RET"> </a> 
          </td> 
          <td> retailed material</td> 
          <td> 
                        Material (player) sold by a retailer (scoper), who also give advice
               to prospective buyers.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 4</td> 
          <td>       EXLOC
            <a name="v3-RoleClass-EXLOC"> </a> 
          </td> 
          <td> event location</td> 
          <td> 
                        A role played by a place at which the location of an event may
               be recorded.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 5</td> 
          <td>         SDLOC
            <a name="v3-RoleClass-SDLOC"> </a> 
          </td> 
          <td> service delivery location</td> 
          <td> 
                        A role played by a place at which services may be provided.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 6</td> 
          <td>           DSDLOC
            <a name="v3-RoleClass-DSDLOC"> </a> 
          </td> 
          <td> dedicated service delivery location</td> 
          <td> 
                        A role of a place (player) that is intended to house the provision
               of services. Scoper is the Entity (typically Organization) that provides these services.
               This is not synonymous with &quot;ownership.&quot;
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 6</td> 
          <td>           ISDLOC
            <a name="v3-RoleClass-ISDLOC"> </a> 
          </td> 
          <td> incidental service delivery location</td> 
          <td> 
                        A role played by a place at which health care services may be
               provided without prior designation or authorization.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 4</td> 
          <td>       EXPR
            <a name="v3-RoleClass-EXPR"> </a> 
          </td> 
          <td> exposed entity</td> 
          <td> 
                        A role played by an entity that has been exposed to a person or
               animal suffering a contagious disease, or with a location from which a toxin has been
               distributed.  The player of the role is normally a person or animal, but it is possible
               that other entity types could become exposed.  The role is scoped by the source of the
               exposure, and it is quite possible for a person playing the role of exposed party to also
               become the scoper a role played by another person.  That is to say, once a person has
               become infected, it is possible, perhaps likely, for that person to infect others.
            <br/>  

                        Management of exposures and tracking exposed parties is a key
               function within public health, and within most public health contexts - exposed parties
               are known as &quot;contacts.&quot;
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 4</td> 
          <td>       HLD
            <a name="v3-RoleClass-HLD"> </a> 
          </td> 
          <td> held entity</td> 
          <td> 
                        Entity that is currently in the possession of a holder (scoper),
               who holds, or uses it, usually based on some agreement with the owner.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 4</td> 
          <td>       HLTHCHRT
            <a name="v3-RoleClass-HLTHCHRT"> </a> 
          </td> 
          <td> health chart</td> 
          <td> 
                        The role of a material (player) that is the physical health chart
               belonging to an organization (scoper).
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 4</td> 
          <td>       IDENT
            <a name="v3-RoleClass-IDENT"> </a> 
          </td> 
          <td> identified entity</td> 
          <td> 
                        A role in which the scoping entity designates an identifier for
               a playing entity.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 4</td> 
          <td>       MANU
            <a name="v3-RoleClass-MANU"> </a> 
          </td> 
          <td> manufactured product</td> 
          <td> 
                        Scoped by the manufacturer
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 5</td> 
          <td>         THER
            <a name="v3-RoleClass-THER"> </a> 
          </td> 
          <td> therapeutic agent</td> 
          <td> 
                        A manufactured material (player) that is used for its therapeutic
               properties.  The manufacturer is the scoper.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 4</td> 
          <td>       MNT
            <a name="v3-RoleClass-MNT"> </a> 
          </td> 
          <td> maintained entity</td> 
          <td> 
                        An entity (player) that is maintained by another entity (scoper).
                This is typical role held by durable equipment. The scoper assumes responsibility for
               proper operation, quality, and safety.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 4</td> 
          <td>       OWN
            <a name="v3-RoleClass-OWN"> </a> 
          </td> 
          <td> owned entity</td> 
          <td> 
                        An Entity (player) for which someone (scoper) is granted by law
               the right to call the material (player) his own.  This entitles the scoper to make decisions
               about the disposition of that material.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 4</td> 
          <td>       RGPR
            <a name="v3-RoleClass-RGPR"> </a> 
          </td> 
          <td> regulated product</td> 
          <td> 
                        A product regulated by some governmentatl orgnization.  The role
               is played by Material and scoped by Organization.
            <br/>  

                        Rationale: To support an entity clone used to identify the NDC
               number for a drug product.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 4</td> 
          <td>       TERR
            <a name="v3-RoleClass-TERR"> </a> 
          </td> 
          <td> territory of authority</td> 
          <td> 
                        Relates a place entity (player) as the region over which the scoper
               (typically an Organization) has certain authority (jurisdiction). For example, the Calgary
               Regional Health Authority (scoper) has authority over the territory &quot;Region 4 of
               Alberta&quot; (player) in matters of health.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 4</td> 
          <td>       USED
            <a name="v3-RoleClass-USED"> </a> 
          </td> 
          <td> used entity</td> 
          <td> 
                        
                           Description:An entity (player) that is used by another entity
               (scoper)
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 4</td> 
          <td>       WRTE
            <a name="v3-RoleClass-WRTE"> </a> 
          </td> 
          <td> warranted product</td> 
          <td> 
                        A role a product plays when a guarantee is given to the purchaser
               by the seller (scoping entity) stating that the product is reliable and free from known
               defects and that the seller will repair or replace defective parts within a given time
               limit and under certain conditions.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 2</td> 
          <td>   
            <span style="color: grey">
              <i> (_RoleClassOntological)</i> 
            </span>  
            <b> 
              <i> Abstract</i> 
            </b> 
          </td> 
          <td> 
            <a name="v3-RoleClass-_RoleClassOntological"> </a> 
          </td> 
          <td> 
                        A relationship in which the scoping Entity defines or specifies
               what the playing Entity is.  Thus, the player's &quot;being&quot; (Greek: ontos) is specified.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 3</td> 
          <td>     EQUIV
            <a name="v3-RoleClass-EQUIV"> </a> 
          </td> 
          <td> equivalent entity</td> 
          <td> 
                        
                           Description: Specifies the player Entity (the equivalent Entity)
               as an Entity that is considered to be equivalent to a reference Entity (scoper).  The
               equivalence is in principle a symmetric relationship, however, it is expected that the
               scoper is a reference entity which serves as reference entity for multiple different equivalent
               entities. 
            <br/>  

                        
                           Examples: An innovator's medicine formulation is the reference
               for &quot;generics&quot;, i.e., formulations manufactured differently but having been
               proven to be biologically equivalent to the reference medicine. Another example is a reference
               ingredient that serves as basis for quantity specifications (basis of strength, e.g.,
               metoprolol succinate specified in terms of metoprolol tartrate.)
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 4</td> 
          <td>       SAME
            <a name="v3-RoleClass-SAME"> </a> 
          </td> 
          <td> same</td> 
          <td> 
                        The &quot;same&quot; role asserts an identity between playing
               and scoping entities, i.e., that they are in fact two records of the same entity instance,
               and, in the case of discrepancies (e.g different DOB, gender), that one or both are in
               error.
            <br/>  

                        
                           Usage:
                        
            <br/>  

                        playing and scoping entities must have same classCode, but need
               not have identical attributes or values.
            <br/>  

                        
                           Example: 
                        
            <br/>  

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

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 4</td> 
          <td>       SUBY
            <a name="v3-RoleClass-SUBY"> </a> 
          </td> 
          <td> subsumed by</td> 
          <td> 
                        Relates a prevailing record of an Entity (scoper) with another
               record (player) that it subsumes.
            <br/>  

                        
                           Examples: Show a correct new Person object (scoper) that subsumes
               one or more duplicate Person objects that had accidentally been created for the same physical
               person.
            <br/>  

                        
                           Constraints: Both the player and scoper must have the same
               classCode.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 3</td> 
          <td>     GEN
            <a name="v3-RoleClass-GEN"> </a> 
          </td> 
          <td> has generalization</td> 
          <td> 
                        Relates a specialized material concept (player) to its generalization
               (scoper).
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 4</td> 
          <td>       GRIC
            <a name="v3-RoleClass-GRIC"> </a> 
          </td> 
          <td> has generic</td> 
          <td> 
                        A special link between pharmaceuticals indicating that the target
               (scoper) is a generic for the source (player).
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 3</td> 
          <td>     INST
            <a name="v3-RoleClass-INST"> </a> 
          </td> 
          <td> instance</td> 
          <td> 
                        An individual piece of material (player) instantiating a class
               of material (scoper).
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr style="background: #EFEFEF">
          <td> 3</td> 
          <td>     SUBS
            <a name="v3-RoleClass-SUBS"> </a>  
            <b> 
              <i> Deprecated</i> 
            </b> 
          </td> 
          <td> subsumer</td> 
          <td> 
                        An entity that subsumes the identity of another.  Used in the
               context of merging documented entity instances. Both the player and scoper must have the
               same classCode.
            <br/>  

                        The use of this code is deprecated in favor of the term SUBY which
               is its inverse and is more ontologically correct.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 2</td> 
          <td>   
            <span style="color: grey">
              <i> (_RoleClassPartitive)</i> 
            </span>  
            <b> 
              <i> Abstract</i> 
            </b> 
          </td> 
          <td> 
            <a name="v3-RoleClass-_RoleClassPartitive"> </a> 
          </td> 
          <td> 
                        An association between two Entities where the playing Entity is
               considered in some way &quot;part&quot; of the scoping Entity, e.g., as a member, component,
               ingredient, or content. Being &quot;part&quot; in the broadest sense of the word can mean
               anything from being an integral structural component to a mere incidental temporary association
               of a playing Entity with a (generally larger) scoping Entity.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 3</td> 
          <td>     CONT
            <a name="v3-RoleClass-CONT"> </a> 
          </td> 
          <td> content</td> 
          <td> 
                        Relates a material as the content (player) to a container (scoper).
                Unlike ingredients, the content and a container remain separate (not mixed) and the content
               can be removed from the container.  A content is not part of an empty container.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 3</td> 
          <td>     EXPAGTCAR
            <a name="v3-RoleClass-EXPAGTCAR"> </a> 
          </td> 
          <td> exposure agent carrier</td> 
          <td> 
                        An exposure agent carrier is an entity that is capable of conveying
               an exposure agent from one entity to another.  The scoper of the role must be the exposure
               agent (e.g., pathogen).
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 4</td> 
          <td>       EXPVECTOR
            <a name="v3-RoleClass-EXPVECTOR"> </a> 
          </td> 
          <td> exposure vector</td> 
          <td> 
                        
                           Description: A vector is a living subject that carries an exposure
               agent.  The vector does not cause the disease itself, but exposes targets to the exposure
               agent.  A mosquito carrying malaria is an example of a vector.  The scoper of the role
               must be the exposure agent (e.g., pathogen).
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 4</td> 
          <td>       FOMITE
            <a name="v3-RoleClass-FOMITE"> </a> 
          </td> 
          <td> fomite</td> 
          <td> 
                        
                           Description: A fomite is a non-living entity that is capable
               of conveying exposure agent from one entity to another.  A doorknob contaminated with
               a Norovirus is an example of a fomite.  Anyone touching the doorknob would be exposed
               to the virus.  The scoper of the role must be the exposure agent (e.g., pathogen).
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 3</td> 
          <td>     INGR
            <a name="v3-RoleClass-INGR"> </a> 
          </td> 
          <td> ingredient</td> 
          <td> 
                        Relates a component (player) to a mixture (scoper). E.g., Glucose
               and Water are ingredients of D5W, latex may be an ingredient in a tracheal tube.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 4</td> 
          <td>       ACTI
            <a name="v3-RoleClass-ACTI"> </a> 
          </td> 
          <td> active ingredient</td> 
          <td> 
                        
                           Definition: a therapeutically active ingredient (player) in
               a mixture (scoper), where the mixture is typically a manufactured pharmaceutical.  It
               is unknown if the quantity of such an ingredient is expressed precisely in terms of the
               playing ingredient substance, or, if it is specified in terms of a closely related substance
               (active moiety or reference substance).
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 5</td> 
          <td>         ACTIB
            <a name="v3-RoleClass-ACTIB"> </a> 
          </td> 
          <td> active ingredient - basis of strength</td> 
          <td> 
                        
                           Description:  Active ingredient, where the ingredient substance
               (player) is itself the &quot;basis of strength&quot;, i.e., where the Role.quantity specifies
               exactly the quantity of the player substance in the medicine formulation. 
            <br/>  

                        
                           Examples: Lopressor 50 mg actually contains 50 mg of metoprolol
               succinate, even though the active moiety is metoprolol,  but also: Tenormin 50 mg contain
               50 mg of atenolol, as free base, i.e., where the active ingredient atenolol is also the
               active moiety.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 5</td> 
          <td>         ACTIM
            <a name="v3-RoleClass-ACTIM"> </a> 
          </td> 
          <td> active ingredient - moiety is basis of strength</td> 
          <td> 
                        
                           Description: Active ingredient, where not the ingredient substance
               (player), but itaTMs active moiety is the &quot;basis of strength&quot;, i.e., where the
               Role.quantity specifies the quantity of the player substance's active moiety in the medicine
               formulation.
            <br/>  

                        
                           Examples: 1 mL of Betopic 5mg/mL eye drops contains 5.6 mg
               betaxolol hydrochloride equivalent to betaxolol base 5 mg.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 5</td> 
          <td>         ACTIR
            <a name="v3-RoleClass-ACTIR"> </a> 
          </td> 
          <td> active ingredient - reference substance is basis of strength</td> 
          <td> 
                        
                           Description: Active ingredient, where not the ingredient substance
               (player) but another reference substance with the same active moiety, is the &quot;basis
               of strength&quot;, i.e., where the Role.quantity specifies the quantity of a reference
               substance, similar but different from the player substance's in the medicine formulation.
            <br/>  

                        
                           Examples: Toprol-XL 50 mg contains 47.5 mg of metoprolol succinate
               equivalent to 50 mg of metoprolol tartrate.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 4</td> 
          <td>       ADJV
            <a name="v3-RoleClass-ADJV"> </a> 
          </td> 
          <td> adjuvant</td> 
          <td> 
                        A component (player) added to enhance the action of an active
               ingredient (scoper) (in the manner of a catalyst) but which has no active effect in and
               of itself.  Such ingredients are significant in defining equivalence of products in a
               way that inactive ingredients are not.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 4</td> 
          <td>       ADTV
            <a name="v3-RoleClass-ADTV"> </a> 
          </td> 
          <td> additive</td> 
          <td> 
                        An ingredient (player)  that is added to a base (scoper), that
               amounts to a minor part of the overall mixture.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 4</td> 
          <td>       BASE
            <a name="v3-RoleClass-BASE"> </a> 
          </td> 
          <td> base</td> 
          <td> 
                        A base ingredient (player) is what comprises the major part of
               a mixture (scoper). E.g., Water in most i.v. solutions, or Vaseline in salves. Among all
               ingredients of a material, there should be only one base. A base substance can, in turn,
               be a mixture.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 4</td> 
          <td>       CNTM
            <a name="v3-RoleClass-CNTM"> </a> 
          </td> 
          <td> contaminant ingredient</td> 
          <td> 
                        An ingredient whose presence is not intended but may not be reasonably
               avoided given the circumstances of the mixture's nature or origin.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 4</td> 
          <td>       IACT
            <a name="v3-RoleClass-IACT"> </a> 
          </td> 
          <td> inactive ingredient</td> 
          <td> 
                        An ingredient which is not considered therapeutically active,
               e.g., colors, flavors, stabilizers, or preservatives, fillers, or structural components
               added to an active ingredient in order to facilitate administration of the active ingredient
               but without being considered therapeutically active. An inactive ingredient need not be
               biologically inert, e.g., might be active as an allergen or might have a pleasant taste,
               but is not an essential constituent delivering the therapeutic effect.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 5</td> 
          <td>         COLR
            <a name="v3-RoleClass-COLR"> </a> 
          </td> 
          <td> color additive</td> 
          <td> 
                        A substance (player) influencing the optical aspect of material
               (scoper).
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 5</td> 
          <td>         FLVR
            <a name="v3-RoleClass-FLVR"> </a> 
          </td> 
          <td> flavor additive</td> 
          <td> 
                        A substance (player) added to a mixture (scoper) to make it taste
               a certain way.  In food the use is obvious, in pharmaceuticals flavors can hide disgusting
               taste of the active ingredient (important in pediatric treatments).
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 5</td> 
          <td>         PRSV
            <a name="v3-RoleClass-PRSV"> </a> 
          </td> 
          <td> preservative</td> 
          <td> 
                        A substance (player) added to a mixture (scoper) to prevent microorganisms
               (fungi, bacteria) to spoil the mixture.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 5</td> 
          <td>         STBL
            <a name="v3-RoleClass-STBL"> </a> 
          </td> 
          <td> stabilizer</td> 
          <td> 
                        A stabilizer (player) added to a mixture (scoper) in order to
               prevent the molecular disintegration of the main substance.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 4</td> 
          <td>       MECH
            <a name="v3-RoleClass-MECH"> </a> 
          </td> 
          <td> mechanical ingredient</td> 
          <td> 
                        An ingredient (player) of a medication (scoper) that is inseparable
               from the active ingredients, but has no intended chemical or pharmaceutical effect itself,
               but which may have some systemic effect on the patient.
            <br/>  

                        An example is a collagen matrix used as a base for transplanting
               skin cells.  The collagen matrix can be left permanently in the graft site.  Because it
               is of bovine origin, the patient may exhibit allergies or may have cultural objections
               to its use.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 3</td> 
          <td>     LOCE
            <a name="v3-RoleClass-LOCE"> </a> 
          </td> 
          <td> located entity</td> 
          <td> 
                        Relates an entity (player) to a location (scoper) at which it
               is present in some way. This presence may be limited in time.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 4</td> 
          <td>       STOR
            <a name="v3-RoleClass-STOR"> </a> 
          </td> 
          <td> stored entity</td> 
          <td> 
                        Relates an entity (player) (e.g. a device) to a location (scoper)
               at which it is normally found or stored when not used.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 3</td> 
          <td>     MBR
            <a name="v3-RoleClass-MBR"> </a> 
          </td> 
          <td> member</td> 
          <td> 
                        A role played by an entity that is a member of a group.  The group
               provides the scope for this role.
            <br/>  

                        Among other uses, groups as used in insurance (groups of covered
               individuals) and in scheduling where resources may be grouped for scheduling and logistical
               purposes.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 3</td> 
          <td>     PART
            <a name="v3-RoleClass-PART"> </a> 
          </td> 
          <td> part</td> 
          <td> 
                        
                           Definition:  an association between two Entities where the
               playing Entity (the part) is a component of the whole (scoper) in the sense of an integral
               structural component, that is distinct from other parts in the same whole, has a distinct
               function in the whole, and, as an effect, the full integrity of the whole depends (to
               some degree) on the presence of this part, even though the part may often be separable
               from the whole.
            <br/>  

                        
                           Discussion: Part is defined in opposition to (a) ingredient
               (not separable), (b) content (not a functional component), and (c) member (not functionally
               distinct from other members).
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 4</td> 
          <td>       ACTM
            <a name="v3-RoleClass-ACTM"> </a> 
          </td> 
          <td> active moiety</td> 
          <td> 
                        The molecule or ion that is responsible for the intended pharmacological
               action of the drug substance, excluding those appended or associated parts of the molecule
               that make the molecule an ester, salt (including a salt with hydrogen or coordination
               bonds), or other noncovalent derivative (such as a complex, chelate, or clathrate).
            <br/>  

                        Examples: heparin-sodium and heparin-potassium have the same active
               moiety, heparin; the active moiety of morphine-hydrochloride is morphine.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 3</td> 
          <td>     SPEC
            <a name="v3-RoleClass-SPEC"> </a> 
          </td> 
          <td> specimen</td> 
          <td> 
                        A role played by a material entity that is a specimen for an act.
               It is scoped by the source of the specimen.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 4</td> 
          <td>       ALQT
            <a name="v3-RoleClass-ALQT"> </a> 
          </td> 
          <td> aliquot</td> 
          <td> 
                        A portion (player) of an original or source specimen (scoper)
               used for testing or transportation.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 4</td> 
          <td>       ISLT
            <a name="v3-RoleClass-ISLT"> </a> 
          </td> 
          <td> isolate</td> 
          <td> 
                        A microorganism that has been isolated from other microorganisms
               or a source matrix.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 1</td> 
          <td> CHILD
            <a name="v3-RoleClass-CHILD"> </a> 
          </td> 
          <td> child</td> 
          <td> 
                        The player of the role is a child of the scoping entity, in a
               generic sense.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 1</td> 
          <td> CRED
            <a name="v3-RoleClass-CRED"> </a> 
          </td> 
          <td> credentialed entity</td> 
          <td> 
                        A role played by an entity that receives credentials from the
               scoping entity.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 1</td> 
          <td> NURPRAC
            <a name="v3-RoleClass-NURPRAC"> </a> 
          </td> 
          <td> nurse practitioner</td> 
          <td/>  
        </tr> 
 
        <tr> 
          <td> 1</td> 
          <td> NURS
            <a name="v3-RoleClass-NURS"> </a> 
          </td> 
          <td> nurse</td> 
          <td/>  
        </tr> 
 
        <tr> 
          <td> 1</td> 
          <td> PA
            <a name="v3-RoleClass-PA"> </a> 
          </td> 
          <td> physician assistant</td> 
          <td/>  
        </tr> 
 
        <tr> 
          <td> 1</td> 
          <td> PHYS
            <a name="v3-RoleClass-PHYS"> </a> 
          </td> 
          <td> physician</td> 
          <td/>  
        </tr> 

      </table> 

    </div> 
  </text> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
    <valueCode value="external"/> 
  </extension> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="0"/> 
  </extension> 
  <url value="http://terminology.hl7.org/CodeSystem/v3-RoleClass"/> 
  <identifier> 
    <system value="urn:ietf:rfc:3986"/> 
    <value value="urn:oid:2.16.840.1.113883.5.110"/> 
  </identifier> 
  <version value="2019-07-31"/> 
  <name value="v3.RoleClass"/> 
  <title value="v3 Code System RoleClass"/> 
  <status value="active"/> 
  <experimental value="false"/> 
  <date value="2019-07-31T00:00:00+00:00"/> 
  <publisher value="HL7, Inc"/> 
  <contact> 
    <telecom> 
      <system value="url"/> 
      <value value="http://hl7.org"/> 
    </telecom> 
  </contact> 
  <description value=" Codes for the Role class hierarchy.  The values in this hierarchy, represent a Role which
     is an association or relationship between two entities - the entity that plays the role
     and the entity that scopes the role.  Roles names are derived from the name of the playing
     entity in that role. The role hierarchy stems from three core concepts, or abstract domains:
        RoleClassOntological
is an abstract domain that collects roles in which the playing entity is defined or specified
     by the scoping entity.   RoleClassPartitive
collects roles in which the playing entity is in some sense a &quot;part&quot; of the
     scoping entity.   RoleClassAssociative
collects all of the remaining forms of association between the playing entity and the
     scoping entity. This set of roles is further partitioned between:    RoleClassPassive
which are roles in which the playing entity is used, known, treated, handled, built, or
     destroyed, etc. under the auspices of the scoping entity. The playing entity is passive
     in these roles in that the role exists without an agreement from the playing entity. 
      RoleClassMutualRelationship
which are relationships based on mutual behavior of the two entities. The basis of these
     relationship may be formal agreements or they may bede facto
behavior.  Thus, this sub-domain is further divided into:    RoleClassRelationshipFormal
in which the relationship is formally defined, frequently by a contract or agreement.
       Personal relationship
which inks two people in a personal relationship. The hierarchy discussed above is represented
     In the current vocabulary tables as a set of abstract domains, with the exception of the
      &quot;Personal relationship&quot; which is a leaf concept.  OpenIssue:
Description copied from Concept Domain of same name.  Must be verified."/> 
  <caseSensitive value="true"/> 
  <valueSet value="http://terminology.hl7.org/ValueSet/v3-RoleClass"/> 
  <hierarchyMeaning value="is-a"/> 
  <content value="complete"/> 
  <property> 
    <code value="notSelectable"/> 
    <uri value="http://hl7.org/fhir/concept-properties#notSelectable"/> 
    <description value="Indicates that the code is abstract - only intended to be used as a selector for other
       concepts"/> 
    <type value="boolean"/> 
  </property> 
  <property> 
    <code value="status"/> 
    <uri value="http://hl7.org/fhir/concept-properties#status"/> 
    <description value="A property that indicates the status of the concept. One of active, experimental, deprecated,
       retired"/> 
    <type value="code"/> 
  </property> 
  <property> 
    <code value="deprecationDate"/> 
    <uri value="http://hl7.org/fhir/concept-properties#deprecationDate"/> 
    <description value="The date at which a concept was deprecated. Concepts that are deprecated but not inactive
       can still be used, but their use is discouraged"/> 
    <type value="dateTime"/> 
  </property> 
  <concept> 
    <code value="ROL"/> 
    <display value="role"/> 
    <definition value="Corresponds to the Role class"/> 
    <concept> 
      <code value="_RoleClassAssociative"/> 
      <display value="RoleClassAssociative"/> 
      <definition value="A general association between two entities that is neither partitive nor ontological."/> 
      <property> 
        <code value="notSelectable"/> 
        <valueBoolean value="true"/> 
      </property> 
      <concept> 
        <code value="_RoleClassMutualRelationship"/> 
        <display value="RoleClassMutualRelationship"/> 
        <definition value="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)."/> 
        <property> 
          <code value="notSelectable"/> 
          <valueBoolean value="true"/> 
        </property> 
        <concept> 
          <code value="_RoleClassRelationshipFormal"/> 
          <display value="RoleClassRelationshipFormal"/> 
          <definition value="A relationship between two entities that is formally recognized, frequently by a contract
             or similar agreement."/> 
          <property> 
            <code value="notSelectable"/> 
            <valueBoolean value="true"/> 
          </property> 
          <concept> 
            <code value="AFFL"/> 
            <display value="affiliate"/> 
            <definition value="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."/> 
          </concept> 
          <concept> 
            <code value="AGNT"/> 
            <display value="agent"/> 
            <definition value="An entity (player) that acts or is authorized to act on behalf of another entity (scoper)."/> 
            <concept> 
              <code value="ASSIGNED"/> 
              <display value="assigned entity"/> 
              <definition value="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."/> 
              <concept> 
                <code value="COMPAR"/> 
                <display value="commissioning party"/> 
                <definition value="An Entity that is authorized to issue or instantiate permissions, privileges, credentials
                   or other formal/legal authorizations."/> 
              </concept> 
              <concept> 
                <code value="SGNOFF"/> 
                <display value="signing authority or officer"/> 
                <definition value="The role of a person (player) who is the officer or signature authority for of a scoping
                   entity, usually an organization (scoper)."/> 
              </concept> 
            </concept> 
            <concept> 
              <code value="CON"/> 
              <display value="contact"/> 
              <definition value="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."/> 
              <concept> 
                <code value="ECON"/> 
                <display value="emergency contact"/> 
                <definition value="An entity to be contacted in the event of an emergency."/> 
              </concept> 
              <concept> 
                <code value="NOK"/> 
                <display value="next of kin"/> 
                <definition value="An individual designated for notification as the next of kin for a given entity."/> 
              </concept> 
            </concept> 
            <concept> 
              <code value="GUARD"/> 
              <display value="guardian"/> 
              <definition value="Guardian of a ward"/> 
            </concept> 
          </concept> 
          <concept> 
            <code value="CIT"/> 
            <display value="citizen"/> 
            <definition value="Citizen of apolitical entity"/> 
          </concept> 
          <concept> 
            <code value="COVPTY"/> 
            <display value="covered party"/> 
            <definition value="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."/> 
            <concept> 
              <code value="CLAIM"/> 
              <display value="claimant"/> 
              <definition value="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
                 &quot;claim&quot; 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."/> 
            </concept> 
            <concept> 
              <code value="NAMED"/> 
              <display value="named insured"/> 
              <definition value="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."/> 
              <concept> 
                <code value="DEPEN"/> 
                <display value="dependent"/> 
                <definition value="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."/> 
              </concept> 
              <concept> 
                <code value="INDIV"/> 
                <display value="individual"/> 
                <definition value="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."/> 
              </concept> 
              <concept> 
                <code value="SUBSCR"/> 
                <display value="subscriber"/> 
                <definition value="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."/> 
              </concept> 
            </concept> 
            <concept> 
              <code value="PROG"/> 
              <display value="program eligible"/> 
              <definition value="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 &quot;claim&quot; 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."/> 
            </concept> 
          </concept> 
          <concept> 
            <code value="CRINV"/> 
            <display value="clinical research investigator"/> 
            <definition value="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."/> 
          </concept> 
          <concept> 
            <code value="CRSPNSR"/> 
            <display value="clinical research sponsor"/> 
            <definition value="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."/> 
          </concept> 
          <concept> 
            <code value="EMP"/> 
            <display value="employee"/> 
            <definition value="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.)"/> 
            <concept> 
              <code value="MIL"/> 
              <display value="military person"/> 
              <definition value="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.)"/> 
            </concept> 
          </concept> 
          <concept> 
            <code value="GUAR"/> 
            <display value="guarantor"/> 
            <definition value="A person or organization (player) that serves as a financial guarantor for another person
               or organization (scoper)."/> 
          </concept> 
          <concept> 
            <code value="INVSBJ"/> 
            <display value="Investigation Subject"/> 
            <definition value="An entity that is the subject of an investigation. This role is scoped by the party responsible
               for the investigation."/> 
            <concept> 
              <code value="CASEBJ"/> 
              <display value="Case Subject"/> 
              <definition value="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)"/> 
            </concept> 
            <concept> 
              <code value="RESBJ"/> 
              <display value="research subject"/> 
              <definition value="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."/> 
            </concept> 
          </concept> 
          <concept> 
            <code value="LIC"/> 
            <display value="licensed entity"/> 
            <definition value="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)."/> 
            <concept> 
              <code value="NOT"/> 
              <display value="notary public"/> 
              <definition value="notary public"/> 
            </concept> 
            <concept> 
              <code value="PROV"/> 
              <display value="healthcare provider"/> 
              <definition value="An Entity (player) that is authorized to provide health care services by some authorizing
                 agency (scoper)."/> 
            </concept> 
          </concept> 
          <concept> 
            <code value="PAT"/> 
            <display value="patient"/> 
            <definition value="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."/> 
          </concept> 
          <concept> 
            <code value="PAYEE"/> 
            <display value="payee"/> 
            <definition value="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."/> 
          </concept> 
          <concept> 
            <code value="PAYOR"/> 
            <display value="invoice payor"/> 
            <definition value="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."/> 
          </concept> 
          <concept> 
            <code value="POLHOLD"/> 
            <display value="policy holder"/> 
            <definition value="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."/> 
          </concept> 
          <concept> 
            <code value="QUAL"/> 
            <display value="qualified entity"/> 
            <definition value="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."/> 
          </concept> 
          <concept> 
            <code value="SPNSR"/> 
            <display value="coverage sponsor"/> 
            <definition value="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 

                        
                           
                              a policy holder of the plan;

                           
                           
                              where the sponsor is the policy holder, who may become a
               subscriber or a dependent to a policy under the plan; or

                           
                           
                              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."/> 
          </concept> 
          <concept> 
            <code value="STD"/> 
            <display value="student"/> 
            <definition value="A role played by an individual who is a student of a school, which is the scoping entity."/> 
          </concept> 
          <concept> 
            <code value="UNDWRT"/> 
            <display value="underwriter"/> 
            <definition value="A role played by a person or an organization.  It is the party that 

                        
                           
                              accepts fiscal responsibility for insurance plans and the
               policies created under those plans;

                           
                           
                              administers and accepts fiscal responsibility for a program
               that provides coverage for services to eligible individuals; and/or

                           
                           
                              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:
                        

                        
                           
                              A health insurer; 

                           
                           
                              Medicaid Program;

                           
                           
                              Lloyd's of London"/> 
          </concept> 
        </concept> 
        <concept> 
          <code value="CAREGIVER"/> 
          <display value="caregiver"/> 
          <definition value="A person responsible for the primary care of a patient at home."/> 
        </concept> 
        <concept> 
          <code value="PRS"/> 
          <display value="personal relationship"/> 
          <definition value="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."/> 
        </concept> 
        <concept> 
          <code value="SELF"/> 
          <display value="self"/> 
          <definition value="The &quot;same&quot; 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."/> 
          <property> 
            <code value="status"/> 
            <valueCode value="retired"/> 
          </property> 
        </concept> 
      </concept> 
      <concept> 
        <code value="_RoleClassPassive"/> 
        <display value="RoleClassPassive"/> 
        <definition value="An association for a playing Entity that is used, known, treated, handled, built, or destroyed,
           etc. under the auspices of the scoping Entity. The playing Entity is passive in these
           roles (even though it may be active in other roles), in the sense that the kinds of things
           done to it in this role happen without an agreement from the playing Entity."/> 
        <property> 
          <code value="notSelectable"/> 
          <valueBoolean value="true"/> 
        </property> 
        <concept> 
          <code value="ACCESS"/> 
          <display value="access"/> 
          <definition value="A role in which the playing entity (material) provides access to another entity. The principal
             use case is intravenous (or other bodily) access lines that preexist and need to be referred
             to for medication routing instructions."/> 
        </concept> 
        <concept> 
          <code value="ADJY"/> 
          <display value="adjacency"/> 
          <definition value="A physical association whereby two Entities are in some (even lose) spatial relationship
             with each other such that they touch each other in some way.

                        
                           Examples: the colon is connected (and therefore adjacent) to
             the jejunum; the colon is adjacent to the liver (even if not actually connected.)

                        
                           UsageConstraints: Adjacency is in principle a symmetrical connection,
             but scoper and player of the role should, where applicable, be assigned to have scoper
             be the larger, more central Entity and player the smaller, more distant, appendage."/> 
          <concept> 
            <code value="CONC"/> 
            <display value="connection"/> 
            <definition value="An adjacency of two Entities held together by a bond which attaches to each of the two
               entities. 

                        
                           Examples: biceps brachii muscle connected to the radius bone,
               port 3 on a network switch connected to port 5 on a patch panel.

                        
                           UsageConstraints: See Adjacency for the assignment of scoper
               (larger, more central) and player (smaller, more distant)."/> 
            <concept> 
              <code value="BOND"/> 
              <display value="molecular bond"/> 
              <definition value="A connection between two atoms of a molecule.

                        
                           Examples: double bond between first and second C in ethane,
                 peptide bond between two amino-acid, disulfide bridge between two proteins, chelate and
                 ion associations, even the much weaker van-der-Waals bonds can be considered molecular
                 bonds.

                        
                           UsageConstraints: See connection and adjacency for the assignment
                 of player and scoper."/> 
            </concept> 
            <concept> 
              <code value="CONY"/> 
              <display value="continuity"/> 
              <definition value="A connection between two regional parts.

                        
                           Examples:  the connection between ascending aorta and the aortic
                 arc, connection between descending colon and sigmoid.

                        
                           UsageConstraints: See connection and adjacency for the assignment
                 of player and scoper."/> 
            </concept> 
          </concept> 
        </concept> 
        <concept> 
          <code value="ADMM"/> 
          <display value="Administerable Material"/> 
          <definition value="A material (player) that can be administered to an Entity (scoper)."/> 
        </concept> 
        <concept> 
          <code value="BIRTHPL"/> 
          <display value="birthplace"/> 
          <definition value="Relates a place (playing Entity) as the location where a living subject (scoping Entity)
             was born."/> 
        </concept> 
        <concept> 
          <code value="DEATHPLC"/> 
          <display value="place of death"/> 
          <definition value="Definition: Relates a place (playing Entity) as the location where a living subject (scoping
             Entity) died."/> 
        </concept> 
        <concept> 
          <code value="DST"/> 
          <display value="distributed material"/> 
          <definition value="A material (player) distributed by a distributor (scoper) who functions between a manufacturer
             and a buyer or retailer."/> 
          <concept> 
            <code value="RET"/> 
            <display value="retailed material"/> 
            <definition value="Material (player) sold by a retailer (scoper), who also give advice to prospective buyers."/> 
          </concept> 
        </concept> 
        <concept> 
          <code value="EXLOC"/> 
          <display value="event location"/> 
          <definition value="A role played by a place at which the location of an event may be recorded."/> 
          <concept> 
            <code value="SDLOC"/> 
            <display value="service delivery location"/> 
            <definition value="A role played by a place at which services may be provided."/> 
            <concept> 
              <code value="DSDLOC"/> 
              <display value="dedicated service delivery location"/> 
              <definition value="A role of a place (player) that is intended to house the provision of services. Scoper
                 is the Entity (typically Organization) that provides these services. This is not synonymous
                 with &quot;ownership.&quot;"/> 
            </concept> 
            <concept> 
              <code value="ISDLOC"/> 
              <display value="incidental service delivery location"/> 
              <definition value="A role played by a place at which health care services may be provided without prior designation
                 or authorization."/> 
            </concept> 
          </concept> 
        </concept> 
        <concept> 
          <code value="EXPR"/> 
          <display value="exposed entity"/> 
          <definition value="A role played by an entity that has been exposed to a person or animal suffering a contagious
             disease, or with a location from which a toxin has been distributed.  The player of the
             role is normally a person or animal, but it is possible that other entity types could
             become exposed.  The role is scoped by the source of the exposure, and it is quite possible
             for a person playing the role of exposed party to also become the scoper a role played
             by another person.  That is to say, once a person has become infected, it is possible,
             perhaps likely, for that person to infect others.

                        Management of exposures and tracking exposed parties is a key
             function within public health, and within most public health contexts - exposed parties
             are known as &quot;contacts.&quot;"/> 
        </concept> 
        <concept> 
          <code value="HLD"/> 
          <display value="held entity"/> 
          <definition value="Entity that is currently in the possession of a holder (scoper), who holds, or uses it,
             usually based on some agreement with the owner."/> 
        </concept> 
        <concept> 
          <code value="HLTHCHRT"/> 
          <display value="health chart"/> 
          <definition value="The role of a material (player) that is the physical health chart belonging to an organization
             (scoper)."/> 
        </concept> 
        <concept> 
          <code value="IDENT"/> 
          <display value="identified entity"/> 
          <definition value="A role in which the scoping entity designates an identifier for a playing entity."/> 
        </concept> 
        <concept> 
          <code value="MANU"/> 
          <display value="manufactured product"/> 
          <definition value="Scoped by the manufacturer"/> 
          <concept> 
            <code value="THER"/> 
            <display value="therapeutic agent"/> 
            <definition value="A manufactured material (player) that is used for its therapeutic properties.  The manufacturer
               is the scoper."/> 
          </concept> 
        </concept> 
        <concept> 
          <code value="MNT"/> 
          <display value="maintained entity"/> 
          <definition value="An entity (player) that is maintained by another entity (scoper).  This is typical role
             held by durable equipment. The scoper assumes responsibility for proper operation, quality,
             and safety."/> 
        </concept> 
        <concept> 
          <code value="OWN"/> 
          <display value="owned entity"/> 
          <definition value="An Entity (player) for which someone (scoper) is granted by law the right to call the
             material (player) his own.  This entitles the scoper to make decisions about the disposition
             of that material."/> 
        </concept> 
        <concept> 
          <code value="RGPR"/> 
          <display value="regulated product"/> 
          <definition value="A product regulated by some governmentatl orgnization.  The role is played by Material
             and scoped by Organization.

                        Rationale: To support an entity clone used to identify the NDC
             number for a drug product."/> 
        </concept> 
        <concept> 
          <code value="TERR"/> 
          <display value="territory of authority"/> 
          <definition value="Relates a place entity (player) as the region over which the scoper (typically an Organization)
             has certain authority (jurisdiction). For example, the Calgary Regional Health Authority
             (scoper) has authority over the territory &quot;Region 4 of Alberta&quot; (player) in
             matters of health."/> 
        </concept> 
        <concept> 
          <code value="USED"/> 
          <display value="used entity"/> 
          <definition value="Description:An entity (player) that is used by another entity (scoper)"/> 
        </concept> 
        <concept> 
          <code value="WRTE"/> 
          <display value="warranted product"/> 
          <definition value="A role a product plays when a guarantee is given to the purchaser by the seller (scoping
             entity) stating that the product is reliable and free from known defects and that the
             seller will repair or replace defective parts within a given time limit and under certain
             conditions."/> 
        </concept> 
      </concept> 
    </concept> 
    <concept> 
      <code value="_RoleClassOntological"/> 
      <display value="RoleClassOntological"/> 
      <definition value="A relationship in which the scoping Entity defines or specifies what the playing Entity
         is.  Thus, the player's &quot;being&quot; (Greek: ontos) is specified."/> 
      <property> 
        <code value="notSelectable"/> 
        <valueBoolean value="true"/> 
      </property> 
      <concept> 
        <code value="EQUIV"/> 
        <display value="equivalent entity"/> 
        <definition value="Description: Specifies the player Entity (the equivalent Entity) as an Entity that is
           considered to be equivalent to a reference Entity (scoper).  The equivalence is in principle
           a symmetric relationship, however, it is expected that the scoper is a reference entity
           which serves as reference entity for multiple different equivalent entities. 

                        
                           Examples: An innovator's medicine formulation is the reference
           for &quot;generics&quot;, i.e., formulations manufactured differently but having been
           proven to be biologically equivalent to the reference medicine. Another example is a reference
           ingredient that serves as basis for quantity specifications (basis of strength, e.g.,
           metoprolol succinate specified in terms of metoprolol tartrate.)"/> 
        <concept> 
          <code value="SAME"/> 
          <display value="same"/> 
          <definition value="The &quot;same&quot; role asserts an identity between playing and scoping entities, i.e.,
             that they are in fact two records of the same entity instance, 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."/> 
        </concept> 
        <concept> 
          <code value="SUBY"/> 
          <display value="subsumed by"/> 
          <definition value="Relates a prevailing record of an Entity (scoper) with another record (player) that it
             subsumes.

                        
                           Examples: Show a correct new Person object (scoper) that subsumes
             one or more duplicate Person objects that had accidentally been created for the same physical
             person.

                        
                           Constraints: Both the player and scoper must have the same
             classCode."/> 
        </concept> 
      </concept> 
      <concept> 
        <code value="GEN"/> 
        <display value="has generalization"/> 
        <definition value="Relates a specialized material concept (player) to its generalization (scoper)."/> 
        <concept> 
          <code value="GRIC"/> 
          <display value="has generic"/> 
          <definition value="A special link between pharmaceuticals indicating that the target (scoper) is a generic
             for the source (player)."/> 
        </concept> 
      </concept> 
      <concept> 
        <code value="INST"/> 
        <display value="instance"/> 
        <definition value="An individual piece of material (player) instantiating a class of material (scoper)."/> 
      </concept> 
      <concept> 
        <code value="SUBS"/> 
        <display value="subsumer"/> 
        <definition value="An entity that subsumes the identity of another.  Used in the context of merging documented
           entity instances. Both the player and scoper must have the same classCode.

                        The use of this code is deprecated in favor of the term SUBY which
           is its inverse and is more ontologically correct."/> 
        <property> 
          <code value="status"/> 
          <valueCode value="retired"/> 
        </property> 
        <property> 
          <code value="deprecationDate"/> 
          <valueDateTime value="2011-12-01"/> 
        </property> 
      </concept> 
    </concept> 
    <concept> 
      <code value="_RoleClassPartitive"/> 
      <display value="RoleClassPartitive"/> 
      <definition value="An association between two Entities where the playing Entity is considered in some way
         &quot;part&quot; of the scoping Entity, e.g., as a member, component, ingredient, or content.
         Being &quot;part&quot; in the broadest sense of the word can mean anything from being
         an integral structural component to a mere incidental temporary association of a playing
         Entity with a (generally larger) scoping Entity."/> 
      <property> 
        <code value="notSelectable"/> 
        <valueBoolean value="true"/> 
      </property> 
      <concept> 
        <code value="CONT"/> 
        <display value="content"/> 
        <definition value="Relates a material as the content (player) to a container (scoper).  Unlike ingredients,
           the content and a container remain separate (not mixed) and the content can be removed
           from the container.  A content is not part of an empty container."/> 
      </concept> 
      <concept> 
        <code value="EXPAGTCAR"/> 
        <display value="exposure agent carrier"/> 
        <definition value="An exposure agent carrier is an entity that is capable of conveying an exposure agent
           from one entity to another.  The scoper of the role must be the exposure agent (e.g.,
           pathogen)."/> 
        <concept> 
          <code value="EXPVECTOR"/> 
          <display value="exposure vector"/> 
          <definition value="Description: A vector is a living subject that carries an exposure agent.  The vector
             does not cause the disease itself, but exposes targets to the exposure agent.  A mosquito
             carrying malaria is an example of a vector.  The scoper of the role must be the exposure
             agent (e.g., pathogen)."/> 
        </concept> 
        <concept> 
          <code value="FOMITE"/> 
          <display value="fomite"/> 
          <definition value="Description: A fomite is a non-living entity that is capable of conveying exposure agent
             from one entity to another.  A doorknob contaminated with a Norovirus is an example of
             a fomite.  Anyone touching the doorknob would be exposed to the virus.  The scoper of
             the role must be the exposure agent (e.g., pathogen)."/> 
        </concept> 
      </concept> 
      <concept> 
        <code value="INGR"/> 
        <display value="ingredient"/> 
        <definition value="Relates a component (player) to a mixture (scoper). E.g., Glucose and Water are ingredients
           of D5W, latex may be an ingredient in a tracheal tube."/> 
        <concept> 
          <code value="ACTI"/> 
          <display value="active ingredient"/> 
          <definition value="Definition: a therapeutically active ingredient (player) in a mixture (scoper), where
             the mixture is typically a manufactured pharmaceutical.  It is unknown if the quantity
             of such an ingredient is expressed precisely in terms of the playing ingredient substance,
             or, if it is specified in terms of a closely related substance (active moiety or reference
             substance)."/> 
          <concept> 
            <code value="ACTIB"/> 
            <display value="active ingredient - basis of strength"/> 
            <definition value="Description:  Active ingredient, where the ingredient substance (player) is itself the
               &quot;basis of strength&quot;, i.e., where the Role.quantity specifies exactly the quantity
               of the player substance in the medicine formulation. 

                        
                           Examples: Lopressor 50 mg actually contains 50 mg of metoprolol
               succinate, even though the active moiety is metoprolol,  but also: Tenormin 50 mg contain
               50 mg of atenolol, as free base, i.e., where the active ingredient atenolol is also the
               active moiety."/> 
          </concept> 
          <concept> 
            <code value="ACTIM"/> 
            <display value="active ingredient - moiety is basis of strength"/> 
            <definition value="Description: Active ingredient, where not the ingredient substance (player), but itaTMs
               active moiety is the &quot;basis of strength&quot;, i.e., where the Role.quantity specifies
               the quantity of the player substance's active moiety in the medicine formulation.

                        
                           Examples: 1 mL of Betopic 5mg/mL eye drops contains 5.6 mg
               betaxolol hydrochloride equivalent to betaxolol base 5 mg."/> 
          </concept> 
          <concept> 
            <code value="ACTIR"/> 
            <display value="active ingredient - reference substance is basis of strength"/> 
            <definition value="Description: Active ingredient, where not the ingredient substance (player) but another
               reference substance with the same active moiety, is the &quot;basis of strength&quot;,
               i.e., where the Role.quantity specifies the quantity of a reference substance, similar
               but different from the player substance's in the medicine formulation.

                        
                           Examples: Toprol-XL 50 mg contains 47.5 mg of metoprolol succinate
               equivalent to 50 mg of metoprolol tartrate."/> 
          </concept> 
        </concept> 
        <concept> 
          <code value="ADJV"/> 
          <display value="adjuvant"/> 
          <definition value="A component (player) added to enhance the action of an active ingredient (scoper) (in
             the manner of a catalyst) but which has no active effect in and of itself.  Such ingredients
             are significant in defining equivalence of products in a way that inactive ingredients
             are not."/> 
        </concept> 
        <concept> 
          <code value="ADTV"/> 
          <display value="additive"/> 
          <definition value="An ingredient (player)  that is added to a base (scoper), that amounts to a minor part
             of the overall mixture."/> 
        </concept> 
        <concept> 
          <code value="BASE"/> 
          <display value="base"/> 
          <definition value="A base ingredient (player) is what comprises the major part of a mixture (scoper). E.g.,
             Water in most i.v. solutions, or Vaseline in salves. Among all ingredients of a material,
             there should be only one base. A base substance can, in turn, be a mixture."/> 
        </concept> 
        <concept> 
          <code value="CNTM"/> 
          <display value="contaminant ingredient"/> 
          <definition value="An ingredient whose presence is not intended but may not be reasonably avoided given the
             circumstances of the mixture's nature or origin."/> 
        </concept> 
        <concept> 
          <code value="IACT"/> 
          <display value="inactive ingredient"/> 
          <definition value="An ingredient which is not considered therapeutically active, e.g., colors, flavors, stabilizers,
             or preservatives, fillers, or structural components added to an active ingredient in order
             to facilitate administration of the active ingredient but without being considered therapeutically
             active. An inactive ingredient need not be biologically inert, e.g., might be active as
             an allergen or might have a pleasant taste, but is not an essential constituent delivering
             the therapeutic effect."/> 
          <concept> 
            <code value="COLR"/> 
            <display value="color additive"/> 
            <definition value="A substance (player) influencing the optical aspect of material (scoper)."/> 
          </concept> 
          <concept> 
            <code value="FLVR"/> 
            <display value="flavor additive"/> 
            <definition value="A substance (player) added to a mixture (scoper) to make it taste a certain way.  In food
               the use is obvious, in pharmaceuticals flavors can hide disgusting taste of the active
               ingredient (important in pediatric treatments)."/> 
          </concept> 
          <concept> 
            <code value="PRSV"/> 
            <display value="preservative"/> 
            <definition value="A substance (player) added to a mixture (scoper) to prevent microorganisms (fungi, bacteria)
               to spoil the mixture."/> 
          </concept> 
          <concept> 
            <code value="STBL"/> 
            <display value="stabilizer"/> 
            <definition value="A stabilizer (player) added to a mixture (scoper) in order to prevent the molecular disintegration
               of the main substance."/> 
          </concept> 
        </concept> 
        <concept> 
          <code value="MECH"/> 
          <display value="mechanical ingredient"/> 
          <definition value="An ingredient (player) of a medication (scoper) that is inseparable from the active ingredients,
             but has no intended chemical or pharmaceutical effect itself, but which may have some
             systemic effect on the patient.

                        An example is a collagen matrix used as a base for transplanting
             skin cells.  The collagen matrix can be left permanently in the graft site.  Because it
             is of bovine origin, the patient may exhibit allergies or may have cultural objections
             to its use."/> 
        </concept> 
      </concept> 
      <concept> 
        <code value="LOCE"/> 
        <display value="located entity"/> 
        <definition value="Relates an entity (player) to a location (scoper) at which it is present in some way.
           This presence may be limited in time."/> 
        <concept> 
          <code value="STOR"/> 
          <display value="stored entity"/> 
          <definition value="Relates an entity (player) (e.g. a device) to a location (scoper) at which it is normally
             found or stored when not used."/> 
        </concept> 
      </concept> 
      <concept> 
        <code value="MBR"/> 
        <display value="member"/> 
        <definition value="A role played by an entity that is a member of a group.  The group provides the scope
           for this role.

                        Among other uses, groups as used in insurance (groups of covered
           individuals) and in scheduling where resources may be grouped for scheduling and logistical
           purposes."/> 
      </concept> 
      <concept> 
        <code value="PART"/> 
        <display value="part"/> 
        <definition value="Definition:  an association between two Entities where the playing Entity (the part) is
           a component of the whole (scoper) in the sense of an integral structural component, that
           is distinct from other parts in the same whole, has a distinct function in the whole,
           and, as an effect, the full integrity of the whole depends (to some degree) on the presence
           of this part, even though the part may often be separable from the whole.

                        
                           Discussion: Part is defined in opposition to (a) ingredient
           (not separable), (b) content (not a functional component), and (c) member (not functionally
           distinct from other members)."/> 
        <concept> 
          <code value="ACTM"/> 
          <display value="active moiety"/> 
          <definition value="The molecule or ion that is responsible for the intended pharmacological action of the
             drug substance, excluding those appended or associated parts of the molecule that make
             the molecule an ester, salt (including a salt with hydrogen or coordination bonds), or
             other noncovalent derivative (such as a complex, chelate, or clathrate).

                        Examples: heparin-sodium and heparin-potassium have the same active
             moiety, heparin; the active moiety of morphine-hydrochloride is morphine."/> 
        </concept> 
      </concept> 
      <concept> 
        <code value="SPEC"/> 
        <display value="specimen"/> 
        <definition value="A role played by a material entity that is a specimen for an act. It is scoped by the
           source of the specimen."/> 
        <concept> 
          <code value="ALQT"/> 
          <display value="aliquot"/> 
          <definition value="A portion (player) of an original or source specimen (scoper) used for testing or transportation."/> 
        </concept> 
        <concept> 
          <code value="ISLT"/> 
          <display value="isolate"/> 
          <definition value="A microorganism that has been isolated from other microorganisms or a source matrix."/> 
        </concept> 
      </concept> 
    </concept> 
  </concept> 
  <concept> 
    <code value="CHILD"/> 
    <display value="child"/> 
    <definition value="The player of the role is a child of the scoping entity, in a generic sense."/> 
    <property> 
      <code value="status"/> 
      <valueCode value="retired"/> 
    </property> 
  </concept> 
  <concept> 
    <code value="CRED"/> 
    <display value="credentialed entity"/> 
    <definition value="A role played by an entity that receives credentials from the scoping entity."/> 
    <property> 
      <code value="status"/> 
      <valueCode value="retired"/> 
    </property> 
  </concept> 
  <concept> 
    <code value="NURPRAC"/> 
    <display value="nurse practitioner"/> 
    <definition value="nurse practitioner"/> 
    <property> 
      <code value="status"/> 
      <valueCode value="retired"/> 
    </property> 
  </concept> 
  <concept> 
    <code value="NURS"/> 
    <display value="nurse"/> 
    <definition value="nurse"/> 
    <property> 
      <code value="status"/> 
      <valueCode value="retired"/> 
    </property> 
  </concept> 
  <concept> 
    <code value="PA"/> 
    <display value="physician assistant"/> 
    <definition value="physician assistant"/> 
    <property> 
      <code value="status"/> 
      <valueCode value="retired"/> 
    </property> 
  </concept> 
  <concept> 
    <code value="PHYS"/> 
    <display value="physician"/> 
    <definition value="physician"/> 
    <property> 
      <code value="status"/> 
      <valueCode value="retired"/> 
    </property> 
  </concept> 
</CodeSystem> 

Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.