OHDSI Home | Forums | Wiki | Github

How should procedures lasting more than a day be stored in PROCEDURE_OCCURRENCE table?

Implementers
#1

Hello

In CDM 5.4, the ETL convention of PROCEDURE_OCCURRENCE indicates “If a procedure lasts more than a day, then it should be recorded as a separate record for each day the procedure occurred”. I am wondering what the rational is for this specification, what use cases they apply to, and what the consequences are if such procedure was stored as one record instead of being broken into separate records.

To be precisely, does “lasts more than a day” mean

  1. procedure’s start time and end time are on different dates, or
  2. procedure elapse over 24 hours from its start to end?

Thanks
Jack

#2

This is an error in the v5.4 documentation (a hold over from v5.3). If you continue with the text in the documentation it says:

If a procedure lasts more than a day, then it should be recorded as a separate record for each day the procedure occurred, this logic is in lieu of the PROCEDURE_END_DATE, which will be added in a future version of the CDM.

And in v5.4 there is a column procedure_end_date. But the question, “what does lasts more than a day mean?” is applicable for CDMs prior to version 5.4. If ETL’ing into a CDM version prior to v5.4, assume “lasts more than a day” means the period exceeds 24 hours.

#3

Don, thank you for clarification. We use CDM 5.4 and I see there is a PROCEDURE_END_DATE, that is what confuses me. Now I get it. It certainly makes sense to break down multiple-day-long procedure if there is no place to store the end date. The v5.4 documentation should be updated.

#4

Thanks both. The documentation for CDM v5.4 and CDM v5.3 has been updated

http://ohdsi.github.io/CommonDataModel/cdm54.html#PROCEDURE_OCCURRENCE

http://ohdsi.github.io/CommonDataModel/cdm53.html#PROCEDURE_OCCURRENCE

t