LinuxForHealth FHIR Implementation Guide
8.0.0 - draft
LinuxForHealth FHIR Implementation Guide - Local Development build (v8.0.0). See the Directory of published versions
Official URL: http://linuxforhealth.org/fhir/cdm/ValueSet/basic-resource-type | Version: 8.0.0 | |||
Active as of 2022-11-10 | Computable Name: BasicResourceTypeValueSet |
Value set for the basic resource type
References
This value set includes codes based on the following rules:
http://terminology.hl7.org/CodeSystem/basic-resource-type
http://linuxforhealth.org/fhir/cdm/CodeSystem/basic-resource-type
This value set contains 17 concepts
Expansion based on:
Code | System | Display | Definition |
consent | http://terminology.hl7.org/CodeSystem/basic-resource-type | Consent | An assertion of permission for an activity or set of activities to occur, possibly subject to particular limitations; e.g. surgical consent, information disclosure consent, etc. |
referral | http://terminology.hl7.org/CodeSystem/basic-resource-type | Referral | A request that care of a particular type be provided to a patient. Could involve the transfer of care, a consult, etc. |
advevent | http://terminology.hl7.org/CodeSystem/basic-resource-type | Adverse Event | An undesired reaction caused by exposure to some agent (e.g. a medication, immunization, food, or environmental agent). |
aptmtreq | http://terminology.hl7.org/CodeSystem/basic-resource-type | Appointment Request | A request that a time be scheduled for a type of service for a specified patient, potentially subject to other constraints |
transfer | http://terminology.hl7.org/CodeSystem/basic-resource-type | Transfer | The transition of a patient or set of material from one location to another |
diet | http://terminology.hl7.org/CodeSystem/basic-resource-type | Diet | The specification of a set of food and/or other nutritional material to be delivered to a patient. |
adminact | http://terminology.hl7.org/CodeSystem/basic-resource-type | Administrative Activity | An occurrence of a non-care-related event in the healthcare domain, such as approvals, reviews, etc. |
exposure | http://terminology.hl7.org/CodeSystem/basic-resource-type | Exposure | Record of a situation where a subject was exposed to a substance. Usually of interest to public health. |
investigation | http://terminology.hl7.org/CodeSystem/basic-resource-type | Investigation | A formalized inquiry into the circumstances surrounding a particular unplanned event or potential event for the purposes of identifying possible causes and contributing factors for the event |
account | http://terminology.hl7.org/CodeSystem/basic-resource-type | Account | A financial instrument used to track costs, charges or other amounts. |
invoice | http://terminology.hl7.org/CodeSystem/basic-resource-type | Invoice | A request for payment for goods and/or services. Includes the idea of a healthcare insurance claim. |
adjudicat | http://terminology.hl7.org/CodeSystem/basic-resource-type | Invoice Adjudication | The determination of what will be paid against a particular invoice based on coverage, plan rules, etc. |
predetreq | http://terminology.hl7.org/CodeSystem/basic-resource-type | Pre-determination Request | A request for a pre-determination of the cost that would be paid under an insurance plan for a hypothetical claim for goods or services |
predetermine | http://terminology.hl7.org/CodeSystem/basic-resource-type | Predetermination | An adjudication of what would be paid under an insurance plan for a hypothetical claim for goods or services |
study | http://terminology.hl7.org/CodeSystem/basic-resource-type | Study | An investigation to determine information about a particular therapy or product |
protocol | http://terminology.hl7.org/CodeSystem/basic-resource-type | Protocol | A set of (possibly conditional) steps to be taken to achieve some aim. Includes study protocols, treatment protocols, emergency protocols, etc. |
patient-tokens | http://linuxforhealth.org/fhir/cdm/CodeSystem/basic-resource-type | Patient Tokens | A set of anonymous patient identifiers created by hashing Personally identifiable information (PII) |
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 |