Missing Visit End Dates
Open
Nobody has claimed this yet.
Question
- Dominant language
- HTML
- Stars
- 1.1k
- Forks
- 508
- Avg merge
- 1h 30m
- Merged PRs (30d)
- 3
Description
| TYPE | NOTES |
|---|---|
| ITEM | How to handle missing visit end dates? Can we leave it blank? |
| FORUM POST | http://forums.ohdsi.org/t/themis-2-how-do-you-handle-missing-visit-end-dates/4308 |
| SOLUTION | Visit_end_date is mandatory. Use the best information to infer a visit end date. If end dates are not provided, possible ways to derive them include: 1) Outpatient Visit: end_date=start_date 2) Emergency Room Visit: end_date=start_date 3) Inpatient Visit: usually there is information about discharge. If not you should be able to derive from the sudden decline of activity, or from the absence of inpatient procedures/drugs. But the latter would be not obvious. 4) Long Term Care Visits: particularly for claims data, if end dates are not provided assume the visit is for the duration of month that it occurs. 5) For inpatient visits ongoing at the date of ETL, put date of processing the data as mandatory visit_end_date and VISIT_TYPE_CONCEPT_ID with 32220-"Still patient" to identify the visit as incomplete. |
| NEXT STEPS | Add this as a convention under VISIT_OCCURRENCE Add the following note to 6.5: "Visit_end_date is mandatory. If there is no definite information, the following heuristic can be used: equate end date to start date, use discharge date or another way to pick the best option" |
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the VISIT_OCCURRENCE documentation, specifically section 6.5, and review the linked forum discussion for context. Add the stated convention about mandatory visit_end_date values and heuristics, then verify that the note is present under VISIT_OCCURRENCE.
Written by the indexing model from the issue text.
Assessment
- Domain
- databases, documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100