@prefix fhir: . @prefix owl: . @prefix rdfs: . @prefix xsd: . # - resource ------------------------------------------------------------------- a fhir:ValueSet; fhir:nodeRole fhir:treeRoot; fhir:Resource.id [ fhir:value "v3-PolicyOrProgramCoverageRoleType"]; fhir:Resource.language [ fhir:value "en"]; fhir:DomainResource.text [ fhir:Narrative.status [ fhir:value "generated" ]; fhir:Narrative.div "

PolicyOrProgramCoverageRoleType

Description: A role recognized through the eligibility of an identified party for benefits covered under an insurance policy or a program based on meeting eligibility criteria.

\n

Eligibility as a covered party may be conditioned on the party meeting criteria to qualify for coverage under a policy or program, which may be mandated by law. These criteria may be:

\n
    \n
  1. The sole basis for coverage, e.g., being differently abled may qualify a person for disability coverage
    2. \n
  2. May more fully qualify a covered party role e.g, being differently abled may qualify an adult child as a dependent
    3. \n
  3. May impact the level of coverage for a covered party under a policy or program, e.g., being differently abled may qualify a program eligible for additional benefits.
    4. \n
\n

Discussion: The Abstract Value Set "CoverageRoleType", which was developed for use in the Canadian realm "pre-coordinate" coverage roles with other roles that a covered party must play in order to be eligible for coverage, e.g., "handicapped dependent". These role.codes may only be used with COVPTY to avoid overlapping concepts that would result from using them to specify the specializations of COVPTY, e.g., the role.class DEPEN should not be used with the role.code family dependent because that relationship has overlapping concepts due to the role.code precoodination and is conveyed in FICO with the personal relationship role that has a PART role link to the covered party role. For the same reasons, the role.class DEPEN should not be used with the role.code HANDIC (handicapped dependent); the role.code DIFFABLE (differently abled) should be used instead.

\n

In summary, the coded concepts in the Abstract Value Set "CoveredPartyRoleType" can be "post-coordinated" with the "RoleClassCoveredParty" Abstract Value Set. Decoupling these concepts is intended to support an expansive range of covered party concepts and their semantic comparability.

\n
" ]; fhir:ValueSet.url [ fhir:value "http://terminology.hl7.org/ValueSet/v3-PolicyOrProgramCoverageRoleType"]; fhir:ValueSet.identifier [ fhir:index 0; fhir:Identifier.system [ fhir:value "urn:ietf:rfc:3986" ]; fhir:Identifier.value [ fhir:value "urn:oid:2.16.840.1.113883.1.11.19809" ] ]; fhir:ValueSet.version [ fhir:value "2.0.0"]; fhir:ValueSet.name [ fhir:value "PolicyOrProgramCoverageRoleType"]; fhir:ValueSet.title [ fhir:value "PolicyOrProgramCoverageRoleType"]; fhir:ValueSet.status [ fhir:value "active"]; fhir:ValueSet.date [ fhir:value "2014-03-26T00:00:00-04:00"^^xsd:dateTime]; fhir:ValueSet.description [ fhir:value "**Description:** A role recognized through the eligibility of an identified party for benefits covered under an insurance policy or a program based on meeting eligibility criteria.\r\n\r\nEligibility as a covered party may be conditioned on the party meeting criteria to qualify for coverage under a policy or program, which may be mandated by law. These criteria may be:\r\n\r\n1. The sole basis for coverage, e.g., being differently abled may qualify a person for disability coverage\r\n2. May more fully qualify a covered party role e.g, being differently abled may qualify an adult child as a dependent\r\n3. May impact the level of coverage for a covered party under a policy or program, e.g., being differently abled may qualify a program eligible for additional benefits.\r\n\r\n**Discussion:** The Abstract Value Set \"CoverageRoleType\", which was developed for use in the Canadian realm \"pre-coordinate\" coverage roles with other roles that a covered party must play in order to be eligible for coverage, e.g., \"handicapped dependent\". These role.codes may only be used with COVPTY to avoid overlapping concepts that would result from using them to specify the specializations of COVPTY, e.g., the role.class DEPEN should not be used with the role.code family dependent because that relationship has overlapping concepts due to the role.code precoodination and is conveyed in FICO with the personal relationship role that has a PART role link to the covered party role. For the same reasons, the role.class DEPEN should not be used with the role.code HANDIC (handicapped dependent); the role.code DIFFABLE (differently abled) should be used instead.\r\n\r\nIn summary, the coded concepts in the Abstract Value Set \"CoveredPartyRoleType\" can be \"post-coordinated\" with the \"RoleClassCoveredParty\" Abstract Value Set. Decoupling these concepts is intended to support an expansive range of covered party concepts and their semantic comparability."]; fhir:ValueSet.compose [ fhir:ValueSet.compose.include [ fhir:index 0; fhir:ValueSet.compose.include.system [ fhir:value "http://terminology.hl7.org/CodeSystem/v3-RoleCode" ]; fhir:ValueSet.compose.include.filter [ fhir:index 0; fhir:ValueSet.compose.include.filter.property [ fhir:value "concept" ]; fhir:ValueSet.compose.include.filter.op [ fhir:value "is-a" ]; fhir:ValueSet.compose.include.filter.value [ fhir:value "_PolicyOrProgramCoverageRoleType" ] ] ] ] . # - ontology header ------------------------------------------------------------ a owl:Ontology; owl:imports fhir:fhir.ttl . # -------------------------------------------------------------------------------------