https://w3id.org/omop/ontology/Person
This table serves as the central identity management for all Persons in the database. It contains records that uniquely identify each person or patient, and some demographic information.
Instances of Person can have the following properties:
| PROPERTY | TYPE | DESCRIPTION | RANGE |
|---|---|---|---|
| From class Person | |||
| Birth datetime | owl:DatatypeProperty | For Person: This field is not required but highly encouraged. For data sources that provide the precise datetime of birth, that value should be stored in this field. For more information on how to populate this field, please refer to the [THEMIS repository](https://ohdsi.github.io/Themis/person.html). | dateTime |
| Day of birth | owl:DatatypeProperty | For Person: For data sources that provide the precise date of birth, the day should be extracted and stored in this field. | integer |
| Ethnicity source value | owl:DatatypeProperty | For Person: This field is used to store the ethnicity of the person from the source data. It is not intended for use in standard analytics but for reference only. If the person has an ethnicity other than the OMB standard of "Hispanic" or "Not Hispanic" store that value from the source data here. | string |
| Month of birth | owl:DatatypeProperty | For Person: For data sources that provide the precise date of birth, the month should be extracted and stored in this field. | integer |
| Race source value | owl:DatatypeProperty | For Person: This field is used to store the race of the person from the source data. It is not intended for use in standard analytics but for reference only. Put the race of the person as it appears in the source data. | string |
| Has ethnicity | owl:FunctionalProperty | For Person: This field captures Ethnicity as defined by the Office of Management and Budget (OMB) of the US Government: it distinguishes only between "Hispanic" and "Not Hispanic". Races and ethnic backgrounds are not stored here. Only use this field if you have US-based data and a source of this information. Do not attempt to infer Ethnicity from the race or ethnic background of the Person. [Accepted ethnicity concepts](http://athena.ohdsi.org/search-terms/terms?domain=Ethnicity&standardConcept=Standard&page=1&pageSize=15&query=) | Concept |
| Has ethnicity source | owl:FunctionalProperty | For Person: Due to the small number of options, this tends to be zero. If the source data codes ethnicity in an OMOP supported vocabulary, store the concept_id here. | Concept |
| Has race | owl:FunctionalProperty | For Person: This field captures race or ethnic background of the person. Only use this field if you have information about race or ethnic background. The Vocabulary contains Concepts about the main races and ethnic backgrounds in a hierarchical system. Due to the imprecise nature of human races and ethnic backgrounds, this is not a perfect system. Mixed races are not supported. If a clear race or ethnic background cannot be established, use Concept_Id 0. [Accepted Race Concepts](http://athena.ohdsi.org/search-terms/terms?domain=Race&standardConcept=Standard&page=1&pageSize=15&query=). | Concept |
| Has race source | owl:FunctionalProperty | For Person: Due to the small number of options, this tends to be zero. If the source data codes race in an OMOP supported vocabulary store the concept_id here. | Concept |
| Has condition era | owl:ObjectProperty | Condition era | |
| Has death | owl:ObjectProperty | Death | |
| Has dose era | owl:ObjectProperty | Dose era | |
| Has drug era | owl:ObjectProperty | Drug era | |
| Has observation period | owl:ObjectProperty | reversed relation, For Observation Period: The Person ID of the PERSON record for which the Observation Period is recorded. | Observation period |
| Has specimen | owl:ObjectProperty | reversed relation, For Specimen: The person from whom the specimen is collected. | Specimen |
| Has visit occurrence | owl:ObjectProperty | Visit occurrence | |
| From class Base person | |||
| Gender source value | owl:DatatypeProperty | For Person: This field is used to store the biological sex of the person from the source data. It is not intended for use in standard analytics but for reference only. Put the assigned sex at birth of the person as it appears in the source data. - For Provider: This is provider's gender as it appears in the source data. Put the provider's gender as it appears in the source data. This field is up to the discretion of the ETL-er as to whether this should be the coded value from the source or the text description of the lookup value. | string |
| Has gender source | owl:FunctionalProperty | For Provider: This is often zero as many sites use proprietary codes to store provider gender. If the source data codes provider gender in an OMOP supported vocabulary store the concept_id here. - For Person: Due to the small number of options, this tends to be zero. If the source data codes assigned sex at birth in a non-standard vocabulary, store the concept_id here. | Concept |
| From class OMOP CDM thing | |||
| Id | owl:DatatypeProperty | For Cohort Definition: This is the identifier given to the cohort, usually by the ATLAS application - 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 Vocabulary: A unique identifier for each Vocabulary, such as ICD9CM, SNOMED, Visit. - 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 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 Note Nlp: A unique identifier for the NLP record. - For Payer Plan Period: A unique identifier for each unique combination of a Person, Payer, Plan, and Period of time. - 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 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 Concept Class: A unique key for each class. - 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 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 Concept: A unique identifier for each Concept across all domains. - For Specimen: Unique identifier for each specimen. - For Domain: A unique key for each domain. - 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 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 Note: A unique identifier for each note. - 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 Metadata: The unique key given to a Metadata record. Attribute value is auto-generated - For Relationship: The type of relationship captured by the relationship record. - For Care Site: Assign an ID to each combination of a location and nature of the site - the latter could be the Place of Service, name or another characteristic in your source data. - 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 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. | 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:Person a owl:Class ;
rdfs:label "Person"^^xsd:string ;
rdfs:comment "This table serves as the central identity management for all Persons in the database. It contains records that uniquely identify each person or patient, and some demographic information."@en ;
rdfs:subClassOf [ a owl:Restriction ;
owl:allValuesFrom omop:Concept ;
owl:onProperty omop:has_race ],
[ a owl:Restriction ;
owl:allValuesFrom omop:Note ;
owl:onProperty omop:has_note ],
[ a owl:Restriction ;
owl:allValuesFrom omop:Death ;
owl:onProperty omop:has_death ],
[ a owl:Restriction ;
owl:allValuesFrom xsd:integer ;
owl:onProperty omop:day_of_birth ],
[ a owl:Restriction ;
owl:allValuesFrom omop:ObservationPeriod ;
owl:onProperty omop:has_observation_period ],
[ a owl:Restriction ;
owl:onProperty omop:year_of_birth ;
owl:someValuesFrom xsd:integer ],
[ a owl:Restriction ;
owl:allValuesFrom omop:DeviceExposure ;
owl:onProperty omop:has_device_exposure ],
[ a owl:Restriction ;
owl:allValuesFrom xsd:integer ;
owl:onProperty omop:year_of_birth ],
[ a owl:Restriction ;
owl:allValuesFrom omop:Concept ;
owl:onProperty omop:has_ethnicity ],
[ a owl:Restriction ;
owl:allValuesFrom omop:Concept ;
owl:onProperty omop:has_ethnicity_source ],
[ a owl:Restriction ;
owl:allValuesFrom xsd:string ;
owl:onProperty omop:race_source_value ],
[ a owl:Restriction ;
owl:allValuesFrom omop:DrugEra ;
owl:onProperty omop:has_drug_era ],
[ a owl:Restriction ;
owl:onProperty omop:has_gender ;
owl:someValuesFrom omop:Concept ],
[ a owl:Restriction ;
owl:allValuesFrom omop:VisitOccurrence ;
owl:onProperty omop:has_visit_occurrence ],
[ a owl:Restriction ;
owl:allValuesFrom omop:Specimen ;
owl:onProperty omop:has_specimen ],
[ a owl:Restriction ;
owl:allValuesFrom omop:Measurement ;
owl:onProperty omop:has_measurement ],
[ a owl:Restriction ;
owl:allValuesFrom omop:Provider ;
owl:onProperty omop:has_provider ],
[ a owl:Restriction ;
owl:allValuesFrom omop:Location ;
owl:onProperty omop:has_location ],
[ a owl:Restriction ;
owl:allValuesFrom omop:Observation ;
owl:onProperty omop:has_observation ],
[ a owl:Restriction ;
owl:onProperty omop:has_ethnicity ;
owl:someValuesFrom omop:Concept ],
[ a owl:Restriction ;
owl:allValuesFrom omop:ProcedureOccurrence ;
owl:onProperty omop:has_procedure_occurrence ],
[ a owl:Restriction ;
owl:allValuesFrom omop:DrugExposure ;
owl:onProperty omop:has_drug_exposure ],
[ a owl:Restriction ;
owl:allValuesFrom omop:Concept ;
owl:onProperty omop:has_race_source ],
[ a owl:Restriction ;
owl:allValuesFrom omop:ConditionOccurrence ;
owl:onProperty omop:has_condition_occurrence ],
[ a owl:Restriction ;
owl:allValuesFrom xsd:string ;
owl:onProperty omop:ethnicity_source_value ],
[ a owl:Restriction ;
owl:allValuesFrom xsd:dateTime ;
owl:onProperty omop:birth_datetime ],
[ a owl:Restriction ;
owl:allValuesFrom omop:PayerPlanPeriod ;
owl:onProperty omop:has_payer_plan_period ],
[ a owl:Restriction ;
owl:allValuesFrom omop:Concept ;
owl:onProperty omop:has_gender ],
[ a owl:Restriction ;
owl:allValuesFrom omop:ConditionEra ;
owl:onProperty omop:has_condition_era ],
[ a owl:Restriction ;
owl:onProperty omop:has_race ;
owl:someValuesFrom omop:Concept ],
[ a owl:Restriction ;
owl:allValuesFrom omop:DoseEra ;
owl:onProperty omop:has_dose_era ],
[ a owl:Restriction ;
owl:allValuesFrom xsd:integer ;
owl:onProperty omop:month_of_birth ],
[ a owl:Restriction ;
owl:allValuesFrom omop:VisitDetail ;
owl:onProperty omop:has_visit_detail ],
omop:BasePerson ;
omop:omop_cdm_name "person"^^xsd:string .