Merge pull request #103 from gowthamrao/patch-1

Update OBSERVATION_PERIOD.md
This commit is contained in:
clairblacketer 2017-08-14 12:44:54 -04:00 committed by GitHub
commit 4d5bd8bd3b
1 changed files with 1 additions and 0 deletions

View File

@ -13,6 +13,7 @@ Field|Required|Type|Description
* One Person may have one or more disjoint observation periods, during which times analyses may assume that clinical events would be captured if observed, and outside of which no clinical events may be recorded.
* Each Person can have more than one valid OBSERVATION_PERIOD record, but no two observation periods can overlap in time for a given person.
* As a general assumption, during an Observation Period any clinical event that happens to the patient is expected to be recorded. Conversely, the absence of data indicates that no clinical events occurred to the patient.
* Both the _start_date and the _end_date of the clinical event has to be between observation_period_start_date and observation_period_end_date.
* No clinical data are valid outside an active Observation Period. Clinical data that refer to a time outside (diagnoses of previous conditions such as "Old MI" or medical history) of an active Observation Period are recorded as Observations. The date of the Observation is the first day of the first Observation Period of a patient.
* For claims data, observation periods are inferred from the enrollment periods to a health benefit plan.
* For EHR data, the observation period cannot be determined explicitly, because patients usually do not announce their departure from a certain healthcare provider. The ETL will have to apply some heuristic to make a reasonable guess on what the observation_period should be. Refer to the ETL documentation for details.