OHDSI / OHDSI/CommonDataModel

Is DEVICE_EXPOSURE.unique_device_id only related to the devices regulated by the FDA?

Open
#677 5 comments 0 reactions 1 assignee View on GitHub

@clairblacketer is already working on this.

Since Apr 25, 2024.

Proposal
Dominant language
HTML
Stars
1.1k
Forks
508
Avg merge
1h 30m
Merged PRs (30d)
3

Description

For the DEVICE_EXPOSURE.unique_device_id field, is it only related to the devices regulated by the FDA?

According to some OHDSI posts and GitHub issue, some people have questions about how to store non-regulated device details into DEVICE_EXPOSURE. They devices are not regulated by FDA. As a result, it is not convenient for them to store their non-FDA regulated device details including those devices ID.

image

In OHDSI posts, they suggest to use DEVICE_EXPOSURE.device_source_value to store their devices detailed information.

  1. https://forums.ohdsi.org/t/adding-manufacturer-and-model-information-to-the-device-exposure-table/16561/6
  2. https://forums.ohdsi.org/t/how-to-record-non-regulated-device-details-in-cdm-6-0/18605

In CDM GitHub issue: https://github.com/OHDSI/CommonDataModel/issues/353, Vojtech Huser made a full proposal which includes suggesting: remove talking about FDA and make sure wording is in world wide scope. But it seems no further response.

For me, I am in China. If this field is only limited to FDA, I may not be able to use this field to store the ID of devices in China because devices may not be regulated by FDA. I also need to store these information into device_source_value field.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.