Merge branch 'master' of https://github.com/OHDSI/CommonDataModel.wiki

StandardizedClinicalDataTables/OBSERVATION_PERIOD.md

@@ -17,6 +17,6 @@ No.|Convention Description
 | 3  | Each Person can have more than one valid OBSERVATION_PERIOD record, but no two observation periods can overlap in time for a given person.|
 | 4  | 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.
 | 5  | 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. |
-| 6  | Events CAN fall outside of an observation period though they should fall in a valid payer plan period, such as Medicare Part D, which can overlap an observation period. However, time outside of an observation period cannot be used to identify people. To ensure quality, events outside of an observation period should not be used for analysis. [THEMIS issue #23](https://github.com/OHDSI/Themis/issues/23) |
+| 6  | Events CAN fall outside of an observation period and payer plan period should be used to capture coverage, such as Medicare Part D, which can overlap an observation period. However, time outside of an observation period cannot be used to identify people. To ensure quality, events outside of an observation period should not be used for analysis. [THEMIS issue #23](https://github.com/OHDSI/Themis/issues/23) |
 | 7  | For claims data, observation periods are inferred from the enrollment periods to a health benefit plan.|
 | 8  | 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. |