FHIR IG Statistics: StructureDefinition/profile-prior-coverage

Resources that use this resource

No resources found

Resources that this resource uses

No resources found

Narrative

No narrative content found in resource

Source

{
  "resourceType": "StructureDefinition",
  "id": "profile-prior-coverage",
  "url": "http://pharmacyeclaims.ca/FHIR/v1.0/StructureDefinition/profile-prior-coverage",
  "name": "PriorCoverage",
  "title": "Prior Coverage",
  "status": "draft",
  "description": "Profile for prior coverages in a claim",
  "purpose": "Used specifically for prior coverages in a claim, with less information than typical coverages",
  "fhirVersion": "4.0.1",
  "kind": "resource",
  "abstract": false,
  "type": "Coverage",
  "baseDefinition": "http://hl7.org/fhir/StructureDefinition/Coverage",
  "derivation": "constraint",
  "differential": {
    "element": [
      {
        "id": "Coverage.text",
        "path": "Coverage.text",
        "max": "0"
      },
      {
        "id": "Coverage.status",
        "path": "Coverage.status",
        "comment": "Set value = \"active\"\r\n\r\nThis element is labeled as a modifier because the status contains the code entered-in-error that marks the coverage as not currently valid.",
        "fixedCode": "active",
        "mustSupport": true
      },
      {
        "id": "Coverage.type",
        "path": "Coverage.type",
        "comment": "Usage Note:   This must be present for prior coverages in order that downstream adjudicators can adequately differentiate between public and private plans which leads to accurate adjudications.    Set value = \"public\" or \"private\".    This supports multiple codings as a sub-type may be provided.\r\n\r\nConformance Rule:   The value is determined from the value set in the prior adjudication response\r\n\r\nCPHA Map:  None: this is a new field\r\n\r\nNot all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.",
        "min": 1,
        "mustSupport": true
      },
      {
        "id": "Coverage.type.coding",
        "path": "Coverage.type.coding",
        "min": 1,
        "mustSupport": true
      },
      {
        "id": "Coverage.type.coding.system",
        "path": "Coverage.type.coding.system",
        "mustSupport": true
      },
      {
        "id": "Coverage.type.coding.code",
        "path": "Coverage.type.coding.code",
        "min": 1,
        "mustSupport": true
      },
      {
        "id": "Coverage.beneficiary",
        "path": "Coverage.beneficiary",
        "mustSupport": true
      },
      {
        "id": "Coverage.payor",
        "path": "Coverage.payor",
        "comment": "Usage Note:   A display value of \"not permitted\" may be used when it is not appropriate to share the insurer ID of the prior coverage.\r\n\r\nMay provide multiple identifiers such as insurance company identifier or business identifier (BIN number).\nFor selfpay it may provide multiple paying persons and/or organizations.",
        "type": [
          {
            "code": "Reference",
            "targetProfile": [
              "http://hl7.org/fhir/StructureDefinition/Organization"
            ]
          }
        ],
        "mustSupport": true
      },
      {
        "id": "Coverage.payor.identifier",
        "path": "Coverage.payor.identifier",
        "comment": "Usage Note:   This will only be specified under specific condtions as specified by the implementer (eg same payor identifier as secondary claim)\r\n\r\nWhen an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. \n\nWhen both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference\n\nApplications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.\n\nReference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference.  For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport).  One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).",
        "mustSupport": true
      },
      {
        "id": "Coverage.payor.display",
        "path": "Coverage.payor.display",
        "comment": "Usage Note:  Must be populated if no identifier is provided.   A value of \"not available\" is acceptable.\r\n\r\nThis is generally not the same as the Resource.text of the referenced resource.  The purpose is to identify what's being referenced, not to fully describe it.",
        "mustSupport": true
      }
    ]
  }
}