This page is part of the Da Vinci Coverage Requirements Discovery (CRD) FHIR IG (v1.1.0-ballot: STU 1.1 Ballot 1) based on FHIR R4. The current version which supercedes this version is 1.0.0. For a full list of available versions, see the Directory of published versions
Official URL: http://hl7.org/fhir/us/davinci-crd/ValueSet/cardType | Version: 1.1.0-ballot | |||
Draft as of 2022-02-17 | Computable Name: CardType |
List of card types
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
http://hl7.org/fhir/us/davinci-crd/CodeSystem/cardType
This value set contains 18 concepts
Expansion based on CRD Card Types Code System v1.1.0-ballot (CodeSystem)
All codes in this table are from the system http://hl7.org/fhir/us/davinci-crd/CodeSystem/cardType
Code | Display | Definition |
coverage | Coverage | Is the therapy covered or not, or are there limitations |
documentation | Documentation | Are there additional documentation requirements |
prior-auth | Prior Authorization | Is prior authorization required or not (and possibly provision of unsolicited prior authorizations) |
dtr-clin | DTR Clin | Indication that DTR is relevant for prior authorization, claim or other documentation requirements and that at least some clinical information needs to be captured |
dtr-admin | DTR Admin | Indication that DTR is relevant for prior authorization, claim or other documentation requirements and that all information to be captured is strictly administrative (and thus it is not necessary that the app be launched by the ordering clinician) |
claim | Claim | Information about what steps need to be taken to submit a claim for the service |
insurance | Insurance | Allows a provider to update the patient's coverage information with additional details from the payer (e.g. expiry date, coverage extensions) |
limits | Limits | Messages warning about the patient approaching or exceeding their limits for a particular type of coverage or expiry date for coverage in general |
network | Network | Providing information about in-network providers that could deliver the order (or in-network alternatives for an order directed out-of-network) |
appropriate-use | Appropriate Use | Guidance on whether appropriate-use documentation is needed |
cost | Cost | What is the anticipated cost to the patient based on their coverage |
therapy-alternatives-opt | Therapy Alternatives Opt | Are there alternative therapies that have better coverage and/or are lower-cost for the patient |
therapy-alternatives-req | Therapy Alternatives Req | Are there alternative therapies that must be tried first prior to coverage being available for the proposed therapy |
clinical-reminder | Clinical Reminder | Reminders that a patient is due for certain screening or other therapy (based on payer recorded date of last intervention) |
duplicate-therapy | Duplicate Therapy | Notice that the proposed intervention has already recently occurred with a different provider when that information isn't already available in the provider system |
contraindication | Contraindication | Notice that the proposed intervention may be contraindicated based on information the payer has in their record that the provider doesn't have in theirs |
guideline | Guideline | Indication that there is a guideline available for the proposed therapy (with an option to view) |
off-guideline | Off Guideline | Notice that the proposed therapy may be contrary to best-practice guidelines, typically with an option to view the relevant guideline |
Explanation of the columns that may appear on this page:
Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
System | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
Code | The code (used as the code in the resource instance) |
Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application |
Definition | An explanation of the meaning of the concept |
Comments | Additional notes about how to use the code |