https://w3id.org/omop/ontology/Cost
The COST table captures records containing the cost of any medical event recorded in one of the OMOP clinical event tables such as DRUG_EXPOSURE, PROCEDURE_OCCURRENCE, VISIT_OCCURRENCE, VISIT_DETAIL, DEVICE_OCCURRENCE, OBSERVATION or MEASUREMENT.
Each record in the cost table account for the amount of money transacted for the clinical event. So, the COST table may be used to represent both receivables (charges) and payments (paid), each transaction type represented by its COST_CONCEPT_ID. The COST_TYPE_CONCEPT_ID field will use concepts in the Standardized Vocabularies to designate the source (provenance) of the cost data. A reference to the health plan information in the PAYER_PLAN_PERIOD table is stored in the record for information used for the adjudication system to determine the persons benefit for the clinical event.
Instances of Cost can have the following properties:
| PROPERTY | TYPE | DESCRIPTION | RANGE |
|---|---|---|---|
| From class Cost | |||
| Billed date | owl:DatatypeProperty | For Cost: The date a bill was generated for a service or encounter | date |
| Cost | owl:DatatypeProperty | For Cost: The actual financial cost amount | decimal |
| Drg source value | owl:DatatypeProperty | For Cost: The source value for the 3-digit DRG source code as it appears in the source data, stored here for reference. | string |
| Incurred date | owl:DatatypeProperty | For Cost: The first date of service of the clinical event corresponding to the cost as in table capturing the information (e.g. date of visit, date of procedure, date of condition, date of drug etc). | date |
| Paid date | owl:DatatypeProperty | For Cost: The date payment was received for a service or encounter | date |
| Revenue code source value | owl:DatatypeProperty | For Cost: The source value for the Revenue code as it appears in the source data, stored here for reference. | string |
| Has currency | owl:FunctionalProperty | For Cost: A foreign key identifier to the concept representing the 3-letter code used to delineate international currencies, such as USD for US Dollar. These belong to the 'Currency' vocabulary | Concept |
| Has drg | owl:FunctionalProperty | For Cost: A foreign key referring to a Standard Concept ID in the Standardized Vocabularies for DRG codes belonging to the 'DRG' vocabulary. | Concept |
| Has revenue code | owl:FunctionalProperty | For Cost: A foreign key referring to a Standard Concept ID in the Standardized Vocabularies for Revenue codes belonging to the 'Revenue Code' vocabulary. | Concept |
| From class OMOP CDM thing | |||
| Id | owl:DatatypeProperty | For Note: A unique identifier for each note. - For Vocabulary: A unique identifier for each Vocabulary, such as ICD9CM, SNOMED, Visit. - For Observation: The unique key given to an Observation record for a Person. Refer to the ETL for how duplicate Observations during the same Visit were handled. Each instance of an observation present in the source data should be assigned this unique key. - For Note Nlp: A unique identifier for the NLP record. - For Location: The unique key given to a unique Location. Each instance of a Location in the source data should be assigned this unique key. - For Drug Exposure: The unique key given to records of drug dispensings or administrations for a person. Refer to the ETL for how duplicate drugs during the same visit were handled. Each instance of a drug dispensing or administration present in the source data should be assigned this unique key. In some cases, a person can have multiple records of the same drug within the same visit. It is valid to keep these duplicates and assign them individual, unique, DRUG_EXPOSURE_IDs, though it is up to the ETL how they should be handled. - For Specimen: Unique identifier for each specimen. - For Observation Period: A Person can have multiple discrete Observation Periods which are identified by the Observation_Period_Id. Assign a unique observation_period_id to each discrete Observation Period for a Person. - For Cohort Definition: This is the identifier given to the cohort, usually by the ATLAS application - For Concept Class: A unique key for each class. - For Device Exposure: The unique key given to records a person's exposure to a foreign physical object or instrument. Each instance of an exposure to a foreign object or device present in the source data should be assigned this unique key. - For Procedure Occurrence: The unique key given to a procedure record for a person. Refer to the ETL for how duplicate procedures during the same visit were handled. Each instance of a procedure occurrence in the source data should be assigned this unique key. In some cases, a person can have multiple records of the same procedure within the same visit. It is valid to keep these duplicates and assign them individual, unique, PROCEDURE_OCCURRENCE_IDs, though it is up to the ETL how they should be handled. - For Cost: A unique identifier for each COST record. - For Domain: A unique key for each domain. - For Survey Conduct: Unique identifier for each completed survey. For each instance of a survey completion create a unique identifier. - For Visit Detail: Use this to identify unique interactions between a person and the health care system. This identifier links across the other CDM event tables to associate events with a visit detail. This should be populated by creating a unique identifier for each unique interaction between a person and the healthcare system where the person receives a medical good or service over a span of time. - For Care Site: Assign an id to each unique combination of location_id and place_of_service_source_value. - For Concept: A unique identifier for each Concept across all domains. - For Measurement: The unique key given to a Measurement record for a Person. Refer to the ETL for how duplicate Measurements during the same Visit were handled. Each instance of a measurement present in the source data should be assigned this unique key. In some cases, a person can have multiple records of the same measurement within the same visit. It is valid to keep these duplicates and assign them individual, unique, MEASUREMENT_IDs, though it is up to the ETL how they should be handled. - For Condition Occurrence: The unique key given to a condition record for a person. Refer to the ETL for how duplicate conditions during the same visit were handled. Each instance of a condition present in the source data should be assigned this unique key. In some cases, a person can have multiple records of the same condition within the same visit. It is valid to keep these duplicates and assign them individual, unique, CONDITION_OCCURRENCE_IDs, though it is up to the ETL how they should be handled. - For Provider: It is assumed that every provider with a different unique identifier is in fact a different person and should be treated independently. This identifier can be the original id from the source data provided it is an integer, otherwise it can be an autogenerated number. - For Person: It is assumed that every person with a different unique identifier is in fact a different person and should be treated independently. Any person linkage that needs to occur to uniquely identify Persons ought to be done prior to writing this table. This identifier can be the original id from the source data provided if it is an integer, otherwise it can be an autogenerated number. - For Visit Occurrence: Use this to identify unique interactions between a person and the health care system. This identifier links across the other CDM event tables to associate events with a visit. This should be populated by creating a unique identifier for each unique interaction between a person and the healthcare system where the person receives a medical good or service over a span of time. - For Payer Plan Period: A unique identifier for each unique combination of a Person, Payer, Plan, and Period of time. | owl:Thing |
| From class Thing | |||
| OMOP CDM name | owl:AnnotationProperty | owl:Thing | |
@prefix omop: <https://w3id.org/omop/ontology/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
omop:Cost a owl:Class ;
rdfs:label "Cost"^^xsd:string ;
rdfs:comment """The COST table captures records containing the cost of any medical event recorded in one of the OMOP clinical event tables such as DRUG_EXPOSURE, PROCEDURE_OCCURRENCE, VISIT_OCCURRENCE, VISIT_DETAIL, DEVICE_OCCURRENCE, OBSERVATION or MEASUREMENT.
Each record in the cost table account for the amount of money transacted for the clinical event. So, the COST table may be used to represent both receivables (charges) and payments (paid), each transaction type represented by its COST_CONCEPT_ID. The COST_TYPE_CONCEPT_ID field will use concepts in the Standardized Vocabularies to designate the source (provenance) of the cost data. A reference to the health plan information in the PAYER_PLAN_PERIOD table is stored in the record for information used for the adjudication system to determine the persons benefit for the clinical event."""@en ;
rdfs:subClassOf [ a owl:Restriction ;
owl:allValuesFrom omop:Concept ;
owl:onProperty omop:has_concept ],
[ a owl:Restriction ;
owl:allValuesFrom omop:Concept ;
owl:onProperty omop:has_type ],
[ a owl:Restriction ;
owl:allValuesFrom omop:Concept ;
owl:onProperty omop:has_source ],
[ a owl:Restriction ;
owl:allValuesFrom owl:Thing ;
owl:onProperty omop:has_event ],
[ a owl:Restriction ;
owl:onProperty omop:has_event ;
owl:someValuesFrom owl:Thing ],
[ a owl:Restriction ;
owl:allValuesFrom omop:Concept ;
owl:onProperty omop:has_event_field ],
[ a owl:Restriction ;
owl:onProperty omop:has_event_field ;
owl:someValuesFrom omop:Concept ],
[ a owl:Restriction ;
owl:allValuesFrom omop:PayerPlanPeriod ;
owl:onProperty omop:has_payer_plan_period ],
[ a owl:Restriction ;
owl:onProperty [ owl:inverseOf omop:has_cost ] ;
owl:someValuesFrom omop:Person ],
[ a owl:Restriction ;
owl:allValuesFrom omop:Concept ;
owl:onProperty omop:has_currency ],
[ a owl:Restriction ;
owl:allValuesFrom xsd:decimal ;
owl:onProperty omop:cost ],
[ a owl:Restriction ;
owl:allValuesFrom xsd:date ;
owl:onProperty omop:incurred_date ],
[ a owl:Restriction ;
owl:allValuesFrom xsd:date ;
owl:onProperty omop:billed_date ],
[ a owl:Restriction ;
owl:allValuesFrom xsd:date ;
owl:onProperty omop:paid_date ],
[ a owl:Restriction ;
owl:allValuesFrom omop:Concept ;
owl:onProperty omop:has_revenue_code ],
[ a owl:Restriction ;
owl:allValuesFrom omop:Concept ;
owl:onProperty omop:has_drg ],
[ a owl:Restriction ;
owl:allValuesFrom xsd:string ;
owl:onProperty omop:revenue_code_source_value ],
[ a owl:Restriction ;
owl:allValuesFrom xsd:string ;
owl:onProperty omop:drg_source_value ],
[ a owl:Restriction ;
owl:allValuesFrom xsd:string ;
owl:onProperty omop:source_value ],
omop:OmopCDMThing ;
omop:omop_cdm_name "cost"^^xsd:string .