site render
This commit is contained in:
Clair Blacketer
parent
f2f202d056
commit
c92b9d7b90
152
docs/cdm53.html
152
docs/cdm53.html
|
|
@ -1335,7 +1335,10 @@ enrollment file, EHR healthcare encounters, or other sources.
|
|||
Choose the observation_period_type_concept_id that best represents how
|
||||
the period was determined. <a
|
||||
href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&standardConcept=Standard&page=1&pageSize=15&query=">Accepted
|
||||
Concepts</a>.
|
||||
Concepts</a>. A more detailed explanation of each Type Concept can be
|
||||
found on the <a
|
||||
href="https://github.com/OHDSI/Vocabulary-v5.0/wiki/Vocab.-TYPE_CONCEPT">vocabulary
|
||||
wiki</a>.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
integer
|
||||
|
|
@ -1722,7 +1725,10 @@ where the record comes from.
|
|||
Populate this field based on the provenance of the visit record, as in
|
||||
whether it came from an EHR record or billing claim. <a
|
||||
href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&standardConcept=Standard&page=1&pageSize=15&query=">Accepted
|
||||
Concepts</a>.
|
||||
Concepts</a>. A more detailed explanation of each Type Concept can be
|
||||
found on the <a
|
||||
href="https://github.com/OHDSI/Vocabulary-v5.0/wiki/Vocab.-TYPE_CONCEPT">vocabulary
|
||||
wiki</a>.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
Integer
|
||||
|
|
@ -1880,10 +1886,11 @@ concept is part of the visit domain and can indicate if a patient was
|
|||
admitted to the hospital from a long-term care facility, for example.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
If available, map the admitted_from_source_value to a standard concept
|
||||
in the visit domain. <a
|
||||
If available, map the admitting_source_value to a standard concept in
|
||||
the visit domain. <a
|
||||
href="https://athena.ohdsi.org/search-terms/terms?domain=Visit&standardConcept=Standard&page=1&pageSize=15&query=">Accepted
|
||||
Concepts</a>.
|
||||
Concepts</a>. If a person was admitted from home or was self-referred,
|
||||
set this to 0.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
integer
|
||||
|
|
@ -2332,7 +2339,10 @@ or where the record comes from.
|
|||
Populate this field based on the provenance of the visit detail record,
|
||||
as in whether it came from an EHR record or billing claim. <a
|
||||
href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&standardConcept=Standard&page=1&pageSize=15&query=">Accepted
|
||||
Concepts</a>.
|
||||
Concepts</a>. A more detailed explanation of each Type Concept can be
|
||||
found on the <a
|
||||
href="https://github.com/OHDSI/Vocabulary-v5.0/wiki/Vocab.-TYPE_CONCEPT">vocabulary
|
||||
wiki</a>.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
integer
|
||||
|
|
@ -2517,10 +2527,11 @@ concept is part of the visit domain and can indicate if a patient was
|
|||
admitted to the hospital from a long-term care facility, for example.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
If available, map the admitted_from_source_value to a standard concept
|
||||
in the visit domain. <a
|
||||
If available, map the admitting_source_value to a standard concept in
|
||||
the visit domain. <a
|
||||
href="https://athena.ohdsi.org/search-terms/terms?domain=Visit&standardConcept=Standard&page=1&pageSize=15&query=">Accepted
|
||||
Concepts</a>.
|
||||
Concepts</a>. If a person was admitted from home or was self-referred,
|
||||
set this to 0.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
Integer
|
||||
|
|
@ -2997,7 +3008,10 @@ claim, registry, or other sources.
|
|||
Choose the CONDITION_TYPE_CONCEPT_ID that best represents the provenance
|
||||
of the record. <a
|
||||
href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&standardConcept=Standard&page=1&pageSize=15&query=">Accepted
|
||||
Concepts</a>.
|
||||
Concepts</a>. A more detailed explanation of each Type Concept can be
|
||||
found on the <a
|
||||
href="https://github.com/OHDSI/Vocabulary-v5.0/wiki/Vocab.-TYPE_CONCEPT">vocabulary
|
||||
wiki</a>.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
integer
|
||||
|
|
@ -3644,7 +3658,10 @@ Choose the drug_type_concept_id that best represents the provenance of
|
|||
the record, for example whether it came from a record of a prescription
|
||||
written or physician administered drug. <a
|
||||
href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&standardConcept=Standard&page=1&pageSize=15&query=">Accepted
|
||||
Concepts</a>.
|
||||
Concepts</a>. A more detailed explanation of each Type Concept can be
|
||||
found on the <a
|
||||
href="https://github.com/OHDSI/Vocabulary-v5.0/wiki/Vocab.-TYPE_CONCEPT">vocabulary
|
||||
wiki</a>.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
integer
|
||||
|
|
@ -4341,7 +4358,10 @@ of the record, for example whether it came from an EHR record or billing
|
|||
claim. If a procedure is recorded as an EHR encounter, the
|
||||
PROCEDURE_TYPE_CONCEPT would be ‘EHR encounter record’. <a
|
||||
href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&standardConcept=Standard&page=1&pageSize=15&query=">Accepted
|
||||
Concepts</a>.
|
||||
Concepts</a>. A more detailed explanation of each Type Concept can be
|
||||
found on the <a
|
||||
href="https://github.com/OHDSI/Vocabulary-v5.0/wiki/Vocab.-TYPE_CONCEPT">vocabulary
|
||||
wiki</a>.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
integer
|
||||
|
|
@ -4885,7 +4905,10 @@ Choose the drug_type_concept_id that best represents the provenance of
|
|||
the record, for example whether it came from a record of a prescription
|
||||
written or physician administered drug. <a
|
||||
href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&standardConcept=Standard&page=1&pageSize=15&query=">Accepted
|
||||
Concepts</a>.
|
||||
Concepts</a>. A more detailed explanation of each Type Concept can be
|
||||
found on the <a
|
||||
href="https://github.com/OHDSI/Vocabulary-v5.0/wiki/Vocab.-TYPE_CONCEPT">vocabulary
|
||||
wiki</a>.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
integer
|
||||
|
|
@ -5387,7 +5410,10 @@ Choose the MEASUREMENT_TYPE_CONCEPT_ID that best represents the
|
|||
provenance of the record, for example whether it came from an EHR record
|
||||
or billing claim. <a
|
||||
href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&standardConcept=Standard&page=1&pageSize=15&query=">Accepted
|
||||
Concepts</a>.
|
||||
Concepts</a>. A more detailed explanation of each Type Concept can be
|
||||
found on the <a
|
||||
href="https://github.com/OHDSI/Vocabulary-v5.0/wiki/Vocab.-TYPE_CONCEPT">vocabulary
|
||||
wiki</a>.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
integer
|
||||
|
|
@ -6068,7 +6094,10 @@ Choose the OBSERVATION_TYPE_CONCEPT_ID that best represents the
|
|||
provenance of the record, for example whether it came from an EHR record
|
||||
or billing claim. <a
|
||||
href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&standardConcept=Standard&page=1&pageSize=15&query=">Accepted
|
||||
Concepts</a>.
|
||||
Concepts</a>. A more detailed explanation of each Type Concept can be
|
||||
found on the <a
|
||||
href="https://github.com/OHDSI/Vocabulary-v5.0/wiki/Vocab.-TYPE_CONCEPT">vocabulary
|
||||
wiki</a>.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
integer
|
||||
|
|
@ -6603,7 +6632,8 @@ death_datetime
|
|||
<td style="text-align:left;">
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
If not available set time to midnight (00:00:00)
|
||||
If you have date and time of death, populate death_datetime, otherwise
|
||||
leave NULL
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
datetime
|
||||
|
|
@ -6633,9 +6663,12 @@ information from a government file so do not assume the Death Type is
|
|||
the same as the Visit Type, etc.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
Use the type concept that be reflects the source of the death record. <a
|
||||
Use the type concept that reflects the source of the death record. <a
|
||||
href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&standardConcept=Standard&page=1&pageSize=15&query=">Accepted
|
||||
Concepts</a>.
|
||||
Concepts</a>. A more detailed explanation of each Type Concept can be
|
||||
found on the <a
|
||||
href="https://github.com/OHDSI/Vocabulary-v5.0/wiki/Vocab.-TYPE_CONCEPT">vocabulary
|
||||
wiki</a>.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
integer
|
||||
|
|
@ -6928,7 +6961,10 @@ The provenance of the note. Most likely this will be EHR.
|
|||
<td style="text-align:left;">
|
||||
Put the source system of the note, as in EHR record. <a
|
||||
href="https://athena.ohdsi.org/search-terms/terms?standardConcept=Standard&domain=Type+Concept&page=1&pageSize=15&query=">Accepted
|
||||
Concepts</a>.
|
||||
Concepts</a>. A more detailed explanation of each Type Concept can be
|
||||
found on the <a
|
||||
href="https://github.com/OHDSI/Vocabulary-v5.0/wiki/Vocab.-TYPE_CONCEPT">vocabulary
|
||||
wiki</a>.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
integer
|
||||
|
|
@ -7772,7 +7808,10 @@ specimen_type_concept_id
|
|||
<td style="text-align:left;">
|
||||
Put the source of the specimen record, as in an EHR system. <a
|
||||
href="https://athena.ohdsi.org/search-terms/terms?standardConcept=Standard&domain=Type+Concept&page=1&pageSize=15&query=">Accepted
|
||||
Concepts</a>.
|
||||
Concepts</a>. A more detailed explanation of each Type Concept can be
|
||||
found on the <a
|
||||
href="https://github.com/OHDSI/Vocabulary-v5.0/wiki/Vocab.-TYPE_CONCEPT">vocabulary
|
||||
wiki</a>.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
integer
|
||||
|
|
@ -8861,11 +8900,12 @@ No
|
|||
provider_name
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
This field contains information that describes a healthcare provider.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
This field is not necessary as it is not necessary to have the actual
|
||||
identity of the Provider. Rather, the idea is to uniquely and
|
||||
anonymously identify providers of care across the database.
|
||||
This field is not required for identifying the Provider’s actual
|
||||
identity. Instead, its purpose is to uniquely and/or anonymously
|
||||
identify providers of care across the database.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
varchar(255)
|
||||
|
|
@ -9099,15 +9139,18 @@ No
|
|||
specialty_source_value
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
This is the kind of provider or specialty as it appears in the source
|
||||
data. This includes physician specialties such as internal medicine,
|
||||
emergency medicine, etc. and allied health professionals such as nurses,
|
||||
midwives, and pharmacists.
|
||||
This refers to the specific type of healthcare provider or field of
|
||||
expertise listed in the source data, encompassing physician specialties
|
||||
like internal medicine, emergency medicine, etc., as well as allied
|
||||
health professionals such as nurses, midwives, and pharmacists. It
|
||||
covers medical specialties like surgery, internal medicine, and
|
||||
radiology, while other services like prosthetics, acupuncture, and
|
||||
physical therapy fall under the domain of “Service.”
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
Put the kind of provider 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.
|
||||
The type of provider and their specialty should be entered as they
|
||||
appear in the source data. The decision to use either the coded value or
|
||||
the text description is left to the discretion of the ETL-er.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
varchar(50)
|
||||
|
|
@ -9392,13 +9435,13 @@ This field represents the organization who reimburses the provider which
|
|||
administers care to the Person.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
Map the Payer directly to a standard CONCEPT_ID. If one does not exists
|
||||
please contact the vocabulary team. There is no global controlled
|
||||
vocabulary available for this information. The point is to stratify on
|
||||
this information and identify if Persons have the same payer, though the
|
||||
name of the Payer is not necessary. <a
|
||||
href="http://athena.ohdsi.org/search-terms/terms?domain=Payer&standardConcept=Standard&page=1&pageSize=15&query=">Accepted
|
||||
Concepts</a>.
|
||||
Map the payer directly to a standard CONCEPT_ID with the domain_id of
|
||||
‘Payer’ (<a
|
||||
href="https://athena.ohdsi.org/search-terms/terms?domain=Payer&standardConcept=Standard&page=1&pageSize=15&query=">Accepted
|
||||
Concepts</a>). This vocabulary is not exhaustive so if there is a value
|
||||
missing, please see the <a
|
||||
href="https://ohdsi.github.io/CommonDataModel/customConcepts.html">custom
|
||||
concepts</a> page.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
integer
|
||||
|
|
@ -9481,13 +9524,13 @@ This field represents the specific health benefit Plan the Person is
|
|||
enrolled in.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
Map the Plan directly to a standard CONCEPT_ID. If one does not exists
|
||||
please contact the vocabulary team. There is no global controlled
|
||||
vocabulary available for this information. The point is to stratify on
|
||||
this information and identify if Persons have the same health benefit
|
||||
Plan though the name of the Plan is not necessary. <a
|
||||
Map the Plan directly to a standard CONCEPT_ID in the ‘Plan’ vocabulary
|
||||
(<a
|
||||
href="http://athena.ohdsi.org/search-terms/terms?domain=Plan&standardConcept=Standard&page=1&pageSize=15&query=">Accepted
|
||||
Concepts</a>.
|
||||
Concepts</a>). This vocabulary is not exhaustive so if there is a value
|
||||
missing, please see the <a
|
||||
href="https://ohdsi.github.io/CommonDataModel/customConcepts.html">custom
|
||||
concepts</a> page.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
integer
|
||||
|
|
@ -9572,13 +9615,13 @@ This includes self-insured, small group health plan and large group
|
|||
health plan.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
Map the sponsor directly to a standard CONCEPT_ID. If one does not
|
||||
exists please contact the vocabulary team. There is no global controlled
|
||||
vocabulary available for this information. The point is to stratify on
|
||||
this information and identify if Persons have the same sponsor though
|
||||
the name of the sponsor is not necessary. <a
|
||||
href="http://athena.ohdsi.org/search-terms/terms?domain=Sponsor&standardConcept=Standard&page=1&pageSize=15&query=">Accepted
|
||||
Concepts</a>.
|
||||
Map the sponsor directly to a standard CONCEPT_ID with the domain_id of
|
||||
‘Sponsor’ (<a
|
||||
href="https://athena.ohdsi.org/search-terms/terms?domain=Sponsor&standardConcept=Standard&page=1&pageSize=15&query=">Accepted
|
||||
Concepts</a>). This vocabulary is not exhaustive so if there is a value
|
||||
missing, please see the <a
|
||||
href="https://ohdsi.github.io/CommonDataModel/customConcepts.html">custom
|
||||
concepts</a> page.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
integer
|
||||
|
|
@ -9689,11 +9732,12 @@ stop_reason_concept_id
|
|||
This field represents the reason the Person left the Plan, if known.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
Map the stop reason directly to a standard CONCEPT_ID. If one does not
|
||||
exists please contact the vocabulary team. There is no global controlled
|
||||
vocabulary available for this information. <a
|
||||
Map the stop reason directly to a standard CONCEPT_ID with a domain of
|
||||
‘Plan Stop Reason’ (<a
|
||||
href="http://athena.ohdsi.org/search-terms/terms?domain=Plan+Stop+Reason&standardConcept=Standard&page=1&pageSize=15&query=">Accepted
|
||||
Concepts</a>.
|
||||
Concepts</a>). If one does not exist visit the <a
|
||||
href="https://ohdsi.github.io/CommonDataModel/customConcepts.html">Custom
|
||||
Concepts</a> pate for more information.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
integer
|
||||
|
|
|
|||
|
|
@ -2003,7 +2003,8 @@ admitted to the hospital from a long-term care facility, for example.
|
|||
If available, map the admitted_from_source_value to a standard concept
|
||||
in the visit domain. <a
|
||||
href="https://athena.ohdsi.org/search-terms/terms?domain=Visit&standardConcept=Standard&page=1&pageSize=15&query=">Accepted
|
||||
Concepts</a>. If a person was admitted from home, set this to 0.
|
||||
Concepts</a>. If a person was admitted from home or was self-referred,
|
||||
set this to 0.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
integer
|
||||
|
|
@ -2622,7 +2623,8 @@ admitted to the hospital from a long-term care facility, for example.
|
|||
If available, map the admitted_from_source_value to a standard concept
|
||||
in the visit domain. <a
|
||||
href="https://athena.ohdsi.org/search-terms/terms?domain=Visit&standardConcept=Standard&page=1&pageSize=15&query=">Accepted
|
||||
Concepts</a>. If the person was admitted from home, set this to 0.
|
||||
Concepts</a>. If a person was admitted from home or was self-referred,
|
||||
set this to 0.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
Integer
|
||||
|
|
@ -7132,7 +7134,8 @@ death_datetime
|
|||
<td style="text-align:left;">
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
If not available set time to midnight (00:00:00)
|
||||
If you have date and time of death, populate death_datetime, otherwise
|
||||
leave NULL
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
datetime
|
||||
|
|
@ -7162,7 +7165,7 @@ information from a government file so do not assume the Death Type is
|
|||
the same as the Visit Type, etc.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
Use the type concept that be reflects the source of the death record. <a
|
||||
Use the type concept that reflects the source of the death record. <a
|
||||
href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&standardConcept=Standard&page=1&pageSize=15&query=">Accepted
|
||||
Concepts</a>. A more detailed explanation of each Type Concept can be
|
||||
found on the <a
|
||||
|
|
@ -9570,11 +9573,12 @@ No
|
|||
provider_name
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
This field contains information that describes a healthcare provider.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
This field is not necessary as it is not necessary to have the actual
|
||||
identity of the Provider. Rather, the idea is to uniquely and
|
||||
anonymously identify providers of care across the database.
|
||||
This field is not required for identifying the Provider’s actual
|
||||
identity. Instead, its purpose is to uniquely and/or anonymously
|
||||
identify providers of care across the database.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
varchar(255)
|
||||
|
|
@ -9808,15 +9812,18 @@ No
|
|||
specialty_source_value
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
This is the kind of provider or specialty as it appears in the source
|
||||
data. This includes physician specialties such as internal medicine,
|
||||
emergency medicine, etc. and allied health professionals such as nurses,
|
||||
midwives, and pharmacists.
|
||||
This refers to the specific type of healthcare provider or field of
|
||||
expertise listed in the source data, encompassing physician specialties
|
||||
like internal medicine, emergency medicine, etc., as well as allied
|
||||
health professionals such as nurses, midwives, and pharmacists. It
|
||||
covers medical specialties like surgery, internal medicine, and
|
||||
radiology, while other services like prosthetics, acupuncture, and
|
||||
physical therapy fall under the domain of “Service.”
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
Put the kind of provider 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.
|
||||
The type of provider and their specialty should be entered as they
|
||||
appear in the source data. The decision to use either the coded value or
|
||||
the text description is left to the discretion of the ETL-er.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
varchar(50)
|
||||
|
|
@ -10101,13 +10108,13 @@ This field represents the organization who reimburses the provider which
|
|||
administers care to the Person.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
Map the Payer directly to a standard CONCEPT_ID. If one does not exists
|
||||
please contact the vocabulary team. There is no global controlled
|
||||
vocabulary available for this information. The point is to stratify on
|
||||
this information and identify if Persons have the same payer, though the
|
||||
name of the Payer is not necessary. <a
|
||||
href="http://athena.ohdsi.org/search-terms/terms?domain=Payer&standardConcept=Standard&page=1&pageSize=15&query=">Accepted
|
||||
Concepts</a>.
|
||||
Map the payer directly to a standard CONCEPT_ID with the domain_id of
|
||||
‘Payer’ (<a
|
||||
href="https://athena.ohdsi.org/search-terms/terms?domain=Payer&standardConcept=Standard&page=1&pageSize=15&query=">Accepted
|
||||
Concepts</a>). This vocabulary is not exhaustive so if there is a value
|
||||
missing, please see the <a
|
||||
href="https://ohdsi.github.io/CommonDataModel/customConcepts.html">custom
|
||||
concepts</a> page.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
integer
|
||||
|
|
@ -10190,13 +10197,13 @@ This field represents the specific health benefit Plan the Person is
|
|||
enrolled in.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
Map the Plan directly to a standard CONCEPT_ID. If one does not exists
|
||||
please contact the vocabulary team. There is no global controlled
|
||||
vocabulary available for this information. The point is to stratify on
|
||||
this information and identify if Persons have the same health benefit
|
||||
Plan though the name of the Plan is not necessary. <a
|
||||
Map the Plan directly to a standard CONCEPT_ID in the ‘Plan’ vocabulary
|
||||
(<a
|
||||
href="http://athena.ohdsi.org/search-terms/terms?domain=Plan&standardConcept=Standard&page=1&pageSize=15&query=">Accepted
|
||||
Concepts</a>.
|
||||
Concepts</a>). This vocabulary is not exhaustive so if there is a value
|
||||
missing, please see the <a
|
||||
href="https://ohdsi.github.io/CommonDataModel/customConcepts.html">custom
|
||||
concepts</a> page.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
integer
|
||||
|
|
@ -10281,13 +10288,13 @@ This includes self-insured, small group health plan and large group
|
|||
health plan.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
Map the sponsor directly to a standard CONCEPT_ID. If one does not
|
||||
exists please contact the vocabulary team. There is no global controlled
|
||||
vocabulary available for this information. The point is to stratify on
|
||||
this information and identify if Persons have the same sponsor though
|
||||
the name of the sponsor is not necessary. <a
|
||||
href="http://athena.ohdsi.org/search-terms/terms?domain=Sponsor&standardConcept=Standard&page=1&pageSize=15&query=">Accepted
|
||||
Concepts</a>.
|
||||
Map the sponsor directly to a standard CONCEPT_ID with the domain_id of
|
||||
‘Sponsor’ (<a
|
||||
href="https://athena.ohdsi.org/search-terms/terms?domain=Sponsor&standardConcept=Standard&page=1&pageSize=15&query=">Accepted
|
||||
Concepts</a>). This vocabulary is not exhaustive so if there is a value
|
||||
missing, please see the <a
|
||||
href="https://ohdsi.github.io/CommonDataModel/customConcepts.html">custom
|
||||
concepts</a> page.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
integer
|
||||
|
|
@ -10398,11 +10405,12 @@ stop_reason_concept_id
|
|||
This field represents the reason the Person left the Plan, if known.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
Map the stop reason directly to a standard CONCEPT_ID. If one does not
|
||||
exists please contact the vocabulary team. There is no global controlled
|
||||
vocabulary available for this information. <a
|
||||
Map the stop reason directly to a standard CONCEPT_ID with a domain of
|
||||
‘Plan Stop Reason’ (<a
|
||||
href="http://athena.ohdsi.org/search-terms/terms?domain=Plan+Stop+Reason&standardConcept=Standard&page=1&pageSize=15&query=">Accepted
|
||||
Concepts</a>.
|
||||
Concepts</a>). If one does not exist visit the <a
|
||||
href="https://ohdsi.github.io/CommonDataModel/customConcepts.html">Custom
|
||||
Concepts</a> pate for more information.
|
||||
</td>
|
||||
<td style="text-align:left;">
|
||||
integer
|
||||
|
|
|
|||
File diff suppressed because one or more lines are too long
Loading…
Reference in New Issue